|
|
## Process management and implementation WIP
|
|
|
|
|
|
### 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
|
|
|
|
|
|
#### Dashboards
|
|
|
|
|
|
The key dashboards are the following:
|
|
|
* [Process phase](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/boards/1375): visualization of the different stages where the initiatives are.
|
|
|
* [Workflow](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/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/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/boards/1374): dashboard that reflects which are the most important initiatives that are currently in associated to the process
|
|
|
* [Initiative type](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/boards/1376): categorization of the initiatives based on its type.
|
|
|
|
|
|
#### Repositories/subgroups
|
|
|
|
|
|
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)
|
|
|
|
|
|
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.
|
|
|
|
|
|
|
|
|
|
|
|
## Community Initiative types
|
|
|
|
|
|
To support further growth and expansion of Oniro, we provide a web-based communication interface to facilitate that endeavor (see it [here](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/issues)). We strongly believe that it is the community that is going to make this project unique and long-lived.
|
|
|
|
|
|
At the moment, we have 3 possible community message types to participate and influence our further development. These are:
|
|
|
|
|
|
- feature requests
|
|
|
- enhancement requests
|
|
|
- general feedbacks
|
|
|
|
|
|
![image](uploads/0e616880a9934db99a2d20f227e4ebc0/image.png)
|
|
|
|
|
|
For each of them we provide templates and examples.
|
|
|
|
|
|
### Feature requests
|
|
|
|
|
|
These are clearly written descriptions for new features that the Oniro project could possibly develop. Those new gains might be related to some specific/missing features as well as to general optimizations, throughput boosts, new hardware ports, new operating systems supported, new architecture components integrated etc.
|
|
|
|
|
|
### Enhancement requests
|
|
|
|
|
|
These requests are related to *existing* features. The request should consider the context within which it is based on e.g. software version, hardware used, configuration used etc.
|
|
|
|
|
|
### General feedbacks
|
|
|
|
|
|
That communication channel is supposed to be used for any comments, feedbacks, that are related to the technical Oniro matters, however, they don't fit into two previous categories.
|
|
|
|
|
|
## Procedure
|
|
|
|
|
|
Any member of the Eclipse Foundation is entitled to file any of the above requests using the previously mentioned interface. This is done by creating a new GitLab issue:
|
|
|
|
|
|
![image](uploads/e6e1a43c1818d6e48e2f0adbc1024df2/image.png)
|
|
|
|
|
|
Once a new issue's form popups up, one can select the request type:
|
|
|
|
|
|
![image](uploads/56e4455cd542f6a85a5ad2c52d661107/image.png)
|
|
|
|
|
|
Finally, filling in all necessary information in the form:
|
|
|
|
|
|
![image](uploads/404f0bc2c58e98eb284b0e3bf6c7cf37/image.png)
|
|
|
|
|
|
Please also add a meaningful title, like: "Support for 400k i2c in the ABC board", to ease further communication.
|
|
|
|
|
|
## Oniro Roadmapping Process approval and implementation
|
|
|
|
|
|
This Roadmapping process must be approved by the Oniro WG Steering Committee. Given its nature, it is expected to be socialized among both the WG and the projects. Feedback from the PMC, committers and participants is essential.
|
|
|
|
|
|
This Oniro roadmapping process must be compatible with Eclipse Foundation processes and practices.
|
|
|
|
|
|
Oniro acknowledges that the implementation of this process should serve its purpose in an effective and efficient way, which will take time.
|
|
|
* The process will need to be put up to test so a critical thinking attitude will be associated with its definition and implementation.
|
|
|
* Before onboarding into Eclipse Foundation, the Members had procedures and practices to create and manage the roadmap. The onboarding of Oniro as a fully functional Eclipse Foundation project requires an evolutive approach from the previous state to one fully embracing EF ByLaws, processes and practices. In any case the starting point have to be compatible with existing EF ByLaws, processes and practices.
|
|
|
* This process will be put in place once the current release roadmap process is approved, not before that event.
|
|
|
* From that moment on, this process will apply governing any change in any of its high level elements (initiatives).
|
|
|
* The goal is to have an oiled Oniro Platform Release Roadmapping process by the time the next release roadmap is created, around 2023Q1 |
|
|
\ No newline at end of file |