At the end of each CentOS Dojo we have an attendee survey. While these never have the response rate I'd like, they do produce interesting data that help us improve future events.

Here's the results from the survey from the Dojo in Brussels, 2020

Q1: I use CentOS for ...

17 responses
76.5% Running services at work
41.2% Software development (professional)
41.2% Running services at home
11.8% My desktop computer
5.9% Software development (personal, hobby)

Q2: I came to this event from:

64.7% Elsewhere in Europe
23.5% Elsewhere in the world
11.8% Brussels

Q3: Talks were ...

88.2% About right
11.8% Not technical enough

Q4: I would like to see more content about:

  • Specific CentOS topics, many talks were not very CentOS related and were then duplicated at the nearby FOSDEM
  • Microsoft's activities to dominate the market
  • CentOS internals
  • id management. Integration with active directory
  • Cloud and storage
  • Containers
  • How to get involved and where is help required
  • How to contribute to CentOS
  • New features in new releases, process of preparation new releases

Just one remark on this last item: We can only schedule talks that are submitted, and for this event, in particular, we had very few submissions. So take this last item as a hint of what kind of talks we'll be looking for next time.

Thank you to everyone that participated in the survey. Your feedback is very helpful!

We will be holding a CentOS Dojo at Facebook, Menlo Park, (San Francisco area) on April 24th. This is the Friday immediately before Red Hat Summit, so you can tack a few extra days on the front of your Summit trip and see how CentOS is used at Facebook.

Details of the event are available at

The Call for Presentations is now open. We're looking for technical talks about stuff that is in and on CentOS. You can see examples of the content we have run in the past at

88% of our attendees in Brussels said that the content was about right, while 12% said it was not technical enough, if that helps set your expectations of what talks to submit.

The CFP closes on March 15th, and space is extremely limited, so don't wait. Get your talk submissions in now.

  1. Do Directors have any questions or concerns about the process being followed to update the CentOS Project logo? Full story in this blog post by Tuomas Kuosmanen;
    1. Specific design concerns should be handled on centos-devel or in the design repo discussion.
  2. Having a face-to-face Board and/or leadership meeting in or near Paris in Summer 2020. What month might be good for Directors?
  3. Directors and other Project leaders are invited and encouraged to collaborate with the now four community architects from Red Hat working in/around the CentOS Project: Rich Bowen, Brian Exelbierd, Tuomas Kuosmanen, and Karsten Wade.
  4. Report out from Karsten on the Board interview/working session room at the Brussels CentOS Dojo.
  5. Consent items
    1. Adopt minutes from 2020-01-08 meeting
    2. Noting that Fabian Arrotin has resigned his role as a CentOS Project Director as of October 2019.
  6. Rolling (last from 2020-01-08):
    1. Any other topics aka What other things do you want on our master initiatives list?
    2. Stepping-up our meeting norms
    3. Transparency initiatives

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:

We've had a number of blog posts in recent days that you'll want to be sure to read:

Releases and updates

On January 19th, CentOS Linux 8.1.1911 was released. You can read the release notes here. Also, have a look at the longer-term roadmap for this, and our other CentOS releases.

Errata and Enhancements Advisories

We issued the following CEEA (CentOS Errata and Enhancements Advisories) during January:

Errata and Security Advisories

We issued the following CESA (CentOS Errata and Security Advisories) during January:

Errata and Bugfix Advisories

We issued the following CEBA (CentOS Errata and Bugfix Advisories) during January:

Other releases

The following releases also happened during January:

Events, CentOS Dojo, and FOSDEM

The last few weeks have been very busy ones. We had representation at 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.

Upcoming events

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.

Host a Dojo

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 - - with your proposal.

SIG Reports

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.

The Cloud SIG and the Software Collections SIG, held SIG update sessions at the recent CentOS Dojo in Brussels. Their slides are on the event page, and the video will be posted shortly.


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.

  • Design - Graphic and design elements for the product itself, the website, materials for events, and so on, are always a great need. This is true of any open source community, where the focus on code can tend to neglect other aspects. Indeed, right now there's an ongoing project to update the CentOS logo and visual identity.
  • Events - While CentOS has an official presence at a few events during the year, we want a wider reach. If you're planning to attend an event, and want to represent CentOS in some way, get in touch with us on the centos-promo mailing list to see how we can support you.
  • Promotion - The Promo SIG does a lot in addition to just events. This includes this newsletter, our social media presence, blog posts, and various other things. We need your help to expand this effort.
  • Documentation - Any open source project is only as good as its documentation. If people can't use it, it doesn't matter. If you're a writer, you are in great demand.

