Mailing-List: contact beehive-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Beehive Developers" <beehive-dev@incubator.apache.org>
Received-SPF: pass (asf.osuosl.org: domain of richfeit@gmail.com designates
 64.233.162.192 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:user-agent:x-accept-language:mime-version:to:cc:subject:references:in-reply-to:x-enigmail-version:x-enigmail-supports:content-type:content-transfer-encoding;
        b=jh0OsODOd8nXsLi4NIPyRZFaXBWo5/2skpqSLx8aoPSxmxIGkxdWTWXMBrMM2aU2i+rmHIHr3CIOFTAus4ghnGgo/VO/d7deHtVSNuiDhqrUQrQ9M278qjEgYNbMAbo1FoN6M1bbtxx92PFErSkHamoQMyrNe4ltmXIiFtQ4Wvg=
Message-ID: <42DE6D22.8080103@gmail.com>
Date: Wed, 20 Jul 2005 09:26:26 -0600
From: Rich Feit <richfeit@gmail.com>
User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716)
MIME-Version: 1.0
To: Kenneth Tam <kentaminator@gmail.com>
CC: beehive-dev@incubator.apache.org,  beehive-ppmc@incubator.apache.org
Subject: Re: beehive 1.0 release status update
References: <e9ac83540507191936ef1aea7@mail.gmail.com>
	 <c5e6325505072001424c53faf8@mail.gmail.com>
	 <c5e6325505072002148f81c53@mail.gmail.com>
 <e52f74f805072004045a067409@mail.gmail.com>
In-Reply-To: <e52f74f805072004045a067409@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

As Cliff suggested earlier, I propose that we take the PMC Chair 
nomination discussion out of beehive-dev and onto beehive-ppmc only, to 
be resumed on beehive-dev once we've selected someone.  :)

Rich

Kenneth Tam wrote:

>I nominate myself for the PMC chair and propose the following resolution:
>
>..that the Apache Beehive PMC be and hereby is responsible for the
>creation and maintenance of a Java enterprise application framework
>focused on ease-of-use via highly toolable metadata-driven programming
>models.
>
>On 7/20/05, Cliff Schmidt <cliffschmidt@gmail.com> wrote:
>  
>
>>To reiterate the schedule I mentioned in my previous email.  Here's my
>>suggestion:
>>
>>Today (Wednesday): start nominations for anyone interested in being VP/PMC chair
>>
>>Today: someone (probably someone willing to be the chair) should
>>propose a resolution -- really just the single phrase that defines the
>>project scope inserted into the standard template (see below)
>>
>>Friday morning (PDT): start vote on resolution
>>
>>Sunday evening (PDT): start vote for VP (giving the rest of this week
>>and weekend for anyone to consider nominations)
>>
>>Tuesday morning (PDT): close vote on resolution and send to Board for
>>review before meeting, leaving VP name blank for the moment.
>>
>>Wednesday evening (PDT): close vote and insert Beehive's proposed VP
>>name into the resolution before board votes on it the next day.
>>
>>Sound good?
>>
>>Cliff
>>
>>On 7/20/05, Cliff Schmidt <cliffschmidt@gmail.com> wrote:
>>    
>>
>>>On 7/20/05, Eddie ONeil <ekoneil@gmail.com> wrote:
>>>      
>>>
>>>>For those who may not have seen, it seems that Beehive has been
>>>>released from the Apache Incubator, so congratulations are in order
>>>>for members of the community (user and dev) for having reached this
>>>>milestone.
>>>>        
>>>>
>>>it does seem that way. ;-)  We should see an official vote result
>>>summary on the incubator general list shortly (I think Dims will be
>>>sending that since he started the vote.)
>>>
>>>      
>>>
>>>>  As per Noel, Cliff and Dims's mails, we're awaiting an Apache Board
>>>>meeting for the discussion about having Beehive become a
>>>>top-level-project (TLP).  More there when we hear further news.  And,
>>>>Cliff, please correct me if I've conveyed any of this information
>>>>incorrectly.
>>>>        
>>>>
>>>I believe the next Board meeting is scheduled for next Thursday.  The
>>>only correction to what you wrote is that Beehive needs to provide a
>>>resolution (which includes a proposed VP) BEFORE the Board meeting --
>>>in fact, preferably a couple days (Tuesday) before the Board meeting.
>>>The idea is that we give the Board something to vote on and hopefully
>>>approve.
>>>
>>>What this means is that the following things need to happen really soon:
>>>a) discussion and a vote on the resolution for Beehive (including a
>>>1/2-line project scope),
>>>b) a vote to determine the proposed VP for the future Beehive TLP
>>>
>>>To have both of these things done by Tuesday (including a three-day
>>>voting period), we should probably start a) today and b) by Friday.
>>>I'd recommend that anyone who wants to nominate one of the PPMC
>>>members (including nominating one's self) as the VP does so in the
>>>next 48 hours or so.  If the Board meeting is Thursday, we could
>>>probably let the VP vote run up until Wednesday and just plug a name
>>>into the resolution text (which we want to have submitted to the Board
>>>by Tuesday to allow them to review it).
>>>
>>>Hope this quickly-written email makes sense.  BTW, I sent info about
>>>this process in response to a PPMC thread.  I will resend that info to
>>>this -dev list (the process is not a secret ;-).  All discussion and
>>>probably the resolution vote should happen on this list, but we may
>>>choose to cast VP votes on the private ppmc list.
>>>
>>>Cliff
>>>
>>>      
>>>
>>>>  I think that it makes sense to start stabilizing for a Beehive 1.0
>>>>release in order to deliver Controls + NetUI to the community in a 1.0
>>>>form.  The situation for WSM relative to JSR 181 TCK compliance has
>>>>not changed, though I'd guess we'll start the TCK work in the next few
>>>>weeks.  Once this has been passed, WSM will be added to Beehive in a
>>>>subsequent release.
>>>>
>>>>  I'd suggest waiting a week or so to hear the outcome of the Apache
>>>>Board's decision relative to TLP status.  Depending on the outcome of
>>>>this discussion, we could do a 1.0 release soon thereafter as a
>>>>full-fledged Apache project (!) or wait / discuss our options if that
>>>>decision is delayed for some reason.  Either way, it makes sense to
>>>>deliver stable APIs soon.
>>>>        
>>>>
>>>makes sense to me
>>>
>>>      
>>>
>>>>  Status mail tracking our bug progress will appear shortly --
>>>>currently, I think we've only got a couple of issues to be resolved in
>>>>the "V1" category.
>>>>
>>>>  Thoughts / comments welcome.
>>>>
>>>>Eddie
>>>>
>>>>        
>>>>
>
>  
>