Hi Everyone,
Our next board meeting will take place at 20:00 UTC on next Wednesday:
`date -d "2023-10-11 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 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/B1RoGTRla
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.
thanks,
--
Thomas 'alphacc' Oulevey
CentOS Board of Directors Secretary
alphacc(a)centosproject.org
Hi Folks,
I've filed the following for discussion with the CentOS Board: https://git.centos.org/centos/board/issue/123
I won't re-paste the text of the ticket here, but the overal vision for this group is to evaluate tools we use to build things in the CentOS project, coordinate technical effort among the SIGs, govern certain secure assets (like SIG Secureboot keys), and make recommendations for future technologies to make available in the project.
To answer a couple of questions I've had so far:
- This group is complementary to (but not replacing) the CentOS Infra SIG which is focused on execution of our technology strategy
- Everything written in the description is open for discussion, and I look forward to hashing out some of the finer governance points as we go
--
Brian Stinson
brian(a)bstinson.com
This covers the last several meetings, for which I failed to send
minutes. Sorries.
# zlib-ng
We want to replace zlib with zlib-ng (in compat mode) for CentOS 10
Stream. In support of that, it would be interesting to rebuild CentOS 9
Stream with zlib-ng in the buildroot (again, in compat mode).
AI: Florian to talk to some folks and see what can be done to support
the zlib-ng transition effort.
# ISA SIG meeting at FOSDEM
I've confirmed internally that there will be some CentOS-related
activity in the days before FOSDEM. There could even be a slot in the
official schedule for the ISA SIG if we wanted that.
# Blog post highlighting Intel work on GCC 13
Previously, in a separate venue, Intel shared their GCC 13 performance
work. We wanted to encourage them to write a blog post about it, but it
turns out that it already exists:
Build Innovation and Performance with GCC* 13
<https://www.intel.com/content/www/us/en/developer/articles/technical/build-…>
# Upcoming AArch64 work.
There might be some AArch64 work items in the ISA SIG space in the
future (validating a GCC bug fix, and experimenting with LSE atomics now
that the Raspberry Pi 5 with support for them has been announced).
Thanks,
Florian
Hi all,
this Sunday, our zabbix monitoring platform informed us that there were
plenty of nodes unreachable in community cage, and after some
investigation it's a whole rack that was cut off access from network
switches.
That causes issues for multiple workloads, including duffy CI infra env,
CentOS Stream env (aka https://testing.stream.centos.org) or
storage/mirror servers used for https://cbs.centos.org.
As we don't know when the root cause will be investigated by the network
team managing the network infra, we have disabled the koji builders, so
don't even try to submit builds to cbs.centos.org as they'd just be
stuck waiting for builders to be available (themselves disabled until we
have access to internal mirror)
--
Fabian Arrotin
The CentOS Project | https://www.centos.org
gpg key: 17F3B7A1 | @arrfab[@fosstodon.org]