Thanks Ian, I actually have a technical question for Andrea on this one, one of the tasks is "Check if docs can skip QA check for LGPL headers". Any tips on how to set that up, or override the configuration to check for CC0 headers? -- Jody Garnett
On Mar 19, 2022 at 2:20:08 AM, Ian Turton <ijtur...@gmail.com> wrote: > +1 > > Ian > > On Fri, 18 Mar 2022 at 20:59, Jody Garnett <jody.garn...@gmail.com> wrote: > >> Here is proposal >> https://github.com/geotools/geotools/wiki/Change-tutorial-and-example-code-from-public-domain-to-CC0 >> -- >> Jody Garnett >> >> >> On Fri, 18 Mar 2022 at 13:48, Jody Garnett <jody.garn...@gmail.com> >> wrote: >> >>> I would like to do a quick proposal: >>> >>> > Use CC0 for our documentation and source code examples, in keeping >>> with our public domain policy in the developers guide >>> >>> CC0 is as I understand it a more useful way to release copyright, while >>> public domain can be american centric. >>> >>> Context - tripped over a couple of things looking at tutorial code: >>> - Sample code was changed to LGPL at some point, when the project policy >>> is public domain >>> - Some of the pom.xml and pom2.xml examples no longer match since these >>> projects are not tested except by hand. I have learned a bit about maven >>> and we can set these up as distinct standalone projects (using deploy.skip) >>> to avoid publishing. >>> >>> There is a pull request here >>> https://github.com/geotools/geotools/pull/3823 showing the result >>> (including developers guide change). >>> -- >>> Jody Garnett >>> >> _______________________________________________ >> GeoTools-Devel mailing list >> GeoTools-Devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> > > > -- > Ian Turton >
_______________________________________________ GeoTools-Devel mailing list GeoTools-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
