An open workshop thrives on those who participate. Here are six ways you can get involved — from a 15-minute issue to a long-term sponsorship. Every contribution counts; none is too small.

• 💻 Contribute code — effort: 2 hours to several weeks; → Browse repositories: Take a look at our repositories on Gitea. Look for issues labeled “good first issue” — there you will find tasks that can be solved without prior knowledge. Pull requests with tests are welcome.

• 📚 Improve documentation — effort: 1 hour to several days; → Wiki on Gitea: Our wiki/Git manuals, tutorials and API documentation thrive on corrections, examples and clarifications. A typo fix is welcome too.

• 🌐 Translate (EN / VI / DE) — effort: 30 min to 4 hours per page; → Offer a translation: Keeping the site multilingual (initially DE / EN / VI) is an ongoing task. Translations can be submitted directly via pull request or via translation memory.

• 🎤 Give a talk / host a workshop — effort: 1 day (preparation + event); → Propose a workshop: Do you have expertise in one of our topics (Git, OSCAL, OPA, compliance, BSI Grundschutz, NIS2, ...)? Contribute a workshop or a talk to our series — on site or remote.

• 🧪 Testing / bug reports — effort: 15 min to 2 hours; → Create an issue: Try out our tools and report bugs. Reproduction steps and screenshots are valuable too. Issue templates per repository.

• 💶 Donate — effort: 1 minute; → Donate now: Your donation strengthens our work. You will receive an official donation receipt under § 50 Abs. 1 EStDV.

Note on boundaries: Contributions in our repositories are compliance-relevant artifacts — records, decisions, evidence, tools. Personal specifications, assessments and weightings of individuals do not belong in the shared collection: they are protected private information and remain local. Anyone who wants to share examples or patterns should anonymize them.