---------- Forwarded message ----------
From: *Benson Margulies*
Date: Monday, November 26, 2012
Subject: [VOTE] Retire Chukwa from incubation
To: "general@incubator.apache.org" <general@incubator.apache.org>


For those voting -1, I'd like to see, on another thread, some
discussion about just how we handle podlings where there are
longstanding issues but no consensus on the PPMC. We've heading in the
same direction on Photark, and some consensus about how or when to
reach a respectful conclusion as a PMC that a project should be
retired even if the PPMC is not of the same opinion would be useful.
We cannot both say that we need projects to have active, supervising,
mentors and shepherds and then not, in some fashion, act on what they
tell us.

-----


I believe that the discussion we should have is how can we help struggling
podlings to grow their community in a sustentable way. Recently, I have
seen an increase in trying to push small communities to retirement, but i'm
yet to see active mentors engaging and helping and motivating the podlings
PPMC to find ways to grow.

Growing communities when a project is backed by corporations that sponsor
engineers to devote their full time volunteering at the project is much
easier compared to those other projects that are developed by a small group
of people, that devote their own free time and are passionate by the Apache
brand, and doing truly open source following the Apache Way.

With my Community development hat, I would really like to see a wide
discussion on how the IPMC and COMDEV PMC could find ways to help these
struggling podlings succeed, instead of just giving ultimates for seeking
retirement. Things that come to mind are : make it easier for new
contributors to find tasks that they could work on, more visibility for
podlings in Apache sponsored conferences, etc

Thoughts ? Other possible ideas ?

Thanks
--
Luciano Resende

Sent from my iPhone









-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Reply via email to