I think this is a great idea, it would be a good exercise to go through the existing ideas that are slated and clean them up in a clear well reasoned way. the limited amount in the queue at any one point in time is probably a good idea as well...force the asking of the tough questions and whatnot..
any idea how the resolution process will go? part of the problem now is that things just get kicked up on the mailing list and then disappear down on the list to atrophy. should there be an attempt to clear one or two MEPs a week? :) jesse On 5/15/06, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
Jason van Zyl wrote: > Hi, > > I was just looking at the wiki for the 2.1 design stuff and was > wondering if we could use a common format for each issue? I was > thinking that we may borrow from a Pattern Language and for each issue > have a Context, Problem, Solution, and maybe Implementation Details. > So for something like having selectable project builders based on version: Not sure if it's apropriate for us, but Python has a similar mechanism called Python Enhancement Proposals (PEPs)[1]. They don't have the same layout for all the requests, but they have a set of states for each proposal. I think this is a process that should outlive Maven 2.1 and should cover all parts of The Maven Project (where Maven the Tool is one sub-project). Just might be worth taking a look at for ideas. [1]: http://www.python.org/dev/peps/ -- Trygve --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
-- jesse mcconnell jesseDOTmcconnellATgmailDOTcom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
