Open Stack

+1

-- 
Jon Benedict
Technical Marketing Engineer, NetApp
Red Hat Technologies
Data Center Platforms

Internal Portal http://redhatnetapp.com
Blog http://captainkvm.com | Twitter @CaptainKVM






On 12/3/13 6:47 AM, "Dave Neary" <dneary at redhat.com> wrote:

>Hi Stefano,
>
>I know that in general the decision has been not to use code names at
>all in "official" communications, but I for one would have found it
>useful when first joining the project to have a page somewhere that
>listed all the project name -> codename relationships - on all the
>developer facing pages only the codenames are used (nova, swift, cinder,
>etc) and on the non-developer facing pages only project names are used
>(compute, object storage, block storage) - and nowhere is there an
>equivalence made between the two ("Heat = Orchestration", "Neutron =
>Networking", etc).
>
>Do you think there's a place for that somewhere?
>
>Cheers,
>Dave.
>
>
>On 12/03/2013 02:20 AM, Stefano Maffulli wrote:
>> On 12/02/2013 02:01 PM, Jeff Jameson wrote:
>>> Okay, I think I understand this now. From a marketing perspective,
>>> the primary project name is not changing.
>> 
>> I apologize for not spending more time carefully crafting my message to
>> this list before sending it. Let me try to clarify.
>> 
>> A while ago there was a decision to officially refer to the various
>> openstack components with their service names, as opposed to their code
>> names. The service name is usually a generic English term that
>> identifies the service provided by the code base. For example, OpenStack
>> marketing material calls the virtual computing service "OpenStack
>> Compute" while the codebase is called Nova. Block Storage instead of
>> Cinder, Object Storage instead of Swift, etc. Check
>> http://openstack.org/start for example.
>> 
>> Since the issues we had with quantum/neutron the decision was to always
>> put more emphasis on the OpenStack <SERVICE> names instead of using the
>> (quite obscure) names of the code base. The <SERVICE> names are also
>> better at conveying what use is the code for and, since they're
>> prepended by the term OpenStack, they also reinforce the brand.
>> 
>> Going back to ceilometer, the name of the code base is *not* changing.
>> What the Technical Committee changed is the name of the program[1] into
>> 'Telemetry', from Metering.
>> 
>> Since Metering is used as the 'official' name for the service provided
>> by the code Ceilometer I sent the message earlier to inform the
>> Marketing community that you may start seeing people calling ceilometer
>> "Telemetry" and that it may be necessary to update some material, like
>> the website. Hope I've made things clearer now.
>> 
>> Cheers,
>> stef
>> 
>> 
>> [1] there is a difference between a program and a project in OpenStack
>> but I prefer not to address that now. If you're interested in learning
>> more about OpenStack Programs read
>> https://wiki.openstack.org/wiki/Programs
>> 
>> 
>
>-- 
>Dave Neary - Community Action and Impact
>Open Source and Standards, Red Hat - http://community.redhat.com
>Ph: +33 9 50 71 55 62 / Cell: +33 6 77 01 92 13
>
>_______________________________________________
>Marketing mailing list
>Marketing at lists.openstack.org
>http://lists.openstack.org/cgi-bin/mailman/listinfo/marketing