The Cathedral and the Bazaar

The Cathedral and the Bazaar

1. The mail must get through

   • Every good work of software starts by scratching a developer
     • Open source project in the bazaar style
     • Help to understand what the Linux community does
   • Good programmers know what to write, Great ones know what to rewrite
     • Presence of multiple support protocols
   • The right attitude
     • You will encounter interesting problems
     • Under the attitude of Carl Harris
   • When you lose interest in a program
     • your last duty is to hand it over to a competent successor
   • Plan to throw one away; you will, anyhow
     • The Problem is not understood until after the solution is implemented
     • Encourage the sharing of codes

2. The importance of having users

   • Trating your users as co-developers
     • Rapid code improvement
     • Efective debugging
     • Ideas and prototype modes
   • Emerges effective hackers
     • Shortens debugging time
       • The users will diagnose problems and suggest solutions

3. Release early

   • Beta-testers and quickly solutions
     • All errors are superficial
     • The "Law of Linus" arises
   • Release early and listen to your customers
     • Conservative and simplifying design
     • keeps its hackers / users constantly stimulated and rewarded
   • Users will only see as few errors as possible

4. When is a rose not a rose

   • Smart data estructure and climb code works a lot better
     • I released early and often
     • Add to it everyone who contacted me about fetchmail
     • I listened to my beta testers
     • I sent chatty announcements to the beta list whenever I released, encouraging people to participate
   • Beta-testers are the most valuable resource
     • The success of fetchmail