Contributing
Vooya is an open-source beta. Contributions are welcome, including bug reports, compatibility evidence, documentation improvements, and proposals that show a current direction is wrong.
Before opening a change
- Read the project status and compatibility matrix.
- Check existing issues and pull requests.
- Keep the change focused: a bug fix, a fixture, a documentation correction, or one clearly bounded design proposal.
- Distinguish observed behavior from a future idea in the description.
What makes a useful contribution
- A reproduction that runs from a clean consumer directory.
- A named toolchain, framework, bundler, and browser when reporting compatibility.
- A test or fixture that protects the behavior being changed.
- Documentation that explains the user-visible boundary, not internal session discussions.
Start small, stay involved
Vooya welcomes a small, complete reproduction, fixture, or documentation fix as the first contribution. People who continue to contribute may, depending on sustained work, project needs, and maintainer judgment, receive public attribution in release notes and changelog entries, credits in documentation or examples, invitations to design discussions, or a path toward reviewer and maintainer responsibilities. These are earned project decisions, not advance promises.
Open-source volunteering is not an employment relationship. Vooya does not promise salary, equity, a title, or a fixed workload. Funding, bounties, or commercial cooperation exist only after a separate public statement describes them.
Design proposals
Use an RFC only for a user-visible contract or architectural decision. Start a GitHub issue titled RFC: <proposal> so alternatives and acceptance criteria can be discussed before a numbered document is added. Ordinary bugs and implementation tasks should remain issues.
See the repository contribution guide for commands, licensing, and pull-request checks.
Follow the code and test conventions for strict types, executable test helpers, generated declarations, and repository language statistics.
Scope for the current beta
The most useful contributions right now are source-authoring ergonomics, clean-machine Rust diagnostics, Vite/Rspack/Webpack evidence, browser QA, TypeScript declarations, and documentation. The old .voo experiment is not a new feature target.