Hi, Responding to Trygve and Kenney from here (beaver suffered an outtage).
Just looking at the PEPs (http://www.python.org/dev/peps/) and looks like a good idea. They have templates and my argument for the same format is the historical success of couching problems a la The Pattern Language as it has been successful in architecture and in software development (Design Patterns). We could have a template for improvements to make it easy to add enhancements requests. But whatever the format the design/enhancement takes I think the queue is more important here. The form of the request can adapt but making everyone focus on the issues, the format can adapt to what becomes most useful. I just use A Pattern Language as it is a successful precedent to follow. I agree that whatever we come up be applied to all the projects. As far as being able to edit designs is good, it's just the focus is on the issues in the queue. As far as implementation I think a wiki page pointing to the five issues in the queue would be fine. Would be nice to have nice linking between doco and issues generated from design ideas but JIRA/Confluence are just too crappy to try and implement this without crying. I think a simple list is fine, when you've had your issue resolved edit the list and take it out and let someone else add one. I think we can integrate the categories that we have on the design issues page, and there is still a disconnect between what's in the wiki and what's in JIRA. So hopefully there will be some more feedback and I will start modifying what's there and try to move toward something we can use for next week. I think just the queue is a good idea. BTW, a bunch of us are getting together in LA next week to discuss some design issues so if anyone is interested in joining us (myself, brett, john, jesse, carlos, joakime) you are most welcome. We'll have whiteboards, lots of ideas and we'll feed anyone who shows up :-) jason.
