Since now, I’ll post some extracts from the nice “The Cathedral & the Bazaar”, the book by ESR which describes the differences between the development process of open and close software.

The diffences derive from opposing assumptions about the nature of debugging. Open way states “given enough eyeballs, all bugs are shallow”.

Linus’ style was release early&often, delegate as possible, be open until promiscuity.

1. Every good work of software starts by scratching a developer’s personal itch.
This explain the average good quality of floss.

2. Good programmers know what to write. Great ones know what to rewrite (and reuse).
Their constructive laziness knows that you get an A for your result, not for your effort.

3. “Plan to throw one [software] away; you will, anyhow.”
You’ll usually learn how to write a software AFTER you’ve finished it: so be ready to start again.

4. If you have the right attitude, interesting problems will find you.
and
5. When you lose interest in a program, your last duty to it is to hand it off to a competent successor.

After you’ve been involved in a floss, you could become its maintainer; and when your interest ends, you must find an heir