Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 70284 invoked from network); 17 Mar 2006 17:51:23 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 17 Mar 2006 17:51:23 -0000 Received: (qmail 59683 invoked by uid 500); 17 Mar 2006 17:51:17 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 59624 invoked by uid 500); 17 Mar 2006 17:51:16 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 59611 invoked by uid 99); 17 Mar 2006 17:51:16 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Mar 2006 09:51:16 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: domain of chirino@gmail.com designates 64.233.184.193 as permitted sender) Received: from [64.233.184.193] (HELO wproxy.gmail.com) (64.233.184.193) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 17 Mar 2006 09:51:15 -0800 Received: by wproxy.gmail.com with SMTP id i21so639126wra for ; Fri, 17 Mar 2006 09:50:54 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=qEIDK4ziTXC+Idj25RdS2DyJybno9Gb7zdFh3JS5qaNFRNmq8g11BKeTsqIPkARurvFOK0LKRT83QrvFS+LXG72HVOCk0eA/HExdSn2iu+AojCTYLQasIvPei62wNYyDdXSqmqPxuJa04lSAf/P/mOE7HXEE+90vrclK9GCLh/M= Received: by 10.64.131.16 with SMTP id e16mr355622qbd; Fri, 17 Mar 2006 09:50:54 -0800 (PST) Received: by 10.65.230.15 with HTTP; Fri, 17 Mar 2006 09:50:54 -0800 (PST) Message-ID: Date: Fri, 17 Mar 2006 12:50:54 -0500 From: "Hiram Chirino" Sender: chirino@gmail.com To: dev@geronimo.apache.org, "Leo Simons" , general@incubator.apache.org, activemq-dev@geronimo.apache.org Subject: Re: ActiveMQ Graduation From Incubator In-Reply-To: <20060317173343.GF16754@bali.sjc.webweaving.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline References: <4418CD3C.60502@toolazydogs.com> <20060317173343.GF16754@bali.sjc.webweaving.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Leo, Many of the folks in the ActiveMQ project already have been through the incubation process once before when we put Geronimo though. It's not like this is our first rodeo. So in our eyes we really do think we are very close to having satisfied the incubation requirements. I think Alan was opening up the discussion to get constructive feed back on what people feel is missing. For example, you have an opinion that "The idea that ActiveMQ as a community is ready to leave the incubator, is well, awkward." You are aware that this was a community that was started by Apache committers and run very much in the Apache meritocratic style when it was the codehaus right? So in sort, it would be nice for you to explain this opinion a little more. Regards, Hiram On 3/17/06, Leo Simons wrote: > Alan, > > Incubation is something incubating communities have to do, and something > incubating communities are responsible for. Those communities get some > help and guidance from their mentors and the people on the > general@incubator mailing list, but never enough since most of those peop= le > are volunteers with other things to do with their free time. > > (...) > > What is not fair is casting aside a few months of e-mail and face-to-face > history of various people trying to help with this incubation thing, stam= p > your feet once every few weeks, and demand that people go and make a > specific list of specific tasks you need to do. This is now the third tim= e > I've seen you do this and it is the third time I'm telling you this is no= t > how it works. > > (...) > > Here's a list of things to do (subjectively, none of these are easy): > > * stop complaining. Right now. It is not fair. > > * compile your own list, try to make it as extensive as possible. > mail-archives.apache.org is your friend, people have spent hundreds > of hours writing hundreds of e-mails to explain this to you and to > those that came before you. > > * send the list out to people (like general@incubator) for feedback > and discussion. > > * work to address the list. > > * keep a record of this work. > > * point to the record (STATUS file). > > * spend time explaining concisely in a format processable by humans > during a concall, what is in this record, what changed, etc, and > send this in time when Noel asks for a report for the board meeting. > > * look back on this process and document what you learned so others > can benefit from it. > > The idea that ActiveMQ as a community (not the software, I have no > clue about the software) is ready to leave the incubator, is well, > awkward. The very fact that there are long e-mail threads like this > everytime I look at general@incubator should be enough indication that > it is not. > > LSD > > On Wed, Mar 15, 2006 at 06:28:12PM -0800, Alan D. Cabrera wrote: > > Noel J. Bergman wrote: > > >Alan D. Cabrera wrote: > > > > > > > > >>I only see infrastructure issues in your list of concerns > > >>that would prevent the graduation of ActiveMQ. > > >> > > > > > >Look again, but also at comments from Dims, Henri and others. > > > > > > > At the moment, only Dims has taken the time to enumerate a list of > > concerns. Henri and the others have provided well thought out points o= n > > the definition of umbrella projects and whether AMQ should be a TLP or > > subproject; these not really being impediments to graduation but the > > necessary discourse about the final disposition of AMQ when it graduate= s > > that I was looking for when I initially sent out my email. > > > > >>You express an opinion that it should be a TLP but mention that it ha= s a > > >>long way to go before it's ready for that. Can you enumerate what > > >>remains, aside from the infrastructure issues > > >> > > > > > >See my reply to Dain. And I do feel that some of it does come down to > > >being > > >able to convey a subjective confidence to the Incubator PMC that the > > >community really does "get it" regarding ASF principles and practices.= And > > >that is supposed to happen before, not after, a community leaves the > > >Incubator. > > > > > > > There are a number of definitions for the word "subjective". If > > subjective means that your concerns may be peculiar to yourself, can yo= u > > not explicitly state what you'd like to see? If you are unable to > > communicate what those are, we may not unable to address them. Is that > > fair to the AMQ community? > > > > >>If AMQ has less inspiring aspirations and was to initially land > > >>as a sub-project > > >> > > > > > >I am not sure how much difference there ought to be, but some of that = comes > > >down to the landing PMC. I do have a concern an issue of fairness. > > > > > >Consider David Blevin's well-stated views, including "We've more or le= ss > > >been running as TLPs [for] the past two plus years already." So if we= have > > >some community that has been autonomous, and it becomes part of anothe= r TLP > > >within the ASF, how fair would it be for the members of that community= to > > >lose their decision making ability? I would say not, so are they goin= g to > > >be made part of the destination PMC, which would be required for them = to > > >have binding votes? > > > > > >This is a generic issue. I would have to cross-reference in detail th= e PMC > > >and committer lists for ActiveMQ and Geronimo to be specific to this c= ase. > > >I do realize that there is overlap, but also others who are part of > > >ActiveMQ > > >and are not part of Geronimo. Is Geronimo prepared to welcome them as > > >Committers on the Geronimo TLP and members of the Geronimo PMC? > > > > > >Related comment will go as a reply to David Blevins. > > > > > > > > > > If I take away the list of infrastructure issues, I only see the need t= o > > have a thorough discussion as to where AMQ will land when it graduates. > > Once this settles down and we, hopefully, reach a consensus we will be > > ready to vote, imho. > > > > > > > > Regards, > > Alan > > > > > -- Regards, Hiram