Open Stack

As I said before,

why not run it as the OSSG is ran?  an opt in group that can work together
to focus on initiatives related to operators needs / wants?

an OSOG ( OpenStack Operators Group ).  If we want to target development or
documentation efforts we can coordinate there.  Also surveys / possibly
setting up something like the UX team for horizon.  A group that cleans up
tickets and provides better information for developers.  Become a resource
with a structured involvement.

One of the reasons I think this ad hoc method works best is that there is
so much variety in operators.  We don't want the rackspaces, and HPs for
the world dominating the discussion / goals.  We want the little guys to be
able to contribute meaningfully.

Thoughts?

-Matt


On Mon, Mar 31, 2014 at 10:43 AM, Joe Topjian <joe at topjian.net> wrote:

>
> As I see it there's (at least) three major community segments, from
>> smallest to largest:
>>
>> * Developer, who write the code
>> * Operators/Administrators/(pick your title), who build and maintain
>> production clouds
>> * Users who actually deploy applications on top of the cloud
>>
>
> +1
>
> _______________________________________________
> OpenStack-operators mailing list
> OpenStack-operators at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20140331/ec48e90a/attachment.html>