"Only permanent resolutions (such as bans) may be appealed." - why?
New FreeBSD Code of Conduct
31–40 of 156 posts
Re: New FreeBSD Code of Conduct
#32> Comments that reinforce systemic oppression related to gender, gender identity and expression, sexual orientation, disability, mental illness, neurodiversity, physical appearance, body size, age, race, or religion. So, there's a lot of "politicking" going on back and forth over this, but I'd like to suggest a specific problem: by attempting to formalize what used to be intuition, you're opening the door for people…
I think a lot of potential technicalities like that are handled pretty well by this paragraph at the start:
> This document is not an exhaustive list of things that you should not do. Rather, consider it a guide to make it easier to enrich all of us and the technical communities in which we participate.
Re: New FreeBSD Code of Conduct
#33> Comments that reinforce systemic oppression related to gender, gender identity and expression, sexual orientation, disability, mental illness, neurodiversity, physical appearance, body size, age, race, or religion. So, there's a lot of "politicking" going on back and forth over this, but I'd like to suggest a specific problem: by attempting to formalize what used to be intuition, you're opening the door for people…
Possibly. But the benefits outweigh the marginal scenario you are envisioning. I again return to the example of HN, which has higher standards of conversation than many other boards, due in part to strong moderating guidelines: https://news.ycombinator.com/newsguidelines.html
To draw a parallel, do you think HN would be more successful if it relied on "intuition" for norms of discussion?
Re: New FreeBSD Code of Conduct
#34Re: New FreeBSD Code of Conduct
#35> Comments that reinforce systemic oppression related to gender, gender identity and expression, sexual orientation, disability, mental illness, neurodiversity, physical appearance, body size, age, race, or religion. So, there's a lot of "politicking" going on back and forth over this, but I'd like to suggest a specific problem: by attempting to formalize what used to be intuition, you're opening the door for people…
Your example is not a 'legal argument', nor is the CoC a law. Lots of organizations have rules that don't have the formality or rigor of laws and they have little trouble interpreting them, applying them and enforcing them in letter and spirit. It's pretty much a non-problem.
Re: New FreeBSD Code of Conduct
#36> Comments that reinforce systemic oppression related to gender, gender identity and expression, sexual orientation, disability, mental illness, neurodiversity, physical appearance, body size, age, race, or religion. So, there's a lot of "politicking" going on back and forth over this, but I'd like to suggest a specific problem: by attempting to formalize what used to be intuition, you're opening the door for people…
By that reasoning, we should never have rules, because any rule will create the possibility of people trying to lawyer out of the rules.
The cost of rules is a court system and the lawyers to argue in it. In the end, introducing rules can lead to more time spent on strife than was spent before the rules, because of this overhead.
If you try to avoid this by interpreting the rules according to the present and changing intuitions of the project leaders, then you haven't really changed much from before.
Re: New FreeBSD Code of Conduct
#37"Only permanent resolutions (such as bans) may be appealed." - why?
Because in communities that require a lot of moderation and CoCks the people who need the protection from uncomfortable content are the mods themselves. You can't get protection from uncomfortable things if you have to review appeals.
Re: New FreeBSD Code of Conduct
#38I've always read that whitelisting is more preferable to blacklisting. So wouldn't a rule like "FreeBSD projects' communication media are strictly restricted to technical and philosophical discussions related to the projects themselves, and all use of language for branding and naming must be politically and socially neutral and not-offensive" would be actually better than a list of what not to do? The law has lots of lists, and quite often we find out that those lists were a bit too short, and things like loopholes happen.
Re: New FreeBSD Code of Conduct
#39Earlier quoted context omitted.
Which part exactly do you find funny and why?
The part where they have to write a CoC to please some groups, and disregard a thing called "common sense" which always existed inside the community. Thus making this a joke.
Ignoring the text of the rules, which are mostly an elaboration on "don't be an asshole", there is also a very important piece -- that there is a reporting and response procedure. In many groups, where there hasn't been a need for this function, when the need arises, nobody knows what to do, and the issue tends to get rapidly worse while people figure out how to handle it.
Re: New FreeBSD Code of Conduct
#40After using FreeBSD since 3.4, I am done with it. This is an utter joke.
What's changed that these CoCs are now supposedly neccessary where they previously weren't?