|
Handy Hint
|
Shiro v1 and v2 version end-of-life notice
As of February 28, 2024, Shiro v1 was superseded by v2.
As of June 29, 2026, Shiro v2 was superseded by v3.
|
Apache Shiro is a top-level project of the Apache Software Foundation (ASF) and is governed under the ASF governance model.
The current members of the project, including the committers and the Project Management Committee (PMC), are listed by the ASF:
Only committers have write access to the source repository and other sensitive project resources (release signing, the website, the security mailing list). The PMC members additionally vote on releases and on adding new committers and PMC members.
| Role | Responsibilities |
|---|---|
User |
Uses Shiro. Asks questions and gives feedback on the mailing lists and in GitHub Discussions. |
Contributor |
Reports defects and submits pull requests, following the contributing guide. Contributors either have an ICLA on file with the ASF or tick the license acknowledgment checkbox in the pull request template. |
Committer |
Has write access. Reviews and merges contributions, triages issues, takes part in discussions, and may act as release manager. |
PMC member |
A committer who also takes part in project governance: votes on releases, new committers and PMC members, handles private reports sent to the security team, and is responsible to the ASF board for the health of the project. |
PMC chair |
Officer of the ASF who reports on the project’s status to the ASF board, and is the administrative contact for the project. |
New committers are proposed by an existing committer and elected by a PMC vote. Before elevated access is granted, the PMC reviews the candidate’s sustained, public contributions, communication on the project’s lists, and willingness to follow the ASF Code of Conduct. New committers must file an ICLA with the ASF. Access to sensitive resources is limited to committers and removed when a committer becomes inactive or leaves the project. See also the ASF new committer guide and the ASF "How it works" documentation.
Decisions are made on the public dev mailing list by consensus, following the ASF voting process. Releases require a PMC vote.