On 2/23/2016 10:24 AM, Paul Jakma wrote:
> On Tue, 23 Feb 2016, Paul Jakma wrote:
>
>> We havn't though had much of a problem with people adding notices when they
>> shouldn't though. The problem is more the reverse.
> Oh, and my desire is for people to be clear, explicit, unambiguous and
> complete in describing the rights interests in any contribution.
sure - but unqualified copyright statements just adds problems down the
road as was covered in the links you provided. Why not just use their
language?
> Whether that's in the commit message, the top of the files modified, or
> elsewhere, we could figure out. Just "Copyright ..." add the top of
> files modified seems a fairly standard, well recognised and clear way to
> do it.
With qualification, yes. Unqualified -- particularly in the case like
this one where none previously existed, seems unreasonable to me.
Again here's what they suggest:
> ... include a description of the modification along with the notice:
> Copyright 2012 Jane Hacker <[email protected]> Fixed random
number generator to
> output numbers other than 9.
I think the proposed language adopted from
https://www.softwarefreedom.org/resources/2012/ManagingCopyrightInformation.html
is pretty clean and straightforward. If you don't like:
+
+ Care should be taken when adding copyright statements to existing
files as
+ not every contribution to a free software project is copyrightable. See
+ http://softwarefreedom.org/resources/2007/originality-requirements.html.
+
Please suggest alternate language, or we can just drop it.
But I think the following addresses both of our main points and the example is
based on a pretty reasonable reference.
+ When adding a copyright based on a modification, you must also include a
+ description of the modification along with the notice. For example:
+ Copyright 2012 Jane Hacker <[email protected]> Fixed
+ random number generator to output numbers other than 9.
+
Lou
> regards,
_______________________________________________
Quagga-dev mailing list
[email protected]
https://lists.quagga.net/mailman/listinfo/quagga-dev
