English source · 2 min
Build the first useful things with Veyndo
Start with the first tour, then pick one small task from good first issues. Comment on the task before starting so two people do not do the same work.
Useful first contributions include an additional operating-system setup report, a precise translation correction, an illustrated sandbox walkthrough or a small app built from the existing workshops. An observed problem with exact reproduction steps is useful even without a code change.
What a small contribution should contain
- One concrete user problem and its first unexpected result.
- The source/image version, operating system and relevant setup.
- A focused correction and proportionate validation from CONTRIBUTING.
- Explicit boundaries where a provider, hardware device or production outcome was not exercised. Use synthetic examples rather than customer data.
We aim to acknowledge first reports within two working days. This is a maintainer goal, not a support SLA. Read the existing task before creating another one.
Public roadmap
| Priority | Useful next outcome | How to participate |
|---|---|---|
| First start | A new developer completes the local round and can restart with data retained | Setup reports and first-tour feedback |
| Native agent work | Restricted identities get consistent HTTP/MCP tools and denied writes | Small reproducible role/operation cases |
| Apps | A useful example runs through the existing Manifest and private preview | App workshops and documented examples |
| International use | Accurate UI copy and content-language inheritance | Small EN/DE/FR/ES corrections with screenshots |
| Reliability | Complete app-data history and stronger operational acceptance | Discuss scoped designs before implementation |
The last row remains development work, not a delivered feature. The current status and consistency audit record implementation and evidence separately.
For agencies
The licensing guide permits paid setup, customization and maintenance of a merchant's own installation within its stated conditions. Managed shops, white-label platforms and commerce SaaS for independent merchants require separate written commercial permission. Start with a non-confidential discussion describing which path you need; confidential terms belong in a private follow-up with the maintainer.