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