The document outlines 7 rules for managing an open source community, including leading by example, getting off the computer to interact with the community in person, being transparent, building consensus even when you think you're right, recognizing you may not always be right, centralizing the community, and that open source is about more than just the license but also includes freedoms like adapting and improving the program. It also mentions the project has 20,000 downloads per day and provides contact information for the author.

1. Managing an Open Source Community

2. Being Managed by an Open Source Community Open Source Community Open Source Community

5. 20,000 downloads a day

6. 7 Rules

7. 1. Lead by example

8. 2. Get off the computer

9. 3. Transparency

10. 4. Build consensus (even when you’re right)

11. 5. You’re not right.

12. 6. Centralize community

13. 7. Open Source has little to do with the license.

14. 8. (bonus!) But use the GPL

15. 0. The freedom to run the program, for any purpose. 1. The freedom to study how the program works, and adapt it to your needs. 2. The freedom to redistribute copies so you can help your neighbor. 3. The freedom to improve the program, and release your improvements to the public, so that the whole community benefits.

17. [email_address] http://ma.tt / /