Slashdot Mirror
Discipline in Open Source Projects?
An anonymous reader asks: "I've recently been elected (with another project member) to lead an open source project that we helped start several years ago. One of our goals as project leads is to implement some way to discipline project members who are disruptive to the project. In the past, the project has been slowed by flames, trolls, and even filibustering. Everyone says they want to work together, but some refuse to accept majority opinion. This passive-aggressiveness, coupled with growing despair on the part of other members, would have caused the project to dissolve if a vote had not taken place to elect new leadership (which the project has been lacking for some time). As co-leads we want the project to continue and grow, and we welcome all opinions, but how can disruptive members be told 'enough is enough'? We've read Ubuntu's Code of Conduct, but how can it or something similar be enforced?"
http://video.google.com/videoplay?docid=-421601196 1522818645
we speak the way we breathe --Fugazi
You can't be sued for libel if it's true.
So don't post the text itself, post links to an archive, preferrably controlled by some completely independent party (say, Google for newsgroups).
Look at this video: http://video.google.nl/videoplay?docid=-4216011961 522818645.
It's a video of a talk given by two guys from Google who founded the Subversion project. The video is titled "How to protect your Open Source project from poisonous people".
Daniel
Carpe Diem
Theo De Raadt lost commit privileges to NetBSD. Paludis isn't quite another operating system.
I can throw myself at the ground, and miss.