On Wed, 15 May 2002, Rasmus Lerdorf wrote: > Personally I'd rather see more effort put towards fixing tomorrow's code > than dwelling on code and processes from years ago.
One of the important roles that Apache plays, apart from being a damned fine product, is as a model of how open software development is *supposed* to work. I think that folks inside the Apache projects are often unaware of that aspect of things. Explaining how Apache works (the project, not the product) is a useful thing for those that are doing their own unrelated development projects. I am a writer and trainer, not a C programmer. Time that I spend on a history project, and on a documentation project, in no way detracts from the fine work that others are doing on the software development, as I don't have a whole lot to offer in that arena anyway. What we're trying to do here is *certainly* not to detract from ongoing work, but to offer the outsider a glimpse of what works, and what doesn't, in what is arguably one of the 3 or 4 most important open software developemnt projects in existence. -- Rich Bowen - [EMAIL PROTECTED] http://kenya.rcbowen.com/
