OEDVM 2021: Difference between revisions

From Openembedded.org
Jump to navigation Jump to search
(→‎Format: remove onerous requirements which are blocking people from participating)
Line 10: Line 10:
Since this will be a virtual meeting we are going to change the format around to try and make it easier to get input from the global community and still maintain an in person portion.
Since this will be a virtual meeting we are going to change the format around to try and make it easier to get input from the global community and still maintain an in person portion.


Running a virtual developer meeting presents a new set of challenges and
As always, we will collect topics on
a chance to engage a larger audience. As always, we will collect topics on
the wiki at https://www.openembedded.org/OEDVM_2021.
the wiki at https://www.openembedded.org/OEDVM_2021. For each topic, we expect at
least three people to agree to be moderators for the discussion. About two
weeks before the meeting (early May), the OpenEmbedded board and technical
steering committee will select 6 topics for discussion.


To increase global participation, we strongly encourage moderators to
For the actual developer meeting, there will be pre-assigned timeslots for
prerecord 10-15 minutes opening statement describing the topic and current
each topic. The moderator(s) have the option of opening with
state of solutions. These will be posted to the OpenEmbedded youtube channel
a short introduction/presentation to introduce the topic.
so people can view them at a convenient time. We would like to collect
feedback as youtube comments (???) (maybe wiki?) We do not expect perfect
videos, this can be done by recording a zoom meeting of the moderators.
The idea is reach the global community across all time zones and allow
them to provide asynchronous input without losing sleep. The remaining 45
minutes are for reviewing comments and further discussion.
 
For the actual developer meeting, there will be six one hour timeslots for
each topic. The moderators have the option of opening with the video or
doing something else if the online discussions warrants a change. The
moderators should summarize the online comments and then moderate a
discussion with the online live audience. We hope that by presenting
the topic early, people have a chance to think out concrete solutions
for discussion.
 
The topics discussed during the live meeting will be selected from the topics with the strongest
topic moderator support. For example, a topic that no one is willing to moderate will not be selected.
If we have more topics with moderators than we can schedule, we will identify the selected topics before
moderators start preparing the topic introduction material.


==Topic Ideas==
==Topic Ideas==

Revision as of 12:51, 19 May 2021

Location and Time

Co-located with the Yocto Project Summit held on May 25-26, 2021.

The Developers Meeting is scheduled for May 25th between 15:30 and 20:00 UTC. The exact times for each individual topic are TBD.

Format

Since this will be a virtual meeting we are going to change the format around to try and make it easier to get input from the global community and still maintain an in person portion.

As always, we will collect topics on the wiki at https://www.openembedded.org/OEDVM_2021.

For the actual developer meeting, there will be pre-assigned timeslots for each topic. The moderator(s) have the option of opening with a short introduction/presentation to introduce the topic.

Topic Ideas

  • Insight into the life of a Maintainer
  • BSPs: best practice exemplars, cross-project issue tracker, linters, incentive loop design
    • Moderator(s):
  • OE Resourcing: gaps, role naming, work metadata, bridging OSS/commercial
    • Moderator(s):
  • X11 is dead; long live X11! what's to become of core-image-sato?
    • Moderator(s): Trevor Woerner
    • Premise:
      • the Yocto Project provides a sample distribution (poky) and images (core-image-minimal, core-image-base, core-image-full-cmdline…) to give users examples to follow and provide a basis for testing purposes
      • core-image-sato was created to fill the GUI niche as an example and for testing
      • core-image-sato is based on gtk+ 3.x and x11
      • both gtk+ 3 and x11 are EOL/unmaintained
    • Discussion:
      • do we need a GUI image going forward (as an example, for testing purposes)?
      • how much testing does core-image-sato receive?
      • how many teams have based their work on core-image-sato?
      • if a GUI image is still needed, upon which toolkit and compositor should it be based?
      • what's to become of core-image-sato?
      • what's to become of x11 support in oecore?
  • Improving Layer quality: Layerindex combined with a layerchecker
    • Moderator(s): Jan-Simon Möller (dl9pf@gmx.de)

FAQ

The format is new, we will try and add clarifications here.

  1. Do I need to be present at the live meeting to moderate a topic? No, just make sure the topic has one or two people for the live session.
Retrieved from "https://www.openembedded.org/w/index.php?title=OEDVM_2021&oldid=10833"