Hi Justin, I very much like the QIP proposal my only concern is about its potential for endless discussion. I understand that the QIPs have timeframes but if discussion has not reached a satisfactory conclusion there is an option to defer. Would we have rules on how often we could defer a QIP before we had to stop and deal with the issue?
How are such difficulties addressed by the Gnome and Python projects? The proposal suggests to me that a QIP must first be approved before any code is written. I think that this would potentially be a bad move as ideas often need prototypes to either prove out the idea or to get community buy in. How would we address the need for a QIP to have some initial development work done in svn? Cheers Martin On 7 January 2011 16:35, Justin Ross <[email protected]> wrote: > I'm very much in favor of source control for draft as well as matriculated > QIPs. I've been thinking along the lines of having > > qpid/doc/qips/draft/qip-exchanges-with-pinstripes.txt > qpid/doc/qips/qip-0002.txt > > where the former is a qip in draft form and the latter is a qip after it's > been accepted and assigned a number. > > On status, definitely. I'll incorporate that into the next version. > > As to source control versus wiki, as Rajith mentioned, I personally prefer > source control, but if someone wants to use a wiki instead, I don't think > that does the process any serious harm. > > Thanks, > Justni > > On Fri, 7 Jan 2011, Ken Giusti wrote: > >> Justin - I like this idea. >> >> Will only the approved QIPs be saved into source control? Seems like a >> good idea to keep the non-approved ones around - if just to have a history >> of feature vetting. >> >> Related: I'd suggest the "Status" section of the QIP document should >> require a rational statement if the final Status is set to Rejected (or even >> Deferred/Withdrawn/Abandoned). I don't want to have to sniff around the >> mailing list archives to determine why a particular feature was rejected... >> >> >> >> -K >> >> ----- Original Message ----- >>> >>> When I sent this I attached some top-level html files, but my mailer >>> seems >>> to have eaten them. >>> >>> The tarball made it through, however. If you look at the output dir >>> inside the tarball, you'll see the QIPs I mentioned in fully rendered >>> form. >>> >>> The other stuff in the tarball is some code to convert QIPs from text >>> format to html and generate an index. >>> >>> Justin >>> >>> On Thu, 6 Jan 2011, Justin Ross wrote: >>> >>>> Hi, everyone. >>>> >>>> I'd like to propose a new way to communicate about the major changes >>>> going >>>> into our releases. The goal is to help us make decisions early in >>>> the >>>> process, coordinate when a change in one place impacts another, and >>>> engender >>>> a broader sense of direction. It should also help to document the >>>> work that >>>> we do. >>>> >>>> To do this, I've imitated an approach that's been used in other >>>> community >>>> software projects. The Python project, for instance, uses Python >>>> Enhancement >>>> Proposals (PEPs) to review important changes to the Python language >>>> [1]. >>>> >>>> I've attempted to produce something very similar here and tie it >>>> into our >>>> release process. It's my hope that during the 0.10 cycle some >>>> contributors >>>> will opt to describe their major changes using the QIP process. This >>>> is, >>>> however, entirely optional. >>>> >>>> The attached QIP 1 and QIP template should provide an overview of >>>> how this >>>> might work. This is very much in an early and unrefined form, so I >>>> hope >>>> you'll take a look and share your thoughts. >>>> >>>> Thanks, >>>> Justin >>>> >>>> --- >>>> [1] http://www.python.org/dev/peps/pep-0001/ >>>> >>> >>> --------------------------------------------------------------------- >>> Apache Qpid - AMQP Messaging Implementation >>> Project: http://qpid.apache.org >>> Use/Interact: mailto:[email protected] >> >> --------------------------------------------------------------------- >> Apache Qpid - AMQP Messaging Implementation >> Project: http://qpid.apache.org >> Use/Interact: mailto:[email protected] >> >> > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:[email protected] > > -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
