I can't see anything wrong with the Code of Conduct. Some people call it "toxic" and they are afraid of the "SWJs" taking over. This is only a problem if you try to loose focus on the quality of the work. Some argue that now that Linus realized how his communication is received sometimes, he will suddenly not be able anymore to tell people when shitty code is shitty. There are a billion ways to tell somebody their co…
And if you dare to question that there are more than two genders then good by.
Linux's new CoC is a piece of shit
21–25 of 25 posts
Re: Linux's new CoC is a piece of shit
#22Earlier quoted context omitted.
This is a silly statement. I'd be amazed if you somehow managed to question this and still make it related to the Linux kernel...
This is the problem with this covenant, anything you say personally in your own social networks will also be taken into account.
> This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
It's very specific. If you're representing the community, and you say something bigoted, then, yeah, that might be brought up. But that should be the case. No project wants its representatives doing stuff that reflects badly on the project or which creates a bad culture in the project community.
Besides, it's also just not a very good idea to post bigoted things, both in terms of making a better society and culture, and in terms of just following the Golden Rule and being nice to other people.
Re: Linux's new CoC is a piece of shit
#23Earlier quoted context omitted.
And if you dare to question that there are more than two genders then good by.
This is a silly statement. I'd be amazed if you somehow managed to question this and still make it related to the Linux kernel...
> The new Code of Conduct explicitly says discrimination and harassment on the basis of sex or gender is not allowed. One Linux Foundation Technical Advisory Board member who did not sign off on the patch is Ted Tso, who is a rape apologist:
Re: Linux's new CoC is a piece of shit
#24Earlier quoted context omitted.
This is the problem with this covenant, anything you say personally in your own social networks will also be taken into account.
That's not true. In fact, it's a specific misrepresentation of the CoC. Whoever planted that idea, did it in bad faith: > This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as…
This is the way of life for most now. If you say anything remotely offensive and it ends up online/traceable to you. You will loose your job and most, if not all other actual job possibilities.
Yes you may argue that one should never do that (and I certainly agree) however, everyone is human and we all make mistakes. So what happens when we as a society decide to totally condemn individuals for their mistakes without allowing them to learn from them in the first place? I would wager, probably something not so nice.
Re: Linux's new CoC is a piece of shit
#25In the opener the author seems to generally agree that toning down ad hominem conduct is a good thing: > He's stated that he'd tone down his language (no more calls to "retroactively abort" people and such. This is all good, and I support it. One of my greatest fears is having my patch/contrition to a FOSS project be publicly dissected and ridiculed. But his bullet point objections either contradict the above (transp…
The mentioned transphobia was never in the Opal project, it was a comment made outside the project, by a member, which would be outside the scope of a such CoC.
For point 4, I think the problem for the author, was that a maintainer won't have the possibility to say a patch is bad to avoid discriminating on 'technical ability'