> On Jan 18, 2022, at 9:28 AM, Kemeter, Mathias via gdal-dev
> wrote:
>
> Hi Even,
>
> thanks for the feedback.
>
> Let me briefly elaborate on the distinction between corporate and
> non-corporate contributors (…which I did not intend in the first place):
> As an individual, I can very w
, 18. January 2022 at 16:07
To: Kemeter, Mathias , gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Call for discussion on RFC 85: Policy regarding
substantial code additions
Mathias,
Hi Even, hi everyone,
As we (SAP) are probably one of the triggers for formalizing this policy, let
me take a
Another comment is about "complicated registration process". I
sympathize but I don't really understand that. So it might be good to
say what's acceptable, which could be one of:
The SDK must be downloadable by a URL with no user interaction
It's ok to have a form which requires a na
Mathias,
Hi Even, hi everyone,
As we (SAP) are probably one of the triggers for formalizing this
policy, let me take a first stab from the perspective of a new
contributor trying to make a substantial contribution:
(My personal position is that a first contribution that is a substantial
on
Hi,
Greg Troxel wrote:
> If that is meant to apply mainly to drivers with proprietary SDKs, it
> looks fine. It's a little hard to tell which things apply to drivers
> that don't have proprietary dependencies.
I think that even drivers with no proprietary dependencies require a thorough
unders
unsubscribe
-Original Message-
From: gdal-dev On Behalf Of Greg Troxel
Sent: Tuesday, January 18, 2022 8:14 AM
To: Even Rouault
Cc: gdal-dev@lists.osgeo.org
Subject: Re: [gdal-dev] Call for discussion on RFC 85: Policy regarding
substantial code additions
If that is meant to apply
If that is meant to apply mainly to drivers with proprietary SDKs, it
looks fine. It's a little hard to tell which things apply to drivers
that don't have proprietary dependencies.
For example:
Drivers require a designated responsible contact.
seems perhaps a bit much, perhaps not, for some
Hi Even, hi everyone,
As we (SAP) are probably one of the triggers for formalizing this policy, let
me take a first stab from the perspective of a new contributor trying to make a
substantial contribution:
* Having such a policy greatly increases transparency on what has to be
done to mak
Working link is https://github.com/OSGeo/gdal/pull/5128
Rob :)
___
gdal-dev mailing list
gdal-dev@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/gdal-dev
Hi,
Please find in https://github.com/OSGeo/gdal/pull/3855a RFC
thatdescribes the policies that the GDAL project will apply to assess
substantial code additions, typically new drivers, in particular coming
for new contributors to the project.
Best regards,
Even
--
http://www.spatialys.com
10 matches
Mail list logo
