FW: Beehive Update

[Cliff Schmidt <cl...@bea.com>]

Now that every committer is finally on the Apache beehive-dev 
list, I thought I'd forward one of the recent emails I sent 
to all the committers about what needs to get done (see below).

I've set up an Incubator status web page to track the issues
that we will need to close out throughout incubation, but 
particularly in the next month or so:
http://incubator.apache.org/projects/beehive.html

This page also links to the main project web page, which is
aimed at supporting the dev and user communities.  The site
that's up there now is temporary until we get something with
Forrest set up:
http://incubator.apache.org/beehive/

As the committers should all know, we were originally talking 
about using Maven right from the start with everything, but 
for a number of reasons it looks like we won't be ready to do 
that right away.  So we're going to go with Forrest for now 
and then slowly figure out the best way to use Maven, especially 
given the testing infrastructure we already have for the 
project.  If anyone wants to volunteer to try to accelerate the 
Maven plan, please speak up.

I think we're still pretty close to being ready to move 
development into Apache by the 15th.  BEA is still working out
some internal infrastructure details to make this happen as
smoothly as possible.  However, in the mean time, there's
no reason why we can't start any development discussions
on this list.  Also, in the mean time, anyone who hasn't
yet faxed in their CLA should do so.  See http://incubator.apache.org/projects/beehive.html
for a summary of the status of all the committers.  Once
everyone has confirmed they've taken care of this, I'll
ask the ASF to confirm they've received them, and we can
make sure everyone has a subversion account in time for
the code drop.

That's all for now.

Cliff

Cliff Schmidt wrote on Thursday, June 17, 2004 7:42 PM:
 
> UPDATE ON PROGRESS
> The short version is:
> Within BEA, we've been getting the Beehive code together, taking
> care of the legal issues, and setting up the infrastructure for
> us to move our development environment to Apache.  I'm hoping
> everything will be in place between July 8th and 15th.
> 
> MAILING LISTS
> For all future updates, I'd like to use the new
> 'beehive-dev@incubator.apache.org' distribution list.  This means
> that each of you need to be subscribed.  I know I said I would
> pre-subscribe you, but for a couple reasons it now looks like it
> works better for you each to subscribe yourself from the email
> account to which you want to receive beehive posts (see below
> for details).  ***PLEASE DO THIS BY MONDAY*** After that point,
> I will no longer send anything directly to your email accounts.
> 
> ACCOUNT NAMES
> I probably wasn't as clear as I could have been regarding the
> Apache account names.  If you aren't already an Apache committer,
> I need you to send me your requested account name, and I'll
> compile the list and get all accounts set up at once, after I
> know that Contributor License Agreements (CLAs) have been signed
> and faxed in for each person.
> 
> CLAs
> Again for people who are not already Apache committers, when you
> email me your preferred account id, please also confirm with me
> that you have signed and faxed in your CLA to Apache.  Only a
> few of you have confirmed this with me so far.
> 
> INTELLECTUAL PROPERTY ISSUES
> Whether you are already a committer or not, please be sure to
> consider any employment contract or law that may apply to you
> that would mean your contributions are actually owned by your
> employer.  Apache wants CLAs from each individual, but that CLA
> only refers to IP that is yours.  If you are an employee of a
> California-based corporation, for example, the law states that,
> unless otherwise agreed upon, your employer owns an IP you create
> a) while on your employer's time, b) using your employer's
> equipment, or c) in your employer's line of work.  Regardless of
> where you live, be sure you know whether future contributions
> from you to the Beehive project are your IP or someone else's.
> If they would belong to your employer, please let me know and I
> can help you deal with that.  For instance, BEA signs a version
> of the CLA that covers all the contributions made by its
> employees, just to be clear that it owns the IP and that it is
> the one licensing all future employee contributions to Apache.
> *************************************************************
> Ensuring these legal issues are handled appropriately is
> extremely important to both the Apache Software Foundation
> and to BEA.
> *************************************************************
> 
> BEEHIVE COORDINATION
> Heather Stephens (one of your Beehive committer peers) is
> going to be responsible for many of the Beehive project
> coordination issues.  She will be particularly focused on
> Beehive project management, logistics, and community building.
> You can expect to see her posts on the beehive-dev list
> as she helps Beehive get set up and organized, and eventually
> helps to bring the community together to figure out how Beehive
> should evolve to really become the next big thing for enterprise
> Java development.
> 
> 
> THINGS I NEED
> 1. EVERYONE must subscribe to the beehive-dev list (for Beehive
> development discussions) and the beehive-ppmc list (for the rare
> time that a private discussion is needed about the future of the
> project -- this should rarely be used).   I am assuming everyone
> will do this by Monday; so all future communication can be done
> on the -dev lists.  The following links will direct the
> subscription request email:
> mailto:beehive-dev-subscribe@incubator.apache.org
> mailto:beehive-ppmc-subscribe@incubator.apache.org
> 
> 2. Everyone is highly encouraged to also subscribe to the
> beehive-user list (to discuss and answer how people will use
> Beehive), plus the incubator general list (to read and
> participate in discussions about the incubation process, which
> we will go through over the next few months).  The following
> links will subscribe you to these lists:
> mailto:beehive-user-subscribe@incubator.apache.org
> mailto:general-subscribe@incubator.apache.org
> 
> 3. Each person who is not already a committer should sign and
> fax in the attached CLA.
> 
> 4. Each person who is not already a committer should then send
> an email to me telling they have done so, plus the account id
> you would prefer.
> 
> 
> That's it for now.
> 
> Thanks,
> Cliff
> 
>