17
Managing an Open Source Community

Managing an Open Source Community

Embed Size (px)

DESCRIPTION

 

Citation preview

Page 1: Managing an Open Source Community

Managing an Open Source Community

Page 2: Managing an Open Source Community

Being Managed by an

Open Source Community

Page 3: Managing an Open Source Community
Page 4: Managing an Open Source Community
Page 5: Managing an Open Source Community

20,000downloads

a day

Page 6: Managing an Open Source Community

7 Rules

Page 7: Managing an Open Source Community

1. Lead by example

Page 8: Managing an Open Source Community

2. Get offthe computer

Page 9: Managing an Open Source Community

3. Transparency

Page 10: Managing an Open Source Community

4. Build consensus(even whenyou’re right)

Page 11: Managing an Open Source Community

5. You’re notright.

Page 12: Managing an Open Source Community

6. Centralizecommunity

Page 13: Managing an Open Source Community

7. Open Source haslittle to do with

the license.

Page 14: Managing an Open Source Community

8. (bonus!)But use the

GPL

Page 15: Managing an Open Source Community

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.

Page 16: Managing an Open Source Community
Page 17: Managing an Open Source Community

[email protected]

http://ma.tt/