Contributing to WAF++
WAF++ lives from contributions. Whether you write code, improve documentation, review RFCs, or share experience from real projects — every contribution shapes the framework.
Ways to contribute
Code, content, community — pick what fits your skills and time.
PRs & Issues
Fix bugs, implement controls, improve tooling. Every PR gets reviewed by a maintainer and linked back to a decision.
Docs & Patterns
Write pillar documentation, reference architectures, best-practice patterns, or concrete examples from real projects.
RFC Reviews
Comment on open RFCs, propose alternatives, or vote on framework decisions. Every voice counts — especially real-world perspective.
Localisation
Help translate content into German, English, or further languages. WAF++ should be accessible to the global cloud community.
Working Groups
Join or propose a Working Group around a specific pillar, scoring model, controls library, or reference architecture.
Talks & BoFs
Present WAF++ at a conference, host a Birds-of-a-Feather session, or run a community workshop. Practical experience is gold.
Getting started
Four steps from newcomer to contributor.
Browse open issues labelled good first issue or help wanted at github.com/waf2p. No issue yet? Open one and describe what you want to tackle.
Join the community on Slack, say hi in #general, ask questions, and find out which Working Group fits your background and interests.
Fork the relevant repository, create a feature branch, and open a pull request. A maintainer will review it, give feedback, and guide you through the process.
For new pillars, breaking changes, scoring changes, or governance updates — draft an RFC in GitHub Discussions. The community reviews it before implementation begins. This keeps decisions traceable.
Working Groups
Working Groups are topic-focused teams building specific parts of WAF++. Anyone can propose one — all you need is a charter, at least one lead, and a maintainer sponsor.
Find a WG
Check open WG proposals on GitHub Discussions and join the matching channel on Slack. You can contribute without a full-time commitment.
Start a WG
Draft a charter in a GitHub Discussion, find a maintainer sponsor, and announce it on Slack. WGs can focus on any scope: a single pillar, a tooling question, a scoring approach.
Ship results
WG outputs flow back as PRs and RFCs. Every result is public, traceable, and citable — consistent with WAF++'s transparency principles.
The RFC process
Significant changes go through an RFC (Request for Comments). The process is lightweight but ensures every decision is community-reviewed and documented.
No contribution is too small.
A typo fix, a clarifying comment, a review — it all moves the framework forward. WAF++ is built in public and the community is always open.