Thanks for taking this up Markus: I know when GeoTools went through incubation we had to change our codebase from "(c) GeoTools Project Management Committee" since it was not a legal entity; indeed retroactively creating a legal entity was shot down as an idea also. The good news is that we have some recent legal guidance from osgeo <http://geotoolsnews.blogspot.com/2016/07/copyright-headers-in-source-code-files.html> on this topic.
The examples that were provided to to incubation simply listed Copyright (c) GRASS Development Team. The approach you describe using "initial author followed by grass development team" sounds much better, it is very similar to what our friends at the eclipse foundation <https://www.eclipse.org/legal/epl-2.0/faq.php#h.aq5xwcjmpy2a> do: *Copyright (c) {date} {owner} [and others]* -- Jody Garnett On Wed, 13 Feb 2019 at 11:56, Markus Neteler <[email protected]> wrote: > Hi PSC, > > in the incubator list the question came up if GRASS Development team > is legal entity to which the copyright can be assigned. > > At time the GRASS Development team is not an incorporated entity but > usually the first copyright holder name in the source code files is > the initial author followed by the GRASS Development team. > If that's legally sufficient I cannot say nor what the implications are. > > Hence this mail to start a discussion on this. > > Best, > Markus > _______________________________________________ > grass-psc mailing list > [email protected] > https://lists.osgeo.org/mailman/listinfo/grass-psc
_______________________________________________ grass-psc mailing list [email protected] https://lists.osgeo.org/mailman/listinfo/grass-psc
