Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of agrieve@google.com designates
 209.85.219.50 as permitted sender)
MIME-Version: 1.0
Sender: agrieve@google.com
In-Reply-To: 
 <CAOBL_k6b5PJotzfqaHap9C0jf=GOfsffLP2RgotdyanLDCoAQA@mail.gmail.com>
References: 
 <CADVgkyNF+5qBe1=UBpW0us33LEiP3TtBKv0uZfD_uWZiEw2eSQ@mail.gmail.com>
 <56B8A48A-2A4C-414A-96D2-A6200664A346@jaguNET.com>
 <CAOBL_k6b5PJotzfqaHap9C0jf=GOfsffLP2RgotdyanLDCoAQA@mail.gmail.com>
From: Andrew Grieve <agrieve@chromium.org>
Date: Tue, 22 Apr 2014 21:17:23 -0400
Message-ID: 
 <CABiQX1U=vsEpb_0NuTV6FPt5A7U8tb55RDyb3puhi7Sx+yuzAA@mail.gmail.com>
Subject: Re: Nomination for a new chair for Apache Cordova
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=UTF-8

Joe - totally uncalled for. Not sure where it even came from. If you
hate Apache so much, then why are you a *volunteer* on an Apache
project?

I'm fairly confident that there is not a good understanding of what it
means to be a PMC, or PMC chair, and Jim is spending his time to help
us out.
Jim - thank you.

On Tue, Apr 22, 2014 at 9:03 PM, Joe Bowser <bowserj@gmail.com> wrote:
> On Tue, Apr 22, 2014 at 5:52 PM, Jim Jagielski <jim@jagunet.com> wrote:
>> There is one other aspect of the chair which, for a somewhat
>> newish PMC is important: The entire PMC is responsible for
>> ensuring that the project is run in a way which abides by,
>> and embraces, the "Apache Way"... when it doesn't, the
>> Chair needs to (1) know that the PMC is going awry and
>> (2) encourage the PMC to fix those problems and (3)
>> interact w/ the board if the PMC needs help in doing so.
>>
>
> So, who is to protect the PMC from yourself and rest of the board
> trying to destroy the project with insults and vitriol?  While I
> believe that Shazron is up to the task, I'm convinced that "The Apache
> Way" is the worst way to run a software project, and that the Apache
> Board spends all their time trying to find ways to debate itself into
> irrelevancy.  I wish that we never joined the ASF, and honestly when
> you told us that we should leave months ago, I welcomed it.  That
> being said, we're still here, despite your best efforts. We've seen
> what happens when the board tries to help, and it generally pisses a
> bunch of committers off, and ends up with people insulting each other
> personally.  This response to your first e-mail on this list should
> not come as any surprise.
>
> The fact is that Shaz fits well, because unlike me, he is diplomatic
> and won't tell you to jump off a cliff every time you or any other
> Apache person comes in and tries to interfere with our project.
>
>
>> Not knowing Shaz personally, how does that all fit in
>> with the nomination?
>>
>> On Apr 22, 2014, at 5:34 PM, Brian LeRoux <b@brian.io> wrote:
>>
>>> Hello Cordova community. To this point I've served as the chair for the
>>> Cordova PMC.
>>>
>>> The duties of chair are solely administrative: board reports, and book
>>> keeping of committer nominations. Some projects at Apache have more formal
>>> incantations. We have, so far, preferred to maintain our lightweight
>>> approach meaning a committer is a PMC member too. This involves sending an
>>> email, updating a text file in SVN, and running a few perl scripts on
>>> http://people.apache.org. Keeping those books is important if some day
>>> there is a dispute to the veracity of our source.
>>>
>>> In evaluation of  my current workload these additional book keeping
>>> responsibilities are not appropriate for me to prioritize and that is not
>>> fair to Cordova.
>>>
>>> I'm going to step down as chair for Cordova and I would like to nominate
>>> Shazron Abdullha to take on the role. Shaz has been with the project since
>>> before it was called Cordova. He lands more code than most, interacts
>>> directly with the community more than anyone, and is committed to work on
>>> Cordova solely full time. He'll be a better chair than I ever was.
>>>
>>> I won't be going anywhere and (I hope!) this means I can contribute more
>>> code than emails in the future. We can be formal and go to a vote if there
>>> is objection or interest in seeing someone else take the admin duties on.
>>> Otherwise, I'll aim to shoot the board official notice early next week.
>>