... | ... | @@ -240,9 +240,7 @@ We will manage the process relaying on the following elements: |
|
|
* Roadmap Team as the main group of people that will take care of the process. This has been described above.
|
|
|
* Dashboards to manage the different elements
|
|
|
* Repositories/subgroups
|
|
|
* initiative-incubation
|
|
|
* initiative-release
|
|
|
* engineering-roadmap
|
|
|
|
|
|
|
|
|
### Dashboards
|
|
|
|
... | ... | @@ -256,7 +254,12 @@ The key dashboards are the following: |
|
|
|
|
|
The following diagram describes the different repositories and their relation:
|
|
|
|
|
|
![](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/raw/main/roadmapping_repositories.png)
|
|
|
![](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/raw/main/roadmapping_repositories.png)
|
|
|
|
|
|
The roadmapping process takes place in three different places:
|
|
|
* initiative-incubation: under the Oniro Working Group Gitlab, this repository is where the initiatives are submitted, matured, evaluated and stored if they are not approved.
|
|
|
* initiative-release: under the Oniro Working Group Gitlab, this subgroup is where the approved initiatives are stored. The goal is to keep this subgroup clean of epics that are not part of the release so our roadmap can be visualised and explained to people with different profiles and backgrounds.
|
|
|
* engineering-roadmap: under the oniro-core project, this subgroup is where the epics are described as user stories and engineering tasks in order to execute them.
|
|
|
|
|
|
## Community Initiative types
|
|
|
|
... | ... | |