Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

To quote you: "If there is a line that gets crossed, it can be dealt with, or even turned into a teaching moment so long as it wasn't too egregious." A code of conduct in many ways is a commitment by the organizer that that's what will happen, even if it'd be more convenient to ignore a problem and avoid confrontation, or if they'd be tempted to treat some people differently. A commitment they can be held to by attendees.

In the same way, for the organizer, it provides something to follow when making a decision, and to point to to justify their decisions when challenged. Something that amounts to "I'll kick people out if they break those rules" is easier to accept than "I'll kick people out when I want to" (even if the latter is often the organizers right from a legal POV too).

If everyone "know[s] the difference between right and wrong, welcome and unwelcome", a Code of Conduct is redundant (which also means one existing shouldn't cause no problems, and when it does the ideas about whats right or wrong typically weren't as common as expected). But experience shows that this doesn't reliably survives contact with reality, and it's easy for issues to never get brought up or silenced because "surely we all are adults and nobody would really do something bad", where again the commitment part of a code of conduct comes into play.

It's always just a tool: It doesn't magically make problems go away, and I'm certainly not saying all code of conducts are perfect, fit the same for all groups or are always applied well.

Re "set of additional rules that are platitudes": So you don't have a problem with an organizer saying "If you misbehave I'll kick you out", but making it more explicit what counts as "misbehave" is a problem?



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: