Open zuphilip opened 9 years ago
I win! Obviously no objections to relicense "mine".
On Tue, Sep 29, 2015 at 11:20 AM, Philipp Zumstein <notifications@github.com
wrote:
It was mentioned in this thread https://github.com/zotero/translators/pull/947#discussion_r40689273 to re-licence the ACM translator to AGPL https://en.wikipedia.org/wiki/Affero_General_Public_License. I found a total of 111 result with a General GPL licence. Should we try to change all translators to AGPL? This is possible if the creator(s) accept to do so.
Here is an uncomplete list:
- @adam3smith https://github.com/adam3smith : 49 results https://github.com/zotero/translators/search?utf8=%E2%9C%93&q=%22copy+of+the+GNU+General+Public+License%22+karcher&type=Code
- @avram https://github.com/avram : 18 results https://github.com/zotero/translators/search?utf8=%E2%9C%93&q=%22copy+of+the+GNU+General+Public+License%22+Avram+&type=Code
- @aurimasv https://github.com/aurimasv : 7 results https://github.com/zotero/translators/search?utf8=%E2%9C%93&q=%22copy+of+the+GNU+General+Public+License%22+aurimas&type=Code
Note, there might be more than one contributors mentioned.
— Reply to this email directly or view it on GitHub https://github.com/zotero/translators/issues/951.
Sebastian Karcher, PhD www.sebastiankarcher.com
No objections from me either, obviously, but I do want to push for a general repo license and having contributors sign it. Not sure it will be possible, but it would be great to hear @dstillman's or @simonster's view on this. I don't think it makes a lot of sense to put a license at the top of each file with a single name when there are so many contributors per file.
We may also want to consider removing author field from translator metadata. It is quite confusing, since there are no clear guidelines on who should be added to the list. Besides, github/git tracks all contributors.
For new contributions, I think a general repo license ("unless otherwise indicated") and removing the author field makes sense. Removing from existing probably has to be on a case-by-case basis, and we also should be careful to document in commit messages when translators are contributed by someone other than the committer.
@simonster Would you agree to relicense your contributions to translators
to AGPL? I would like to prepare a commit to reduce the number of old licenced translators...
I analyzed all found results and created a list of all contributors: https://docs.google.com/spreadsheets/d/1wlFuKtz19UkcXta9qJ-bdszHNili5KbZhUgeefSnKnk/edit?usp=sharing . Thus, if @simonster and @dstillman agree, we could certainly change to the AGPL licence for those 54 translators.
Contributions by me and @simonster can certainly be considered to be under the AGPL.
Okay, that is good to know. AFAIK there are two versions of the AGPL licence statement:
I use at the moment more often the first version, but I forgot if there is any reason for that. Any preference which version we should use?
@dstillman Would you be able to say the same thing for contributions by @stakats and indeed any other CHNM employee's contributions (thinking mainly of Michael Berkowitz)?
For reference, CHNM employees who worked on the project are listed here: https://www.zotero.org/support/credits_and_acknowledgments
Yes.
It was mentioned in this thread to re-licence the ACM translator to AGPL. I found a total of 111 result with a General GPL licence. Should we try to change all translators to AGPL? This is possible if the creator(s) accept to do so.
Here is an uncomplete list:
Note, there might be more than one contributors mentioned.