[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[oniro-wg] MoM - Oniro WG Steering Committee 2022wk43
|
Dear Oniro ecosystem members,
## MoM Oniro Steering Committee 2022wk43
please find the Minutes of Meeting (MoM), approved on 2022-11-17.
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/
2022wk43-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
This meeting was held at EclipseCon 2022. 2 sessions were held in two
different days.
### MoM key points Session 1
" ### 2023 vision
#### Technical Direction
Andrei mainly reports
A Blueprint for a vertical will live in a separate add-on. In a separate
subproject. Showing both technology and an use case.
We need One single big element strongly associated to the platform and
visible. Find a company that wants to bring Oniro into production. We already
have the concept of design win. We could not execute.
We need to invest more to support the lifecycle. Done well for Linux, less so
for Zephyr.
Davide: The does the horizontal layer need more work next year or is it ready
to support building components on the top?
Showing features part is ok, as for production-ready artifacts, there is still
much to do. Many further aspects we need to handle, like identity etc., to be
production ready. There is a tension between adding more features and
finishing them to make them production ready. We might not have the resources
to do both.
Ettore: for the security part we need to implement some security features, but
the part we are more concerned into is functional. My clients need to be
working and being reliable.
Davide: """
I see here two directions
- Not about breadth -- being a good base for addons
- Work on production ready details
We need production partners (like Seco) to define production details to
showcase. """
We need more feedback from partners. We have no good system to receive
feedback, especially requirements.
More manpower from partners also is needed.
Yocto compatibility would raise the value.
#### Specific on the compliance toolchain
Alberto reports.
We have added a graphical database to achieve graph queries. We have found
another EF member, Kinetics, they are interested in helping us to design,
develop the functionality.
We could be able to finally use all the information we have achieved to spot
any incompatibility. Not any manual work any more.
The work we have done should be put in the open, through some API. We want to
involve other EF members to invest in the project with developing, spec
definition, standard.
Our current production toolchain covers only sources. The extra mile to
binaries is done manually. Nobody else is doing this in Yocto at least. We are
close to filling the gap. We also need to sell the concept that we need to add
to Yocto some facilities to collect metadata at build time to such respect.
Adrian: do we have the ability to accept external contributions given the
infrastructure?
No, but they can do MR -- actually the present team is doing the same for the
Dashboard. Before externals can be elected committers, many more things should
happen, not just code, but also requirements, design, architecture
suggestions, etc.
Adrian: Oniro Compliance toolchain raises a lot of interest any time we
present it. Needs not to be a WG member to consume and contribute to the
project.
Agustin: you can do two ways: as a tool or as a service (in or outside Eclipse
project, sharing resources). It's something you must decide, and be clear
about.
like a commercial/marketing action, suggestion to move to SG2.
Daniel Izquierdo from Bitergia is invited to provide some analytics concerning
Oniro, using their tools.
Davide: Need to preserve the Commons and reflect into the KPI. The way to keep
the commons active: list key functions, staff and resource those functions
#### V3 release
