Return-Path: X-Original-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-bloodhound-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 0C7B4EC4F for ; Thu, 24 Jan 2013 11:22:39 +0000 (UTC) Received: (qmail 85326 invoked by uid 500); 24 Jan 2013 11:22:39 -0000 Delivered-To: apmail-incubator-bloodhound-dev-archive@incubator.apache.org Received: (qmail 85168 invoked by uid 500); 24 Jan 2013 11:22:37 -0000 Mailing-List: contact bloodhound-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: bloodhound-dev@incubator.apache.org Delivered-To: mailing list bloodhound-dev@incubator.apache.org Received: (qmail 85019 invoked by uid 99); 24 Jan 2013 11:22:31 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2013 11:22:31 +0000 X-ASF-Spam-Status: No, hits=-0.7 required=5.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of joachim.dreimann@wandisco.com designates 209.85.214.172 as permitted sender) Received: from [209.85.214.172] (HELO mail-ob0-f172.google.com) (209.85.214.172) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 24 Jan 2013 11:22:26 +0000 Received: by mail-ob0-f172.google.com with SMTP id ta17so4336817obb.31 for ; Thu, 24 Jan 2013 03:22:05 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type:content-transfer-encoding :x-gm-message-state; bh=eMOHVSeA026Yc789gGF8HmNQxjojtWYcDqsRadulZqI=; b=hv6Oz0NmSooEWkHKwiaHSXWo38Ne49EgNGJRV2FNqPhBBWGqY4rdqJrwLJvzd25VkR 9J2citWqmSR62gQs+F1/fKlBuj67tbp/p2waQF16udh19wQwRRW8naZHsNNvrnyZ+GOV E+LBWqvuAtIsY+9tm2iRgeXDXKAei72zCQnXl2C1sMDLzomDZGCK1BB8L4DnHPNjhB9g wo26TwkasaoGXD/ErCNTrFUCF/3aRZsgniVgxkGTqEzfa9H3ufK3b0FlILpOSyiAm9Fc 8nTQ83115YF+FhriIT/7iQ77IBXhBdNJfMqBNTI1e9/nscrec1IYxqTcvpPalHk6EL7a gBBw== MIME-Version: 1.0 X-Received: by 10.182.110.1 with SMTP id hw1mr1129025obb.68.1359026525425; Thu, 24 Jan 2013 03:22:05 -0800 (PST) Received: by 10.76.77.33 with HTTP; Thu, 24 Jan 2013 03:22:05 -0800 (PST) In-Reply-To: References: <51002AB6.7060708@wandisco.com> <510044AD.90708@wandisco.com> Date: Thu, 24 Jan 2013 11:22:05 +0000 Message-ID: Subject: Re: Getting IPMC members to vote Re: [VOTE] Release Apache Bloodhound 0.4 (incubating) From: Joachim Dreimann To: "bloodhound-dev@incubator.apache.org" Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQk0DffmT2yKr3H5iEh9GomonOlP9JeInKm6odz+J4bNizFFnO4vrOaEMDg58gFokGYfRq8H X-Virus-Checked: Checked by ClamAV on apache.org I also fully subscribe to the fact that we need to improve community diversity, that part is not red tape. - Joe On 23 Jan 2013, at 22:19, Gary Martin wrote: > On 23 January 2013 20:14, Branko =C4=8Cibej wrote: > >> On 23.01.2013 20:45, Joe Dreimann wrote: >>> I don't know if it's allowed to combine both votes, but I'm in favour o= f >> it if it is. >> >> It's not. IPMC procedures dictate that the project community shall do >> everything necessary to produce an Apache release, then the IPMC will >> review those results by means of a second release vote. The idea being >> that as long as the project is a podling, it's learning the ropes. > > I was pretty sure that was the case but I happened to check here: > http://incubator.apache.org/guides/releasemanagement.html#best-practice-i= ncubator-release-vote > and noted that the wording "The conventional process is for the podling t= o > follow the usual Apache process" is quite suggestive that there is the > potential for something other than a conventional process. What confuses = me > is that I felt that I knew it was definitely a two stage vote - did I get > that from a different source? Anyway, it seemed worth checking. > > >> >> Note that you wouldn't really gain much by going straight to the IPMC, >> since that vote thread is initialized with existing mentor votes. > > Well, I could try to argue advantages of only having the possibility of > just 72 hours of voting but I am not attempting to get a change in the > rules of the incubator so it is all moot. > > >>> In relation to the currently stalled voting, I'd like to propose Gary a= s >> a future IPMC member. Is there a process for this? >> >> As soon as he becomes an ASF member, he can also become an IPMC member. > > Sounds good for some far off future when Bloodhound is out of incubation. > If it were possible before then it would just seem like an abuse of the > position. > > > >>> Also or alternatively, is there a process for recruiting further >> mentors? Or is it "simply" a case of picking out potential mentors and >> asking them? >> >> It's more or less a matter of asking on the IPMC. Really, though, this >> project has enough active mentors, and relying on purely mentor votes >> sounds like "cheating". > > We already have enough IPMC members in principle but everyone has limited > time and I do not feel that it is right to insist on their vote. In > addition, while I want votes to be completed quickly I would also prefer > new people examining our release each time as this increases the chance o= f > spotting issues that we have missed. > > >> The proper way to avoid blocking on release votes is to graduate. :) >> Which I believe this community is ready for. Except for the community >> diversity issue, which you're all actively working on. >> >> I know it's frustrating, but even though I'm typically prepared to cut >> through a lot of red tape, I do feel that community diversity is >> important. And we all know exactly how diverse this particular community >> is. > I have no objection at all to that point of view. > > Cheers, > Gary