[1] https://np.reddit.com/r/programming/comments/3e5c6f/why_the_... [2] https://news.ycombinator.com/item?id=9966118
[1] https://np.reddit.com/r/programming/comments/3e5c6f/why_the_... [2] https://news.ycombinator.com/item?id=9966118
And Github, like most other providers, have catch-all clauses in the ToS. This one, perhaps:
> We may, but have no obligation to, remove Content and Accounts containing Content that we determine in our sole discretion are unlawful, offensive, threatening, libelous, defamatory, pornographic, obscene or otherwise objectionable or violates any party's intellectual property or these Terms of Service.
I suppose my point is that if you're a business you shouldn't rely on Github etc.
What I find unsettling is that what they could consider "objectionable" is wide open and resolution of raised issues is expected so rapidly. Silly story time..
A developer in MajorCorp leaves a code comment (which is eventually committed) saying "// TODO: Fix this later, GitHub is down again, GitHub is trash!". GitHub could fairly request its removal as it is likely to be objectionable to them.
However, the main contact on the account is away at a conference and gets to their email a couple of days later. Is their repo or even their entire account now toast? How much would someone want to bet against that?
This is a farfetched contrived story, but now there's a demonstrated (again, assuming the screenshot is legit) attempt to enforce this clause and evidence of "24 hours" being the timeframe allowed for resolution, the tiny risk of such an outcome is going to hit sentiment and get legal departments twitching.
(My personal suspicion is paying and enterprise users will not receive such threats, but in the above example I'm being idealistic and assuming everyone gets equal treatment.)
(Personally I can't understand hosting your source code offsite in the first place if you're a business and not an open source project, but it seems to be popular)
I agree that the ToS clause is very broad, and that (if the email is real) that the timeframe is short.
But that seems to be standard across different providers.
For example, Google will close several types of account without warning.
I'm not willing to say it "will fall soon", but it has substantially damaged my opinion of GitHub as a company, and has diminished my trust in the integrity of their service as it serves the needs of open-source communities.
I suspect what you mean is that you are actively patronizing businesses who reinforce your current political beliefs; I doubt very much that you are patronizing businesses who engage in censorship which runs contrary to your political beliefs out of some idealistic respect for their courage to take a stand. And that's fine - we all naturally tend to support those we agree with, and not support those we disagree with - but framing it as admiration of the will to censor is just almost certainly spurious.
And what you suspect is incorrect. This decision is largely driven by finding them more pleasant environments rather than my current political beliefs. If that were the case, I wouldn't be patronizing GitHub. Nor would I have had had lunch at Chick-fil-a.
It's understandable that they're concerned about how the "feminist community" sees them. They're this generation's SourceForge and "feminist" backed shitstorms against them are likely posing a considerable risk to their brand. Just look at Gittip[2] (now Gratipay)[3].
[0]: http://geekfeminism.wikia.com/wiki/Category:GitHub
[1]: https://news.ycombinator.com/item?id=2605739
[2]: http://geekfeminism.wikia.com/wiki/Gittip_crisis
[3]: Gratipay lives and they had to change business models for unrelated reasons but I'm fairly certain the "crisis" has an impact on their brand and growth even if it didn't outright kill them.
You're right the actual GitHub interface is not as amazing as it is often heralded. I've always thought the issue tracker was a joke, for instance.
I speak this as someone who managed developers at a company that was still using CVS. And yes, we discussed moving to git every so often, but it always was lower on my priorities than new features.
The alternative would have to aggressively undercut gitHub's enterprise sales model while competing with gitHub's uptime.
Customers aren't going anywhere.