panurus

Maintainers

Changes to either list below are made by pull request against this file. After such a pull request is merged, the corresponding GitHub team (panurus-maintainers) must be updated manually to match.

Active Maintainers

Name	GitHub ID	Scope	LFID	Discord ID	Email	Company Affiliation
Angelo De Caro	adecaro	Maintainer		adecaro	adc@zurich.ibm.com	IBM
Kaoutar Elkhiyaoui	KElkhiyaoui	Maintainer		KElkhiyaoui	kao@zurich.ibm.com	IBM
Arne Rutjes	arner	Maintainer		arner	arne.rutjesISC@nl.ibm.com	IBM
Alexandros Filios	alexandrosfilios	Maintainer		lio	alexandros.filios@alumni.ethz.ch	Independent
Akram Bitar	AkramBitar	Maintainer		akrambitar	akram@il.ibm.com	IBM

Emeritus Maintainers

Name	GitHub ID	Scope	LFID	Discord ID	Email	Company Affiliation
Alessandro Sorniotti	ale-linux	Maintainer		aso	ale.linux@sopit.net	IBM
Elli Androulaki	elli-androulaki	Maintainer		elli-androulaki	lli@zurich.ibm.com	IBM
Mathilde Ffrench	mffrench	Maintainer		mffrench	mathilde.ffrench@fr.ibm.com	IBM

Scopes

Panurus uses a single maintainer scope covering the whole repository.

Scope	Definition	GitHub Role	GitHub Team
Maintainer	Maintainer for the entire repository	Maintain	panurus-maintainers

Maintainer Duties

Maintainers are expected to:

• Review and merge pull requests, and keep CI green.
• Triage incoming issues.
• Participate in project calls and technical discussions.
• Contribute to the mid-year project update and annual review filed with the LFDT TAC.
• Mentor contributors working toward maintainership.

Members of the security team carry the additional responsibilities described in SECURITY.md.

How to Become a Maintainer

Candidates for maintainership are expected to have:

• a sustained history of substantive contributions to Panurus — code, review, documentation, or release engineering,
• demonstrated good judgement in code review, and
• familiarity with the project’s architecture and contribution process (see CONTRIBUTING.md).

The process is:

1. An existing active maintainer sponsors the candidate.
2. The sponsor opens a pull request adding the candidate to the Active Maintainers table above, with a justification in the pull request description summarising the candidate’s contributions.
3. Current active maintainers have two weeks to review and raise objections.
4. Approval requires a majority of active maintainers, with no sustained objection.
5. Once merged, the panurus-maintainers GitHub team is updated to grant access.

An emeritus maintainer may return to active status by the same process, without requiring a new sponsor.

How Maintainers are Removed or Moved to Emeritus Status

A maintainer may be moved to emeritus status:

• At their own request — open a pull request moving your row to the Emeritus Maintainers table. This needs no further approval.
• Through inactivity — a maintainer with no meaningful contribution or review activity for twelve months may be proposed for emeritus status.
• For conduct — a violation of the Code of Conduct may result in removal.

Proposals follow the same path as additions: a pull request against this file with a justification, a two-week comment window, and approval by a majority of active maintainers. Moving to emeritus status is not a judgement on past contributions; it reflects current activity, and the door back is described above.

This site is open source. Improve this page.