PAXECT Maintainers & Contributors — 5-in-1 Ecosystem (2–4 h/week, Remote)

[PAXECT-Interface]

---

PAXECT MAINTAINERS & CONTRIBUTORS — 5-IN-1 ECOSYSTEM (REMOTE 2–4H/WEEK)

This post lists current maintainer opportunities and contribution roles for the PAXECT ecosystem (Core, AEAD Hybrid, Polyglot, SelfTune, Link).
We’re expanding the 1.x enterprise series and seeking reliable contributors to help maintain deterministic, open-source modules.

---

SCOPE & OWNERSHIP

We are recruiting maintainers for:

• Plugin Maintenance: Core, AEAD Hybrid, Polyglot, SelfTune, Link
• Community Management: Discussions, onboarding, FAQs
• Updates Coordination: Changelog and release planning
• Documentation: README, guides, and example updates

---

ROLES (CHOOSE ONE OR TWO)

Plugin Maintenance — Triage issues, review PRs, maintain demos, prepare module releases.
Community Maintenance — Manage issues/discussions, apply labels, assist contributors, maintain FAQs.
Updates Maintenance — Keep changelogs and mini-release updates consistent; assist with versioning.
Documentation Maintenance — Maintain READMEs, guides, and examples in sync across repositories.

---

WORKFLOW SUMMARY

• Issues → use labels: good first issue, help wanted, plugin:*, docs, security
• Pull Requests → feature branches only; at least one 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

Enterprise and partner inquiries → see ENTERPRISE_PACK_OVERVIEW.md

APPLY — REPLY WITH THIS FORMAT

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

---

EXPECTATIONS & RECOGNITION

• Follow determinism and privacy-by-default standards (no telemetry by default).
• Contributors are credited in release notes and, where appropriate, in the README.
• Reliability and consistency matter more than seniority.

All nationalities are welcome.
Contributors in CET/CEST or Dutch-speaking regions may find onboarding easier but this is not required.

---

GOVERNANCE & OWNERSHIP

• Ownership: All PAXECT products and trademarks remain property of the Owner.
• License: Apache-2.0 source code only (trademark rights excluded).
• Core Decisions: Architectural or brand-sensitive merges require owner approval.
• Contributions: Reviewed under CODEOWNERS and branch protection.
• Naming/Branding: Written permission required for use of the PAXECT name or logo (see TRADEMARKS.md).

---

GETTING STARTED

New contributors can begin by:

• Updating documentation
• Running or improving example demos

Step-by-step onboarding support is available for all maintainers.

---

SEO SUMMARY
PAXECT Link plugin ecosystem: deterministic, plug-and-play, adaptive tuning modules for enterprise automation, IoT, and cloud environments.

---