User:NeoPhyte Rep/Stuff everyone knows and forgets anyway

From The_Open_Source_Way

< User:NeoPhyte Rep(Difference between revisions)
Jump to: navigation, search
(Copy current structure of existing page)
(Structured Communities)
 
(One intermediate revision not shown)
Line 1: Line 1:
-
1 Embrace failure
+
This is an edit of the list on [[Stuff everyone knows and forgets anyway]]
-
<br />
+
# Embrace failure
-
2 Communities require care and feeding to get started ...
+
# Communities
-
<br />
+
## require care and feeding to get started
-
3 ... And communities need to be left to grow and evolve
+
## need to be left to grow and evolve
-
<br />
+
# Remember what you learned in Kindergarten
-
4 Remember what you learned in Kindergarten
+
## Per Robert Fulghum
-
<br />
+
## Four new virtues to live by
-
4.1 Four new virtues to live by
+
# Turn annoying newbies in to instant contributors with the power of To Document
-
<br />
+
# Take extra extra extra care to have all discussions in the open
-
5 Turn annoying newbies in to instant contributors with the power of To Document
+
## Radically visible meetings at all times
-
<br />
+
## No decision point is too small to pre-announce to a mailing list
-
6 Take extra extra extra care to have all discussions in the open
+
## It's okay to be disappointed but never okay to be surprised
-
<br />
+
## How to let a mailing list run itself
-
6.1 Radically visible meetings at all times
+
# Take even more care to do all design and decisions in the open
-
<br />
+
# Use version control for your content as well as code - everyone watches the changes
-
6.2 No decision point is too small to pre-announce to a mailing list
+
# Choose open tools that can be extended
-
<br />
+
## Make sure everyone has an equal and clear method for access to write-commit to open tools
-
6.3 It's okay to be disappointed but never okay to be surprised
+
## Tie this together with open content
-
<br />
+
# Focus on healthy and open community interaction
-
6.4 How to let a mailing list run itself
+
## Make governance as clear as possible
-
<br />
+
## Use your lawyers well while avoiding too much legalese
-
7 Take even more care to do all design and decisions in the open
+
## Do not let poisonous people bog down the community
-
<br />
+
## Communicators need to communicate - do not let liaisons go silent
-
8 Use version control for your content as well as code - everyone watches the changes
+
## Disable poisonous communication
-
<br />
+
# Seek consensus - use voting as a last resort
-
9 Choose open tools that can be extended
+
# Reassign your benevolent dictators while evolving toward a consensus-based democracy
-
<br />
+
# Do not forget to release early and release often
-
9.1 Make sure everyone has an equal and clear method for access to write-commit to open tools
+
## Release early and release often is for more than just code
-
<br />
+
# Evolve with the growth of your audience and contributors
-
9.2 Tie this together with open content
+
# Use a predictable schedule type and stick to it
-
<br />
+
# A good teacher is a good student - ask questions and put yourself in a position of being taught by others
-
10 Focus on healthy and open community interaction
+
-
<br />
+
-
10.1 Make governance as clear as possible
+
-
<br />
+
-
10.2 Use your lawyers well while avoiding too much legalese
+
-
<br />
+
-
10.3 Do not let poisonous people bog down the community
+
-
<br />
+
-
10.4 Communicators need to communicate - do not let liaisons go silent
+
-
<br />
+
-
10.5 Disable poisonous communication
+
-
<br />
+
-
11 Seek consensus - use voting as a last resort
+
-
<br />
+
-
12 Reassign your benevolent dictators while evolving toward a consensus-based democracy
+
-
<br />
+
-
13 Do not forget to release early and release often
+
-
<br />
+
-
13.1 Release early and release often is for more than just code
+
-
<br />
+
-
14 Evolve with the growth of your audience and contributors
+
-
<br />
+
-
15 Use a predictable schedule type and stick to it
+
-
<br />
+
-
16 A good teacher is a good student - ask questions and put yourself in a position of being taught by others
+

Latest revision as of 22:41, 5 August 2010

This is an edit of the list on Stuff everyone knows and forgets anyway

  1. Embrace failure
  2. Communities
    1. require care and feeding to get started
    2. need to be left to grow and evolve
  3. Remember what you learned in Kindergarten
    1. Per Robert Fulghum
    2. Four new virtues to live by
  4. Turn annoying newbies in to instant contributors with the power of To Document
  5. Take extra extra extra care to have all discussions in the open
    1. Radically visible meetings at all times
    2. No decision point is too small to pre-announce to a mailing list
    3. It's okay to be disappointed but never okay to be surprised
    4. How to let a mailing list run itself
  6. Take even more care to do all design and decisions in the open
  7. Use version control for your content as well as code - everyone watches the changes
  8. Choose open tools that can be extended
    1. Make sure everyone has an equal and clear method for access to write-commit to open tools
    2. Tie this together with open content
  9. Focus on healthy and open community interaction
    1. Make governance as clear as possible
    2. Use your lawyers well while avoiding too much legalese
    3. Do not let poisonous people bog down the community
    4. Communicators need to communicate - do not let liaisons go silent
    5. Disable poisonous communication
  10. Seek consensus - use voting as a last resort
  11. Reassign your benevolent dictators while evolving toward a consensus-based democracy
  12. Do not forget to release early and release often
    1. Release early and release often is for more than just code
  13. Evolve with the growth of your audience and contributors
  14. Use a predictable schedule type and stick to it
  15. A good teacher is a good student - ask questions and put yourself in a position of being taught by others
Personal tools