Thanks for your comments Matt.
Well, it's after the holidays. Time to pick this thread back up.
This issue needs to be resolved before we graduate.
On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote:
Thanks for starting the discussion about this. I think there are a
few different issues so I'll try to separate them. The issues we
need to address is the trademark of VCL and the other is the
identity of the community. Perhaps we should talk about these in
First is the identity of the community. The move of the
development for the VCL codebase from NC State to Apache marked the
formation of a community outside of NC State. So, what NC State
decides to do or not to do is not particularly relevant to the
community collaborating at Apache. Given this separation, perhaps a
different name is appropriate so their is a clear distinction
between NC State's use of VCL and the Apache Incubator's community.
As far as the name goes. Since Virtualization and hosting is, well,
virtual, perhaps a name like spectre or Casper would be good :)
(ya, I already can see the naming police coming).
On Dec 19, 2008, at 10:19 AM, Henry E Schaffer wrote:
If VCL is a trademark owned by NCSU then they would have to assign
trademark to the ASF or we would have to change our project's name.
OK - I think we've reached a very clear question to be resolved. I
think here's what needs to be resolved (at least in my mind):
If VCL is a trademark owned by NCSU, and If NCSU assigns the
to the ASF - then would ASF give NCSU permission to continue its web
site as is (possibly with an acknowledgement to the ASF)?
Alternatively: If VCL is a trademark owned by NCSU, and If NCSU
doesn't assign the ownership to the ASF, but gives permission to
ASF to use
"VCL" as part of naming this ASF project - could, and would the ASF
"AVCL" ("Apache VCL") as the name? (Or some other formulation which
would be an Apache name but clearly portray to users and potential
that it's the same project.)
Does the above make sense?