You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ode.apache.org by Matthieu Riou <ma...@offthelip.org> on 2008/09/23 17:24:09 UTC
Graduation process
Hi guys,
So it seems that everybody agrees it's time to get ready for graduation.
There's a nice guide that details the whole process here:
http://incubator.apache.org/guides/graduation.html
The trickiest part is to prepare a resolution for the board to adopt.
Ultimately, that's what we will vote on, what the incubator PMC will vote on
and what the board adopts. And the trickiest parts in the resolution itself
are:
- The target: Top Level Project or subproject of another TLP. For buildr
I think it would be TLP but if someone things otherwise it's a good time to
mention it.
- The charter: this should define the scope of the project. It should be
short, sweet and non ambiguous but sufficiently large in scope to cover
further expansion of the project. So getting the proper wording can be
tough. There are example here [1] and if you want more I can point you to
others.
- The project chair: I'll send another e-mail about that.
- The future PMC: actually that's the easiest, it's usually the same
composition as the PPMC.
So at this point, it would be nice if someone drafted a first charter
paragraph so we can increment from it. The rest of the resolution can easily
be created using the charter and a few names.
Thanks,
Matthieu
Re: Graduation process
Posted by Matthieu Riou <ma...@offthelip.org>.
Please ignore that mail, wrong mailing list ;) Was meant ofr buildr-dev.
On Tue, Sep 23, 2008 at 8:24 AM, Matthieu Riou <ma...@offthelip.org>wrote:
> Hi guys,
>
> So it seems that everybody agrees it's time to get ready for graduation.
> There's a nice guide that details the whole process here:
>
> http://incubator.apache.org/guides/graduation.html
>
> The trickiest part is to prepare a resolution for the board to adopt.
> Ultimately, that's what we will vote on, what the incubator PMC will vote on
> and what the board adopts. And the trickiest parts in the resolution itself
> are:
>
> - The target: Top Level Project or subproject of another TLP. For
> buildr I think it would be TLP but if someone things otherwise it's a good
> time to mention it.
> - The charter: this should define the scope of the project. It should
> be short, sweet and non ambiguous but sufficiently large in scope to cover
> further expansion of the project. So getting the proper wording can be
> tough. There are example here [1] and if you want more I can point you to
> others.
> - The project chair: I'll send another e-mail about that.
> - The future PMC: actually that's the easiest, it's usually the same
> composition as the PPMC.
>
> So at this point, it would be nice if someone drafted a first charter
> paragraph so we can increment from it. The rest of the resolution can easily
> be created using the charter and a few names.
>
> Thanks,
> Matthieu
>
Re: Graduation process
Posted by Matthieu Riou <ma...@offthelip.org>.
You might want to resend that mail too :)
On Tue, Sep 23, 2008 at 8:51 AM, Alex Boisvert <bo...@intalio.com> wrote:
> Charter by triangulation:
>
> "... that the Apache Buildr project be responsible for the creation and
> maintenance of build system, software configuration and software lifecycle
> management related tools."
>
> alex
>
> PS: I don't like the definitions of SCM and SLM in wikipedia. They sound
> like they were written by vendors with a very narrow vision.
>
> On Tue, Sep 23, 2008 at 8:24 AM, Matthieu Riou <matthieu@offthelip.org
> >wrote:
>
> > Hi guys,
> >
> > So it seems that everybody agrees it's time to get ready for graduation.
> > There's a nice guide that details the whole process here:
> >
> > http://incubator.apache.org/guides/graduation.html
> >
> > The trickiest part is to prepare a resolution for the board to adopt.
> > Ultimately, that's what we will vote on, what the incubator PMC will vote
> > on
> > and what the board adopts. And the trickiest parts in the resolution
> itself
> > are:
> >
> > - The target: Top Level Project or subproject of another TLP. For
> buildr
> > I think it would be TLP but if someone things otherwise it's a good
> time
> > to
> > mention it.
> > - The charter: this should define the scope of the project. It should
> be
> > short, sweet and non ambiguous but sufficiently large in scope to cover
> > further expansion of the project. So getting the proper wording can be
> > tough. There are example here [1] and if you want more I can point you
> to
> > others.
> > - The project chair: I'll send another e-mail about that.
> > - The future PMC: actually that's the easiest, it's usually the same
> > composition as the PPMC.
> >
> > So at this point, it would be nice if someone drafted a first charter
> > paragraph so we can increment from it. The rest of the resolution can
> > easily
> > be created using the charter and a few names.
> >
> > Thanks,
> > Matthieu
> >
>
Re: Graduation process
Posted by Alex Boisvert <bo...@intalio.com>.
Charter by triangulation:
"... that the Apache Buildr project be responsible for the creation and
maintenance of build system, software configuration and software lifecycle
management related tools."
alex
PS: I don't like the definitions of SCM and SLM in wikipedia. They sound
like they were written by vendors with a very narrow vision.
On Tue, Sep 23, 2008 at 8:24 AM, Matthieu Riou <ma...@offthelip.org>wrote:
> Hi guys,
>
> So it seems that everybody agrees it's time to get ready for graduation.
> There's a nice guide that details the whole process here:
>
> http://incubator.apache.org/guides/graduation.html
>
> The trickiest part is to prepare a resolution for the board to adopt.
> Ultimately, that's what we will vote on, what the incubator PMC will vote
> on
> and what the board adopts. And the trickiest parts in the resolution itself
> are:
>
> - The target: Top Level Project or subproject of another TLP. For buildr
> I think it would be TLP but if someone things otherwise it's a good time
> to
> mention it.
> - The charter: this should define the scope of the project. It should be
> short, sweet and non ambiguous but sufficiently large in scope to cover
> further expansion of the project. So getting the proper wording can be
> tough. There are example here [1] and if you want more I can point you to
> others.
> - The project chair: I'll send another e-mail about that.
> - The future PMC: actually that's the easiest, it's usually the same
> composition as the PPMC.
>
> So at this point, it would be nice if someone drafted a first charter
> paragraph so we can increment from it. The rest of the resolution can
> easily
> be created using the charter and a few names.
>
> Thanks,
> Matthieu
>