You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tapestry.apache.org by Howard Lewis Ship <hl...@gmail.com> on 2006/04/13 17:13:48 UTC
Tapestry Project -- April 2006 Board Report
Tapestry has been in a state of transition away from a Jakarta
sub-project and to an Apache top level project.
Two new PMC members / committers have been added: Andreas Andreou and
Brian K. Wallace. Andreas has been active in the external Tacos
project (Ajax components for Tapestry). He and Brian have been
actively mentoring and supplying patches for months.
Bug fix releases of Tapestry 3 (release 3.0.4) and Tapestry 4 (release
4.0.1) have been released. These efforts have been spearheaded by
Jesse Kuhnert and Brian K. Wallace.
We've succesfully moved the SVN repository out from under the Jakarta
project. Howard Lewis Ship has taken over responsibility for granting
SVN access karma to Tapestry team members.
We're beginning to formulate rules and procedures for breaking the
Tapestry project into individual sub-projects. We are facing a large
amount of work to convert from an Ant-based build to a Maven2-based
build, primarily in terms of documentation (reams of which are
currently in Forrest XML format).
We are working on a new logo for Tapestry and expect to debut the new
http://tapestry.apache.org/ web site when it is ready. Our remaining
transfer tasks concern other bits of infrastructure to move out from
under Jakarta: the Tapestry wiki, and the Tapestry mailing lists.
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry Project -- April 2006 Board Report
Posted by Howard Lewis Ship <hl...@gmail.com>.
I wasn't aware of that change in policy, but I'm totally in favor of
it! The other was going to be a big headache.
On 4/24/06, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
> On 4/24/06, Howard Lewis Ship <hl...@gmail.com> wrote:
> > I can see how this looked, but no, I wasn't granting anyone access by
> > fiat, the granting of karma followed proper voting procedures. The
> > thing we're working on is identifying sub-projects and determine which
> > commiters will have access to each sub-project. The consensus was that
> > until we actually have sub projects, we would continue as we did under
> > Jakarta ... voted onto the team means access to all the code.
>
> As a general rule of advice, we prefer (but do not require!) that
> commit access is granted to the entire TLP space instead of
> partitioned out. There's a reason why Jakarta has switched back to a
> TLP-wide commit model. We tend to find that by segmenting the
> committers, we also segment the community - which can turn out to be a
> dangerous thing down the road. -- justin
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry Project -- April 2006 Board Report
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 4/24/06, Howard Lewis Ship <hl...@gmail.com> wrote:
> I can see how this looked, but no, I wasn't granting anyone access by
> fiat, the granting of karma followed proper voting procedures. The
> thing we're working on is identifying sub-projects and determine which
> commiters will have access to each sub-project. The consensus was that
> until we actually have sub projects, we would continue as we did under
> Jakarta ... voted onto the team means access to all the code.
As a general rule of advice, we prefer (but do not require!) that
commit access is granted to the entire TLP space instead of
partitioned out. There's a reason why Jakarta has switched back to a
TLP-wide commit model. We tend to find that by segmenting the
committers, we also segment the community - which can turn out to be a
dangerous thing down the road. -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry Project -- April 2006 Board Report
Posted by Howard Lewis Ship <hl...@gmail.com>.
I can see how this looked, but no, I wasn't granting anyone access by
fiat, the granting of karma followed proper voting procedures. The
thing we're working on is identifying sub-projects and determine which
commiters will have access to each sub-project. The consensus was that
until we actually have sub projects, we would continue as we did under
Jakarta ... voted onto the team means access to all the code.
On 4/24/06, Justin Erenkrantz <ju...@erenkrantz.com> wrote:
> On 4/13/06, Howard Lewis Ship <hl...@gmail.com> wrote:
> > We've succesfully moved the SVN repository out from under the Jakarta
> > project. Howard Lewis Ship has taken over responsibility for granting
> > SVN access karma to Tapestry team members.
>
> I imagine that the intent is right, but this phrasing is a little off.
> So, let me try to restate what should be going on here to ensure that
> we're all on the same page here.
>
> The new Tapestry PMC as a whole has the responsiblity for granting
> karma to new committers to Tapestry. Once a new committer is approved
> by the PMC, the PMC Chair (in this case, Howard) is responsible for
> executing that decision by twiddling the SVN karma or filing the right
> request forms with infra@. However, the PMC Chair shouldn't be adding
> or removing committers without consulting the rest of the PMC first.
>
> Other than that, looks fine to me. Keep up the good work! -- justin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
>
>
--
Howard M. Lewis Ship
Independent J2EE / Open-Source Java Consultant
Creator, Jakarta Tapestry
Creator, Jakarta HiveMind
Professional Tapestry training, mentoring, support
and project work. http://howardlewisship.com
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry Project -- April 2006 Board Report
Posted by Justin Erenkrantz <ju...@gmail.com>.
On 4/24/06, James Carman <ja...@carmanconsulting.com> wrote:
> What if the committers *are* the other PMC members? Does he still have to
> vote on it? I'm just curious, trying to learn the Apache way (especially
> since they've asked me to be the HiveMind PMC chair).
When the Board initially approves a resolution creating a new TLP
(such as HiveMind or Tapestry), there is a submitted roster of PMC
members and a designated PMC Chair. When that resolution passes, all
of those people become PMC members and the PMC Chair is appointed.
As part of the TLP creation process, someone (usually an existing
infra@ person) is going to do some twiddly bits and execute the
Board's decision. At that point, usually the PMC Chair gets the
ability to assign karma. But, if the infra@er is feeling really lazy,
they may just assign the Chair karma to assign karma and leave it at
that. But, because the Board has already approved the PMC members (by
passing the resolution), the Chair should feel free to assign those
people karma to the new project - they're just executing the whims of
the Board. ;-)
Note that the Board is the only entity that can change the composition
of a PMC. This is why PMC Chairs must send an email to board@ and a
Director must send an acknowledgement. 72 hours after that ACK if no
other Director raises a concern, then the composition of that PMC can
then change.
I hope this helps. It's probably not half as complicated as I make it
sound. ;-) -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
RE: Tapestry Project -- April 2006 Board Report
Posted by James Carman <ja...@carmanconsulting.com>.
What if the committers *are* the other PMC members? Does he still have to
vote on it? I'm just curious, trying to learn the Apache way (especially
since they've asked me to be the HiveMind PMC chair).
-----Original Message-----
From: justin.erenkrantz@gmail.com [mailto:justin.erenkrantz@gmail.com] On
Behalf Of Justin Erenkrantz
Sent: Tuesday, April 25, 2006 1:13 AM
To: board@apache.org
Cc: Tapestry development
Subject: Re: Tapestry Project -- April 2006 Board Report
On 4/13/06, Howard Lewis Ship <hl...@gmail.com> wrote:
> We've succesfully moved the SVN repository out from under the Jakarta
> project. Howard Lewis Ship has taken over responsibility for granting
> SVN access karma to Tapestry team members.
I imagine that the intent is right, but this phrasing is a little off.
So, let me try to restate what should be going on here to ensure that
we're all on the same page here.
The new Tapestry PMC as a whole has the responsiblity for granting
karma to new committers to Tapestry. Once a new committer is approved
by the PMC, the PMC Chair (in this case, Howard) is responsible for
executing that decision by twiddling the SVN karma or filing the right
request forms with infra@. However, the PMC Chair shouldn't be adding
or removing committers without consulting the rest of the PMC first.
Other than that, looks fine to me. Keep up the good work! -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org
Re: Tapestry Project -- April 2006 Board Report
Posted by Justin Erenkrantz <ju...@erenkrantz.com>.
On 4/13/06, Howard Lewis Ship <hl...@gmail.com> wrote:
> We've succesfully moved the SVN repository out from under the Jakarta
> project. Howard Lewis Ship has taken over responsibility for granting
> SVN access karma to Tapestry team members.
I imagine that the intent is right, but this phrasing is a little off.
So, let me try to restate what should be going on here to ensure that
we're all on the same page here.
The new Tapestry PMC as a whole has the responsiblity for granting
karma to new committers to Tapestry. Once a new committer is approved
by the PMC, the PMC Chair (in this case, Howard) is responsible for
executing that decision by twiddling the SVN karma or filing the right
request forms with infra@. However, the PMC Chair shouldn't be adding
or removing committers without consulting the rest of the PMC first.
Other than that, looks fine to me. Keep up the good work! -- justin
---------------------------------------------------------------------
To unsubscribe, e-mail: tapestry-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tapestry-dev-help@jakarta.apache.org