... | ... | @@ -28,46 +28,26 @@ The roadmapping process takes place in three different places: |
|
|
* 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
|
|
|
At the moment, we have 1 possible community message type to participate and influence our further development. It's:
|
|
|
|
|
|
![image](uploads/0e616880a9934db99a2d20f227e4ebc0/image.png)
|
|
|
- feature request
|
|
|
|
|
|
For each of them we provide templates and examples.
|
|
|
We provide template and example to ease filing similar items.
|
|
|
|
|
|
### 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.
|
|
|
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 & adopted etc. However, rather high-level features integration are recommended.
|
|
|
|
|
|
## 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)
|
|
|
Any member of the Eclipse Foundation is entitled to file the above request using the previously mentioned interface.
|
|
|
|
|
|
Finally, filling in all necessary information in the form:
|
|
|
### Implementation flow in the system - proposal
|
|
|
|
|
|
![image](uploads/404f0bc2c58e98eb284b0e3bf6c7cf37/image.png)
|
|
|
To implement whole process in the GitLab we propose to leverage following flow. It takes minimum human involvement. Additioanlly, it allows for the streamling and ease pipeline statitistics tracking and reporting.
|
|
|
|
|
|
Please also add a meaningful title, like: "Support for 400k i2c in the ABC board", to ease further communication. |
|
|
![image](uploads/0ef8d75f09dc92e5d90a18e1c7232530/image.png) |
|
|
\ No newline at end of file |