Wow, Macrochip on BCT posted this video on "how open source projects survive poisonous people" and I just thought this was one of the most intelligent and probably overlooked points:
Document your mistakes.
You know how the amendments to the constitution are never simply removed but rather
repealed. They stay there for all eternity so that we can see the mistakes of the past. Hopefully to keep from making them again in the future
The next point they make, which I can totally see happening - especially with our new project proposal system, is what they call "power plant code" meaning, people that go off to write code that is supposed to be inserted into the project, and "deliver" it in one huge chunk. Then nobody has the time to review that code, and it gets committed with all it's flaws. We haven't talked about how all these projects are going to be integrated at all, we've just been building a way to pay people to work on DASH. We
WILL have to create a chain of command, a review board,
something to handle incoming code. Once the "public" who really don't know anything about implementation, vote to pay for a feature, we have to have staff that will review the code and direction, etc... that the project is taking, and that will mean that the project will have to have
ongoing review, not one time dump that no one has the time to review. Sure, if the people want a feature, they vote to pay for it, etc... They must get it, but someone (Core Developers as they're being paid) will have to be there to manage and integrate these projects. Maybe we have to hire extra core developers who enjoy and are good at code review.
I think this video is so good, as it doesn't just cover poisonous people, but also on how to run a group of talent and keep them productive. I think it may be worth it to watch it every once in a while, just to catch all the good ideas