If any of these things interests you, please come talk to us on the centos-devel mailing list, the centos-promo mailing list, or any of the various social media channels.

The community needs dedicated people who are willing to help the community grow. Start contributing today!


The CentOS Promotion SIG exists to provide promotion, and consistent messaging, of CentOS, both at physical events and online.


The Promo SIG continues to struggle to find interested individuals to contribute to the effort. We are very interested in finding people to help with events, our presence on social media, and writing content for our monthly newsletter.

In the coming quarter we will be attempting to more clearly document what volunteer roles are available, in order to more effectively attract people to those roles.

The SIG wiki page - - accurately reflects SIG membership.


In the past quarter (November - February) we participated in just one event - SC19 (SuperComputing) in Denver: A number of blog posts about it appeared on

Our most active social media presence is Twitter. In this quarter:

November: 239.2k impressions
December: 240.8k impressions
January: 367k impressions

Our engagement on other social media platforms - Facebook, Reddit, LinkedIn - tends to be much less, and typically around events and the monthly newsletter.

In the January and early Febrary, we participated in, FOSDEM and FOSSAsia. A report from the FOSDEM CentOS Dojo is on the blog.

We are in the planning stages for Dojos, as listed on Details will be posted there as they are available.

We are, as always, looking for organizations who are interested in hosting Dojos around the world.

Issues for the Board

We have no issues to bring to the board's attention at this time.

Tomorrow, I intend to push a change to nodes that will have a (good) impact to CentOS EC2 instances running from AWS network.

Thanks to AWS, sponsoring the required backend infra for this to happen, our mirrorlist nodes will redirect yum/dnf operations internally in the EC2/AWS network.

What does that mean for you ?

  • faster updates (due to Cloudfront caching, and so most of the recent packages/rpms being kept in cache in each region)
  • less data transfer costs (due to such updates being served from inside EC2 network[s] and so not leaving EC2 infrastructure)

How does it work ?

  • When your CentOS EC2 instance hits, it's identified as coming from EC2 network, thanks to, loaded into our mirrorlist code
  • You'll be redirected to CloudFront, itself using a dedicated origin to which we automatically push all updates directly
  • if you're the first one asking for that update/rpm, Edge (cache server in that region) will retrieve it and will cache it while also serving it to you
  • if someone requested same rpm that you're asking for, it will be directly served from cache, so at "local" speed (we saw some rpm being downloaded on second attempt at ~80MB/s)

We already tested with several volunteers in our staging environment that it was working fine, and so far so good.

We have no real estimate about the number of CentOS EC2 instances in all regions, so we plan on doing a canary-style deployment, so Ansible switching our mirrorlist code/role one-by-one and observe the cloudfront statistics.

Should you encounter any issue, feel free to reply to this thread and/or #centos-devel on

CentOS Dojo, Brussels, January 31, 2020
Grant Place Marriott
Event details:

Just the facts:

Registered: 125
Attended: Approx 110 (12% no-show)
13 sessions. Slides and video will be posted at the above address over the coming 2 weeks.

Event report:

We held the annual CentOS Dojo ahead of FOSDEM again this year. We were at the Grand Place Marriott for (I think) the 4th year. (Maybe 3rd?) This venue is always very helpful in supporting our event, and addressing problems as they arise. Recommend we keep doing it there for next year.

We “sold out” of our 125 tickets by 3 weeks before the event. Leading up to the event, I encourage registered attendees to cancel their tickets if they were not, in fact, attending, and I saw probably 30 cancelations, all *immediately* followed by new registrations. As a result, our no-show rate was very low. Note that the 110 attendees is an estimate based on an after-lunch count, and is *probably* low, as people came and left throughout the day.

I would consider running more tracks, except that getting talks for the event was exceptionally difficult this year. I’m not sure why that was, but I need to do more direct talk solicitation (ie, asking individuals to give specific talks) ahead of next year’s event.

