we've talked about RFCs for Perl 6 features and so on. Perhaps we should come up with a something similar to PEP: http://python.sourceforge.net/peps/ notice the following features of a PEP: * there is a human who "owns" the proposal. that is, someone has taken responsibilty for it * they are very well written, mostly, with good descriptions of the problem * they have a status * there is a PEP editor who coordinates it all for a librarian perspective, not a technical merit perspective i see several positive (social) points about such a system: * apart from the black hole of a mailing list, a proposal, no matter its merit or status, can easily be accessed without wading through the drudge of irrelevant material. this should make such ideas more accessible to the community that p5p may have shut out. * proposals have a contact address where the author can receive feedback, and, as a result of that, update the proposal. this reinforces the mentoring goal of the new development process. * proposals can be assigned to working groups once they have an identity. if this sort of thing seems like a good idea to the community, and i'm not stepping into someone else's area of responsibility, i would volunteer to develop a system for use by Perl 6. my only requirement is that the appropriate person (Nat?) bless this way of doing things. when that happens, i can have something out for the community very quickly, in some form, so that the community can start participating as well. again - implementation issues aside, should i go ahead with this? (we can always make changes to the process later, but the longer we wait, the more we potentially lose in participation) -- brian d foy <brian@smithrenaud.com> Director of Technology, Smith Renaud, Inc. 875 Avenue of the Americas, 2510, New York, NY 10001 V: (212) 239-8985Thread Next