Jump to: navigation, search

Governance/Foundation/IncubationUpdate2013

< Governance‎ | Foundation
Revision as of 16:27, 18 December 2012 by AlanClark (talk)

Committee Description and Scope

Now that the OpenStack Foundation is launched, and the Technical Committee (TC) and OpenStack Board are formed it is important to update the Incubator process to better align with the bylaws and mission of the OpenStack Foundation.

Perceptions around the current defined Incubator process have grown to infer that a project must either graduate to the status of an OpenStack Core Project (Core) or it must eventually fail to make progress or becomeabandoned. This perception needs to change and the Incubator process updated. The OpenStack community will grow to contain many projects critical to the success of OpenStack but in which it will not be prudent nor necessary to be destined for Core.

Since the bylaws define that the TC exercises the authority to add, combine, delete, or split modules from the OpenStack Project and as it is the responsibility of the Board to approve or reject additions, combinations, splits and deletions from the Core OpenStack Project it is important to update the current Incubator process to enable and promote efforts within the community while facilitating the TC and Board to work together for the proper advancement of OpenStack technologies.

Specifically the OpenStack Board and TC is asking that we work together to examine the current incubator process. The scope of the effort should include:

  1. Update the definition and terms of the Incubator process
  2. Level set Incubator status expectations
  3. Refine the definition of Core
  4. Define multiple avenues for project entry, growth and incubator exit
  5. Upon completion of the effort, the TC and Board will approve, publish and promote the updated process

