I was reading this article and was pondering how you would create the ultimate distributed source management system for a project like Linux.

I was thinking of using personal sites (every programmer has one) to post patches and create a community driven development proces.

Some things to consider:
- Everybody publishes the patches he/she applied to his own code-base
- Use md5 for identifying patches/files/packages/versions etc.
- Highly regarder developers get a higher pagerank so google can be used for search
- Mayority rules, but you (or a group) can do whatever
- Distributions also have their own site with patches
- Differences can stay
- Survival of the fittest
- Now if only you could compile linux faster, then everyone could have its own version of linux (you could apply patches early).
- Patches should be signed
- Public key should be present on site
- No ultimate leader, no select few who can commit changes
- Every patch/file/package/version should have a name (and a number?)
- Rss could be deployed
- The system should work with any webserver (iis/apache) and maybe even with services like blogger.com
- The files function like .torrent files, and have a reference to the authors site