Le comité de pilotage de l'ingénierie AlmaLinux
ALESCo est le point de rencontre central pour la collaboration entre tous ceux qui travaillent sur tout ce qui concerne le projet AlmaLinux. En ayant des discussions ouvertes et en invitant les points de vue de tous ceux qui touchent à AlmaLinux, nous nous assurons qu'AlmaLinux continue à servir sa communauté.
About ALESCo
Surnommé « contrôle aérien » pour toutes les questions d'ingénierie, ALESCo garantira la robustesse, la fiabilité et la pérennité d'AlmaLinux tout en collaborant avec les groupes d'intérêt spéciaux (SIG) concernés et en supervisant les décisions techniques au sein de ces groupes. Le comité assumera cinq responsabilités clés :
- Supervision technique du système d'exploitation
- Transparence dans les décisions d'ingénierie
- Garantir la stabilité à long terme
- Gestion des versions
- Prise en charge des SIG
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
Submitted
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...
Membres d'ALESCo
The maintainers, packagers, and SIG leads who steer AlmaLinux’s technical direction.
Andrew Lukoshko
Architecte principal AlmaLinux
CloudLinux
Ben Thomas
Développeur principal d'infrastructure de recherche
UCL
Jonathan Wright
Ambassadeur AlmaLinux
CloudLinux
Neal Gompa
Consultant principal
Velocity Limitless
Lance Albertson
Director
Oregon State University Open Source Lab
