{"type":"doc","content":[{"type":"panel","attrs":{"panelType":"info"},"content":[{"type":"paragraph","content":[{"text":"IMPORTANT: This 2013 document is a DRAFT and should not be considered final or official in any way. ","type":"text"}]}]},{"type":"bodiedExtension","attrs":{"extensionType":"com.atlassian.confluence.macro.core","extensionKey":"section","parameters":{"macroParams":{},"macroMetadata":{"schemaVersion":{"value":"1"},"title":"Section"}}},"content":[{"type":"extension","attrs":{"extensionType":"com.atlassian.confluence.migration","extensionKey":"legacy-content","text":"","parameters":{"reason":"A column macro in a rich body macro can't be created or edited in the new editor.","nestedContent":{"type":"doc","content":[{"type":"bodiedExtension","attrs":{"extensionType":"com.atlassian.confluence.macro.core","extensionKey":"column","parameters":{"macroParams":{"width":{"value":"60%"}},"macroMetadata":{"schemaVersion":{"value":"1"},"title":"Column"}}},"content":[{"type":"heading","attrs":{"level":2},"content":[{"text":"Introduction","type":"text"}]},{"type":"paragraph","content":[{"text":"Credit: Much of this proposed project lifecycle has been initially adapted from the ","type":"text","marks":[{"type":"em"}]},{"text":"Eclipse Development Process","type":"text","marks":[{"type":"link","attrs":{"href":"http://www.eclipse.org/projects/dev_process/development_process_2011.php"}},{"type":"em"}]},{"text":".","type":"text","marks":[{"type":"em"}]},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"The OpenMRS community is the sum of all of its constituent projects, including the OpenMRS core platform, add-on modules, distributions, and other tools and services used by the community. ","type":"text"},{"text":"One of the OpenMRS community values is stated as, \"We are open, honest, and transparent in both our processes and our software.\" In accordance with that value, we have adopted a stated process of how projects in the community can be created, how they can grow, and how they can be managed to help realize our values, mission, and vision. This project lifecycle process is intended to help projects:","type":"text"}]},{"type":"bulletList","content":[{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Communicate their project plans and feature roadmaps in a timely, open, and transparent way","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Create software that helps move the OpenMRS platform forward","type":"text"}]}]},{"type":"listItem","content":[{"type":"paragraph","content":[{"text":"Provide technology tools that help meet the values, mission, and vision of OpenMRS","type":"text"}]}]}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Phases of Projects","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":" ","type":"text"},{"text":"Pre-Proposal","type":"text"}]},{"type":"paragraph","content":[{"text":"This is not really a project phase per se, but describes the ideas that exist in the minds of one or more people in the OpenMRS community before they are documented. ","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Proposed","type":"text"}]},{"type":"paragraph","content":[{"text":"To be described.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Incubation","type":"text"}]},{"type":"paragraph","content":[{"text":"To be described.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Mature","type":"text"}]},{"type":"paragraph","content":[{"text":"To be described.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Top-Level","type":"text"}]},{"type":"paragraph","content":[{"text":"Projects that have demonstrated the characteristics of a Top-Level Project (e.g., consistent leadership in a technical area and the recruitment of a wider developer community) can be promoted to Top-Level Project status. This promotion occurs through a Promotion Review. Upon the successful completion of a Promotion Review, OpenMRS Leadership may recommend that the project be promoted and ask that its Charter be reviewed and approved.","type":"text"},{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":"Top-Level Project has a Charter which describes the purpose, Scope, and operational rules for the Top-Level Project. The Charter should refer to, and describe any refinements to, the provisions of this Development Process. The Board approves the Charter of each Top-Level Project.","type":"text"}]},{"type":"paragraph","content":[{"text":"Top-Level Projects cannot be incubated and can only be created from one or more existing Mature-phase Projects.","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Archived","type":"text"}]},{"type":"paragraph","content":[{"text":"Projects that become inactive, either through dwindling resources or by reaching their natural conclusion, are ","type":"text"},{"text":"archived","type":"text","marks":[{"type":"strong"}]},{"text":". Projects can reach their natural conclusion in a number of ways: for example, a project might become so popular that it is absorbed into one of the other projects. Projects are moved to Archived status through a ","type":"text"},{"text":"Termination Review","type":"text","marks":[{"type":"strong"}]},{"text":". ","type":"text"},{"text":"If there is sufficient community interest in reactivating an Archived Project, the Project will start again with ","type":"text"},{"text":"Creation Review","type":"text","marks":[{"type":"strong"}]},{"text":". As there must be good reasons to have moved a Project to the Archives, the Creation Review provides a sufficiently high bar to prove that those reasons are no longer valid.","type":"text"}]},{"type":"heading","attrs":{"level":2},"content":[{"text":"Types of Reviews","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Creation Review","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Graduation Review","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Promotion Review","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Termination Review","type":"text"}]},{"type":"heading","attrs":{"level":3},"content":[{"text":"Project Review","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]}]}],"version":1},"cxhtml":"60%

Introduction

Credit: Much of this proposed project lifecycle has been initially adapted from the Eclipse Development Process.

The OpenMRS community is the sum of all of its constituent projects, including the OpenMRS core platform, add-on modules, distributions, and other tools and services used by the community. One of the OpenMRS community values is stated as, "We are open, honest, and transparent in both our processes and our software." In accordance with that value, we have adopted a stated process of how projects in the community can be created, how they can grow, and how they can be managed to help realize our values, mission, and vision. This project lifecycle process is intended to help projects:

Communicate their project plans and feature roadmaps in a timely, open, and transparent way
Create software that helps move the OpenMRS platform forward
Provide technology tools that help meet the values, mission, and vision of OpenMRS

Phases of Projects

Pre-Proposal

This is not really a project phase per se, but describes the ideas that exist in the minds of one or more people in the OpenMRS community before they are documented.

Proposed

To be described.

Incubation

To be described.

Mature

To be described.

Top-Level

Projects that have demonstrated the characteristics of a Top-Level Project (e.g., consistent leadership in a technical area and the recruitment of a wider developer community) can be promoted to Top-Level Project status. This promotion occurs through a Promotion Review. Upon the successful completion of a Promotion Review, OpenMRS Leadership may recommend that the project be promoted and ask that its Charter be reviewed and approved.

Top-Level Project has a Charter which describes the purpose, Scope, and operational rules for the Top-Level Project. The Charter should refer to, and describe any refinements to, the provisions of this Development Process. The Board approves the Charter of each Top-Level Project.

Top-Level Projects cannot be incubated and can only be created from one or more existing Mature-phase Projects.

Archived

Projects that become inactive, either through dwindling resources or by reaching their natural conclusion, are archived. Projects can reach their natural conclusion in a number of ways: for example, a project might become so popular that it is absorbed into one of the other projects. Projects are moved to Archived status through a Termination Review. If there is sufficient community interest in reactivating an Archived Project, the Project will start again with Creation Review. As there must be good reasons to have moved a Project to the Archives, the Creation Review provides a sufficiently high bar to prove that those reasons are no longer valid.

Types of Reviews

Creation Review

Graduation Review

Promotion Review

Termination Review

Project Review

"}}},{"type":"extension","attrs":{"extensionType":"com.atlassian.confluence.migration","extensionKey":"legacy-content","text":"","parameters":{"reason":"A column macro in a rich body macro can't be created or edited in the new editor.","nestedContent":{"type":"doc","content":[{"type":"bodiedExtension","attrs":{"extensionType":"com.atlassian.confluence.macro.core","extensionKey":"column","parameters":{"macroParams":{"width":{"value":"40%"}},"macroMetadata":{"schemaVersion":{"value":"1"},"title":"Column"}}},"content":[{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"extension","attrs":{"extensionType":"com.atlassian.confluence.macro.core","extensionKey":"gliffy","parameters":{"macroParams":{"name":{"value":"Project Hierarchy"}},"macroMetadata":{"schemaVersion":{"value":"1"},"placeholder":[{"type":"image","data":{"url":"https://confluence-connect.gliffy.net/diagram/image/placeHolder.png?name=Project+Hierarchy"}}],"title":"Gliffy Diagram"}}}},{"type":"extension","attrs":{"extensionType":"com.atlassian.confluence.macro.core","extensionKey":"gliffy","parameters":{"macroParams":{"name":{"value":"OpenMRS Project Lifecycle"}},"macroMetadata":{"schemaVersion":{"value":"1"},"placeholder":[{"type":"image","data":{"url":"https://confluence-connect.gliffy.net/diagram/image/placeHolder.png?name=OpenMRS+Project+Lifecycle"}}],"title":"Gliffy Diagram"}}}}]}],"version":1},"cxhtml":"40%

Project Hierarchy

OpenMRS Project Lifecycle

"}}}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]},{"type":"paragraph","content":[{"text":" ","type":"text"}]}],"version":1}