[Geoserver-devel] A couple questions for OSGeo incubation

GeoServer GeoServer Developer
1

Landon was looking for a couple things over on the incubation list …

  1. Code Contribution

I remember signing a code contribution agreement with http://openplans.org - while I got a nice T-shirt out of the deal, it is not mentioned in our docs at any point. Do we still require a code contribution agreement?

Our docs have lots of guidance on the mechanics of getting commit access, but are light on how we get agreement.

Options:

  • If we have a code contribution agreement for people to sign, we can make note of it in our developers guide
  • Or we should note in our developers guide something like, when invited for core commit access we ask for a formal email to geoserver-devel accepting our GPL license etc… (this is what MapServer does)
  1. Documentation License

Two ways we can take this:

  • Stick creative commons with attribution on it (think that is fair if people reuse our content I would like readers to know where it came from )
  • or we can do what GeoMoose did and indicate that the source code for our documentation is provided (under our normal GPL license)
  1. And one more thing …

Our headers say “The Open Planning Project” right now, I think that organisation has changed name to “Open Plans” - do we need to change our headers? Like did they legally change their name?

–
Jody Garnett

2

On Tue, Jan 8, 2013 at 11:03 PM, Jody Garnett <jody.garnett@anonymised.com>wrote:

Landon was looking for a couple things over on the incubation list …

1) Code Contribution

I remember signing a code contribution agreement with http://openplans.org- while I got a nice T-shirt out of the deal, it is not mentioned in our
docs at any point. Do we still require a code contribution agreement?

Our docs have lots of guidance on the mechanics of getting commit access,
but are light on how we get agreement.

Options:
- If we have a code contribution agreement for people to sign, we can make
note of it in our developers guide
- Or we should note in our developers guide something like, when invited
for core commit access we ask for a formal email to geoserver-devel
accepting our GPL license etc… (this is what MapServer does)

2) Documentation License

Two ways we can take this:
- Stick creative commons with attribution on it (think that is fair if
people reuse our content I would like readers to know where it came from )
- or we can do what GeoMoose did and indicate that the source code for our
documentation is provided (under our normal GPL license)

3) And one more thing ...

Our headers say "The Open Planning Project" right now, I think that
organisation has changed name to "Open Plans" - do we need to change our
headers? Like did they legally change their name?

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.
*/

--

Jody Garnett

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.

3

The second one looks nicer to the eyes, and the entity is really the same, just changed name,
so I guess it’s ok to go with the simpler version?
The former is more precise though… anyone with enough legal insight to nudge us in one
direction or the other?

Should we ask on osgeo-discuss, lots of people there, it may be that someone knows?

Cheers
Andrea

···

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.
    */
4

On Thu, Jan 10, 2013 at 3:52 AM, Andrea Aime
<andrea.aime@anonymised.com>wrote:

On Wed, Jan 9, 2013 at 5:31 PM, Justin Deoliveira <jdeolive@anonymised.com>wrote:

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.
*/

The second one looks nicer to the eyes, and the entity is really the same,
just changed name,
so I guess it's ok to go with the simpler version?
The former is more precise though... anyone with enough legal insight to
nudge us in one
direction or the other?

IANAL, but I feel the second is fine, as it is the same entity.

Should we ask on osgeo-discuss, lots of people there, it may be that
someone knows?

Cheers
Andrea

--

Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------

------------------------------------------------------------------------------
Master Java SE, Java EE, Eclipse, Spring, Hibernate, JavaScript, jQuery
and much more. Keep your Java skills current with LearnJavaNow -
200+ hours of step-by-step video tutorials by Java experts.
SALE $49.99 this month only -- learn more at:
http://p.sf.net/sfu/learnmore_122612
_______________________________________________
Geoserver-devel mailing list
Geoserver-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

5
  1. Documentation License

Two ways we can take this:

  • Stick creative commons with attribution on it (think that is fair if people reuse our content I would like readers to know where it came from )

Went ahead and created this (at least to capture any discussion):

6

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 :stuck_out_tongue:

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

7

On Thu, Jan 10, 2013 at 4:47 AM, Jody Garnett <jody.garnett@anonymised.com> wrote:

  1. Documentation License

Two ways we can take this:

  • Stick creative commons with attribution on it (think that is fair if people reuse our content I would like readers to know where it came from )

Went ahead and created this (at least to capture any discussion):

The license choice seems good to me, but I don’t if we can get the license footer you want:

© Copyright 2014, OpenPlans. Last updated on Jan 07, 2013. Created using Sphinx.
GeoServer User Manual by geoserver.org is licensed under a Creative Commons Attribution 3.0 Unported License. Based on a work at docs.geoserver.org/latest/en/user/.

