From: "Trevor Woerner" <twoerner@gmail.com>
To: yocto@yoctoproject.org
Subject: Yocto Technical Team Minutes, Engineering Sync, for June 16 2020
Date: Tue, 23 Jun 2020 14:52:38 -0400 [thread overview]
Message-ID: <20200623185238.GA16972@linux-uys3> (raw)
Yocto Technical Team Minutes, Engineering Sync, for June 16 2020
archive: https://docs.google.com/document/d/1ly8nyhO14kDNnFcW2QskANXW3ZT7QwKC5wWVDg9dDH4/edit
== disclaimer ==
Best efforts are made to ensure the below is accurate and valid. However,
errors sometimes happen. If any errors or omissions are found, please feel
free to reply to this email with any corrections.
== attendees ==
Trevor Woerner, Jan-Simon Möller, Armin Kuster, Alejandro, Richard Purdie,
Stephen Jolly, Steve Sakoman, David Reyna, Mark Morton, Tim Orling,
Scott Murray, Joshua Watt, Vineela, Michael Halstead, Ross Burton, Randy
MacLeod, Daniel Dragomir, Paul Barker, Bruce Ashfield, Jeremy Puhlman, Mark
Asselstine, Peter Kjellerstedt
== notes ==
- 3.1.1 just out of QA, looks good, will go to TSC for release
- 3.2-m1 built shortly (next day or 2)
- still struggling to find maintainers for key components
- kudos to Paul Barker and Joshua Watt for key patches
== general ==
Randy: growth of medium+ is apparent
Steven Jolly: mediums down, medium+ up. perhaps an issue of grading
RP: there’s a natural undulation that corresponds with releases
RP: to Michael: do we have the data going back 10 years?
MH: not for full 10 years
RP: i’d like to get the WDD charts going back as far as possible
see: https://wiki.yoctoproject.org/charts/combo.html
RP: kudos to Paul and JPEW for stability improvements, some are invasive,
don’t think we should backport them, however
RP: i see Mark Morton is on, any updates?
MM: should see updates later today
RP: lots of stuff on AB, testing, etc aren’t documented anywhere, these
changes are to improve these areas
MM: there’s a meeting tomorrow to discuss conversion to Sphinx, kudos to Nico
David R: links are up to yocto devday! lots of good content, good speakers,
separate from ELC
JPEW: same platform as ELC?
David R: no, we’re just using zoom (professional, holds 500 people)
Scott: using the slide deck as before?
David: yes, we’ll each host our own slides, but i want a master,
consolidated deck
JPEW: 16x9 slides please?
David: yes, we have to ☺
Randy: maybe we can recruit at devday too (maintainers for key areas)?
RP: if anyone has any other ides, please approach the TSC
JPEW: i like to add a “how to get involved” slide at the end of any
presentation
RP: should start something on wiki, then it can be used for more than slides
in presentations
Randy: sometimes it’s difficult for someone to contribute due to lawyers
RP: best to introduce the lawyers from one company (who can’t figure it out)
to lawyers who have figured it out so they can talk in their own language
Randy: any suggestions?
RP: i’ll poke LF
Paul: “latest activity” on yocto website seems to have stopped updating
about a month ago (Scott noticed it too)
Michael: i’ll raise it with Tracy and Nico, should be an easy fix
reply other threads:[~2020-06-23 18:52 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200623185238.GA16972@linux-uys3 \
--to=twoerner@gmail.com \
--cc=yocto@yoctoproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox