News for hackers. Stuff that matters.
Re:Introducing GitHub Community Guidelines by orblivion on Tuesday October 18, 2016 @09:42PM (#12740321)
By and large I agree that none of these things have any relevance to software development. (And Github shouldn't be forced to tolerate anything, not sure where that came from.) But a couple edge cases may be relevant:

> Hate speech and discrimination

Gender as an entry field. People have a variety of views on this one. I imagine that the prevailing view is going to call certain other views "hate speech" no matter how politely expressed. It is up to Github if they want to take this stance on it, but it is understandably going to get them called the "PC Police" should it ever come up.

> Sexually explicit content

I understand not bringing this into discussions for no reason. But what if someone is developing a Leisure Suit Larry clone? I think implementing a NSFW warning for viewing a project is perfectly reasonable by almost anybody's standards. But disallowing it entirely will preclude such projects from Github. But again, totally understandable if Github decides that it's not the place for such things.

Re:Introducing GitHub Community Guidelines by qb45 on Wednesday October 19, 2016 @05:21AM (#12742316)
Add:

> Active malware or exploits

Metasploit has been hosted at GitHub for few years and they never seemed to have a problem with that. Are they going to kick them now? Why should they care?

Re:Introducing GitHub Community Guidelines by drvdevd on Saturday October 22, 2016 @03:05AM (#12767611)
This in particular angers me because it's so broad IMO and antithetical to open source and security research. This smells like political pressure and censorship. Like the beginning of the end for GitHub...