... | @@ -7,17 +7,17 @@ |
... | @@ -7,17 +7,17 @@ |
|
The roadmapping process defines how the elements that form the Oniro Platform roadmap are proposed, described, discussed, agreed, tracked, evolved, approved, deprecated...
|
|
The roadmapping process defines how the elements that form the Oniro Platform roadmap are proposed, described, discussed, agreed, tracked, evolved, approved, deprecated...
|
|
|
|
|
|
The following considerations apply:
|
|
The following considerations apply:
|
|
* In an open environment a rodamap needs to be kept clean for a variety of reasons:
|
|
* In an open environment a roadmap needs to be kept clean for a variety of reasons:
|
|
* The roadmap is a business development tool.
|
|
* The roadmap is a business development tool.
|
|
* Different members and engineers are interested in different parts of the Platform. The roadmap is a coordination tool.
|
|
* Different members and engineers are interested in different parts of the Platform. The roadmap is a coordination tool.
|
|
* We expect and promote participation from community members without affiliation to Oniro Members. The process needs to promote such particpation while keeping management and housekeeping needs under control.
|
|
* We expect and promote participation from community members without affiliation to Oniro Members. The process needs to promote such participation while keeping management and housekeeping needs under control.
|
|
* We are in early stages of Oniro's development life cycle. Still, a high number of developers and managers from a variety of organizations are involved.
|
|
* We are in the early stages of Oniro's development life cycle. Still, a high number of developers and managers from a variety of organizations are involved.
|
|
* Our intention is to become upstream of organization that develop products based partly or entirely on Oniro. Our roadmap is an essential product design tool for them.
|
|
* Our intention is to become upstream of organizations that develop products based partly or entirely on Oniro. Our roadmap is an essential product design tool for them.
|
|
* This roadmapping process has been designed to have a clean roadmap while, at the same time, promoting interaction with as many people as possible, affiliated to Oniro Members or not, being commiters/participants of Oniro projects or not.
|
|
* This roadmapping process has been designed to have a clean roadmap while, at the same time, promoting interaction with as many people as possible, affiliated to Oniro Members or not, being committers/participants of Oniro projects or not.
|
|
* As stated at the [Oniro WG Charter](https://www.eclipse.org/org/workinggroups/oniro-charter.php)... "_Define and manage a product roadmap that brings together the Oniro developer's community and the platform consumers' expectations and needs, helping the adoption of Oniro technologies by the Working Group Members as well as the wider industry._", the definition of the Oniro Platform roadmap correspond to the Oniro WG, as well as the management responsibility.
|
|
* As stated at the [Oniro WG Charter](https://www.eclipse.org/org/workinggroups/oniro-charter.php)... "_Define and manage a product roadmap that brings together the Oniro developer's community and the platform consumers' expectations and needs, helping the adoption of Oniro technologies by the Working Group Members as well as the wider industry._", the definition of the Oniro Platform roadmap correspond to the Oniro WG, as well as the management responsibility.
|
|
* Given that WGs do not deal with technical matters, the ownership is limited to business and product related topics. Technical topics are owned by the projects.
|
|
* Given that WGs do not deal with technical matters, the ownership is limited to business and product related topics. Technical topics are owned by the projects.
|
|
* Given that business and product topics affect, and sometimes drive, technical topics (the opposite is also true), coordination between business/product people (Working Group) and technical people (Projects) is required, to define and manage the roadmap.
|
|
* Given that business and product topics affect, and sometimes drive, technical topics (the opposite is also true), coordination between business/product people (Working Group) and technical people (Projects) is required to define and manage the roadmap.
|
|
* Given that operating systems (and HW/SW platforms) are tightly coupled systems and that Oniro is currently in an early stage of its development process, such coordination is even more important.
|
|
* Given that operating systems (and HW/SW platforms) are tightly coupled systems and that Oniro is currently in an early stage of its development process, such coordination is even more important.
|
|
* This coordination materializes through the Roadmap Team, beyond the fact that Committers are represented at the Oniro WG Steering Committee.
|
|
* This coordination materializes through the Roadmap Team, beyond the fact that Committers are represented at the Oniro WG Steering Committee.
|
|
|
|
|
|
![](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/raw/main/oniro_roadmapping_process_infographic.png)
|
|
![](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/raw/main/oniro_roadmapping_process_infographic.png)
|
... | @@ -34,7 +34,7 @@ For all these reasons, Oniro intends to avoid such a concept, understanding that |
... | @@ -34,7 +34,7 @@ For all these reasons, Oniro intends to avoid such a concept, understanding that |
|
|
|
|
|
Instead of *requirements* we will use the word *initiative*. We are seeking a better word.
|
|
Instead of *requirements* we will use the word *initiative*. We are seeking a better word.
|
|
|
|
|
|
An initiative is the name assigned to the artefacts that describes the Oniro Platform users' needs that the Oniro WG and projects intend to address. It is expressed in a templated form, using a use oriented language and managed on Gitlab thorugh issues and, once approved, thorugh Epics.
|
|
An initiative is the name assigned to the artifacts that describe the Oniro Platform users' needs that the Oniro WG and projects intend to address. It is expressed in a templated form, using a use oriented language and managed on Gitlab through issues and, once approved, through Epics.
|
|
|
|
|
|
Every initiative will be owned by a person. Such a person could represent one or several organizations. The main reason for this is that any initiative could potentially be challenged at any time and the best way to do it is by knowing who is responsible for it.
|
|
Every initiative will be owned by a person. Such a person could represent one or several organizations. The main reason for this is that any initiative could potentially be challenged at any time and the best way to do it is by knowing who is responsible for it.
|
|
|
|
|
... | @@ -61,7 +61,7 @@ Considerations about business initiatives: |
... | @@ -61,7 +61,7 @@ Considerations about business initiatives: |
|
|
|
|
|
#### Product initiatives
|
|
#### Product initiatives
|
|
|
|
|
|
Product initiatives or requirements described needs that the product aims to satisfy. They prescribe properties of the product.
|
|
Product initiatives or requirements describe needs that the product aims to satisfy. They prescribe properties of the product.
|
|
|
|
|
|
> It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.
|
|
> It is a broad concept that could speak to any necessary (or sometimes desired) function, attribute, capability, characteristic, or quality of a system for it to have value and utility to a customer, organization, internal user, or other stakeholder.
|
|
>
|
|
>
|
... | @@ -80,8 +80,8 @@ We refer to roadmap item to: |
... | @@ -80,8 +80,8 @@ We refer to roadmap item to: |
|
* These elements are managed by using issues (gitlab terminology).
|
|
* These elements are managed by using issues (gitlab terminology).
|
|
* They are managed at project level.
|
|
* They are managed at project level.
|
|
|
|
|
|
In a code first organization, like Eclipse Foundation, it is wise that both, initiaitives (requirements) and items are expressed in a user-centric way. Such approach has a variety of benefits:
|
|
In a code first organization, like Eclipse Foundation, it is wise that both, initiatives (requirements) and items are expressed in a user-centric way. Such approach has a variety of benefits:
|
|
* It enables the definiton of differet elements like Specifications, initiatives, roadmap items or Test Compatibility Kit in different _languages and formats_ when needed.
|
|
* It enables the definition of different elements like Specifications, initiatives, roadmap items or Test Compatibility Kit in different _languages and formats_ when needed.
|
|
|
|
|
|
## Relation between initiatives, roadmap items and other elements
|
|
## Relation between initiatives, roadmap items and other elements
|
|
|
|
|
... | @@ -117,13 +117,13 @@ To achieve such goals, the Roadmap Team is formed by two groups: |
... | @@ -117,13 +117,13 @@ To achieve such goals, the Roadmap Team is formed by two groups: |
|
* 3 People appointed by the Oniro WG SC
|
|
* 3 People appointed by the Oniro WG SC
|
|
* Support by EF, as usual, when needed.
|
|
* Support by EF, as usual, when needed.
|
|
|
|
|
|
The roadmap team does not manage the technical roadmap at project level. That correspond to each project and it is coordinated within the PMC, according to the Eclipse Project Handbook. The roadmap team manages the roadmap at Oniro WG level.
|
|
The roadmap team does not manage the technical roadmap at project level. That corresponds to each project and it is coordinated within the PMC, according to the Eclipse Project Handbook. The roadmap team manages the roadmap at Oniro WG level.
|
|
|
|
|
|
### Oniro WG SC
|
|
### Oniro WG SC
|
|
|
|
|
|
The Oniro roadmap is owned by the Oniro WG.
|
|
The Oniro roadmap is owned by the Oniro WG.
|
|
|
|
|
|
The Oniro WG SC approves the initiatives that belongs to the current Roadmap cycle. This Governance Body provides guidelines to the roadmap team on what kind of information is required for them to evaluate the convenience and impact of each initiative on the overall product.
|
|
The Oniro WG SC approves the initiatives that belong to the current Roadmap cycle. This Governance Body provides guidelines to the roadmap team on what kind of information is required for them to evaluate the convenience and impact of each initiative on the overall product.
|
|
|
|
|
|
The Oniro WG SC appoints 3 members of the Roadmap team.
|
|
The Oniro WG SC appoints 3 members of the Roadmap team.
|
|
|
|
|
... | @@ -136,7 +136,7 @@ This is an organization or individual, like a community member, that supports th |
... | @@ -136,7 +136,7 @@ This is an organization or individual, like a community member, that supports th |
|
* Assuming the communication costs related with the initiative including promotion, community management, etc.
|
|
* Assuming the communication costs related with the initiative including promotion, community management, etc.
|
|
* Support those entitled to develop, maintain and manage the initiative in whatever they need to keep the initiative, associated code and artifacts healthy.
|
|
* Support those entitled to develop, maintain and manage the initiative in whatever they need to keep the initiative, associated code and artifacts healthy.
|
|
|
|
|
|
In other words, in order for an initiative to be part of the Oniro release, it requires a sponsor. Members will assume the spoonsor role for initiatives proposed by community members. The Oniro WG SC will determine the capacity/costs assigned to this purpose.
|
|
In other words, in order for an initiative to be part of the Oniro release, it requires a sponsor. Members will assume the sponsor role for initiatives proposed by community members. The Oniro WG SC will determine the capacity/costs assigned to this purpose.
|
|
|
|
|
|
If during the life cycle of the initiative, the sponsor leaves or no longer assumes the expected commitments diligently, a similar process to the one described below for the Owner role will be executed.
|
|
If during the life cycle of the initiative, the sponsor leaves or no longer assumes the expected commitments diligently, a similar process to the one described below for the Owner role will be executed.
|
|
|
|
|
... | @@ -150,7 +150,7 @@ When the owner leaves the Oniro project, no longer wants to hold such responsibi |
... | @@ -150,7 +150,7 @@ When the owner leaves the Oniro project, no longer wants to hold such responsibi |
|
* Through a call for ownership process.
|
|
* Through a call for ownership process.
|
|
* Appointed by the Roadmap team.the initiative sponsor will propose a candidate.
|
|
* Appointed by the Roadmap team.the initiative sponsor will propose a candidate.
|
|
* It is expected the support of the Sponsor in this process.
|
|
* It is expected the support of the Sponsor in this process.
|
|
* Such process will be elaborated and approved by the roadmap team and ratified by the Oniro WG SC.
|
|
* Such a process will be elaborated and approved by the roadmap team and ratified by the Oniro WG SC.
|
|
|
|
|
|
## Process structure and workflow
|
|
## Process structure and workflow
|
|
|
|
|
... | @@ -178,7 +178,7 @@ The stages of the Roadmapping Process at the Incubation phases are: |
... | @@ -178,7 +178,7 @@ The stages of the Roadmapping Process at the Incubation phases are: |
|
* Initiative.Approval
|
|
* Initiative.Approval
|
|
* Parking lot
|
|
* Parking lot
|
|
|
|
|
|
You can see a repressentation of the different stages in this board: [Process Stages board](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/boards/1375)
|
|
You can see a representation of the different stages in this board: [Process Stages board](https://gitlab.eclipse.org/eclipse-wg/oniro-wg/roadmap-oniro-wg/wishlist-roadmap/wishlist-repo/-/boards/1375)
|
|
|
|
|
|
##### Initiative.Proposal
|
|
##### Initiative.Proposal
|
|
|
|
|
... | @@ -193,7 +193,7 @@ You can see a repressentation of the different stages in this board: [Process St |
... | @@ -193,7 +193,7 @@ You can see a repressentation of the different stages in this board: [Process St |
|
##### Initiative.Description
|
|
##### Initiative.Description
|
|
|
|
|
|
* With the support of the Roadmap Team, the Submitter will add additional required information.
|
|
* With the support of the Roadmap Team, the Submitter will add additional required information.
|
|
* When the Roadmap Team considers it ready, the initiative is proposed to the Oniro WG SC for its assessment as potential part of the release.
|
|
* When the Roadmap Team considers it ready, the initiative is proposed to the Oniro WG SC for its assessment as a potential part of the release.
|
|
|
|
|
|
##### Initiative.Assessment
|
|
##### Initiative.Assessment
|
|
|
|
|
... | @@ -216,7 +216,7 @@ You can see a repressentation of the different stages in this board: [Process St |
... | @@ -216,7 +216,7 @@ You can see a repressentation of the different stages in this board: [Process St |
|
|
|
|
|
#### Description of this phase
|
|
#### Description of this phase
|
|
|
|
|
|
The approved iniitatives will become part of the Roadmap. They are described as roadmap items as part of the Release backlog.
|
|
The approved initiatives will become part of the Roadmap. They are described as roadmap items as part of the Release backlog.
|
|
|
|
|
|
#### Stages
|
|
#### Stages
|
|
|
|
|
... | @@ -259,7 +259,7 @@ We will manage the process relaying on the following elements: |
... | @@ -259,7 +259,7 @@ We will manage the process relaying on the following elements: |
|
### Dashboards
|
|
### Dashboards
|
|
|
|
|
|
The key dashboards are the following:
|
|
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): viasualization of the different stages where the initiatives are.
|
|
* [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.
|
|
* [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
|
|
* [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.
|
|
* [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.
|
... | @@ -272,12 +272,12 @@ The following diagram describes the different repositories and their relation: |
... | @@ -272,12 +272,12 @@ The following diagram describes the different repositories and their relation: |
|
|
|
|
|
The roadmapping process takes place in three different places:
|
|
The roadmapping process takes place in three different places:
|
|
* initiative-incubation: under the Oniro Working Group Gitlab, this repository is where the initiatives are submitted, matured, evaluated and stored if they are not approved.
|
|
* initiative-incubation: 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 visualised and explained to people with different profiles and backgrounds.
|
|
* 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.
|
|
* 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 Initiative types
|
|
|
|
|
|
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.
|
|
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:
|
|
At the moment, we have 3 possible community message types to participate and influence our further development. These are:
|
|
|
|
|
... | @@ -315,26 +315,26 @@ Finally, filling in all necessary information in the form: |
... | @@ -315,26 +315,26 @@ Finally, filling in all necessary information in the form: |
|
|
|
|
|
![image](uploads/404f0bc2c58e98eb284b0e3bf6c7cf37/image.png)
|
|
![image](uploads/404f0bc2c58e98eb284b0e3bf6c7cf37/image.png)
|
|
|
|
|
|
Please also add meaningful title, like: "Support for 400k i2c in the ABC board", to ease further communication.
|
|
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
|
|
## Oniro Roadmapping Process approval and implementation
|
|
|
|
|
|
This Roadmapping process should be approved by the Oniro WG Steering Committee. Given its nature, it is expected to be socialised among both, the WG and the projects. Feedback from the PMC, committers and particpants is essential.
|
|
This Roadmapping process should 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 should to be compatible with Eclipse Foundation processes and practices.
|
|
This Oniro roadmapping process should be compatible with Eclipse Foundation processes and practices.
|
|
|
|
|
|
Oniro acknowledge that the implementation of this process should serve its purpose in an effective and efficient way, which will take time.
|
|
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 to its definition and implementation.
|
|
* 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 pooint have to be compatible with existing EF ByLaws, processes and practices.
|
|
* 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 pooint 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.
|
|
* 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).
|
|
* 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 relase roadmap is created, around 2023Q1
|
|
* The goal is to have an oiled Oniro PLatform Release Roadmapping process by the time the next release roadmap is created, around 2023Q1
|
|
|
|
|
|
## Contacts and feedback
|
|
## Contacts and feedback
|
|
|
|
|
|
In order to ask questions of provide feedback, please contact the Roadmap Team.
|
|
In order to ask questions or provide feedback, please contact the Roadmap Team.
|
|
|
|
|
|
Note: since the Oniro Roadmapping Process has not been approoved yet, the contact people are:
|
|
Note: since the Oniro Roadmapping Process has not been approved yet, the contact people are:
|
|
* Agustin Benito Bethencourt @toscalix
|
|
* Agustin Benito Bethencourt @toscalix
|
|
* Sebastian Serewa @sserewa
|
|
* Sebastian Serewa @sserewa
|
|
* Jarek Marek @jmarek |
|
* Jarek Marek @jmarek |
|
|
|
\ No newline at end of file |