ALESCoはAlmaLinuxのエンジニアリング活動の「空中交通管制」として、AlmaLinuxの堅牢性や信頼性、持続可能性を確保する一方で、関連する専門分科会(SIGs)と協力したり、SIGsの技術的な決定を監視しています。委員会には次の5つの重要な責任があります:
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.
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.
Proposals are written as RFCs and submitted as pull requests, then move through these stages in the open.
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.
The RFC is under active discussion in the open and may go through several revisions.
ALESCo announces a Final Comment Period to signal that a decision is near, and adds the “vote at next meeting” tag.
ALESCo makes the final call, weighing community feedback. An RFC ends in one of these outcomes:
In rare cases that touch trademarks, significant resources, or partnerships, the AlmaLinux Foundation Board provides input before a vote.
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...
The maintainers, packagers, and SIG leads who steer AlmaLinux’s technical direction.




