Dear CentOS enthusiast,
After a slowdown over the past few months, the year is off to a busy start. I'm getting the newsletter out a little later than usual, due to having spent last week in Brussels, at FOSDEM. More about this below.
Special thanks go to Aman Gupta, who stepped up to help with the newsletter this month. If you are interested in helping us write the monthly newsletter, please do get in touch. And see the section below on other ways you can contribute to the CentOS community.
Those of you who are following CentOS Stream progress will have noticed that updates are starting to flow.
dnf update to get those updates, which are a preview of the next release of Red Hat Enterprise Linux. We continue to work on the tooling, as discussed in this email thread, and others on the CentOS-devel mailing list.
Please also see the thread about the choice of git forge solution which will be run by the Red Hat CPE team on behalf of the CentOS community. Your input is valuable in that decision.
The January Board meeting agenda has been posted to the blog: https://blog.centos.org/2020/01/agenda-for-centos-board-of-directors-2020-01-08-meeting/
We've had a number of blog posts in recent days that you'll want to be sure to read:
We issued the following CEEA (CentOS Errata and Enhancements Advisories) during January:
We issued the following CESA (CentOS Errata and Security Advisories) during January:
We issued the following CEBA (CentOS Errata and Bugfix Advisories) during January:
The following releases also happened during January:
The last few weeks have been very busy ones. We had representation at DevConf.cz in Brno, Czech Republic, and at FOSDEM, in Brussels, Belgium, as we do most years. DevConf is an event by developers, for developers, and so there's always a big turnout of CentOS fans there. We had a standing-room-only presentation about CentOS Stream, and the video of that session (as well as all of the others) will be available in the next week or two. Watch our Twitter for that video.
In Brussels, we also ran a one day CentOS Dojo, as we have every year for a decade. We had about 110 in attendance, and some great content. We're starting to publish the video on YouTube, and the talk slides are all published to the event page. There's also a full detailed event report on the blog.
We have a very full schedule of events coming up for the year, which you can always seen listed on the Events page in the wiki.
Follow us on Twitter for announcements as these events shape up over the coming weeks.
If your University, company, or research organization, wants to host a CentOS Dojo, we would love to hear from you. You'll need a space where 100-200 people can attend technical talks, and someone who is able to work with us on logistics and talk acquisition. We'll help promote the event, and work with you to craft the schedule of talks. Drop us a note on the CentOS-Promo mailing list - https://lists.centos.org/mailman/listinfo/centos-promo - with your proposal.
The SIGs - special interest groups - are where most of the interesting stuff in CentOS happens. They are communities packaging and testing layered projects on top of CentOS, and ensuring that they work reliably.
The CentOS Promo SIG has published their quarterly report on the blog.
The AltArch SIG has published new notes about CentOS 8.
We look forward to hearing from you, and helping you figure out where you can fit in.
You could spend months, or even years, planning a first contribution to a code base. Or you could start small, work your way up, and make that awesome contribution today. As with any open source project, there's a lot more than just code.
If you aren't well versed in programming, then start with the documentation. Why? Well, it is a great way to get a feel for the process, and all projects need better documentation. Pick a part of the project that you use, and look at the documentation to see if there's a way that you can improve it.
It’s less about the actual value you added to the project, and more about entering the OSS community and contributing whatever you can to help the community, If you’re a maintainer, help a newcomer make their first PR! Or help them to work on the documentation.
If you want to get involved, but you're not a programmer or packager, there's still a ton of places where you can plug in.
The community needs dedicated people who are willing to help the community grow. Start contributing today!