incubator-general mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Noel J. Bergman" <>
Subject RE: Incubator Roles revisited
Date Sun, 19 Feb 2006 17:33:26 GMT
Berin Lautenbach wrote:

> I'd be happy for non-members who have met your criteria [with]
> one caveat - I'd prefer to have at least one member on each
> project to make sure there is someone in the podling that the
> membership as a whole have agreed is looking out for the wider
> interests of the ASF.

Is this expressing concern that we would elect someone to the PMC who is
more concerned about a specific podling, or a particular TLP, than the ASF?
I suppose that is a fair concern, but doesn't that indicate whom should be
elected to the PMC?

Interstingly, when you look over the bullet lists associated with the role
you may notice that we have enumerated important oversight issues, but only
one bullet even hints at the major responsibility of helping out with
community building.  And none talk about technical contributions.  I feel
that the former should be more explicit, but the latter is probably given as
much emphasis (or lack thereof) as it deserves.

Rich Bowen mentioned how he would like to be a Mentor, but doesn't know
Java.  Mentors need the ability to maintain the required oversight, and
skill in community building.  But I would rather have someone with those
qualifications than someone skilled in the technical domain.  A Mentor
lacking the latter is likely to focus on community building, and helping the
community to make its own decisions -- perhaps using the Socratic method --
rather than inserting himself or herself into the midst of technical issues.
Helping the community to make collaborative decisions seems the right
approach to me, especially with more and more sophisticated projects.

	--- Noel

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message