Is programming lame enough yet that we can get away from everything being done by hr and get back to doing cool things with weird people?
Heavy codes of conduct are unnecessary for open source projects
11–20 of 270 posts
Re: Heavy codes of conduct are unnecessary for open source projects
#12CoCs are one of the reasons why I choose to not contribute. I don't enjoy the risk of someone with an axe to grind to drag me into some absurd GitHub comments drama and feel justified by some generic wording on the CoC.
But could they not do the same without a CoC?
Humans should be able to interact politely in any setting and if they don't, the issue needs to be settled with good old human interaction anyways.
Re: Heavy codes of conduct are unnecessary for open source projects
#13The thing is that codes of conduct do not help honest actors “regulate” and deal with troublemakers. I used to organize meetups and I visited meetups organized by others who had code of conduct, and I just never understood what they were hoping to achieve with that. If someone behaves poorly, you can point at a document all you want, but it doesn’t help you deal that the problematic individual. A document that you pu…
Has it occurred to you that's actually exactly why they exist? :)
Re: Heavy codes of conduct are unnecessary for open source projects
#14No, CoCs - or rules in general - are not inherently bad. HN has some, which the moderators and the community enforce well, and it's generally one of the best platforms on the Internet for intelligent discussion.
Yes, heavy CoCs can be weaponized and abused, if there is little or no trust between the community and its leaders. But with or without a CoC, such a community will always be prone to such abuse. You think moderators need to establish a CoC to push their politics on people if they want? How does that even make sense? Why not just... do that, without a CoC?
Re: Heavy codes of conduct are unnecessary for open source projects
#15However, there's probably a cutoff point for core infrastructure where we should move away from having a single person in charge.
Re: Heavy codes of conduct are unnecessary for open source projects
#16> Participants are expected to be tolerant of opposing views.
If you can't tolerate that others will have different perspectives to you then it means you're likely to be a very difficult and inflexible person to work with.
Re: Heavy codes of conduct are unnecessary for open source projects
#17The thing is that codes of conduct do not help honest actors “regulate” and deal with troublemakers. I used to organize meetups and I visited meetups organized by others who had code of conduct, and I just never understood what they were hoping to achieve with that. If someone behaves poorly, you can point at a document all you want, but it doesn’t help you deal that the problematic individual. A document that you pu…
Re: Heavy codes of conduct are unnecessary for open source projects
#18CoCs are one of the reasons why I choose to not contribute. I don't enjoy the risk of someone with an axe to grind to drag me into some absurd GitHub comments drama and feel justified by some generic wording on the CoC.
But could they not do the same without a CoC?
Re: Heavy codes of conduct are unnecessary for open source projects
#19What matters is that people are operating in good faith.
I would also say that IF you have been accepted as a member of a community then you and your feelings must matter to that community unless and until you are ejected from the community. There needs to be a system for accepting and expelling people, and that system should rest on the judgment of people that the community has selected as trustworthy (until and unless those people are expelled).
Re: Heavy codes of conduct are unnecessary for open source projects
#20I feel that having a detailed COC, while a very good sentiment in theory, in practice must bring about people who will try their best to skirt around the edge of COC and make trouble for the maintainers - who I expect want to stay "nice", but they're forced to act harshly in the end anyway.