On 08/01/15 16:48, Chip Childers wrote:
On Wed, Jan 07, 2015 at 08:18:59PM -0800, Marvin Humphrey wrote:
Retiring the role of Champion sounds like an idea whose time has come. We
gave the Champion additional oversight responsibilities a while back -- but
how many times since then has having that additional layer made a difference?
My 2 cents:
In my experience, the "Champion" is a useful concept for the purpose of
having discussions with the incoming project's community *before* they
become a podling. I've acted as a champion for one podling so far, as
well as acted in this role for one community that ended up *not* wanting
to incubate.
I see this as a valuable activity (I don't care what it's called),
because it's important that incoming projects understand what they are
signing up for. As much as it's an investment for the ASF to accept
podlings, it's an investment for the inbound communities to make the
proposal.
For the project that I acted as a Champion for, I considered that part
of the work to be done when they became a podling. I also asked to be a
mentor, and am doing so now... and being a mentor is a bit different
from that initial introduction.
In the end though, regardless of what we name things, podlings should
have support from people here in the incubator from the time they start
considering the move to the time they become a TLP.
+1
The other minor aspect of "champion" can making sure getting bootstrap
happens quickly. Other mentors may not immediately be active, or as well
known to the podling. It is "admin" smoothing over the transition, not
vital, but helpful.
Andy
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
