- General
-
Questions
Copyright holder
This discussion was imported from CodePlex
objo wrote at 2014-02-16 14:43:
Currently the copyright holder in the license text shows the name of the coordinator.
When other collaborators contribute with large portions of code, it feels strange to list my name there. And I guess they also want to be released from liability.
I also want to encourage contributions, and it may be strange to create a major fature and put my name in the copyright text...
Should it be changed?
a. more generic text like "OxyPlot contributors"? then list contributors in a separate file?
b. list of all contributors on each file? it is more work to keep track of it, cannot replace by general header
When other collaborators contribute with large portions of code, it feels strange to list my name there. And I guess they also want to be released from liability.
I also want to encourage contributions, and it may be strange to create a major fature and put my name in the copyright text...
Should it be changed?
a. more generic text like "OxyPlot contributors"? then list contributors in a separate file?
b. list of all contributors on each file? it is more work to keep track of it, cannot replace by general header
stephenroe wrote at 2014-02-24 21:15:
Why not go for:
Copyright (c) 2014 OxyPlot.org
and then maintain a CONTRIBUTORS file located in the root of the project?
Copyright (c) 2014 OxyPlot.org
and then maintain a CONTRIBUTORS file located in the root of the project?
objo wrote at 2014-02-25 08:30:
Yes, a contributors file should be added, maybe also a AUTHORS file that lists the copyright holders?
like
http://golang.org/CONTRIBUTORS
http://golang.org/AUTHORS
http://golang.org/LICENSE
Another alternative: Copyright (c) 2014 The OxyPlot Authors.
Should there be a CLA?
http://en.wikipedia.org/wiki/Contributor_License_Agreement
like
http://golang.org/CONTRIBUTORS
http://golang.org/AUTHORS
http://golang.org/LICENSE
Another alternative: Copyright (c) 2014 The OxyPlot Authors.
Should there be a CLA?
http://en.wikipedia.org/wiki/Contributor_License_Agreement
objo wrote at 2014-02-25 20:41:
stephenroe wrote at 2014-02-25 23:33:
Yes, and it has a nice copyright phrase:
Copyright (c) 2014 jQuery foundation and other contributors
Going in this direction would allow you to keep your name as the major copyright holder. For example:
Copyright (c) 2014 Oystein Bjorke and other contributors
At the end of the day, due to source control, it is very easy to identify each authors contribution.
http://stackoverflow.com/questions/2228188/finding-the-author-of-a-line-of-code-in-mercurial
Copyright (c) 2014 jQuery foundation and other contributors
Going in this direction would allow you to keep your name as the major copyright holder. For example:
Copyright (c) 2014 Oystein Bjorke and other contributors
At the end of the day, due to source control, it is very easy to identify each authors contribution.
http://stackoverflow.com/questions/2228188/finding-the-author-of-a-line-of-code-in-mercurial
objo wrote at 2014-02-27 20:32:
I changed to Copyright (c) 2014 OxyPlot contributors and added AUTHORS and CONTRIBUTORS files. Will update the file headers in the source code soon.
The list in the CONTRIBUTORS file was compiled from the Hg history, but it is very possible some contributors are missing. Please send me a notification to be added to the CONTRIBUTORS or AUTHORS lists. Also let me know about other improvements. (CLA?)
I am currently reading "Producing OSS" by Karl Fogel and my goal is simply to get more collaborators on the project!
http://www2.econ.iastate.edu/tesfatsi/producingoss.karlfogel2005.pdf
http://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590
The list in the CONTRIBUTORS file was compiled from the Hg history, but it is very possible some contributors are missing. Please send me a notification to be added to the CONTRIBUTORS or AUTHORS lists. Also let me know about other improvements. (CLA?)
I am currently reading "Producing OSS" by Karl Fogel and my goal is simply to get more collaborators on the project!
http://www2.econ.iastate.edu/tesfatsi/producingoss.karlfogel2005.pdf
http://www.amazon.com/Producing-Open-Source-Software-Successful/dp/0596007590
Customer support service by UserEcho
