[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[oniro-wg] MoM - Oniro WG Steering Committee 2022wk39
|
Dear Oniro ecosystem members,
## MoM Oniro Steering Committee 2022wk39
please find the Minutes of Meeting (MoM), approved on 2022-10-13.
Link: https://gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/blob/main/2022-mom-oniro-wg-sc/
2022wk39-eclipse-oniro-wg-steering-committee-agenda-mom.md
Please find on gitlab the approved minutes from previous meetings.
Link: https://gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/tree/main/2022-mom-oniro-wg-sc
### MoM key points
"### Oniro WG SC meeting minutes
#### Approval of the meeting minutes from the 2022-09-01 2022wk35 Oniro WG SC
Meeting
* Agenda and meeting minutes to be approved #link <https://gitlab.eclipse.org/
eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/steering-committee-
private-oniro-wg/-/blob/main/agenda-minutes-to-approve/2022wk35-eclipse-oniro-
wg-steering-committee-agenda-mom.md>
Commit considered: 897cea19
No objections recorded, minutes are approved
#### Support the decision of the PMC of changing the license to some of the
Oniro components
The Oniro repository (https://gitlab.eclipse.org/eclipse/oniro-core/oniro)
currently uses 3 licenses for the included files:
* Apache-2.0 (Yocto/OE layers files)
* CC-BY-4.0 (documentation)
* MIT.txt (Yocto/OE layers files)
Due to how these Yocto/OE layers interact with upstream layers (including oe-
core), having parts of our layers licensed under Apache when most (if not all)
of our upstream dependencies (and generally the entire ecosystem) are MIT,
would pose a couple of issues:
* Using our layers would introduce a new license to a downstream consumer that
needs to be assessed.
* Reusing parts of our code would pose an issue of relicensing on Oniro or the
downstream side.
* Upstreaming Apache code would need relicensing on the Oniro side before
upstream could accept contributions (unless upstream is up for a license
addition which in most cases is not an option).
* Mistakes can happen and end up with "silent" relicensing in different
situations.
To avoid all the above we propose to change all the existing Yocto/OE
Apache-2.0 files in this repository to MIT. The list of the Apache-2.0 files
in the scope of this relicensing is: #link <https://gitlab.eclipse.org/
eclipse/oniro-core/oniro/-/issues/824#note_1020152> Please check also at the
end of this document the full list of affected files.
Amit K. proposes a vote to support this decision so both, projects and working
group are aligned.
Sharon asks whether all the SC members and copyright holders have been
consulted and approve the change.
Davide and Agustin report that PMC has already approved the change and the
committers have had the opportunity.
Amit, Carlo, Stefano, acknowledge and have no further recommendation.
#### Resolutions
* Approved unanimously the 2022wk35 MoM
* The PMC decision of relicensing the list is acknowledged
### Oniro WG SC All Members Meeting minutes
#### Welcome Politecnico Milano to Oniro
Andrea Miele provide a quick introduction.
#### 2023 Huawei R&D involvement / realistic capacity
Davide reports on the reduced budget/technical capacity of Huawei owing to a
company-wide reduction of certain activities.
This brings an urge to speed up the 2.0 release.
After mid-Octobr, there will be still some technical capacity (overall 4-12
including other partners). Asks what would Oniro be like next year?
Carlo asks if the economic capacity will be unaffected (budged contribution)
by the decision. Strategic level. But other non-budgetary contributions shall
be taken care by the WG at large, by sponsorship and new members fees.
Sharon: Program plan - EF budgets according to the budget approved. Davide
suspects that as far as activities are concerned, there will be a shortage.
#### Lessons learned: Oniro minimum viable core team and risk mitigation
strategies
Is relying on one single member a wise decision (budget, technical, IP
compliance).
Makers leveraging a project for making their products should support and share
the burdens of the project to make it viable in the long run, at least after
some time after bootstrap.
Strategic assets/activities that need to be shared and kept alive:
- IP
- IT & Infrastructure / Gitlab runners
- Marketing
- Technical oversight, technical
- Maintaining OS images, bugfixing platforms, testing.
This had the input of the members.
#### Oniro v2.0 roadmap plan and alignment
Product documentation:
* Current Oniro Platform Release Roadmap #link <https://gitlab.eclipse.org/
eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-
commitee-oniro-wg/-/blob/main/resources_documentation_presentations/
oniro_platform_release_roadmap_alpha_beta_20220708-share.pdf>
* Proposed Oniro Platform Release Roadmap (draft) #link <https://
gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/
meetings-steering-commitee-oniro-wg/-/blob/main/
resources_documentation_presentations/
oniro_platform_release_roadmap_draft_20220922.pdf>
* Oniro v2.0 detailed roadmap: #link <https://gitlab.eclipse.org/groups/
eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/-/
epic_boards/59>
The different versions of the Oniro Platform Release Roadmap are stored in
this folder: #link <https://gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/tree/main/
resources_documentation_presentations>
Oniro v2.0 release checklist (WIP): #link <https://gitlab.eclipse.org/eclipse-wg/oniro-wg/products-services-oniro-wg/release-roadmap-oniro-wg/initiative-qualification-roadmap-oniro-wg/-/issues/23>
Release early so that the feedback of the EF release team lands when technical
capacity is still with us.
Amit presents.
Davide suggests that for the next release the single platforms are split in
subprojects, so that Oniro per se concentrates on a smaller project and allows
more frequent release of updates, IP validation and etc, minimizing shared
costs when some features are belonging to a single member.
#### 2023 KPIs initial brainstorm - Davide Ricci 10 minutes
These are the links where you can find the Oniro Program Plan draft:
* In .pptx format: #link <https://gitlab.eclipse.org/eclipse-wg/oniro-wg/
oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/blob/
main/program-plan-and-budget-oniro-wg/program_plan_2023_drafts/
Oniro_Program_Plan_2023_draft.pptx>
* In .odt format: #link <https://gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/blob/main/
program-plan-and-budget-oniro-wg/program_plan_2023_drafts/
Oniro_Program_Plan_2023_draft.odp>
* In .pdf format #link <https://gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/blob/main/
program-plan-and-budget-oniro-wg/program_plan_2023_drafts/
Oniro_Program_Plan_2023_draft.pdf>
All the Oniro Program Plan drafts and templates are stored in Gitlab: #link
<https://gitlab.eclipse.org/eclipse-wg/oniro-wg/oniro-wg-committees/sc-wg-oniro/meetings-steering-commitee-oniro-wg/-/tree/main/program-plan-and-budget-oniro-wg/program_plan_2023_drafts>
Due to shortage of time, we punt it to offline discussion.
How: offline via MR or braninstorming meeting next week
#### AoB (Open Floor)
None"
Best Regards
--
Agustin Benito Bethencourt
Program Manager | Eclipse Foundation
Eclipse Foundation: The Community for Open Innovation and Collaboration