We started the day with a session on CentOS Stream, which was standing room only, and generated some really good questions. People seem very interested in Stream, and seem to get the concept. Related: Facebook said, in their talk, that they are retiring CentOS 7 and moving their entire infra over to CentOS Stream. That’s *millions* of servers. So … wow.

We saw a huge spike in Twitter engagement on the 31st (roughly 9 times usual) fading a little on Saturday (roughly six times usual) and Sunday (about 3 times usual). Historically, we’ll see another spike as we start posting the slides and videos in the coming days.

During the course of the day, we arranged for upcoming CentOS Dojos at CERN (October 23rd) and Facebook (tentatively, April 24, which is *really* soon). Details coming to CentOS news channels near you hopefully by the end of this week.

We added a new feature this year - we had a room where attendees were encouraged to go to discuss their CentOS experiences with Karsten Wade. These conversations were confidential, and encouraged candid feedback about what was broken, what they’d like to see done in the coming year, challenges they face in the community, and so on. We hope to see some feedback from Karsten about this in the coming days.


This event is definitely worth doing. The attendees tend to be the core of our project, and other deeply technical people using CentOS. The hallway track is always active, showing that people come as much for the interactions as for the technical content.

The struggle to find content, though, is troubling, and something that we need to work on throughout the year, rather than just during the CFP. My impression is that people don’t think that what they’re working on is of general interest. However, feedback from actual talks is that our audience really wants to see the every day stuff (here’s how I made my life easier on a normal day at work) is every bit as interesting as the cutting edge talks (here’s a fancy new thing that might be useful to you 2 years from now). So, reminder to self: Solicit these talks all year long, as you see interesting *practical* things being discussed on the lists, not just the shiny new stuff.


The current logo has a long history, and is well recognized, but the design is essentially 15 years old.  There have been comments on the mailing list that the brand should be updated. The logo also has a lot of colors which makes printing and embroidery more expensive, and sometimes leads into color matching issues as well.

CentOS project has also grown to be more than just a Linux distribution. The Special Interest Groups, CentOS Stream, and other sub-projects could also use a related logo, and we thought it would be a good time to update the branding to reflect that.

As CentOS Stream needed some kind of a logo, we had the Red Hat brand team create some proposed logos for Stream announcement. At the same time we started to feel that it was the right time to refresh the logo and branding as well, and that the process should happen openly in the community.


We shared the Stream logo design files with the centos-devel list in November, which started a good collaboration with me and Alain (who has been doing great work on the current logo and brand style wiki pages) and we quickly realized, that we need to take the design idea brainstorming away from the developers mailing list to avoid spamming everyone with attachments (or risking possible broken links to images late in the list archives) - so we started a discussion in the CentOS Artwork issue tracker.

This lead to a lively and active collaboration, and we attracted also brokenkeyframe to contribute. We went through several ideas, some better than others, and settled into a stylized version of the original chaos symbol of the CentOS logo, which keeps the history alive, while making it more modern.

The logo is a single color, which makes it easy for embroidery for example, but also lets us have the logo with a photo or texture as background. The corners of the chaos symbol are slightly rounded to give it a modern touch, and we also updated the font to match the style of the symbol.

The font is called Montserrat, originally created by Julieta Ulanovsky, a designer from Argentina. Montserrat is an effort to celebrate and preserve the historic signs and lettering found in the Montserrat neighborhood of Buenos Aires. Montserrat is a beautiful typeface with several variants, and it is licensed with the libre SIL Open Font License. Julieta had a successful Kickstarter project to fund the development, and since then the project has been updated and extended by a community of collaborators. The Kickstarter page has a nice video introduction, if you are interested in typography or inspiration behind the project.

We also thought about sub-project logos (Stream, the distro itself, various Special Interest Groups) and worked on a logo template system for those.

The work will be presented to the CentOS governing board soon, but we wanted to share our current progress (and the path that lead to it) with all of you. It is likely that not so many of you have actively followed our progress on the issue tracker.

We will announce this blog post also on the CentOS developers mailing list, and I encourage you to share your feedback there, instead of commenting on this post, or on the above git issue, which we wish to keep on the topic of design, so we can focus on the task better. We’ll be sure to read your comments on the mailing list and take them to heart.

Also, I want to thank everyone who contributed and shared their thoughts and feedback!

About this document

