Contribute to Varve

Varve is community-shaped. Whether you contribute code, documentation, testing, or design, your help is valued and appreciated.

Varve is not yet accepting external contributions. The page below describes the process we intend to use once the project opens up. In the meantime, feedback and ideas are welcome in GitHub Discussions.

Ways to Contribute

Code Contributions

Fix bugs, add features, improve performance

Documentation

Improve docs, write tutorials, translate content

  • Fix typos or clarify confusing sections
  • Write tutorials for specific workflows
  • Add examples and screenshots
  • Translate documentation to other languages

Testing

Test on different platforms and report bugs

  • Test on specific Linux distributions
  • Test on different macOS versions
  • Test accessibility with screen readers
  • Verify bug fixes and report regressions

Design

Create UI mockups, icons, website improvements

  • Design new feature interfaces
  • Create icon designs
  • Improve website UX
  • Design marketing materials

Getting Started

  1. Read the contribution guidelines and code of conduct
  2. Set up your development environment following AGENTS.md
  3. Check existing issues for "good first issue" labels
  4. Fork the repository and create a feature branch
  5. Make your changes and add tests
  6. Submit a pull request with a clear description

Contribution Licensing

Once open, all contributions to Varve will need to be licensed under FSL-1.1-MIT. By contributing, you will grant a license for your code to be included in the project under the same license. You retain copyright to your contributions.

All contributions require a Developer Certificate of Origin (DCO) sign-off. See the contribution guidelines for details.

Recognition

Contributors are recognized in the following ways:

  • GitHub contributor list (automatic)
  • Release notes acknowledgment (with permission)
  • Contributors section on the About page

Want to know when contributions open?

Follow GitHub Discussions