Beehive initial code drop

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

(moving discussion to incubator general list - others may be 
interested in the outcome of this decision, as an example of
how one company does a software grant.)

Roy T. Fielding wrote on Thursday, July 15, 2004 4:45 PM:

> Actually, for legal reasons, it would be better for Apache not to
> have the development history of the BEA code base -- that history
> might include the deletion of code that could not be open sourced,
> for whatever reason, and then we would be liable for making it public.

Right - I don't think it makes sense for a company to contribute the
change history before contribution.  

As of today, the ASF should have BEA's software grant for Beehive.
Exhibit A simply reads, "Beehive", which represents all files that
make up the forthcoming initial code drop into the "incubator/beehive" 
SVN directory.

As far as the actual code drop, I was planning on just asking one of 
the BEA employee/committers to simply check-in the entire code base 
into SVN, as BEA did with the initial XMLBeans contribution.  However, 
we could also ftp a tarball of the same code if anyone thinks it would
be preferable to also do this (and if so, where?).  Personally, I 
think a software grant for "Beehive", followed by one large initial 
check-in from a BEA employee into the "beehive directory, should be 
pretty clear.  

Does this sound good to everyone?

Cliff


---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org