Re: Copyright dates

2017-01-30 Thread Mark Atwood
I will sweep through the documentation files, and add the correct forms and content for the copyright and license markings. ..m On Mon, Jan 30, 2017 at 12:02 PM Gary E. Miller wrote: > Yo Mark! > > On Mon, 30 Jan 2017 18:58:55 + > Mark Atwood wrote: > > > When you create a new file, mark i

Re: Copyright dates

2017-01-30 Thread Gary E. Miller
Yo Mark! On Mon, 30 Jan 2017 18:58:55 + Mark Atwood wrote: > When you create a new file, mark it as follows (updating the year) as > required: [...] Can you add this advice to some doc that is in tree? RGDS GARY --- G

Re: Copyright dates

2017-01-30 Thread Mark Atwood
Oh god, yeah. Stack Overflow copypastes are a constant headache today when doing due diligence when acquiring tech companies. Lots of people have been begging Stack Overflow to do something about it. The CC license that SO defaults all it's content to is not compatible with any open source or eve

Re: Copyright dates

2017-01-30 Thread Daniel Poirot
What's fun is hearing "No copyright needed, I got it off Stack Overflow!" ...wrong > On Jan 30, 2017, at 12:58 PM, Mark Atwood wrote: > > Commercial FOSS audit tools like Protecode and Blackduck will be able to > recognize the SPDX tags, and the Copyright text. > > > In our file ntpsec/deve

Re: Copyright dates

2017-01-30 Thread Mark Atwood
Commercial FOSS audit tools like Protecode and Blackduck will be able to recognize the SPDX tags, and the Copyright text. In our file ntpsec/devel/hacking.txt : We use the SPDX convention for inclusion by reference. You can read about this at http://spdx.org/licenses When you create a n

Re: Copyright dates

2017-01-30 Thread Daniel Poirot
Commercial FOSS audit tools like Protecode and BlackDuck will match a snippet and attribute to the FOSS project. > On Jan 30, 2017, at 12:30 PM, Mark Atwood wrote: > > That's... complicated. > > We don't need to have a notice attached to every file, because there is a > copyright notice att

Re: Copyright dates

2017-01-30 Thread Mark Atwood
That's... complicated. We don't need to have a notice attached to every file, because there is a copyright notice attached to the project as a whole, and there is a notice attached to each repo. Individual files generally don't each need their own notice, since individual files generally no longe

Re: Copyright dates

2017-01-30 Thread Hal Murray
fallenpega...@gmail.com said: > Right now our standard copyright text is "Copyright $YEAR_YOU_ARE_WRITING_THI > S by the NTP Project contributors" Should the documentation files have a copyright notice? -- These are my opinions. I hate spam. ___

Re: Copyright dates

2017-01-29 Thread Mark Atwood
copyright lengths will always be increased to keep Steamboat Willy under copyright. Right now our standard copyright text is "Copyright $YEAR_YOU_ARE_WRITING_THIS by the NTP Project contributors" After 50ish years goes by from now-ish, we can revisit. ..m On Sun, Jan 29, 2017 at 1:02 PM Gary E.

Re: Copyright dates

2017-01-29 Thread Gary E. Miller
Yo Mark! On Sun, 29 Jan 2017 07:58:24 + Mark Atwood wrote: > > Do they need to be updated? I just noticed one that was 2015. > they don't require updating US Copyright is now generally 70 years after the death of the author. You plan to live that long? RGDS GARY

Re: Copyright dates

2017-01-28 Thread Mark Atwood
they don't require updating On Sat, Jan 28, 2017, 5:38 PM Hal Murray wrote: > > Do they need to be updated? I just noticed one that was 2015. > > Should that go on the release checklist? > > > -- > These are my opinions. I hate spam. > > > > ___ > de

Copyright dates

2017-01-28 Thread Hal Murray
Do they need to be updated? I just noticed one that was 2015. Should that go on the release checklist? -- These are my opinions. I hate spam. ___ devel mailing list devel@ntpsec.org http://lists.ntpsec.org/mailman/listinfo/devel