You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@vcl.apache.org by Brian Bouterse <bm...@ncsu.edu> on 2009/02/17 16:35:17 UTC
Re: VCL, is this name kosher?
I wanted to revisit this thread, because no conclusion was reached.
The current status is that after much discussion on the list, no name
changes were proposed, or ratified.
There are ASF naming guidelines located here. Personally, I interpret
this as a non-issue because the NCSU service is called the "Virtual
Computing Lab," and the ASF project name is "VCL" which is not the same.
What do you think?
my 2 cents,
Brian
Brian Bouterse
Secure Open Systems Initiative
919.698.8796
On Jan 6, 2009, at 11:18 AM, Josh Thompson wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Maybe we should look at this from a different angle - is there
> anything that
> *can* happen for the name to continue as "VCL" at ASF?
>
> Josh
>
> On Tuesday January 06, 2009, Alan D. Cabrera wrote:
>> 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.
>>
>>
>> Regards,
>> Alan
>>
>> On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote:
>>> Alan,
>>>
>>> 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
>>> reverse order.
>>>
>>> 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:
>>>> Alan writes:
>>>>> ...
>>>>> If VCL is a trademark owned by NCSU then they would have to assign
>>>>> the
>>>>> 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
>>>> ownership
>>>> 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
>>>> use
>>>> "AVCL" ("Apache VCL") as the name? (Or some other formulation
>>>> which
>>>> would be an Apache name but clearly portray to users and potential
>>>> users
>>>> that it's the same project.)
>>>>
>>>> Does the above make sense?
>>>> --
>>>> --henry schaffer
>
>
>
> - --
> - -------------------------------
> Josh Thompson
> Systems Programmer
> Virtual Computing Lab (VCL)
> North Carolina State University
>
> Josh_Thompson@ncsu.edu
> 919-515-5323
>
> my GPG/PGP key can be found at pgp.mit.edu
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.6 (GNU/Linux)
>
> iD8DBQFJY4RhV/LQcNdtPQMRAtNJAJ9CViggEk5XIPl5DH/Q+cL2JerOoQCbBHsv
> O7WjXdHQWfQ6B3uUTkTr9+g=
> =iwnz
> -----END PGP SIGNATURE-----
Re: VCL, is this name kosher?
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
On Feb 19, 2009, at 7:03 AM, Brian Bouterse wrote:
> Within the world of apache nothing. Do all acronyms drip with
> meaning in Apache or do some just pick a few letters?
You're being coy with me. It's obvious that the meaning of VCL is the
same as what NCSU uses.
> There hasn't been a lot of discussion on this topic, yet it needs
> resolution. When does this get put to vote?
You will not get my binding vote. I suspect you may have difficulty
getting other binding votes when you try to push this issue through in
this manner.
Regards,
Alan
>
>
> Best,
> Brian
>
> Brian Bouterse
> Secure Open Systems Initiative
> 919.698.8796
>
>
>
>
> On Feb 18, 2009, at 11:12 PM, Alan D. Cabrera wrote:
>
>> What does VCL stand for then?
>>
>>
>> Regards,
>> Alan
>>
>> On Feb 17, 2009, at 7:35 AM, Brian Bouterse wrote:
>>
>>> I wanted to revisit this thread, because no conclusion was
>>> reached. The current status is that after much discussion on the
>>> list, no name changes were proposed, or ratified.
>>>
>>> There are ASF naming guidelines located here. Personally, I
>>> interpret this as a non-issue because the NCSU service is called
>>> the "Virtual Computing Lab," and the ASF project name is "VCL"
>>> which is not the same.
>>>
>>> What do you think?
>>>
>>> my 2 cents,
>>> Brian
>>>
>>> Brian Bouterse
>>> Secure Open Systems Initiative
>>> 919.698.8796
>>>
>>>
>>>
>>>
>>> On Jan 6, 2009, at 11:18 AM, Josh Thompson wrote:
>>>
>>>> -----BEGIN PGP SIGNED MESSAGE-----
>>>> Hash: SHA1
>>>>
>>>> Maybe we should look at this from a different angle - is there
>>>> anything that
>>>> *can* happen for the name to continue as "VCL" at ASF?
>>>>
>>>> Josh
>>>>
>>>> On Tuesday January 06, 2009, Alan D. Cabrera wrote:
>>>>> 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.
>>>>>
>>>>>
>>>>> Regards,
>>>>> Alan
>>>>>
>>>>> On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote:
>>>>>> Alan,
>>>>>>
>>>>>> 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
>>>>>> reverse order.
>>>>>>
>>>>>> 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:
>>>>>>> Alan writes:
>>>>>>>> ...
>>>>>>>> If VCL is a trademark owned by NCSU then they would have to
>>>>>>>> assign
>>>>>>>> the
>>>>>>>> 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
>>>>>>> ownership
>>>>>>> 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
>>>>>>> use
>>>>>>> "AVCL" ("Apache VCL") as the name? (Or some other formulation
>>>>>>> which
>>>>>>> would be an Apache name but clearly portray to users and
>>>>>>> potential
>>>>>>> users
>>>>>>> that it's the same project.)
>>>>>>>
>>>>>>> Does the above make sense?
>>>>>>> --
>>>>>>> --henry schaffer
>>>>
>>>>
>>>>
>>>> - --
>>>> - -------------------------------
>>>> Josh Thompson
>>>> Systems Programmer
>>>> Virtual Computing Lab (VCL)
>>>> North Carolina State University
>>>>
>>>> Josh_Thompson@ncsu.edu
>>>> 919-515-5323
>>>>
>>>> my GPG/PGP key can be found at pgp.mit.edu
>>>> -----BEGIN PGP SIGNATURE-----
>>>> Version: GnuPG v1.4.6 (GNU/Linux)
>>>>
>>>> iD8DBQFJY4RhV/LQcNdtPQMRAtNJAJ9CViggEk5XIPl5DH/Q+cL2JerOoQCbBHsv
>>>> O7WjXdHQWfQ6B3uUTkTr9+g=
>>>> =iwnz
>>>> -----END PGP SIGNATURE-----
>>>
>>
>
>
Re: VCL, is this name kosher?
Posted by Brian Bouterse <bm...@ncsu.edu>.
Within the world of apache nothing. Do all acronyms drip with meaning
in Apache or do some just pick a few letters?
There hasn't been a lot of discussion on this topic, yet it needs
resolution. When does this get put to vote?
Best,
Brian
Brian Bouterse
Secure Open Systems Initiative
919.698.8796
On Feb 18, 2009, at 11:12 PM, Alan D. Cabrera wrote:
> What does VCL stand for then?
>
>
> Regards,
> Alan
>
> On Feb 17, 2009, at 7:35 AM, Brian Bouterse wrote:
>
>> I wanted to revisit this thread, because no conclusion was
>> reached. The current status is that after much discussion on the
>> list, no name changes were proposed, or ratified.
>>
>> There are ASF naming guidelines located here. Personally, I
>> interpret this as a non-issue because the NCSU service is called
>> the "Virtual Computing Lab," and the ASF project name is "VCL"
>> which is not the same.
>>
>> What do you think?
>>
>> my 2 cents,
>> Brian
>>
>> Brian Bouterse
>> Secure Open Systems Initiative
>> 919.698.8796
>>
>>
>>
>>
>> On Jan 6, 2009, at 11:18 AM, Josh Thompson wrote:
>>
>>> -----BEGIN PGP SIGNED MESSAGE-----
>>> Hash: SHA1
>>>
>>> Maybe we should look at this from a different angle - is there
>>> anything that
>>> *can* happen for the name to continue as "VCL" at ASF?
>>>
>>> Josh
>>>
>>> On Tuesday January 06, 2009, Alan D. Cabrera wrote:
>>>> 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.
>>>>
>>>>
>>>> Regards,
>>>> Alan
>>>>
>>>> On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote:
>>>>> Alan,
>>>>>
>>>>> 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
>>>>> reverse order.
>>>>>
>>>>> 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:
>>>>>> Alan writes:
>>>>>>> ...
>>>>>>> If VCL is a trademark owned by NCSU then they would have to
>>>>>>> assign
>>>>>>> the
>>>>>>> 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
>>>>>> ownership
>>>>>> 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
>>>>>> use
>>>>>> "AVCL" ("Apache VCL") as the name? (Or some other formulation
>>>>>> which
>>>>>> would be an Apache name but clearly portray to users and
>>>>>> potential
>>>>>> users
>>>>>> that it's the same project.)
>>>>>>
>>>>>> Does the above make sense?
>>>>>> --
>>>>>> --henry schaffer
>>>
>>>
>>>
>>> - --
>>> - -------------------------------
>>> Josh Thompson
>>> Systems Programmer
>>> Virtual Computing Lab (VCL)
>>> North Carolina State University
>>>
>>> Josh_Thompson@ncsu.edu
>>> 919-515-5323
>>>
>>> my GPG/PGP key can be found at pgp.mit.edu
>>> -----BEGIN PGP SIGNATURE-----
>>> Version: GnuPG v1.4.6 (GNU/Linux)
>>>
>>> iD8DBQFJY4RhV/LQcNdtPQMRAtNJAJ9CViggEk5XIPl5DH/Q+cL2JerOoQCbBHsv
>>> O7WjXdHQWfQ6B3uUTkTr9+g=
>>> =iwnz
>>> -----END PGP SIGNATURE-----
>>
>
Re: VCL, is this name kosher?
Posted by "Alan D. Cabrera" <li...@toolazydogs.com>.
What does VCL stand for then?
Regards,
Alan
On Feb 17, 2009, at 7:35 AM, Brian Bouterse wrote:
> I wanted to revisit this thread, because no conclusion was reached.
> The current status is that after much discussion on the list, no
> name changes were proposed, or ratified.
>
> There are ASF naming guidelines located here. Personally, I
> interpret this as a non-issue because the NCSU service is called the
> "Virtual Computing Lab," and the ASF project name is "VCL" which is
> not the same.
>
> What do you think?
>
> my 2 cents,
> Brian
>
> Brian Bouterse
> Secure Open Systems Initiative
> 919.698.8796
>
>
>
>
> On Jan 6, 2009, at 11:18 AM, Josh Thompson wrote:
>
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Maybe we should look at this from a different angle - is there
>> anything that
>> *can* happen for the name to continue as "VCL" at ASF?
>>
>> Josh
>>
>> On Tuesday January 06, 2009, Alan D. Cabrera wrote:
>>> 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.
>>>
>>>
>>> Regards,
>>> Alan
>>>
>>> On Dec 19, 2008, at 1:01 PM, Matt Hogstrom wrote:
>>>> Alan,
>>>>
>>>> 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
>>>> reverse order.
>>>>
>>>> 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:
>>>>> Alan writes:
>>>>>> ...
>>>>>> If VCL is a trademark owned by NCSU then they would have to
>>>>>> assign
>>>>>> the
>>>>>> 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
>>>>> ownership
>>>>> 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
>>>>> use
>>>>> "AVCL" ("Apache VCL") as the name? (Or some other formulation
>>>>> which
>>>>> would be an Apache name but clearly portray to users and potential
>>>>> users
>>>>> that it's the same project.)
>>>>>
>>>>> Does the above make sense?
>>>>> --
>>>>> --henry schaffer
>>
>>
>>
>> - --
>> - -------------------------------
>> Josh Thompson
>> Systems Programmer
>> Virtual Computing Lab (VCL)
>> North Carolina State University
>>
>> Josh_Thompson@ncsu.edu
>> 919-515-5323
>>
>> my GPG/PGP key can be found at pgp.mit.edu
>> -----BEGIN PGP SIGNATURE-----
>> Version: GnuPG v1.4.6 (GNU/Linux)
>>
>> iD8DBQFJY4RhV/LQcNdtPQMRAtNJAJ9CViggEk5XIPl5DH/Q+cL2JerOoQCbBHsv
>> O7WjXdHQWfQ6B3uUTkTr9+g=
>> =iwnz
>> -----END PGP SIGNATURE-----
>