Contribute to Varve
Varve is community-shaped. Clear bug reports, thoughtful workflow ideas, cross-platform testing, documentation, and design feedback all help the project move forward.
Contributions are open for docs and examples, translations, plugins in your own repository, testing and device reports, and the nine libraries under MIT OR Apache-2.0. App code remains maintainer-only for now. See CONTRIBUTING.md for details.
Ways to Help Today
Bug Reports
Give the maintainer a reliable reproduction
- Search existing Issues first
- Include steps, expected and actual result, and environment
- Add screenshots, logs, or a small source document when useful
- Use the bug template
Documentation & Examples
Make the product easier to understand and use
- Point out confusing or stale passages
- Share tutorials, examples, and workflow recipes
- Suggest screenshots or accessibility improvements
- Use the docs issue form for corrections and Discussions for examples
Cross-Platform Testing
Expand confidence beyond the maintainer's machine
- Record OS, architecture, package type, and Varve version
- Test on Linux, macOS, and Windows where available
- Check keyboard access and screen-reader behavior
- Confirm fixes and report regressions with exact actions
Workflow & Design Feedback
Help prioritize the next useful design-tool improvement
- Describe the task you are trying to complete
- Share a sketch, mockup, or before/after comparison
- Discuss interaction, accessibility, and visual hierarchy
- Post proposals in Discussions
Contribution lanes
Docs and examples, translations, plugins in your own repository, testing and device reports, and contributions to the nine MIT OR Apache-2.0 libraries are open today. App code remains maintainer-only for now.
Start with pnpm verify:plan, run pnpm verify:affected, and record the commands in the pull request. The full gate is reserved for explicit high-impact changes and requires a stated reason. See the contribution guidelines and the development contributor guide for the complete workflow.
Getting Started Today
- Read the contribution guidelines and code of conduct
- Search existing Issues and Discussions before starting a new thread
- Choose Issues for reproducible bugs and Discussions for ideas, workflows, and architecture
- Include platform, version, exact steps, and evidence that helps someone reproduce the report
- For local development, follow the setup guide and AGENTS.md
Contribution Licensing
The app is source-available under FSL-1.1-MIT. Contributions use DCO 1.1 sign-off under the licence of the files changed.
Contributors are credited in release notes. See CONTRIBUTING.md for the DCO text and PR process.
Recognition
Contributors are recognized in the following ways:
- GitHub contributor list (automatic)
- Release notes acknowledgment (with permission)
- Contributors section on the About page