News for hackers. Stuff that matters.
Re:New GitHub Terms of Service require removing many open-so... by smilekzs on Wednesday March 01, 2017 @02:57PM (#13767658)
> there was a review phase, but my reviews pointing out the problems were not answered, and, while the language is somewhat changed from the draft, they became effective immediately

I find this disturbing.

Also, although extremely unlikely, I would imagine Github finally panicking upon a large exodus of high-profile FOSS projects.

Re:New GitHub Terms of Service require removing many open-so... by Karunamon on Wednesday March 01, 2017 @03:02PM (#13767702)
It's sad, but given the (positive, don't get me wrong!) response to the Dear Github letter from a while back, it seems that mass outrage is the only thing the company understands.

Most companies are allergic to lawyers. As in, they'd rather avoid the issue outright and go elsewhere if a hint of a legal question comes up. The fact that they didn't bother floating this change by the greater community at large does not give me the warm fuzzies that they learned their lesson.

Re:New GitHub Terms of Service require removing many open-so... by mirabilos on Wednesday March 01, 2017 @10:10PM (#13771094)
They actually had a review period, and did some good changes.

But then, they took a week to look at the reviews (ostensibly; I, as well as others, never got any response to them), went and made some minor changes (which were not enough to address the problems at all) AND BROUGHT THE CHANGED DOCUMENT INTO PRODUCTION RIGHT ON THE NEXT DAY, without any further review or warning. That’s like bad.