settingsLogin | Registersettings

[OpenStack-DefCore] Interop - Guideline Rename Workstream

0 votes

Hello Everyone,

As part of our rename work stream, we need a standard way to refer to the guidelines provided by this group.

As we discussed in our last meeting [1]. “DefCore Guidelines” was a very specific name pointing to the guidelines from this group... so we need something at this level with the new name (not open to interpretation).
Some ideas:

· OpenStack Interop Guidelines

· Interoperability Guidelines

· Interop WG Guidelines

· Add label “Oficial” to differentiate our guideline from any other custom interop guideline.

Please let me know your comments, concerns or any question (if any).

[1] http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt

Thanks, Regards
Luz Cazares


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
asked Dec 2, 2016 in defcore-committee by Cazares,_Luz (380 points)  

5 Responses

0 votes

Hello Luz,

Thank you for working on this! I think "OpenStack Interoperability Guidelines" or just "Interoperability Guidelines" would work, but I am also interested to hear what others think.

Thank you,

Egle


From: Cazares, Luz luz.cazares@intel.com
Sent: Friday, December 2, 2016 12:43 PM
To: defcore-committee@lists.openstack.org
Subject: [OpenStack-DefCore] Interop - Guideline Rename Workstream

Hello Everyone,

As part of our rename work stream, we need a standard way to refer to the guidelines provided by this group.

As we discussed in our last meeting [1]. "DefCore Guidelines" was a very specific name pointing to the guidelines from this group... so we need something at this level with the new name (not open to interpretation).

Some ideas:

· OpenStack Interop Guidelines

· Interoperability Guidelines

· Interop WG Guidelines

· Add label "Oficial" to differentiate our guideline from any other custom interop guideline.

Please let me know your comments, concerns or any question (if any).

[1] http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt

Thanks, Regards

Luz Cazares


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Dec 6, 2016 by Egle_Sigler (2,300 points)   3
0 votes

On Dec 6, 2016, at 6:02 PM, Egle Sigler ushnishtha@hotmail.com wrote:

Hello Luz,

Thank you for working on this! I think "OpenStack Interoperability Guidelines”

Likewise. I also like the idea of providing a UI hint (a label, bold text, something) to make these a bit more distinct in the interface.

or just "Interoperability Guidelines" would work, but I am also interested to hear what others think.

Another thought: the Guidelines the Interop WG produces ultimately determine a product’s eligibility for the OpenStack Powered (TM) programs. We could refer to them as “OpenStack Powered (TM) Guidelines” which would help folks be clear on the relationship between the two.

At Your Service,

Mark T. Voelker

Thank you,
Egle

From: Cazares, Luz luz.cazares@intel.com
Sent: Friday, December 2, 2016 12:43 PM
To: defcore-committee@lists.openstack.org
Subject: [OpenStack-DefCore] Interop - Guideline Rename Workstream

Hello Everyone,

As part of our rename work stream, we need a standard way to refer to the guidelines provided by this group.

As we discussed in our last meeting [1]. “DefCore Guidelines” was a very specific name pointing to the guidelines from this group... so we need something at this level with the new name (not open to interpretation).
Some ideas:
· OpenStack Interop Guidelines
· Interoperability Guidelines
· Interop WG Guidelines
· Add label “Oficial” to differentiate our guideline from any other custom interop guideline.

Please let me know your comments, concerns or any question (if any).

[1] http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt

Thanks, Regards
Luz Cazares


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Dec 7, 2016 by Mark_Voelker (4,000 points)   2 3
0 votes

++ on using “OpenStack Powered (TM) Guidelines”. The name clearly
articulates the goal and the originator of the guidelines.

Catherine Diep
----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 12/07/2016 12:07 PM


From: Mark Voelker mvoelker@vmware.com
To: Egle Sigler ushnishtha@hotmail.com
Cc: "defcore-committee@lists.openstack.org"

Date: 12/07/2016 06:45 AM
Subject: Re: [OpenStack-DefCore] Interop - Guideline Rename Workstream

On Dec 6, 2016, at 6:02 PM, Egle Sigler ushnishtha@hotmail.com wrote:

Hello Luz,

Thank you for working on this! I think "OpenStack Interoperability
Guidelines”

Likewise. I also like the idea of providing a UI hint (a label, bold text,
something) to make these a bit more distinct in the interface.

or just "Interoperability Guidelines" would work, but I am also
interested to hear what others think.

Another thought: the Guidelines the Interop WG produces ultimately
determine a product’s eligibility for the OpenStack Powered (TM) programs.
We could refer to them as “OpenStack Powered (TM) Guidelines” which would
help folks be clear on the relationship between the two.

At Your Service,

Mark T. Voelker

Thank you,
Egle

From: Cazares, Luz luz.cazares@intel.com
Sent: Friday, December 2, 2016 12:43 PM
To: defcore-committee@lists.openstack.org
Subject: [OpenStack-DefCore] Interop - Guideline Rename Workstream

Hello Everyone,

As part of our rename work stream, we need a standard way to refer to the
guidelines provided by this group.

As we discussed in our last meeting [1]. “DefCore Guidelines” was a very
specific name pointing to the guidelines from this group... so we need
something at this level with the new name (not open to interpretation).
Some ideas:
· OpenStack Interop Guidelines
· Interoperability Guidelines
· Interop WG Guidelines
· Add label “Oficial” to differentiate our guideline from any
other custom interop guideline.

Please let me know your comments, concerns or any question (if any).

