On 2005.02.06, Torben Brosten <[EMAIL PROTECTED]> wrote: > This *is* a suggestion for cooperative development of two versions in > the interests of AOL and the community, perhaps with oversight by a > steering committee if you like. > > As documentation develops that answers Andrew Piskorski's (and > others') questions on "core server design docs", there will likely be > a natural reaction to try changing a few things --see if performance > can be increased in some way or applied in a new way. It will take > time and people interested in trying out an experimental version to > see what works and what does not. Why not create a version that > includes these variations?
Because it takes precious limited time and effort away from the mainline codebase. If we had so many active developers and contributors that a few of us could just go off in the weeds and play with "wouldn't it be cool if" type of ideas, I'd be the first to suggest this kind of a code-fork or branching pattern, to keep them from mucking with the mainline code that everyone else has to deal with. But, we don't. Yet. How do we get there? -- Dossy -- Dossy Shiobara mail: [EMAIL PROTECTED] Panoptic Computer Network web: http://www.panoptic.com/ "He realized the fastest way to change is to laugh at your own folly -- then you can let go and quickly move on." (p. 70) -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
