The CentOS Board of Directors is delighted to welcome two new directors - Davide Cavalca and Josh Boyer - to the Board.
Please join us in welcoming them, and thanking them for their willingness to dedicate some of their time to the endeavor of steering the CentOS Project.
Once again, we thank outgoing directors Karsten Wade and Carl Trieloff for their years of service.
Release for CentOS Linux 8 (2105) We are pleased to announce the general availability of the latest version of CentOS Linux 8. Effectively immediately, this is the current release for CentOS Linux 8 and is tagged as 2105, derived from Red Hat Enterprise Linux 8.4 Source Code. As always, read through the Release Notes at: http://wiki.centos.org/Manuals/ReleaseNotes/CentOS8.2105 - these notes contain important information about the release and details about some of the content inside the release from the CentOS QA team. These notes are updated constantly to include issues and incorporate feedback from users. ---------- Updates, Sources, and DebugInfos Updates released since the upstream release are all posted, across all architectures. We strongly recommend every user apply all updates, including the content released today, on your existing CentOS Linux 8 machine by just running 'dnf update'. As with all CentOS Linux 8 components, this release was built from sources hosted at git.centos.org. Sources will be available from vault.centos.org in their own dedicated directories to match the corresponding binary RPMs. Since there is far less traffic to the CentOS source RPMs compared with the binary RPMs, we are not putting this content on the main mirror network. If users wish to mirror this content they can do so using the reposync command available in the yum/dnf-utils package. All CentOS source RPMs are signed with the same key used to sign their binary counterparts. Developers and end users looking at inspecting and contributing patches to the CentOS Linux distro will find the code hosted at git.centos.org far simpler to work against. Details on how to best consume those are documented along with a quick start at: http://wiki.centos.org/Sources Debuginfo packages have been signed and pushed. Yum configs shipped in the new release file will have all the context required for debuginfo to be available on every CentOS Linux install. This release supersedes all previously released content for CentOS Linux 8, and therefore we highly encourage all users to upgrade their machines. Information on different upgrade strategies and how to handle stale content is included in the Release Notes. Note that older content, obsoleted by newer versions of the same applications are trim'd off from repos like extras/ and centosplus/ ---------- Download We produced the following installer images for CentOS Linux 8 # CentOS-8.4.2105-aarch64-boot.iso: 677838848 bytes SHA256 (CentOS-8.4.2105-aarch64-boot.iso) = 106d9ce13076441c52dc38c95e9977a83f28a4c1ce88baa10412c1e3cc9b2a2b # CentOS-8.4.2105-aarch64-dvd1.iso: 7325042688 bytes SHA256 (CentOS-8.4.2105-aarch64-dvd1.iso) = 6654112602beec7f6b5c134f28cf6b77aedc05b2a7ece2656dacf477f77c81df # CentOS-8.4.2105-ppc64le-boot.iso: 722780160 bytes SHA256 (CentOS-8.4.2105-ppc64le-boot.iso) = 4a83e12f56334132c3040491e5894e01dfe5373793e73f532c859b958aeeb900 # CentOS-8.4.2105-ppc64le-dvd1.iso: 8484990976 bytes SHA256 (CentOS-8.4.2105-ppc64le-dvd1.iso) = 9cfca292a59a45bdb1737019a6ac0383e0a674a415e7c0634262d66884a47d01 # CentOS-8.4.2105-x86_64-boot.iso: 758120448 bytes SHA256 (CentOS-8.4.2105-x86_64-boot.iso) = c79921e24d472144d8f36a0d5f409b12bd016d9d7d022fd703563973ca9c375c # CentOS-8.4.2105-x86_64-dvd1.iso: 9928966144 bytes SHA256 (CentOS-8.4.2105-x86_64-dvd1.iso) = 0394ecfa994db75efc1413207d2e5ac67af4f6685b3b896e2837c682221fd6b2 Information for the torrent files and sums are available at http://mirror.centos.org/centos/8/isos/ -------- Additional Images Vagrant and Generic Cloud images are available at: http://cloud.centos.org/centos/8/ Amazon Machine Images for Amazon Web Services are published by ID into a number of regions. A table of AMI IDs can be found here: https://wiki.centos.org/Cloud/AWS ---------- Getting Help The CentOS ecosystem is sustained by community driven help and guidance. The best place to start for new users is at http://wiki.centos.org/GettingHelp We are also on social media, you can find the project: on Twitter at :http://twitter.com/CentOS on Facebook at :https://www.facebook.com/groups/centosproject/ on LinkedIn at :https://www.linkedin.com/groups/22405 And you will find the core team and a majority of the contributors on irc, on irc.Libera.chat in #centos ; talking about the finer points of distribution engineering and platform enablement. ---------- Contributors This release was made possible due to the hard work of many people, foremost on that list are the Red Hat Engineers for producing a great distribution and the CentOS QA team, without them CentOS Linux would look very different. Many of the team went further and beyond expectations to bring this release to you, and I would like to thank everyone for their help. We are also looking for people to get involved with the QA process in CentOS, if you would like to join this please introduce yourself on the centos-devel list (http://lists.centos.org/mailman/listinfo/centos-devel). Finally, please join me in thanking the donors who all make this possible for us. Enjoy the fresh new release! Thanks, Johnny Hughes
Quorum and started at :05
Directors in attendance were:
Others in attendance:
Topic: CentOS Stream Feature Request SIG approval
Topic: Departure of Board members and Board nominations
Proposal: Monthly meeting with the community to discuss board meeting outcome
Reviewed issues :
Adjournment at :38
Thank you to everyone who responded to my call for feedback on the SIG process. A few people responded on-list. More people responded off-list. I’ve summarized common complaints, and in a few cases provided comments verbatim - especially when they already went to a public list.
Please see the centos-devel mailing list for further discussion of what happens next.
The following areas were identified by one or more people as pain points in the SIG process.
Several people said that we do a poor job of communicating what SIGs are for, what should be a SIG, whether something should be a SIG or part of EPEL, and, in general, what the value of a SIG is.
When SIGs were introduced, they were meant to provide an incubator for projects in the CentOS space and also to provide infra/space to give projects a chance to CI test within CentOS, i.e "how does your project work on CentOS?" Has that focus been dropped? If not, would it be a good idea to reinforce the message?
We need to make it clear that Red Hat still has an interest in CentOS. That message would also be valuable for [Red Hat employees]. CentOS is an important place to put Red Hat’s “upstream first” message into action, but this often gets ignored.
Almost everyone said that the proposal process was vague and opaque.
It is unclear what the board is looking for in a proposal. While there is a template - https://wiki.centos.org/SpecialInterestGroup/ProposalTemplate - examples of good proposals, and what kind of specific things the board will look for, would make this process easier.
Access to the wiki to post the initial proposal is a bit of a chicken-and-egg - that is, without a SIG, who has authority to edit a wiki page for the SIG?
The deliberation/discussion of the proposal should happen on-list, not hidden/secret in board meetings. This will also give other potential projects insight into what they should be thinking about in their proposals.
Several people said that onboarding was confusing and undocumented, and seemed to assume you already know what you’re supposed to do.
Note: Several people specifically called out Fabian Arrotin as being extremely helpful in this setup process, with the caveat that he may not scale if we start getting more SIGs onboarding.
The “what’s next” after a SIG has been approved is very unclear. Once approved, what is the process for getting resources set up?
In the past, the SIG onboarding was often gated on one person, and getting their attention was difficult. This should be better with the new Infra sig.
One of the biggest hurdles is the repo setup (deciding on the cbs/koji setup, naming, setting up repositories for mirrors, etc). If you have never touched koji before, this is going to be tough for you. We need much better onboarding documentation for beginners, along with recommended best practices.
If you’re not a Red Hat “insider,” there’s a good chance that your SIG proposal will be ignored, or at least not given priority. The onboarding for [several SIGs] too more than a year - not because it was controversial, but because nobody prioritized it.
A number of respondents commented from the contributor side, about the lack of information/communication from SIGs.
The SIG wiki page says that quarterly reporting is required, but the majority of SIGs do not report, and there is no consequence for failing to report.
It is very difficult to find out from the SIGs themselves what opportunities there are for involvement. One respondent replied “I'd like to be more deeply involved in the [name] SIG. It's always a surprise to me how much I push to be a part of the group and how little opportunity there is.” SIGs need to be much more proactive in what volunteer opportunities there are.
Some SIGs have weekly meetings, some monthly, and some never meet. This is very frustrating to people who want to get involved in the SIGs, but don’t know where to start.
Having an easier, documented way to contact a SIG with questions or offers of help is needed. Right now, we have out-of-date wiki pages with inaccurate lists of SIG members, and no way to contact them even if it was accurate.
SIG wiki pages must be updated with current information. They should also have a standard format, so that basic required information is always available.
Several developers complained that they were just expected to know what to do, and not provided much guidance or advice as to how to proceed.
Clearer documentation (or pointers to documentation elsewhere) about package building, and how to set up a CI environment.
It would help if every SIG had the same buildroot setup, so that you know what to expect, and moving from one SIG to another was easier. This will increase cross-SIG engagement.
Developer experience on git.centos.org and CBS. Notably:
- the way the lookaside works: https://pagure.io/centos-infra/issue/259
- hard to discover clone URLs: https://pagure.io/centos-infra/issue/245
- support for modularity in CBS: https://pagure.io/centos-infra/issue/294
The PR workflow in particular is problematic -- right now we rely on SIG members pushing directly to the repos, which makes code review difficult. It's also a blocker for external contributions (as, though one can technically put up a PR, there is no way to actually merge it).
I would love to have something closer to the workflow in Fedora. specifically:
- allow SIG members to review and merge PRs onto their branch
- kick off scratch builds on PRs to get signal
We need a way for SIGs to publish structured documentation on docs.centos.org, akin to the "quick docs" model that Fedora uses.
Missing -devel subpackages (I know this has been discussed a lot and fix is in progress).
I'd like to build, tag and push release rpms (as centos-release-openstack). In CentOS7 we could build and tag by ourselves (although it needed infra action to push). In CentOS8 we need to rely on CentOS infra to build and publish them in extras repos.
TL;DR: #centos and #centos-* are moving to libera.chat
Over the past few days, there has been some upheaval on the Frenode IRC network, resulting in a number of the staff members quitting and starting a new IRC network. I don't wish to explain all the details here, but you can read more at https://kline.sh which also links to other sources.
The various ops have discussed the situation, and we intend to migrate all of the various #centos-* channels from Freenode over to libera.chat over the coming days.
This will take time, since libera is still spinning up, and some servers are moving from one network to the other.
As libera is still in the early stages of setup, you may have significantly more timeouts/disconnects, netsplits and other issues for now. Until the new network is fully stable, we'll all continue to be present in the Freenode channels.
Please bring further questions to the IRC channels, which you can join on irc.libera.chat.
The Community Platform Engineering group, or CPE for short, is the Red Hat team combining IT and release engineering from Fedora and CentOS. Our goal is to keep core servers and services running and maintained, build releases, and other strategic tasks that need more dedicated time than volunteers can give.
See our wiki page here for more information: https://docs.fedoraproject.org/en-US/cpe/
We are hiring new talent to come work full time on Fedora and CentOS. The following positions are now open:
Please note that due to a constraint in how the jobs system works, a single country is nominated for the advertisement. Please kindly ignore that, two of the roles are available in the geographical regions outlined above.
We are looking forward to meeting you and hopefully working with you soon!
Quorum and started at :05
Directors in attendance were:
Others in attendance:
A welcome was given to guest Josh Boyer, representing RHEL engineering interests.
Topic: Board reappointment, and nomination of new directors
Discussion of development packages not provided in CentOS Stream: Red Hat is keenly aware of the desire to make buildroot packages available in the CentOS Stream project. Progress has been made on plans to enable this in some manner in CentOS Stream without requiring changes to Red Hat Enterprise Linux. The team is currently working to resolve some technical issues.
Discussion of CentOS Stream SIG proposal. https://git.centos.org/centos/board/issue/33 and https://wiki.centos.org/SpecialInterestGroup/StreamFeatureRequest General support, but will take this to the mailing list and commit to timely response to this request.
Adjournment at :00
On 2021-03-10 the CentOS Board of Directors met to discuss ongoing business.
A proposal to discuss the re-appointment of Directors has been presented by Karsten Wade. The document will be reviewed and it will be then proposed for approval during the next meeting. (More info on the governance updates in issues #22 and #24).
Rich Bowen, annouced that a new online Dojo is planned on May 13th and 14th 2021. All the details can be found at :
No other issue has been discussed this month, and updates will be amended to tickets if necessary.