Contribute

We are building out the maintainer team now. If you know Vue and these libraries well, you are the person we are looking for.

The quickest way in is the Discord server. Ask questions, propose changes, or say hello before picking up an issue.

Where help is most needed

• Issue backlog. Reproducing, triaging and fixing inherited issues is the highest-value work right now.
• Migration reports. If npx @openvue/migrate misses something in your codebase, file it. That makes the path easier for everyone behind you.
• Accessibility. Real assistive-technology testing on components, reported against specific screen readers and versions.
• Documentation. Gaps and inaccuracies on openvue.dev, especially around theming and unstyled mode.

Development setup

The monorepo uses pnpm workspaces.

git clone https://github.com/openvi-foundation/openvue.git
cd openvue
pnpm install
pnpm run dev

The full setup, project layout and review process are in the contributing guide.

Before you open a pull request

• Open an issue first for anything bigger than a bug fix, so the approach can be agreed on.
• Keep the component API compatible with PrimeVue 4.x unless there is a documented migration path.
• Include a test where the change is testable, and run the existing suites.
• One logical change per pull request. Reviewable diffs get merged faster.

Becoming a maintainer

Commit access follows sustained, review-quality contribution rather than affiliation. Start by picking up issues, then reach out on Discord or at contact@openvi.dev. See governance for how decisions get made.

Reporting a security issue

Do not open a public issue. Follow the security policy.