Re:New GitHub Terms of Service require removing many open-so...
by cakeface on Wednesday March 01, 2017 @03:00PM
(#13767686)
Are you using a self hosted GitLab? I feel that GitLab would have the exact same issues that GitHub has. The TOS are just clarifying what is required to run a cloud source code repository. If they want to do things like index the code, run tests on it, fork it to other users, show it on their website, then they need certain permissions from the copyright holders of the code. These permissions are not special to github I don't feel. Anyone with the same set of features would require the same permissions.
Re:New GitHub Terms of Service require removing many open-so...
by kefka on Wednesday March 01, 2017 @03:10PM
(#13767790)
The contract states that I have to effectively grant them a BSD license for whatever I do there. Then open source licenses can stack on others' as I choose.
Nah. Not worth it. If I want it as GPL3, I expect them to comply with GPL3.
Re:New GitHub Terms of Service require removing many open-so...
by lauretas on Wednesday March 01, 2017 @03:01PM
(#13767692)
> I'll move on to things like GitLab or IPFS for transmitting projects I'm working on.
Or NotABug (https://notabug.org) which is a lot more friendlier toward open source projects. IPFS sounds good, I'd love to see something P2P in this space, but nothing P2P seems to be mature enough.
I still want to maintain a user purely for ownership of presence there. But I certainly won't use it.
I'll move on to things like GitLab or IPFS for transmitting projects I'm working on.