Community & contributing

The same friendly process works for every project — pick the repo, follow the steps below.

Ways to help

• Star a project on GitHub — it genuinely helps.
• Report bugs or request features via issues.
• Ask questions and share ideas in Discussions.
• Contribute code or docs with a pull request.
• Sponsor to fund maintenance and unlock a commercial license — see licensing.

Project channels

Issues, discussions and pull requests live on each project's own GitHub repository:

Contribution workflow

All projects share the same branching model. Contributions target the single release branch:

1. Fork the repository and create a feature branch fromrelease.
2. Make your change with clear, focused commits (e.g.feat: add waterfall chart).
3. Add or update tests and docs where relevant.
4. Open a pull request against release describing the change and the motivation. Merging the PR automatically publishes a new alpha; stable releases are cut later by a maintainer pushing a vX.Y.Z tag.

Reporting a good issue

A useful bug report usually includes:

• The project and version (stable or alpha) you're using.
• A minimal, reproducible example.
• What you expected vs. what happened.
• Your OS, language/runtime and toolchain versions.

Be excellent to each other

Please keep interactions respectful and constructive. Harassment or hostility isn't welcome in any project space.

Direct contact

For commercial licensing or private matters, reach out atcontact@draviavemal.com.