So, my intention wasn't to start a big argument. If the feeling is that the page describes the behavior correctly let's leave it. It seemed to me like we wanted all proposals to be up on the wiki, based on the way some of the comments have come through...
John On Sun Nov 23 2014 at 2:59:31 PM Dennis E. Hamilton <dennis.hamil...@acm.org> wrote: > +1 on Jan's observations, below. > > Also, from my experience with the Proposal for Apache OpenOffice and a few > others, there is considerable refinement of proposals from first draft to > the version that is essentially frozen at the time of podling-acceptance > balloting. The Wiki is perfect for this, as is community involvement in > the refinement. (Some podling proposals are a bit more "closely-held" than > the way the AOO one was developed and edited, so *maybe* that doesn't > matter so much.) The key thing is that early proposals are moving targets > and while some are advanced by a single benevolent editor, it is useful to > have a wiki for the ground-truth du jour, addition of initial committers, > etc. > > -----Original Message----- > From: jan i [mailto:j...@apache.org] > Sent: Sunday, November 23, 2014 11:00 > To: general@incubator.apache.org > Subject: Re: Proposals - wiki required? > > On 23 November 2014 at 19:41, Alan Cabrera <l...@toolazydogs.com> wrote: > > [ ... ] > > > As for storing them in one place after acceptance, why? > > > SImple so that new "recruits" can go and get ideas of how to interpret the > different headlines. The headlines might be simple to you, but I had to > look at some proposals to understand some of the headlines. > > I am champion for 2 projects (one seems to go in another direction) and > found it very useful to point the projects at the wiki. It saved my quite a > lot of explanations (and discussions). I have found that projects who want > to join, dont really understand how/why a proposal is needed, giving > examples of successful projects makes that part a lot easier. > > > > > > Adding strongly worded "should"s dilutes guidelines and adds to the > > reading homework of new podlings that will already have the good sense to > > use a wiki, or something better that us old folk haven't thought of. > > > > Like you I am against "rules", and I don't care whether its wiki or foo, I > simply like to know where I can find "real life" proposals. My idea of > using "should" instead of "rule" was to signal, that it must be stored > somewhere, preferable (for now) in wiki. > > Seen with my iPMC hat on, it is a bit of history that we should not throw > away, I used it a couple of times on a couple of projects to see how they > have evolved. > > [ ... ] > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > For additional commands, e-mail: general-h...@incubator.apache.org > >
