The AlmaLinux Engineering Steering Committee

ALESCo acts as the central meeting point for collaboration between everyone working on anything related to the AlmaLinux Project. By having open discussions and inviting viewpoints from everyone that touches AlmaLinux, we ensure AlmaLinux continues to serve its community.

AlmaLinux contributors working together at the 2024 leadership summit

About ALESCo

Dubbed “air traffic control” for all engineering matters, ALESCo will ensure AlmaLinux’s robustness, reliability, and sustainability while working collaboratively with and overseeing technical decisions in relevant Special Interest Groups (SIGs). The committee will hold five key responsibilities:

  • Technical oversight for the operating system
  • Transparency in engineering decisions
  • Ensuring Long-Term Stability Focus
  • Release Management
  • SIG support

ALESCo brings together the maintainers, packagers, and SIG leads who build and sustain AlmaLinux OS. It is not a closed body. Anyone working on or using AlmaLinux is welcome to bring proposals, raise concerns, and help shape technical direction in the open.

How ALESCo works

ALESCo meets every two weeks, and the schedule is posted on events.almalinux.org. Decisions are made by majority vote of the committee, and the chair role rotates among members every six months. Discussion happens in the open in the alesco channel on chat.almalinux.org, and technical proposals are tracked as pull requests in the ALESCo repository on GitHub. Anyone working on or using AlmaLinux is welcome to join a meeting, raise a topic, or open a proposal.

Lifecycle of a proposal

Proposals are written as RFCs and submitted as pull requests, then move through these stages in the open.

1

The RFC is opened as a pull request and reviewed for formatting and fit with the RFC process. Once it qualifies, the “accepted for discussion” tag is added.

2 Accepted for Discussion

The RFC is under active discussion in the open and may go through several revisions.

3 Vote at Next Meeting

ALESCo announces a Final Comment Period to signal that a decision is near, and adds the “vote at next meeting” tag.

4 Closed

ALESCo makes the final call, weighing community feedback. An RFC ends in one of these outcomes:

Accepted Rejected Withdrawn Superseded

In rare cases that touch trademarks, significant resources, or partnerships, the AlmaLinux Foundation Board provides input before a vote.

Open Proposals

These are the RFCs currently before ALESCo, along with their status. We love hearing from our community about the proposals under consideration, so every perspective is in the room before a decision is made.

Loading open proposals...

View all on GitHub

Members of ALESCo

The maintainers, packagers, and SIG leads who steer AlmaLinux’s technical direction.

Andrew Lukoshko
Andrew Lukoshko
AlmaLinux Lead Architect
CloudLinux
Ben Thomas
Ben Thomas
Principal Research Infrastructure Developer
UCL
Jonathan Wright
Jonathan Wright
AlmaLinux Evangelist
CloudLinux
Neal Gompa
Neal Gompa
Principal Consultant
Velocity Limitless
Lance Albertson
Lance Albertson
Director
Oregon State University Open Source Lab

Stay updated!