Return-Path: Delivered-To: apmail-incubator-general-archive@www.apache.org Received: (qmail 57360 invoked from network); 24 Jun 2009 08:03:27 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 24 Jun 2009 08:03:27 -0000 Received: (qmail 41442 invoked by uid 500); 24 Jun 2009 08:03:37 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 41257 invoked by uid 500); 24 Jun 2009 08:03:36 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 41246 invoked by uid 99); 24 Jun 2009 08:03:36 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 08:03:36 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of martijn.dashorst@gmail.com designates 209.85.220.223 as permitted sender) Received: from [209.85.220.223] (HELO mail-fx0-f223.google.com) (209.85.220.223) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 24 Jun 2009 08:03:28 +0000 Received: by fxm23 with SMTP id 23so379221fxm.12 for ; Wed, 24 Jun 2009 01:03:07 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type :content-transfer-encoding; bh=KaTUy2gOIKv1DQtNRJqfmWw6fiKoLA6ICRMGXTlPvYc=; b=mTtVx0RUV7U4huAfch5RMkMlZUaig5SmP2MG5iImw4sGmmcZnONO6vhZ22oj//+HdP XjiDS9xzkkiu68YqxW6l8ynPqbSI7x6gFdxv9s7zdgG19BvIhFsYVFi/GmPzbGYvj8wZ J6qAeCuchQjOkw01mwVbUcMI2K13Xay9CpeZY= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type:content-transfer-encoding; b=ml5Mt/Fsj+lM0ov0hFgHbjOVKIPjr+0OzCrbELAMOoQC9dx+KMNRxPp3K5iH2JeRDP W43zu27o7RkTv2UMSFnPspfCu4SVH1Bh3M3+cCFJ7RWB6U6lOMCeQI2qXb3u5LCEDZNW d3wBvkz4XgCiwWlbQw84N5p1CY6+s+Pw01ORU= MIME-Version: 1.0 Received: by 10.103.160.9 with SMTP id m9mr494096muo.96.1245830587191; Wed, 24 Jun 2009 01:03:07 -0700 (PDT) In-Reply-To: References: <918312fe0906231508q58159418k75aed72a3c882f87@mail.gmail.com> Date: Wed, 24 Jun 2009 10:03:07 +0200 Message-ID: <918312fe0906240103p79d1dbeat6eecc72173c3fec7@mail.gmail.com> Subject: Re: Community readiness-when does it show? From: Martijn Dashorst To: general@incubator.apache.org Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Jun 24, 2009 at 5:42 AM, J Aaron Farr wrote: >> If a community meets all the criteria, but hasn't discovered a new >> committer (or two) by itself, is the community ready for graduation? >> If not, how can we=97mentors=97 nudge the community to focus on this >> thing, without it becoming an exercise in "checking the check marks"? > > There are at least two scenarios: Yup, but I'd like to add a third one: - the podling has voted in a new committer, but only because the committer was 'discovered' by the mentors It is hard work to keep track of contributors and identify those with enough merit, when you are busy solving licensing issues, releasing and trying to keep your project going. Wouldn't a community only be ready when they themselves are capable of looking beyond their own coding, contemplate what's happening in their community and take necessary action? While I understand that Mentors should prod the community into action at times, but shouldn't Mentors also take a step back and let the community become enlightened by themselves? Martijn --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org For additional commands, e-mail: general-help@incubator.apache.org