Given Alan's assessment below, there appears to be an impasse without
changing the project name. I propose we resolve this by suggesting names and
conducting a vote by either instant runoff (
http://en.wikipedia.org/wiki/Instant-runoff_voting) or exhaustive ballot (
http://en.wikipedia.org/wiki/Exhaustive_ballot). I prefer exhaustive ballot
since there is no real benefit in ending the process with one vote. If we
get stuck while using exhastive ballot, we can resolve by irv.
To start the process, here are a few name ideas:
- cloud provisioning engine - cpe
- datacenter builder
*From: *"Alan D. Cabrera" <l...@toolazydogs.com>
> *Date: *February 22, 2009 10:54:48 AM EST
> *To: *vcl-...@incubator.apache.org
> *Subject: **Re: VCL, is this name kosher?*
> *Reply-To: *vcl-...@incubator.apache.org
> The VCL team has built a wonderful product and it's admirable that they
> wish to move the project to ASF. They have a lot to be proud of and I agree
> it's understandable why they would wish to retain the VCL name.
> On Feb 21, 2009, at 2:01 PM, Matt Hogstrom wrote:
> 2. NCSU consumes the project from Apache and is the NCSU Virtual Computing
> Lab Powered by Apache VCL.
> The second option sounds like what is more like where we are, or at least
> this is where we are going. If that is the case then the real question is
> does NCSU need to not use the Virtual Computing Lab name. I don't see a
> problem with that (although some Apache volunteer lawyers should probably
> comment on this) as one is a place and the other is a thing (code).
> NCSU VCL is not a natural landmark in North Carolina. Apache VCL is not a
> thing, its a project. NCSU VCL is the progenitor of the VCL project which
> has moved to Apache VCL.
> VCL stands for Virtual Computing Lab. Simply breaking out the acronym in
> one case and not the other does not obfuscate the obvious connection.