Communication Channels:

  • foundation@lists.openstack.org
    • Please use this mail list to make comments and feedback to the committee
    • The committtee will provide meeting summaries and updates to this mail list
  • This wiki page (Governance/Foundation/IncubationUpdate2013)
    • Location for the meeting agendas and committee approved information and updates
  • Etherpad (https://etherpad.openstack.org/IncUp)
    • For meeting discussion and note taking, draft materials, etc.
Committee meetings
  • Held weekly on Thursdays 8am pacific
  • Agenda's are kept on this wiki page

Committee Members

Secretary:

  • Alan Clark

Board members (3):

  • Monty Taylor
  • Rob Hirshfield (Alternate)
  • Randy Bias
  • Boris Renski (Alternate)
  • Kyle MacDonald
  • Eileen Evans (Alternate)

TC members (3):

  • Anne Gentle
  • Mark McLoughlin
  • Thierry Carrez
  • Russell Bryant (Alternate)

Other:

  • Jonathan Bryce
  • Mark Collier (Alternate)

December 20th 8am pacific Committee Meeting Agenda

Bylaws definition of Core

  • The “OpenStack Project” shall consist of a “Core OpenStack Project,” library projects, gating projects and supporting projects. . The Core OpenStack Project means the software modules which are part of an integrated release and for which an OpenStack trademark may be used. The other modules which are part of the OpenStack Project, but not the Core OpenStack Project may not be identified using the OpenStack trademark except when distributed with the Core OpenStack Project. ... On formation of the Foundation, the Core OpenStack Project is the Block Storage, Compute, Dashboard, Identity Service, Image Service, Networking, and Object Storage modules. 1. Get to the heart of Core
    1. Who the users are:
    2. Is core the ultimate destination from Incubation or simply one of many?
      1. Reference: http://wiki.openstack.org/Projects/
      2. Should we keep the concept of a project being "part of the OpenStack project" separate from the concept of "required in all OpenStack(r) clouds" and if so how do we achieve that?"
  • Expectations of core
    1. projects follow process / defined lifecycle
    2. set of projects part of integrated release
    3. essential to run cloud (anything beyond that can't be core)
    4. Trademark
    5. API

January XX Committee Meeting Agenda


December 6th Committee Meeting Agenda

Attendees: Alan Clark, Monty Taylor, Russell Bryant (listening, since ttx was able to join), Mark McLoughlin, Anne Gentle, Thierry Carrez, Rob Hirschfeld (listening), RandyB

  1. Introductions - AlanClark
  2. Keeping community updated and involved - AlanClark
    • Discussion Results:<
      > - Discussion resulted in the following:
    • - markmc will send an email to openstack-dev and openstack-tc lists informing them of the committee effort and that if interested in this topic they should join the foundation mailing list; informing everyone that the email postings on the foundation mailing list will be used as the mechanism to gather feedback to the committee. (alan will leverage markmc email to send similar email to the board) - alan will send a summary update to the foundation mailing list after each meeting pointing to the etherpad and wiki page for the meeting content. - markmc and others will blog throughout the process
  3. Future meeting logistics: dates/times/frequency - AlanClark
    • Discussion Results: <
      > - Plan for at lest 6 weekly meetings - The committee will meet on Thursdays 8am pacific including Thursday December 13.
  4. Committee Scope - AlanClark
    • Discussion Results:' <
      > - The committee reviewed and approved the scope as written at the top of this wiki page
  5. Develop a basis of understanding of how things work today and the current issue 1. Review of the current Incubator process - Mark
    1. What we expect from Incubating projects, how we help them and how we decide whether they're ready to graduate
    2. What "Core" currently means and why the term is causing confusion
      1. Learning from others: Should we invite LSB, Eclipse or ASF to discuss how they address this similar question?
  6. How the TC and Board see the project growing over time <
    >Discussion Results: - This agenda item was not completed. Discussion will continue at the next meeting. Discussion notes are on the etherpad. Action item for each committee member is to update the etherpad to help minimize the time needed for this topic during the next meeting. https://etherpad.openstack.org/IncUp
  7. Should we keep the concept of a project being "part of the OpenStack project" separate from the concept of "required in all OpenStack(tm) clouds" and if so how do we achieve that?"
    • Discussion Results:' <
      > - This agenda item was not discussed during this meeting - pushed to next meeting

December 13th 8am pacific Committee Meeting

Attendees: Alan, Boris, Eilieen, Jonathan, Mark Atwood, Mark Collier, Mark McLoughlin, Monty, Rob, Thierry

Agenda:

  1. Develop a basis of understanding of how things work today and the current issue
    1. (Continued) Review of the current Incubator process - Mark
    2. What we expect from Incubating projects, how we help them and how we decide whether they're ready to graduate
    3. What "Core" currently means and why the term is causing confusion Learning from others: Should we invite LSB, Eclipse or ASF to discuss how they address this similar question?
    4. How the TC and Board see the project growing over time.
  2. Should we keep the concept of a project being "part of the OpenStack project" separate from the concept of "required in all OpenStack(r) clouds" and if so how do we achieve that?"

Meeting Notes:

New projects enter into the OpenStack community through the OpenStack Project Expansion Process. This is the process how a project was approved for core before the bylaws came into being: http://wiki.openstack.org/Governance/Approved/NewProjectProcessThe new project process includes the current Incubation process as defined at:http://wiki.openstack.org/Governance/Approved/IncubationAs the Incubation page outlines, to enter the incubacation process the project submitts the following application:http://wiki.openstack.org/Projects/IncubatorApplicationPrior to Incubatioin projects are able to utilize the following Openstack resources: * CI via stackforge

Resources used from OpenStack as part of the incubation process: * Release manager help and training (incl. in weekly release status meeting)

  • CI
  • CI testing
  • Infrastructure team starts caring
  • openstack github org namespace
  • PTL or co-leads are named (not on TC)
  • PTL guide: http://wiki.openstack.org/PTLguide
  • Release cycle: http://wiki.openstack.org/ReleaseCycle
  • Branch model: http://wiki.openstack.org/BranchModel
  • Release process: http://wiki.openstack.org/ReleaseTeam/HowToRelease
  • CI docs: http://ci.openstack.org/
  • Doc: provide guidance for tooling but not doc work
  • Integration: jenkins jobs
  • Weekly release team meeting tracking time
    • daily tracking, release definitions through blueprint tagging, an overall release schedule, and time at the weekly Project meeting - Incubated = Priority 2 for release manager
  • DevStack as possible integration testing
  • Committeed projects are given room at Summits to 'incorporate' and discuss; have some access to rooms to collaborate, depend upon need.
  • testing gated via DevStack
  • Gate testing
    • qualitative measurement is done per project . TC mainly gages alignment with project processes and resources
  • No formal trademark search today. Before a project becomes associated with OpenStack need a process for this.earlier the better. Projects can always be renamed, but the earlier the better.
  • If project goes through Stackforge, CLA is signed in order to use that Gerrit-based system

By end of incubation the project should be able to be part of the devstack integration testing gate, meaning it should consistently work with and not break the other projects- website descriptions at http://www.openstack.org/software/