... | ... | @@ -27,20 +27,12 @@ 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
|
|
|
## Community Initiatives
|
|
|
|
|
|
To support further growth and expansion of Oniro, we provide a web-based communication interface to facilitate that endeavour (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 1 possible community message type to participate and influence our further development. It's:
|
|
|
|
|
|
- feature request
|
|
|
|
|
|
We provide template and example to ease filling 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 & adopted etc. However, rather high-level features integration are recommended.
|
|
|
|
|
|
## Procedure
|
|
|
|
|
|
Any member of the Eclipse Foundation is entitled to file the above request using the previously mentioned interface.
|
... | ... | |