... | ... | @@ -71,16 +71,3 @@ 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 |