... | ... | @@ -7,10 +7,17 @@ |
|
|
The roadmapping process defines how the elements that form the Oniro Platform roadmap are proposed, described, discussed, agreed, tracked, evolved, approved, deprecated...
|
|
|
|
|
|
The following considerations apply:
|
|
|
* A roadmap in an open environment needs to be kept clean for a variety of reasons:
|
|
|
* The roadmap is a business development tool.
|
|
|
* Different members and engineers are interested in different parts of the Platform. The roadmap is a coordination tool.
|
|
|
* We expect and promote participation from community members without affiliation to Oniro Members. The process needs to promote such particpation while keeping management and housekeeping needs under control.
|
|
|
* We are in early stages of Oniro's development life cycle. Still, a high number of developers and managers from a variety of organizations are involved.
|
|
|
* Our intention is to become upstream of organization that develop products based partly or entirely on Oniro. Our roadmap is an essential product design tool for them.
|
|
|
* This roadmapping process has been designed to kee the roadmap clean.
|
|
|
* The roadmap is owned by the Working Group, according to the Oniro WG Charter, that follows the Eclipse Working Groups Process.
|
|
|
* Given that WGs do not deal with technical matters, the ownership limits to business and product related items.
|
|
|
* Technical content is owned by the projects. If coordination is required, the PMC will get involved.
|
|
|
* Given that operating systems and platforms are tightly coupled systems and we are in early stages of the development process, a strong coordination is required among the following two groups: those behind the business/product elements of the roadmap and those behind the technical ones. This process contemplates such need.
|
|
|
* Given that WGs do not deal with technical matters, the ownership is limited to business and product related items.
|
|
|
* Technical content is owned by the projects. Coordination is required so committers should get involved.
|
|
|
* Given that operating systems and platforms are tightly coupled systems and that we are in early stages of the development process, a strong coordination is required among the following two groups: those behind the business/product elements of the roadmap and those behind the technical ones. This process contemplates such need.
|
|
|
* This coordination materializes within the Roadmap Team.
|
|
|
* This process will kick off as soon as it is approved by the Oniro WG SC, which will happen after Oniro Platform Initiatives for the Goofy release are approved. The process will start by governing the changes on Goofy's release roadmap.
|
|
|
|
... | ... | |