The board had its monthly meeting last week. The recording, minutes,
and recap are all available.
Recording:
https://youtu.be/Tmr1MI7bY74
Minutes:
https://hackmd.io/@centosboard/SkDqdm_En
Recap:
https://blog.centos.org/2023/05/centos-board-meeting-recap-may-2023/
We'll have the followup office hours this Thursday, May 18, at 14:00
UTC. Everybody is welcome to join and talk to the baord.
https://us06web.zoom.us/j/85621888235?pwd=UmVzdy9jU1VKVU81MENVTU5nNXYxdz09
Hightlights of the recap:
* The board discussed work left to be done around the ISA SIG (Issue
115) and the mission statement (Issue 85).
* We had a lengthy conversation about defining success and developing
project goals.
* We discussed some issues around trademarks, including trademark use
for mirrors (Issue 113 and Issue 114).
* We had brief updates on secureboot (Issue 67) and Azure images (Issue
3).
* Due to the cancellation of DevConf.US, we're working on moving CentOS
Connect to Flock in August.
Hi SIGs folks (and testing community) !
Just to inform you that next Monday (May 15th) , we'll migrate our
sign-and-push process to a different infra/machine, but you shouldn't
see any service disruption.
We'll also implement signing for the packages tagged to -testing, and so
landing on https://buildlogs.centos.org.
It's a request that came through the Infra tracker
(https://pagure.io/centos-infra/issue/1131) and that was approved by the
CentOS Project board (all details in that ticket)
There is nothing to do at your side (it's not an opt-in scenario, it
will be implemented for all SIGs), as it will be transparently processed
next time you'll (un)tag-build a package (or more) to your -testing
tags. (We can also manually process existing -testing repositories on
demand , should there be a need/request)
You can though bump your 'release' pkg (that contains the .repo files)
to reflect gpgcheck=1 and point to same key as for repositories going to
the mirror network, but that's optional (SIG's choice)
I'll also update the SIG Guide (https://sigs.centos.org/guide/delivery/)
to reflect that change.
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Let's chat about centos mailing lists !
https://lists.centos.org is powered by mailman package, available in
CentOS 7 , itself going EOL next year.
There is no packaged (yet) mailman3 stack (more components than simple
mailman 2 stack).
Options :
# use mailman2 package from RHEL8
That means (in theory) that we can just reinstall the machine with
RHEL8, and use the package that is available in AppStream repository:
mailman.x86_64
3:2.1.29-12.module+el8.5.0+13466+327eb9f3.2
Normally that should be more or less (to be tested though) transparent
migration, but as that module is still relying on python2 itself, we
don't know when it will itself go EOL in RHEL8 (BaseOS should be 10y but
apps in AppStream can have a shorter TTL)
# migrate to mailman3
Clearly much more work to do including see if the mailman3 stack
maintainer can branch to epel9 and then we can reuse it.
Also time to investigate how to import previous archives from mailman2
to mailman3 but should be doable (needs time to investigate and a PoC)
# something else ?
All comments, opinions are welcome and let's discuss it in advance and
not wait next year when machine will be powered off
Kind Regards,
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]
Hi Everyone,
Our next board meeting will take place at 20:00 UTC tomorrow:
`date -d "2023-05-10 20:00 UTC"`
If you would like to attend please send me an email to
alphacc(a)centosproject.org ( please do not reply to @centos-devel or use
another email address) and you will receive a link to a Zoom meeting
room with a passcode, 1 hour before the meeting takes place.
The agenda can be checked at (work in progress) :
https://hackmd.io/@centosboard/SkDqdm_En
As a reminder we will enforce few rules :
* Wait to be recognized by the Chair before speaking
* Respect the Chair when told your time to speak is over - this will
allow us to remain on agenda, and complete the meetings in the
allotted time
* In the event that there are Board-confidential topics, these will be
put at the end of the meeting, in Executive Session, and guests will be
asked to leave. We hope to minimize these items, but they do sometimes
happen. The most common scenarios in which this may happen are personnel
issues, or information that Red Hat wishes to share with the Board, but
is not yet public.
* Muting of participants, or, in extreme situations, ejection from the
meeting, is at the sole discretion of the Chair.
* Meetings will be recorded, and published to YouTube (possibly with
edits/redaction, as approved by the Directors). Thus, by joining the
meeting you consent to have your presence at the meeting, and anything
you say during the meeting, made public.
I hope some of you can join.
Sorry for the late announcement.
thanks,
--
Thomas 'alphacc' Oulevey
CentOS Board of Directors Secretary
alphacc(a)centosproject.org
CentOS Stream 8 and CentOS Linux 7 will both come to an end in about a
year. CentOS Stream 8 will reach end of builds on May 31, 2024. CentOS
Linux 7 will reach end of life on June 30, 2024.
More information is available on the CentOS blog:
https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-an…
Please help us spread the word by linking to the blog post. Nobody
likes getting caught off guard on these things.
Thanks,
Shaun McCance
CentOS Community Architect
Red Hat Open Source Program Office
===================================
#centos-meeting: Virtualization SIG
===================================
Meeting started by sbonazzo at 16:02:28 UTC. The full logs are available
athttps://www.centos.org/minutes/2023/May/centos-meeting.2023-05-03-16.02.l…
.
Meeting summary
---------------
* kata-containers (sbonazzo, 16:03:22)
* no updates this week (sbonazzo, 16:03:29)
* oVirt updates (sbonazzo, 16:04:30)
* upstream developers are suggesting users to swithch to nightly
builds as there are no regular releases planned (sbonazzo,
16:04:42)
* LINK:
https://lists.ovirt.org/archives/list/users@ovirt.org/thread/DMCC5QCHL6ECXN…
(sbonazzo, 16:04:49)
* Automotive SIG collaboration (sbonazzo, 16:05:55)
* working with qemu upstream adding virtio-multitouch and enable GTK3
to use it (sbonazzo, 16:06:06)
* LINK:
https://lists.nongnu.org/archive/html/qemu-devel/2023-04/msg01961.html
(sbonazzo, 16:06:14)
* working with qemu upstream adding virtio shared dma-buf (sbonazzo,
16:06:34)
* LINK:
https://lists.gnu.org/archive/html/qemu-devel/2023-05/msg00598.html
(sbonazzo, 16:06:44)
* working with qemu upstream adding Pipewire audio backend for QEMU
(sbonazzo, 16:06:55)
* LINK:
https://lists.nongnu.org/archive/html/qemu-devel/2023-04/msg02287.html
(sbonazzo, 16:07:03)
Meeting ended at 16:11:06 UTC.
Action Items
------------
Action Items, by person
-----------------------
* **UNASSIGNED**
* (none)
People Present (lines said)
---------------------------
* sbonazzo (23)
* centguard (4)
* etrunko (4)
--
Sandro Bonazzola
MANAGER, SOFTWARE ENGINEERING - Red Hat In-Vehicle Operating System
Red Hat EMEA <https://www.redhat.com/>
sbonazzo(a)redhat.com
<https://www.redhat.com/>
*Red Hat respects your work life balance. Therefore there is no need to
answer this email out of your office hours.*
The CentOS password reset procedure email is sent from:
Fedora Account System <fas(a)fedoraproject.org>
Does this mean that the password reset affects FAS as well?
Thanks,
Florian