News for hackers. Stuff that matters.
Re:Writing Open Source Software? Make Sure You Know Your Cop... by Nursie on Tuesday March 26, 2013 @01:58PM (#5444965)
(IANAL)

Git isn't my primary source control solution -- edit: corrected in view of useful information below --

If you accept pull requests and pull data into your repo from other folks without a asking them to assign copyright or sign a very open CLA then that means the copyright is now joint.

The ramifications of this tend to be that you cannot re-license the code without their permission, unless the original license says you can.

Example - your project is GPL, you accept submissions from a bunch of other people. You decide you want to release a closed-source binary-only commercially-supported extra-special version with plugins and hotsauce. You can't unless you get permission from everyone that's contributed to the project, because the rights you have to their submissions are governed by the GPL. With copyright assignment, you as the now sole copyright holder could do this.

Ramifications will vary by license and by what you want to do.

Re:Writing Open Source Software? Make Sure You Know Your Cop... by tholmes on Tuesday March 26, 2013 @02:05PM (#5445009)
You have the right idea about pull but you're mixing up pull and pull request. Pull is a git verb that means to get code from another location. A pull request is asking someone else to get my changes.

So for an example, if you found a bug in some open source software you used you could make a change in the code that fixed it and then file a pull request with the original author of the software. This asks them to incorporate your changes.

Re:Writing Open Source Software? Make Sure You Know Your Cop... by Nursie on Tuesday March 26, 2013 @02:15PM (#5445072)
Thanks, wasn't sure on that point! I assumed a pull request was someone asking you/your server if they could pull data from it, not requesting you/your server pull data from elsewhere.

Now I know.

Re:Writing Open Source Software? Make Sure You Know Your Cop... by zobzu on Tuesday March 26, 2013 @02:16PM (#5445078)
thats why the licenses recommend to put the license on top of EVERY SINGLE FILE. Failing to do so, is, well, not a good idea.

The pull request will then either contain a join copyright (then only THIS file has a joint copyright), either no change to copyright (explicitly assigning the copyright to you alone)

that's if the copyright goes to <your name, email>, not "et al", obviously