This document lays out a problem statement, requirements, and constraints according to the Open Decision Framework. The aim is to arrive at a transparent decision about the future of a git forge for the communities that represent the platforms that the Community Platform Engineering (CPE) team manages. Those communities are the CentOS and Fedora platforms and also include the Red Hat Enterprise Linux (RHEL) platform from a tooling and integration perspective. This document is the first in a series of documents capturing the conversation about the problems we face and driving the conversation to implement the decisions captured.


The problem statement for this ODF can be broken down into a number of disctinct problems. They are listed in no particular order or priority:

CPE Mission Statement

The Community Platform Engineering (CPE) team have a mission statement to support the infrastructure and services that build and deliver platform artifacts. The mission statement aims to focus the team’s work from overcommitting to work, running multiple projects in a disconnected manner and to ultimately provide focus and value for our Communities. The remit of the team needed to be defined to allow the team to both manage the workload and the expectations.
Using this definition, the current git forge, Pagure, does not align with what CPE can focus on from both a roadmap development perspective and the operational requirements that such a service demands long term. While Pagure was historically driven by the CPE team, developing a gitforge is outside of building and delivering platform artifacts. [See the later sections for more focus on this.] A self-hosted and self-developed git forge is not required to build and deliver platform artifacts.
While we can make exceptions to the mission statement, we first need to know why we should consider a specific exception. This helps justify the inclusion and subsequent prioritisation of work. We recognise that Pagure is deeply integrated into our daily workflows and is used extensively by the Community. This is the reason the CPE team has not re-examined this commitment, and is a primary driver to openly discuss the team’s and community’s requirements for a git forge.

Development work on Pagure

The CPE team has been unable to commit a development team to Pagure for several months now. This situation is unlikely to change based on our current known priorities.
Historically, Pagure was maintained by individuals (including members of the Fedora community who aren’t on the CPE team) where spare cycles allowed. However, CPE’s mode of working is now that of feature teams, removing the siloed contributions in favour of building sustainable team practices. The feature roadmap for Pagure, however, cannot be executed solely by the CPE team, since the feature requests need to be weighed against the team’s other priorities.
Pagure represents one app out of our current ownership of 100+ code bases. Therefore progression of the roadmap is not guaranteed and certainly not at the pace seen previously. Similarly, bug fixes and enhancements are currently on a best-effort basis. The code is therefore frozen from a functionality perspective pending the outcome of this ODF.

Operational considerations of Pagure

Every line of code and application CPE supports as a team has a cost burden for maintenance and uptime. Pagure is highly-connected to numerous services that are critical to successfully running services that CPE and the community need and support. Therefore, the team must look at long term maintenance including bug fixes and server maintenance as requirements.

At the same time, integrations that already exist in Pagure may need to be created for another git forge, which is a cost as well. This also needs to be fully considered by the team as part of the requirement gathering.

Another major consideration to operationally own an application is its performance and scalability. A git forge may have key requirements for uptime, availability and responsiveness for end users. The current scalability profile of Pagure is unlikely to substantially change as it is resourced today – while the consumption profile of the user base and interconnected applications is likely to increase.

History of gathering requirements

TThe original purpose of Pagure was to mirror the functionality of popular git forge solutions that were available at the time (when most were nascent). Pagure’s feature enhancements were driven by community needs and the team’s viewpoint of where a git forge should go. The team has not solicited requirements in a holistic way from its users and the community, and its internal customers have mainly consisted of the team itself.

However, we also recognize that the feature gap between Pagure and some other forges is substantial and growing. Without either a dedicated development team, or stealing resources from other priority initiatives, it will be almost impossible to close those gaps. Depending on the consumers’ requirements, we recognize this could put Pagure in an untenable situation versus other solutions.

This makes gathering a full set of requirements even more critical. If we fail to capture requirements completely, this discussion is very likely to happen again, only more urgently and with less time for the team to plan and react.

Problems we’re not trying to solve

Feature gap between various git forge solutions

This conversation does not focus on whether Feature X exists in Forge Y or Forge Z. Instead it focuses on functional and non functional requirements for a git forge in general.

CPE time and resourcing investment

This conversation does not focus on how the CPE team invest their time and limited resources. That is not a factor in this discussion.

CPE Mission Statement

