Difference between revisions of "Working Group Template"

Latest revision as of 14:42, 22 October 2016

Status: {Forming, Active, Ended}

'Co-Chairs:

 * Name Surname <Name.Surname@example.org>
 * Name Surname <Name.Surname@example.org>

As the first paragraph, give a clear statement on the purpose of your working group, including specific, detailed outcomes.

Please make a clear statement on which user group, audiences, professions, and/or sectors which your Working Group is aimed at supporting.

Scope

Specify which items are in *and out* of scope for this working group. It it important to avoid overlap and duplication of efforts with other working groups.

How to Join

Give some simple instructions on how a prospective new member could join the working group.

NB By default Working Groups should have all members join the user-committee mailing list where all user-committee activity is overseen by the User Committee.

Structure

Is your group a single group, or are there multiple sub-groups? Is your WG time based with multiple phases (will take place over several summit cycles)?

For each part of your working group structure, please ensure you list organisers (e.g. co-chairs or scribe) and nominated persons.

@@ Line 1: / Line 1: @@
-'''Status''': {Forming}
+'''Status''': {Forming, Active, Ended}
 '''Co-Chairs'':
-   * Jamey McCabe <jm6819@att.com>
+   * Name Surname <Name.Surname@example.org>
-  * Cecilia Comeau <cc0943@att.com>
+   * Name Surname <Name.Surname@example.org>
-   * Shilla Saebi <Shilla.Saebi@gmail.com>
-==Mission and Scope==
+As the first paragraph, give a clear statement on the purpose of your working group, including specific, detailed outcomes.
-The working group aims to define the use cases and identify and prioritise the requirements which are needed to deploy, manage, and run telecommunication services on top of OpenStack. This work includes identifying functional gaps, creating blueprints, submitting and reviewing patches to the relevant OpenStack projects and tracking their completion in support of telecommunication services.
-==Key Tenets==
+Please make a clear statement on which user group, audiences, professions, and/or sectors which your Working Group is aimed at supporting.
-'''Drive Community Roadmap Awareness'''
-The LCOO exists to drive Community awareness of platform enhancements necessary to meet the needs of Large “Multi-Clouds” Operators and Network Service Providers.  Multi-Clouds is defined as multiple regions, availability zones and multi-tenant in OpenStack.  LCOO does this through the publishing of its use cases and Roadmap as well as by participating in and contributing thought leadership to OpenStack community Working Groups, Project Teams and other OpenStack groups. The LCOO also leverages blogs, white papers, Summit presentations, Summit presence and any other practical means to carry its message to the broad community.
-'''Drive Focused OpenStack Enhancements'''
+==Scope==
-The LCOO works openly, transparently and collaboratively within the OpenStack community to be engaged in continuous enhancement of the OpenStack platform. The LCOO’s coordinates the upstream software development activities of its member’s resources in order to advance the platform while ensuring that efforts align with the spirit and goals of the OpenStack Foundation.
+Specify which items are in *and out* of scope for this working group. It it important to avoid overlap and duplication of efforts with other working groups.
-'''Increase Upstream Contributions to OpenStack'''
-The LCOO seeks to advance the OpenStack platform by building and growing a joint LCOO committed engineering team focused on a shared agenda of development that drives its overall mission forward, along a number of vectors:
-* Multisite Management and Operations including Upgradeability
-* Resiliency at Scale
-* Networking, SDN and NFV Infrastructure
-* Security, Policy and Operational Insights
-* Workload Enablement
-* Feature Requests and Bug fixes across all of the projects
-'''Accelerate OpenStack Innovation'''
-Through its multi-cultural, globally distributed and technologically diverse member companies, the LCOO creates an environment for its members that promotes far greater opportunity for innovation, learning, mentoring and accomplishment than would ever be possible by any member alone. This same large and diverse member coalition of community contributors is also able to engage much more deeply, broadly and effectively within the community in order to further its objectives of raising awareness and accelerating improvement.
 ==How to Join==
-Member companies should meet these criteria:
+Give some simple instructions on how a prospective new member could join the working group.
-* Be a Multi-Cloud Operator and/or Network Service Provider
-* Participate equally with other members in the meetings and other activities of the coalition
-* Be a contributor to the OpenStack platform with at least 4 FTEs contributing regularly
-* Contribute 2 FTEs to upstream activities aligned to the LCOO roadmap
-If a member should fail to continue to meet these minimum criteria after joining, their membership may be revoked through an action of the board. Add method of advocating for new members and new members to introduce and join here.
+NB By default Working Groups should have all members join the user-committee mailing list where all user-committee activity is overseen by the User Committee.
 ==Structure==
 Is your group a single group, or are there multiple sub-groups?
 Is your WG time based with multiple phases (will take place over several summit cycles)?
 For each part of your working group structure, please ensure you list organisers (e.g. co-chairs or scribe) and nominated persons.