User:NeoPhyte Rep/Stuff everyone knows and forgets anyway

From The_Open_Source_Way

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

Revision as of 21:40, 5 August 2010

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

  1. Embrace failure
  2. Communities require care and feeding to get started ...
  3. ... And communities need to be left to grow and evolve
  4. Remember what you learned in Kindergarten
    1. Per Robert Fulghum
    2. Four new virtues to live by
  5. Turn annoying newbies in to instant contributors with the power of To Document
  6. 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
  7. Take even more care to do all design and decisions in the open
  8. Use version control for your content as well as code - everyone watches the changes
  9. 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
  10. 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
  11. Seek consensus - use voting as a last resort
  12. Reassign your benevolent dictators while evolving toward a consensus-based democracy
  13. Do not forget to release early and release often
    1. Release early and release often is for more than just code
  14. Evolve with the growth of your audience and contributors
  15. Use a predictable schedule type and stick to it
  16. A good teacher is a good student - ask questions and put yourself in a position of being taught by others
Retrieved from "http://www.theopensourceway.org/wiki/User:NeoPhyte_Rep/Stuff_everyone_knows_and_forgets_anyway"
Personal tools