[1]
http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt

Thanks, Regards
Luz Cazares


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Dec 7, 2016 by Catherine_Cuong_Diep (1,320 points)   2
0 votes

I like that as well!

On Dec 7, 2016, at 3:01 PM, Catherine Cuong Diep cdiep@us.ibm.com wrote:

++ on using "OpenStack Powered (TM) Guidelines". The name clearly articulates the goal and the originator of the guidelines.

Catherine Diep
----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 12/07/2016 12:07 PM -----

From: Mark Voelker mvoelker@vmware.com
To: Egle Sigler ushnishtha@hotmail.com
Cc: "defcore-committee@lists.openstack.org" defcore-committee@lists.openstack.org
Date: 12/07/2016 06:45 AM
Subject: Re: [OpenStack-DefCore] Interop - Guideline Rename Workstream


On Dec 6, 2016, at 6:02 PM, Egle Sigler ushnishtha@hotmail.com wrote:

Hello Luz,

Thank you for working on this! I think "OpenStack Interoperability Guidelines"

Likewise. I also like the idea of providing a UI hint (a label, bold text, something) to make these a bit more distinct in the interface.

or just "Interoperability Guidelines" would work, but I am also interested to hear what others think.

Another thought: the Guidelines the Interop WG produces ultimately determine a product's eligibility for the OpenStack Powered (TM) programs. We could refer to them as "OpenStack Powered (TM) Guidelines" which would help folks be clear on the relationship between the two.

At Your Service,

Mark T. Voelker

Thank you,
Egle

From: Cazares, Luz luz.cazares@intel.com
Sent: Friday, December 2, 2016 12:43 PM
To: defcore-committee@lists.openstack.org
Subject: [OpenStack-DefCore] Interop - Guideline Rename Workstream

Hello Everyone,

As part of our rename work stream, we need a standard way to refer to the guidelines provided by this group.

As we discussed in our last meeting [1]. "DefCore Guidelines" was a very specific name pointing to the guidelines from this group... so we need something at this level with the new name (not open to interpretation).
Some ideas:
* OpenStack Interop Guidelines
* Interoperability Guidelines
* Interop WG Guidelines
* Add label "Oficial" to differentiate our guideline from any other custom interop guideline.

Please let me know your comments, concerns or any question (if any).

[1] http://eavesdrop.openstack.org/meetings/defcore/2016/defcore.2016-11-30-16.00.log.txt

Thanks, Regards
Luz Cazares


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Dec 8, 2016 by Egle_Sigler (2,300 points)   3
0 votes

I like it, too. I thought we needed something like that, but couldn't
think of a way to make it sound good. I was thinking more the legalese and
Mark found the right mix.

--rocky

On Wed, Dec 7, 2016 at 5:54 PM, Egle Sigler ushnishtha@hotmail.com wrote:

I like that as well!

On Dec 7, 2016, at 3:01 PM, Catherine Cuong Diep cdiep@us.ibm.com wrote:

++ on using “OpenStack Powered (TM) Guidelines”. The name clearly
articulates the goal and the originator of the guidelines.

Catherine Diep
----- Forwarded by Catherine Cuong Diep/San Jose/IBM on 12/07/2016 12:07
PM -----

From: Mark Voelker mvoelker@vmware.com
To: Egle Sigler ushnishtha@hotmail.com
Cc: "defcore-committee@lists.openstack.org" <defcore-committee@lists.
openstack.org>
Date: 12/07/2016 06:45 AM
Subject: Re: [OpenStack-DefCore] Interop - Guideline Rename Workstream


On Dec 6, 2016, at 6:02 PM, Egle Sigler ushnishtha@hotmail.com wrote:

Hello Luz,

Thank you for working on this! I think "OpenStack Interoperability
Guidelines”

Likewise. I also like the idea of providing a UI hint (a label, bold
text, something) to make these a bit more distinct in the interface.

or just "Interoperability Guidelines" would work, but I am also
interested to hear what others think.

Another thought: the Guidelines the Interop WG produces ultimately
determine a product’s eligibility for the OpenStack Powered (TM) programs.
We could refer to them as “OpenStack Powered (TM) Guidelines” which would
help folks be clear on the relationship between the two.

At Your Service,

Mark T. Voelker

Thank you,
Egle

From: Cazares, Luz luz.cazares@intel.com
Sent: Friday, December 2, 2016 12:43 PM
To: defcore-committee@lists.openstack.org
Subject: [OpenStack-DefCore] Interop - Guideline Rename Workstream

Hello Everyone,

As part of our rename work stream, we need a standard way to refer to
the guidelines provided by this group.

As we discussed in our last meeting [1]. “DefCore Guidelines” was a very
specific name pointing to the guidelines from this group... so we need
something at this level with the new name (not open to interpretation).
Some ideas:
· OpenStack Interop Guidelines
· Interoperability Guidelines
· Interop WG Guidelines
· Add label “Oficial” to differentiate our guideline from any
other custom interop guideline.

Please let me know your comments, concerns or any question (if any).

[1] http://eavesdrop.openstack.org/meetings/defcore/2016/
defcore.2016-11-30-16.00.log.txt

Thanks, Regards
Luz Cazares


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee


Defcore-committee mailing list
Defcore-committee@lists.openstack.org
http://lists.openstack.org/cgi-bin/mailman/listinfo/defcore-committee
responded Dec 8, 2016 by rockyg_at_gmail.com (340 points)   1
...