Paul at 23:32, 7 September 2010

2010-09-07T23:32:57Z

Paul: New page: I think we need to create a mission statement. I also think we need to lay out some ground rules prior to providing access. http://opengeodata.org/enough-is-enough-disinfecting-osm-from-p...

2010-08-17T22:51:00Z

New page: I think we need to create a mission statement. I also think we need to lay out some ground rules prior to providing access. http://opengeodata.org/enough-is-enough-disinfecting-osm-from-p...

New page

I think we need to create a mission statement.

I also think we need to lay out some ground rules prior to providing access.
http://opengeodata.org/enough-is-enough-disinfecting-osm-from-poison?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Opengeodata+%28OpenGeoData%29

Summary of the poisonous people talk:

comprehension - understand the problem of poisonous people
*you need to protect the attention focus of community - limited amount of time
*poisonous people
*distract
*emotionally drain
*cause needless infighting
*slow you down
*either on purpose on by accident

fortification - protect project from poisonous people
*in a project you need politeness, respect, humility, trust
*have a mission, with examples
*have a scope, limit the mission
*do not let people reopen old discussions
*don't reply to _every_ message in a thread, summarise
*poisnous people derail discussion:
"it's a technique that poisonous people can use to derail a consensus-based
community from actually achieving consensus. You have this noisy minority
make a lot of noise and people look and say 'oh wow there is no agreement
on this' and if you look carefull the 'no agreement' comes from one person
while seven or eight people actually agree"
*document your projects history for future use to point people to
*have code collaboration guidelines
*email review, reasonably sized patches
*increase the bus factor so if someone drops out, others can take over
*have well defined processes for
*releasing software
*test / release cycles
*admitting new core people
*voting is a last resort in a healthy community
*everything else should be tried before a vote

identification - who are the poisonous people?
*it's usually obvious who will suck and drain your time
*usually use silly nicknames
*use CAPITAL LETTERS, !!!?!?!one!!, WTFLOLOMG
*hostility, demands help, blackmail, rile people deliberately
*accusations of conspiracy
*conceit, refuse to acknowledge arguments
*sweeping claims, reopen topics continuously
*lack of cooperation

disinfection - removing the poisonous people
*assess the damage
*how are they affecting your attention and focus?
*are they distracting / paralysing the project?
_dont_
*feed the troll
*give jerks a purpose/purchase
*get emotional (stick to the facts)
_do_
*pay attention to newcomers, even if annoying
*look for the fact under the emotion
*extract real bug report / action
*know when to give up and ignore
*know when to boot from community

@@ Line 1: / Line 1: @@
 I think we need to create a mission statement.
 I also think we need to lay out some ground rules prior to providing access.
-http://opengeodata.org/enough-is-enough-disinfecting-osm-from-poison?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Opengeodata+%28OpenGeoData%29
+[http://opengeodata.org/enough-is-enough-disinfecting-osm-from-poison?utm_source=feedburner&utm_medium=feed&utm_campaign=Feed%3A+Opengeodata+%28OpenGeoData%29 See this]
 Summary of the poisonous people talk:

User talk:Paul - Revision history

Paul at 23:32, 7 September 2010

Paul: New page: I think we need to create a mission statement. I also think we need to lay out some ground rules prior to providing access. http://opengeodata.org/enough-is-enough-disinfecting-osm-from-p...