Re: Learning from Python: PEPping the PHP Development

On Fri, 27 Aug 2004, Sebastian Bergmann wrote: > Rasmus Lerdorf wrote: > > 1. Submit proposal to web app > > 2. web app sends it to internals@ or some other relevant list > > 3. Replies to that email automatically get picked up by the web app > > 4. Alternatively, you can add comments via the web app which would > > also get bounced to the relevant mailing list > > Then again, why use a webapp at all? AFAICS, Python uses a special > directory in CVS [1] to which the PEPs are added. Well, the same could be said of the bug report system. I think having a more accessible interface is the entire point here. A single place for tracking features and proposals and making it easier to later go back and review the discussion. Right now it becomes a treasure hunt through the mailing list archives that we don't have any control over to begin with and it really is quite a hassle to go spelunking for the reasons things were done the way they were done. It would guide people to how to actually submit an idea in a structured way, and more importantly, it would hopefully stop people from suggesting the same stupid feature that someone else had already suggested and was shot down. I suppose it ends up being a filtered and structured view of the development mailing list where general chit-chat is filtered out and each tracked thread is about a specific feature or enhancement. This sort of email tie-in has been on my wishlist for the bug system for years as well. Bugzilla does this quite well, but we never got around to adding it to ours. I'll have a look at this CLEW system and see if I can come up with a prototype. -Rasmus