... | ... | @@ -4,12 +4,15 @@ |
|
|
|
|
|
### Description
|
|
|
|
|
|
The roadmapping process defines how the elements that form the Oniro Platform roadmap are proposed, described, discussed, agreed, tracked, evolved, approved, deprecated... considering the following:
|
|
|
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:
|
|
|
* 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 woned by the projects. If coordination is required, the PMC will get involved.
|
|
|
* 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.
|
|
|
* This coordination materializes within the Roadmap Team.
|
|
|
* 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.
|
|
|
|
|
|
![](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/raw/main/oniro_roadmapping_process_infographic.png)
|
|
|
|
... | ... | |