Open Stack

FYI..
https://wiki.openstack.org/wiki/LCOO

Also listed under UC:
https://wiki.openstack.org/wiki/Governance/Foundation/UserCommittee#Structure

Current LCOO collaboration tool:
https://openstack-lcoo.atlassian.net/

This is a "relatively new" working group and we are recently engaged and
helping the team to integrate with the community.

Thanks!


On Mon, Feb 6, 2017 at 8:37 AM, Steven Dake (stdake) <stdake at cisco.com>
wrote:

> Jay,
>
> I don’t see a reference to the wiki page in your email and don’t
> immediately see the LCOO working group wiki.  From what you describe this
> working group is not working within the framework of the 4 opens which is
> one of OpenStack’s fundamental philosophies.
>
> Thanks for bringing up your questions; I hope someone that represents this
> group can at least get this working group operating within the 4 opens
> framework if they are not already.
>
> Regards
> -steve
>
>
> -----Original Message-----
> From: Jay Pipes <jaypipes at gmail.com>
> Reply-To: "OpenStack Development Mailing List (not for usage questions)" <
> openstack-dev at lists.openstack.org>
> Date: Thursday, February 2, 2017 at 1:14 PM
> To: OpenStack Development Mailing List <openstack-dev at lists.openstack.org>,
> "openstack-operators at lists.openstack.org" <openstack-operators at lists.
> openstack.org>
> Subject: [openstack-dev] Large Contributing OpenStack Operators working
> group?
>
>     Hi,
>
>     I was told about this group today. I have a few questions. Hopefully
>     someone from this team can illuminate me with some answers.
>
>     1) What is the purpose of this group? The wiki states that the team
>     "aims to define the use cases and identify and prioritise the
>     requirements which are needed to deploy, manage, and run services on
> top
>     of OpenStack. This work includes identifying functional gaps, creating
>     blueprints, submitting and reviewing patches to the relevant OpenStack
>     projects, contributing to working those items, tracking their
> completion."
>
>     What is the difference between the LCOO and the following existing
>     working groups?
>
>       * Large Deployment Team
>       * Massively Distributed Team
>       * Product Working Group
>       * Telco/NFV Working Group
>
>     2) According to the wiki page, only companies that are "Multi-Cloud
>     Operator[s] and/or Network Service Provider[s]" are welcome in this
>     team. Why is the team called "Large Contributing OpenStack Operators"
> if
>     it's only for Telcos? Further, if this is truly only for Telcos, why
>     isn't the Telco/NFV working group appropriate?
>
>     3) Under the "Guiding principles" section of the above wiki, the top
>     principle is "Align with the OpenStack Foundation". If this is the
> case,
>     why did the group move its content to the closed Atlassian Confuence
>     platform? Why does the group have a set of separate Slack channels
>     instead of using the OpenStack mailing lists and IRC channels? Why is
>     the OPNFV Jira used for tracking work items for the LCOO agenda?
>
>     See https://wiki.openstack.org/wiki/Gluon/Tasks-Ocata for examples.
>
>     4) I see a lot of agenda items around projects like Gluon, Craton,
>     Watcher, and Blazar. I don't see any concrete ideas about talking with
>     the developers of the key infrastructure services that OpenStack is
>     built around. How does the LCOO plan on reaching out to the developers
>     of the long-standing OpenStack projects like Nova, Neutron, Cinder, and
>     Keystone to drive their shared agenda?
>
>     Thanks for reading and (hopefully) answering.
>
>     -jay
>
>     ____________________________________________________________
> ______________
>     OpenStack Development Mailing List (not for usage questions)
>     Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:
> unsubscribe
>     http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20170206/fc492d0f/attachment-0001.html>