41 lines
1.4 KiB
Markdown
41 lines
1.4 KiB
Markdown
# Contributing
|
|
|
|
VerseVDI Data Plane engineering currently occurs in the private Gitea
|
|
repository. Contributions must preserve the GPL/proprietary process boundary
|
|
and the gateway-only product architecture.
|
|
|
|
## Before changing source
|
|
|
|
1. Read `AGENTS.md` and the active OpenSpec change.
|
|
2. Confirm the requirement belongs to this repository.
|
|
3. Record the exact upstream commit, license, file, and derivation method
|
|
before using any Apollo/Moonlight/reference material.
|
|
4. Add no proprietary Connection Server or private Planning Hub content.
|
|
5. Add no dependency until its present need, license, maintenance, security,
|
|
and pure-Go boundary are documented.
|
|
|
|
## Verification
|
|
|
|
Run:
|
|
|
|
```bash
|
|
make verify
|
|
git diff --check
|
|
```
|
|
|
|
For implementation changes, also run the focused, race, fuzz, integration, and
|
|
lab checks named by the active OpenSpec task. Do not repeat an unchanged full
|
|
suite or live matrix merely because time passed; record the evidence and rerun
|
|
only when an input or affected behavior changes.
|
|
|
|
## Commits and review
|
|
|
|
- Use concise Conventional Commit subjects.
|
|
- Keep Protocol, gateway, provider, operations, and native-client changes in
|
|
reviewable increments.
|
|
- Never commit credentials, raw media/input, unredacted captures, private
|
|
infrastructure addresses, or proprietary source.
|
|
- Do not push, merge, publish, or create a release without explicit authority.
|
|
|
|
Report security issues through the private process in `SECURITY.md`.
|