The footer as far as I know it shared among all pages, and the “last updated” message
is referring to the generation of the HTML from the RST.
What we don’t have is the year (2014 in your example) when the single .rst file has
been last updated, it’s not something we have in the .rst files and don’t know if we can
put add it all in a useful way

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

8

The footer as far as I know it shared among all pages, and the “last updated” message
is referring to the generation of the HTML from the RST.
What we don’t have is the year (2014 in your example) when the single .rst file has
been last updated, it’s not something we have in the .rst files and don’t know if we can
put add it all in a useful way

Footer is configured in config.py - I had to correct them in Dec. So we can sort out something at the bottom of the page, even if just the small CCbyA logo.

9

On Thu, Jan 10, 2013 at 1:52 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

The footer as far as I know it shared among all pages, and the “last updated” message
is referring to the generation of the HTML from the RST.
What we don’t have is the year (2014 in your example) when the single .rst file has
been last updated, it’s not something we have in the .rst files and don’t know if we can
put add it all in a useful way

Footer is configured in config.py - I had to correct them in Dec. So we can sort out something at the bottom of the page, even if just the small CCbyA logo.

Ok, then maybe I mistunderstood the intention of “2014” in that footer.I thought it was the last year in which the specific file we’re looking at has
been modified, whilst the footer is instead shared among all the pages

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

10

Ok, then maybe I mistunderstood the intention of “2014” in that footer.
I thought it was the last year in which the specific file we’re looking at has
been modified, whilst the footer is instead shared among all the pages

Since it is a document license, we are considering the entire document as one thing (so the footer is consistent between the pages).
I may as well prepare the patch as long as discussion has died down.

Jody

11

+1. Good thinking, Jody. Some parts of the documentation, including production Tomcat and database configuration and remarks on standards, are quite general, and it would benefit the community if these could be reused. In my view, CC-BY is a good choice.

As an aside, I note that on the GSIP page, I was pencilled-in as a +0 in my absence, which is not the same thing as having not voted. Perhaps we should leave a blank to make it clearer when someone has not voted, as +0 is a valid vote?

Kind regards,
Ben.

On 10/01/13 11:47, Jody Garnett wrote:

2) Documentation License

Two ways we can take this:
- Stick creative commons with attribution on it (think that is fair if
people reuse our content I would like readers to know where it came from )

Went ahead and created this (at least to capture any discussion):

-
http://geoserver.org/display/GEOS/GSIP+89+Creative+Commons+with+Attribution

--
Ben Caradoc-Davies <Ben.Caradoc-Davies@anonymised.com>
Software Engineer
CSIRO Earth Science and Resource Engineering
Australian Resources Research Centre

12

On Tuesday, 22 January 2013 at 12:17 PM, Ben Caradoc-Davies wrote:

+1. Good thinking, Jody. Some parts of the documentation, including
production Tomcat and database configuration and remarks on standards,
are quite general, and it would benefit the community if these could be
reused. In my view, CC-BY is a good choice.

Thanks Ben. More importantly CC-BY is widely understood leading to less questions (although I am tempted for an example “attribution” for the developers guide).

As an aside, I note that on the GSIP page, I was pencilled-in as a +0 in
my absence, which is not the same thing as having not voted. Perhaps we
should leave a blank to make it clearer when someone has not voted, as
+0 is a valid vote?

Yeah trouble no matter what way we go, it is useful to mark down “assume consent” when the GSIP goes ahead without input. In my review of the GSIPs I found many of the completed pages had gone ahead with no recorded votes. I did not clean things up (by checking email?) and simply moved them over to the “done” pile.

Jody

13

Pull request now available: https://github.com/geoserver/geoserver/pull/131

–
Jody Garnett

On Thursday, 10 January 2013 at 2:47 PM, Jody Garnett wrote:

  1. Documentation License

Two ways we can take this:

  • Stick creative commons with attribution on it (think that is fair if people reuse our content I would like readers to know where it came from )

Went ahead and created this (at least to capture any discussion):

14

On Thu, Jan 31, 2013 at 1:15 PM, Jody Garnett <jody.garnett@anonymised.com> wrote:

Pull request now available: https://github.com/geoserver/geoserver/pull/131

Pretty simple one, merged it

Cheers
Andrea

–

==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more information.

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39 339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

15

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.

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.garnett@…403…>

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 :stuck_out_tongue:

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@anonymised.comsts.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-devel

16

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.

···

2013/1/10 Jody Garnett <jody.garnett@anonymised.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 :stuck_out_tongue:

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