Build the tools.
Fix a focused bug, improve performance or make an existing workflow easier to maintain.
A useful first step
Prepare a code contribution Reproduce one issue, describe the smallest fix and include how you tested it.
COMMUNITY / GET INVOLVED
THE NEXT WAVE.
BUILT TOGETHER.
Built for an open-source community. Bring your craft, your curiosity or a production problem. Help make creative tools that everyone can build on.
SIX WAYS IN / ONE SHARED PROJECT
Your skills belong here.
A clear bug report, a welcoming answer and a small code improvement all move the project forward. Pick a first task you can finish and explain.
Make the next step clear.
Improve interaction, accessibility or visual communication around a real production task.
A useful first step
Prepare a design contribution Show a confusing moment and sketch a change with keyboard and small-screen use in mind.
Turn a rehearsal into progress.
Help the team understand what works on real devices and where the preview needs attention.
A useful first step
Prepare a test report Record your build, platform, reproduction steps, expected result and actual result.
Share what you learned.
Write a practical guide, explain a control or correct a step that left you guessing.
A useful first step
Prepare a documentation change Walk through one task and suggest a specific improvement to its guide.
Open another door.
Help people work in their language through clear interface terms and accessible learning material.
A useful first step
Prepare a translation Choose a short guide, note the language and explain terminology a reviewer should check.
Help someone find their feet.
Welcome a new operator, explain a workflow or turn a shared question into a useful resource.
A useful first step
Prepare a community contribution Document a repeat question, a workshop idea or a practical answer others can reuse.
FROM AN IDEA TO A SHARED IMPROVEMENT
Small changes.
Thoughtful review.
Our contribution workflow starts with the problem and ends with something another person can understand, test and use.
Discuss.
Describe the need and check existing work. Agree larger features or changes in direction before implementation.
Build.
Keep the change focused. Follow the project guidance and explain the choices a reviewer needs to understand.
Review.
Ask the relevant maintainer to review the work. Share context, respond to feedback and revise together.
Test & document.
Show the result, check affected workflows and update the guide. Record limitations that remain.
Release & credit.
A maintainer decides when to merge. Record the change for a release and confirm how contributors want to be credited.
Start with the scope. A small correction can go straight to a focused review. Larger changes need an agreed direction and a written discussion others can follow.
Follow the full contribution guide ↗SHARED RESPONSIBILITY
A clear place for each decision.
These are the responsibilities we are organizing around. They describe the working model; module teams and named maintainer appointments will be published as they are established.
CONTRIBUTORS
Bring the context.
Explain the problem, prepare a focused contribution and take part in review. First-time and non-code contributors are equally welcome.
MODULE MAINTAINERS
Care for an area.
Help agree scope, review changes and keep an area coherent. Start with the workspace or guide your contribution affects.
RELEASE STEWARDS
Check what is ready.
Coordinate release checks, known issues and clear notes so operators understand the build they are downloading.
PROJECT STEWARDSHIP
Keep decisions visible.
Document project direction, responsibilities and funding decisions, with space for community feedback.
MAKE YOUR WORK VISIBLE
Progress with people behind it.
Prepare a local contribution draft, explore checked activity and choose named or anonymous recognition. A contribution can be useful long before it is a line on a graph.
Opening contribution activity and draft tools…
Support the people.
Make room for the work.
Time, expertise and financial support can all help the project grow. Explore the development fund and sponsorship proposals.