Governance/Foundation/IncubationUpdate2013 - Revision history

Alan Clark: /* Project Inclusion Processes */

2013-04-08T21:06:59Z

‎Project Inclusion Processes

Alan Clark: added diagram

2013-04-03T19:45:22Z

added diagram

Alan Clark: Updated page to show final report

2013-04-03T19:42:39Z

Updated page to show final report

Show changes

Ryan Lane: Text replace - "DevStack" to "DevStack"

2013-02-17T23:32:33Z

Text replace - "DevStack" to "DevStack"

Ryan Lane: Text replace - "NOTOC" to ""

2013-02-17T23:29:25Z

Text replace - "__NOTOC__" to ""

AlanClark: fixed spelling

2013-01-16T00:07:13Z

fixed spelling

AlanClark at 00:35, 15 January 2013

2013-01-15T00:35:26Z

AlanClark at 15:48, 10 January 2013

2013-01-10T15:48:36Z

AlanClark at 15:17, 10 January 2013

2013-01-10T15:17:45Z

Doug: typo

2013-01-09T17:04:59Z

typo

@@ Line 64: / Line 64: @@
 | style="border-top:none;border-bottom:0.05pt solid #000000;border-left:0.05pt solid #000000;border-right:none;padding:0.0382in;"|
 * Ceilometer
 * Heat

← Older revision		Revision as of 19:45, 3 April 2013
Line 85:		Line 85:


−	[[Image:]]	+	[[Image:IncUpDiagram1.png]]

	Note that library projects and supporting projects do not go through incubation but should undergo many of the same steps, gating and processes including trademark review.		Note that library projects and supporting projects do not go through incubation but should undergo many of the same steps, gating and processes including trademark review.

@@ Line 135: / Line 135: @@
 * 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
+* 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]]
+* testing gated via DevStack
 * Gate testing
 ** qualitative measurement is done per project . TC mainly gages alignment with project processes and resources

@@ Line 1: / Line 1: @@
-__NOTOC__
 === 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.

@@ Line 118: / Line 118: @@
 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
+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/Incubation As the Incubation page outlines, to enter the incubation process the project submits the following application:http://wiki.openstack.org/Projects/IncubatorApplicationPrior to Incubation 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)

@@ Line 53: / Line 53: @@
 * Mark Collier (Alternate)
-=== January 10 Committee Meeting Agenda ===
+=== January 10-17 Committee Meeting Agenda ===
-* 1.user 'of core' experiences / Use cases
+* 1.user 'of core' experiences / Use cases<<BR>>
 *# Discuss user experiences / use cases
 * Which model?

@@ Line 52: / Line 52: @@
 * Jonathan Bryce
 * Mark Collier (Alternate)
 === December 20th 8am pacific Committee Meeting Agenda ===
 Bylaws definition of Core
@@ Line 69: / Line 84: @@
 *# Trademark
 *# API
 === December 6th Committee Meeting Agenda ===

@@ Line 71: / Line 71: @@
 === January XX Committee Meeting Agenda ===
+.user 'of core' experiences / Use cases
+# Homework - identify and prepare use cases for discussions
 ----

@@ Line 3: / Line 3: @@
 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.
+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 become abandoned.  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.