[Incubator] PyWPS code contribution agreements

[Jody Garnett]

If you have accepted any changes Jachym, those changes are not "(c) Jachym
Cepicky", it would be "(c) Jachym Cepicky and others" (and git history
would provide the others).

The critical part of a contribution agreement (or whatever you decide) is
to be sure everyone who contributed is happy with the open source license
being used. You may decide a contribution agreement is fun (it allows you
to relicense later), or you may decide you just want an email sent to your
developer list (how OSGeo Live works
<https://wiki.osgeo.org/wiki/Live_GIS_Disc#Git_migration>)

--
Jody Garnett

On 22 February 2016 at 10:23, Jachym Cepicky <jachym.cepicky at gmail.com>
wrote:

> Hi,
>
> the master branch licence says:
>
> Copyright (C) 2014-2016 PyWPS Development Team, represented by Jachym
> Cepicky
>
> Copyright should currently go to one person - me - in order to make e.g.
> joining of OSGeo easier
>
> J
>
> po 22. 2. 2016 v 15:31 odesílatel Even Rouault <even.rouault at spatialys.com>
> napsal:
>
>> Le lundi 22 février 2016 14:23:24, Tom Kralidis a écrit :
>> > Hi all: in PyWPS we are working through code contributor and license
>> policy
>> > as per the project graduation checklist [1].
>> >
>> > The project is moving with [2] as source code header/copyright.
>> >
>> > Given this copyright do we still require specific code contribution
>> > agreements? Guessing yes, but looking for confirmation here.
>>
>> There's the alternative mentionned in
>>
>> https://wiki.osgeo.org/wiki/Incubation_FAQ#Q:_Is_a_code_contribution_agreement_required
>> :
>> - either each contributor (or depending on the situation: their employer,
>> or
>> the entity funding the work, etc...) retains his copyright
>> - either they accept to assign copyright to a single entity such as
>> "Copyright
>> (C) 2014-YYYY PyWPS Development Team, represented by
>> PyWPS Project Steering Committee". But I'm not sure if the later would be
>> a
>> valid legal entity that could exercice its rights regarding copyright
>> enforcement.
>>
>> (My personal opinion: for the X/MIT license, there's probably little
>> point in
>> having copyright assignment to a single entity. Makes more sense if you
>> use a
>> copyleft license to reconsider later relicensing to non-copyleft)
>>
>> >
>> > Thanks
>> >
>> > ..Tom
>> >
>> > [1] https://github.com/geopython/pywps/issues/84#issuecomment-184989790
>> > [2]
>> https://github.com/geopython/pywps/wiki/Templates#source-code-header
>> > _______________________________________________
>> > Incubator mailing list
>> > Incubator at lists.osgeo.org
>> > http://lists.osgeo.org/mailman/listinfo/incubator
>>
>> --
>> Spatialys - Geospatial professional services
>> http://www.spatialys.com
>> _______________________________________________
>> Incubator mailing list
>> Incubator at lists.osgeo.org
>> http://lists.osgeo.org/mailman/listinfo/incubator
>
>
> _______________________________________________
> Incubator mailing list
> Incubator at lists.osgeo.org
> http://lists.osgeo.org/mailman/listinfo/incubator
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osgeo.org/pipermail/incubator/attachments/20160222/25fce7be/attachment.html>