I can see the appeal of having "2011-present" or similar, but I'm not sure it
is valid.
I believe the point of the date is to establish when a version was published
for copyright law purposes. This means if a file isn't touched for several
years, it will have an invalid publication date ("present") from the
perspective of copyright law.
This had a few useful insights:
http://stackoverflow.com/questions/2390230/do-copyright-dates-need-to-be-updated
Being that the copyright on even the oldest part of GeoServer's code is
probably not going to expire until everyone who reads this has snuffed it
(unless there are some *very* young GeoTools developers!), I think the Google
ethos is simplest:
"Google doesn't update their copyright dates because they don't care whether
some page they started in 1999 and updated this year falls into the public
domain in 2094 or 2109."
Cheers,
Jonathan
---- On Fri, 20 May 2016 14:48:08 +0100 Justin Deoliveira
<jdeol...@gmail.com> wrote ----
Thanks Ben. I am going to go ahead with this and update the proposal. Thanks
for the input everyone.
On Thu, May 19, 2016 at 5:19 PM Ben Caradoc-Davies <b...@transient.nz>
wrote:
A fixed date might imply that this was the last time the file changed.
Could we write this to start with the file creation year but make it an
open date range?
(C) 2011-, Open Source Geospatial Foundation (OSGeo)
or
(C) 2011-present, Open Source Geospatial Foundation (OSGeo)
as the en-dash (open number range) might otherwise be incorrectly parsed
as an em-dash (a pause in text).
If the project ever undergoes another copyright ownership change, we can
locate all these "-present," elements and rewrite them to the date that
the change occurs, and add a new open-ended copyright line for the new
owner.
Kind regards,
Ben.
On 20/05/16 07:36, Torben Barsballe wrote:
> Copyright header with file creation date sounds like a good idea, although
> a would assume we would still want aspects of option B here -
specifically,
> if there is ever a copyright transfer event, all the headers would need
> updating. I assume we would do something similar to the following:
>
> /* (c) 2014 Open Source Geospatial Foundation (OsGeo)
> * (c) 2001 - 2013 OpenPlans
> */
>
> Where 2001 is the file creation date, and 2014 is the copyright transfer
> date (Example taken from GeoServer).
>
> Torben
>
> On Thu, May 19, 2016 at 10:47 AM, Justin Deoliveira
<jdeol...@gmail.com>
> wrote:
>
>> To be clear option C is not to drop the copyright header all together,
>> just the date that lives in the header.
>>
>> I am for any option that doesn’t require us to continuously change the
>> header for every commit. So I am +1 with a copyright header that
contains
>> the file creation date.
>>
>> On Thu, May 19, 2016 at 11:42 AM Andrea Aime
<andrea.a...@geo-solutions.it>
>> wrote:
>>
>>> On Thu, May 19, 2016 at 7:37 PM, Jody Garnett
<jody.garn...@gmail.com>
>>> wrote:
>>>
>>>> Putting those two tensions together can I recommend a
compromise -
>>>>
>>>> "Copyright header using file creation date"
>>>>
>>>> This compromise provides copyright header and does not
require ongoing
>>>> extra effort to maintain.
>>>>
>>>
>>> I'd second this one too (based on my previous research about
foundations,
>>> and finding
>>> none that recommends having no copyright headers)
>>>
>>> Cheers
>>> Andrea
>>>
>>> --
>>> ==
>>> GeoServer Professional Services from the experts! Visit
>>> http://goo.gl/it488V for more information.
>>> ==
>>>
>>> Ing. Andrea Aime
>>> @geowolf
>>> Technical Lead
>>>
>>> GeoSolutions S.A.S.
>>> Via di Montramito 3/A
>>> 55054 Massarosa (LU)
>>> phone: +39 0584 962313
>>> fax: +39 0584 1660272
>>> mob: +39 339 8844549
>>>
>>> http://www.geo-solutions.it
>>> http://twitter.com/geosolutions_it
>>>
>>> *AVVERTENZE AI SENSI DEL D.Lgs. 196/2003*
>>>
>>> Le informazioni contenute in questo messaggio di posta
elettronica e/o
>>> nel/i file/s allegato/i sono da considerarsi strettamente
riservate. Il
>>> loro utilizzo è consentito esclusivamente al destinatario del
messaggio,
>>> per le finalità indicate nel messaggio stesso. Qualora riceviate
questo
>>> messaggio senza esserne il destinatario, Vi preghiamo
cortesemente di
>>> darcene notizia via e-mail e di procedere alla distruzione del
messaggio
>>> stesso, cancellandolo dal Vostro sistema. Conservare il messaggio
stesso,
>>> divulgarlo anche in parte, distribuirlo ad altri soggetti,
copiarlo, od
>>> utilizzarlo per finalità diverse, costituisce comportamento
contrario ai
>>> principi dettati dal D.Lgs. 196/2003.
>>>
>>>
>>>
>>> The information in this message and/or attachments, is intended
solely
>>> for the attention and use of the named addressee(s) and may be
confidential
>>> or proprietary in nature or covered by the provisions of privacy
act
>>> (Legislative Decree June, 30 2003, no.196 - Italy's New Data
Protection
>>> Code).Any use not in accord with its purpose, any disclosure,
reproduction,
>>> copying, distribution, or either dissemination, either whole or
partial, is
>>> strictly forbidden except previous formal approval of the named
>>> addressee(s). If you are not the intended recipient, please
contact
>>> immediately the sender by telephone, fax or e-mail and delete the
>>> information in this message that has been received in error. The
sender
>>> does not give any warranty or accept liability as the content,
accuracy or
>>> completeness of sent messages and accepts no responsibility for
changes
>>> made after they were sent or for other risks which arise as a
result of
>>> e-mail transmission, viruses, etc.
>>>
>>> -------------------------------------------------------
>>>
>>
>>
>>
------------------------------------------------------------------------------
>> Mobile security can be enabling, not merely restricting. Employees who
>> bring their own devices (BYOD) to work are irked by the imposition of
MDM
>> restrictions. Mobile Device Manager Plus allows you to control only
the
>> apps on BYO-devices by containerizing them, leaving personal data
>> untouched!
>> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>> _______________________________________________
>> GeoTools-Devel mailing list
>> GeoTools-Devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>>
>>
>
>
>
>
------------------------------------------------------------------------------
> Mobile security can be enabling, not merely restricting. Employees who
> bring their own devices (BYOD) to work are irked by the imposition of MDM
> restrictions. Mobile Device Manager Plus allows you to control only the
> apps on BYO-devices by containerizing them, leaving personal data
untouched!
> https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
>
>
>
> _______________________________________________
> GeoTools-Devel mailing list
> GeoTools-Devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/geotools-devel
>
--
Ben Caradoc-Davies <b...@transient.nz>
Director
Transient Software Limited <http://transient.nz/>
New Zealand
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
------------------------------------------------------------------------------
Mobile security can be enabling, not merely restricting. Employees who
bring their own devices (BYOD) to work are irked by the imposition of MDM
restrictions. Mobile Device Manager Plus allows you to control only the
apps on BYO-devices by containerizing them, leaving personal data untouched!
https://ad.doubleclick.net/ddm/clk/304595813;131938128;j
_______________________________________________
GeoTools-Devel mailing list
GeoTools-Devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geotools-devel
