Sure. An informative header that names the project, links to to project page, and references the licence is my my view the most useful thing we can provide. The lawyer said that a public notice warning that the work is copyrighted might deter some infringers, even if it is not legally binding.
Kind regards, Ben. On 27/07/16 19:43, Andrea Aime wrote: > Hi Ben, > Jody told us during the meeting that adding a header referencing the > license is still good as people > cannot claim they did not read/know about the license file in the root > folder. > This seems like good advice to add, even if not legally binding > > Cheers > Andrea > > > On Wed, Jul 27, 2016 at 5:17 AM, Ben Caradoc-Davies <[email protected]> > wrote: > >> Jody, >> >> I have written a draft post "Copyright Headers in Source Code File" son >> the GeoTools blog. Please review and publish (in your capacity as OSGeo >> project officer and board member). >> >> I also updated your earlier post on this topic as it had some broken >> formatting and content and I needed to link to it. Apologies in advance! >> >> Kind regards, >> Ben. >> >> On 27/07/16 07:22, Jody Garnett wrote: >>> *Getting a head(er) with OSGeo Legal* >>> >>> Ben and I met with OSGeo legal council last week, waiting on Ben to send >>> email summary/write blog post. >>> >>> TLDR: We are good with respect to headers, small advantage >>> - headers not required for (c) >>> - small advantage to headers is opportunity to document license >>> >>> Actions: >>> - (done) Brad: Change geoserver dev guide? Is this done/merged ... >>> https://github.com/geoserver/geoserver/wiki/Proposals/GSIP-147 >>> - Ben: Write up blog post for use by wider community (ie incubation, >> other >>> osgeo projects) >> >> -- >> Ben Caradoc-Davies <[email protected]> >> Director >> Transient Software Limited <http://transient.nz/> >> New Zealand >> >> >> ------------------------------------------------------------------------------ >> What NetFlow Analyzer can do for you? Monitors network bandwidth and >> traffic >> patterns at an interface-level. Reveals which users, apps, and protocols >> are >> consuming the most bandwidth. Provides multi-vendor support for NetFlow, >> J-Flow, sFlow and other flows. Make informed decisions using capacity >> planning >> reports.http://sdm.link/zohodev2dev >> _______________________________________________ >> GeoTools-Devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geotools-devel >> > > > -- Ben Caradoc-Davies <[email protected]> Director Transient Software Limited <http://transient.nz/> New Zealand ------------------------------------------------------------------------------ What NetFlow Analyzer can do for you? Monitors network bandwidth and traffic patterns at an interface-level. Reveals which users, apps, and protocols are consuming the most bandwidth. Provides multi-vendor support for NetFlow, J-Flow, sFlow and other flows. Make informed decisions using capacity planning reports.http://sdm.link/zohodev2dev _______________________________________________ GeoTools-Devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
