If you need an out - put a readme.rst file in the same directory ( like we do
in data dirs )indicating where the file came from, under what license it is
used.
--
Jody Garnett
On 02/04/2013, at 6:21 PM, Frank Gasdorf <fg...@users.sourceforge.net> wrote:
> Hello everybody,
>
> since all the java headers are updated I'm wondering about missing headers in
> other resource files, e.g. applicationContext.xml and
> GeoServerApplication*.properties
> Some of the applicationContext files have the following license header
> include whereas others (e.g. in community and extensions sub-modules) haven't
> any header at all.
>
> <!--
> Copyright (c) 2001 - 2013 OpenPlans - www.openplans.org. All rights reserved.
> This code is licensed under the GPL 2.0 license, available at the root
> application directory.
> -->
>
>
> Is it contributor-dependent or is all the code under the same Copyright?
>
> Should I raise a ticket at JIRA?
>
> I assume we should consolidate all these files as well and add the same
> header.
>
> For properties files it would a header would look like this:
>
> # Copyright (c) 2001 - 2013 OpenPlans - www.openplans.org. All rights
> reserved.
> # This code is licensed under the GPL 2.0 license, available at the root
> # application directory.
>
> But how do we deal with contributions coming from external platforms in the
> future - like the translated properties files from Transifex.com
> (https://www.transifex.com/projects/p/geoserver/). Is it a must to have a
> header for properties files or just optional?
>
> Any opinions?
>
> Cheers, Frank
>
>
>
>
> 2013/1/10 Jody Garnett <jody.garn...@gmail.com>
>>> Asked folks at OpenPlans and they said:
>>>
>>> Yes, we legally changed our name to OpenPlans, Inc a couple of years ago,
>>> so if the copyright was assigned to TOPP it should be assigned to
>>> OpenPlans.
>>>
>>> The year it changed was 2010.
>>>
>>> So I guess we need to update our headers. I can volunteer some time given
>>> that it should just boil down to some script writing. How should the header
>>> read exactly? Should we just change TOPP to OpenPlans or should we include
>>> both entities with a date range for topp like:
>>>
>>>> /* Copyright (c) 2010 - 2013 OpenPlans - www.openplans.org. All rights
>>>> reserved.
>>>> * Copyright (c) 2001 - 2010 TOPP - www.openplans.org. All rights reserved.
>>>> * This code is licensed under the GPL 2.0 license, availible at the root
>>>> * application directory.
>>>> */
>>>
>>> Or just:
>>>>
>>>> /* Copyright (c) 2001 - 2013 OpenPlans - www.openplans.org. All rights
>>>> reserved.
>>>> * This code is licensed under the GPL 2.0 license, availible at the root
>>>> * application directory.
>>>> */
>>
>> Good question :P
>>
>> I would go for the second one (easier search and replace - and it is the
>> same legal entity?)
>> (and because you are changing the file you can update the end of the date
>> range to say 2013 in each case).
>>
>> Jody
>>
>>
>> ------------------------------------------------------------------------------
>> Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS,
>> MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current
>> with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft
>> MVPs and experts. ON SALE this month only -- learn more at:
>> http://p.sf.net/sfu/learnmore_122712
>> _______________________________________________
>> Geoserver-devel mailing list
>> Geoserver-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/geoserver-devel
>
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