This document does not focus on the CPE Mission Statement or whether a git forge should fit that Mission Statement.

Who is making the decision?

The decision will be made by the management of the CPE team with careful consideration of the requirements for both the Fedora and CentOS communities as well as the needs of the team. The CPE team is the group that manages the integration of services and tooling with a git forge solution on behalf of our communities, and will choose the most sustainable, functional, and scalable option to improve our workflows long term.

Choices Available

There exist three choices for such a solution. Github, Gitlab and Pagure. There are no other forges that we could find that had both the product maturity and standing in open source communities, therefore no other solutions are under consideration as the three choices here represent the main git forge solutions on the market. The team will use the requirements gathered to make an informed decision on which of the 3 to pursue.

Who has input into the decision?

Please see the section on Stakeholders below.


Identify functional requirements of a git forge that end users and stakeholders need

The goal is to outline what is needed from the day to day perspective of:

  • Using a git forge solution.
  • Maintaining a git forge solution
  • Future proofing a git forge solution

Requirements are welcome from members of the CPE team and the groups identified as being impacted by such a decision.

Identify non-functional requirements of a git forge that end users and stakeholders need

Examples of non-functional requirements include but are not limited to performance, scalability, availability, reliability, maintability, and capacity. The goal here is to include considerations of this nature from any group impacted by this decision.

Make an informed decision on the future of our git forge solution

Upon gathering the requirements of a git forge solution, the intention is to:

  • Examine requirements gathered versus available git forges
  • Examine the cost of each forge from the CPE teams perspective. This cost is not exclusively a monetary amount and includes maintenance and development costs and trade offs versus our teams roadmap

To be clear, the outcome here may be a decision to invest heavily in Pagure to meet the requirements or it may be to opt for another git forge to meet the requirements. No option is off the table.

Who may be impacted

  • Package maintainers for Fedora, EPEL, CentOS Linux, and CentOS Stream
  • Developers of apps/services for infrastructure that integrate via Pagure
  • The CPE team
  • Developers (and users) that use Pagure for their upstream source
  • Members of the Fedora and CentOS communities who currently use Pagure as a source repository or ticket system

Who are the key stakeholders

While we apprecaited that all individual voices matter, for a more sane approach to gathering requirements we will identify key stakeholders to collate and present a singular view of their representation.

  • Fedora Council will represent the individual community members of the Fedora Project
  • CentOS Board will represent the individual community members of the CentOS Project
  • Paul Frields will represent the RHEL perspective
  • Aoife Moloney will roll up the requirements of the CPE team as our Feature Driver.

How will information be gathered and disseminated?

It is recommended that both Fedora Council and CentOS Board gather input and present their concerns in a manner that is consistent with how their communities work. The RHEL and CPE requirements will be gathered through Red Hat communication mechanisms and presented publicly via a HackMD file to ensure transparency in their source. This will be published and distributed in due course. Additionally, a live video call and associated IRC meetings will be held and advertised in advance to discuss the requirements, talk about concerns and address any questions. We want transparency to be at the heart of this decision.

Timeline of Phases

  • January 13th 2020 sharing of the ODF for consideration within CPE Team
  • January 20th 2020 sharing of the ODF for consideration to Community
  • February 10th 2020, closing of comments from stakeholders which marks the end of the Ideation Phase
  • CPE Management evaluate the requests and where necessary may instruct the CPE team to begin a Planning and Research phase to take in the inputs from the Ideation Phase
  • CPE design, develop and test proof of concept plans based on the decision made by CPE Management and share this with the Community
  • CPE closes the ODF with a decision made and a path forward for our git forge

On behalf of the Board, a group of us is working on an update to the CentOS Project goals that were originally laid out in 2014 and are online at We’re hosting informal user and contributor interviews in a room throughout the day at the CentOS Dojo later this month in Brussels.

Please join us and share your open and honest experiences with CentOS the project, technologies, community, and so forth. We’d like to hear from you and, ultimately, see how your input can inform the goal-setting process and outcome. You are welcome to bring your questions about community, governance, project direction, other strategic thoughts, and so forth.

If you're interested in participating in this informal opinion-gathering, please come see Karsten or Rich at the Dojo, or at the CentOS table at FOSDEM.

/signed Karsten Wade on behalf of CentOS Board and other co-authors