Skip to content

MAINTAINERS.md

Latest commit

 

History

History
44 lines (31 loc) · 1.64 KB

MAINTAINERS.md

File metadata and controls

44 lines (31 loc) · 1.64 KB
Raw

Maintainers

This file lists the current maintainers of AegisBPF, their scope, and how to reach them. Maintainers have merge rights, release authority, and security triage responsibility as defined in GOVERNANCE.md.

Active maintainers

Maintainer GitHub Scope Organization
Eren Arı @ErenAri Project lead, BPF programs, daemon, release Independent

Seeking co-maintainers

AegisBPF is actively seeking additional maintainers from different organizations to meet CNCF Incubation requirements and to distribute release, review, and security-triage load. Strong candidates demonstrate:

  1. Sustained high-quality contributions across BPF programs, daemon, operator, or CI/testing.
  2. Ownership of a subsystem (for example: operator & webhooks, network policy, policy compiler, fuzzing, performance gates).
  3. Active code review with a pattern of timely, thoughtful feedback.
  4. Availability to respond to release and security matters on a predictable cadence.

If you are interested, please open a GitHub Discussion titled "Maintainer candidacy: your-name" summarizing your contributions and desired scope. Existing maintainers will respond within two weeks.

Emeritus maintainers

None yet.

Security contacts

For private security reports, follow the instructions in SECURITY.md. The security team routes reports to active maintainers via the channel described there.

Changing this file

Additions or removals of maintainers require approval by a majority of existing maintainers, per GOVERNANCE.md.