Volunteers & Maintainers — roll-call (light commitment: 2–4h/week)

[PAXECT-Interface]

Scope & ownership

• We’re looking for maintainers for plugins (PAXECT-Core, AEAD Hybrid, Polyglot, SelfTune, Link), community, updates, and docs.

Roles (pick 1–2)

• Plugin maintenance: issue triage, PR reviews, keep examples up-to-date, prep module releases.
• Community maintenance: Discussions/Issues triage, labels, contributor onboarding, maintain FAQ.
• Updates maintenance: changelog, mini-announcements, coordinate the release checklist.
• Docs maintenance: keep README/Guides/FAQ current; small example projects.

Workflow (short)

• Issues: use labels good first issue, help wanted, plugin:*, docs, security.
• PRs: feature branches only; at least 1 maintainer review; Owner sign-off for Core/policy.
• Releases: CI must pass; changelog + version bump; Owner tags the release.
• Security: report privately (see SECURITY.md); no public PoCs for live issues.

Apply — reply with this format

• Skills / area: (PAXECT-Core, AEAD Hybrid / Polyglot / SelfTune / Link / Docs/CI)
• Timezone & availability: (e.g., 2–4h/week)
• Examples: 1–2 PRs or gists (links)
• Focus (next 2 weeks): short bullet(s)

Enterprise and partner inquiries → see ENTERPRISE_PACK_OVERVIEW.md

Expectations & recognition

• Follow determinism & privacy standards (no telemetry by default).
• We credit contributors in release notes and (where appropriate) in the README.

---

We welcome a mix of students and experienced contributors. You don’t need to be an expert — curiosity and reliability matter most.
All nationalities are welcome. If you’re in the CET/CEST timezone or Dutch-speaking, that’s a bonus for pairing and onboarding, but not required.

Governance & Ownership

• Ownership: All PAXECT products and trademarks (PAXECT™ name + logo) remain the property of the Owner.
• License: Source code is Apache-2.0; trademark rights are not granted by the code license.
• Core decisions: Architectural decisions and final merges for Core and brand-sensitive repos require Owner approval.
• Contributions: PRs are welcome and reviewed by maintainers; merges follow CODEOWNERS + branch protection.
• Naming/branding: Do not use the PAXECT name/logo for derived projects without written permission; see TRADEMARKS.md.