... | ... | @@ -5,6 +5,7 @@ |
|
|
### Process Management
|
|
|
|
|
|
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
|
... | ... | @@ -12,9 +13,10 @@ We will manage the process relaying on the following elements: |
|
|
#### Dashboards
|
|
|
|
|
|
The key dashboards are the following:
|
|
|
* [Process phase](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/boards/1375): visualization of the different stages where the initiatives are.
|
|
|
* [Workflow](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/boards/1373): this dashboard shows the initiatives that are subject of active work or will be soon.
|
|
|
* [Priority](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/boards/1374): dashboard that reflects which are the most important initiatives that are currently in associated to the process
|
|
|
|
|
|
* [Process phase](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/boards/1375): visualization of the different stages where the initiatives are. `` `#F00` ``(fixme)
|
|
|
* [Workflow](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/boards/1373): this dashboard shows the initiatives that are subject of active work or will be soon. `` `#F00` ``(fixme)
|
|
|
* [Priority](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/boards/1374): dashboard that reflects which are the most important initiatives that are currently in associated to the process `` `#F00` ``(fixme)
|
|
|
|
|
|
#### Repositories/subgroups
|
|
|
|
... | ... | @@ -23,9 +25,10 @@ The following diagram describes the different repositories and their relation: |
|
|
![](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-release-roadmap-oniro-wg/-/raw/main/roadmapping_repositories.png)
|
|
|
|
|
|
The roadmapping process takes place in three different places:
|
|
|
* initiative-creation: 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 visualized 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.
|
|
|
|
|
|
* initiative-creation: 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 visualized 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 Initiatives
|
|
|
|
... | ... | @@ -39,6 +42,6 @@ Any member of the Eclipse Foundation is entitled to file the above request using |
|
|
|
|
|
### Implementation flow in the system - proposal
|
|
|
|
|
|
To implement whole process in the GitLab we propose to leverage following flow. It takes minimum human involvement. Additionally, it allows for the streamlining and ease pipeline statistics tracking and reporting.
|
|
|
To implement whole process in the GitLab we propose to leverage following flow. It takes minimum human involvement. Additionally, it allows for the streamlining and ease pipeline statistics tracking and reporting.
|
|
|
|
|
|
![image](uploads/0ef8d75f09dc92e5d90a18e1c7232530/image.png) |
|
|
![image](uploads/0ef8d75f09dc92e5d90a18e1c7232530/image.png) |
|
|
\ No newline at end of file |