Merged with FeaturesInWikiSoftwareForFacilitatingConsensus
Participants
Wiki Features for Achieving Consensus
- Make the backing page (talk or whatever) a really an article in and of itself that explains why the page is the way it is (remove egos and signatures)
- Try branches so that someone could demo what it looks like ... add merge
- Choose your own adventure potentially (different versions/branches of the same page)
- Brainstorming tools - adding in tools to let people's ideas flow, making lists, etc.
- Signing vs not signing posts - conflict? Competition, personalisation, "ownership of comments", etc.
- "Communities of practise" - consensus, there's point in producing something
Creating Adult Content Policy Via ConsensusPolling
- Started polarized ("adult content is immoral, if we have it I need to leave the company vs. censorship is immoral if we ban it I'll have to leave the company")
- 30 out of 32 participants at YES on the policy (including the two most polarized individuals)
http://www.aboutus.org/index.php?title=AdultContentPolicy&oldid=6603536
- Keys
- One document ... like a bus with different drivers over time (wanders around but we arrive together)
- Not Yet ... responsibility to articulate what it would take to get to yes (most efficient to just edit the policy)
- YES ... responsibility to help Not Yet folks articulate their concerns