Open the project up at 1.0 (mirror, packaging, contribution surface) #188

New issue

Open

opened 2026-08-28 01:31:36 -04:00 by mysticalsoap · 0 comments

mysticalsoap commented

2026-08-28 01:31:36 -04:00

Owner

Decisions already made (don't re-litigate):

Forgejo stays canonical: code, CI, and the working issue tracker. GitHub gets a push mirror as the public front door (audience is there — qomui's fork network and search). Optional second mirror to Codeberg; issues/PRs accepted in one place only (GitHub).
Push mirrors carry git data only — issues, PRs, releases, wiki stay home. GitHub is an inbox: accepted external reports get a one-line Forgejo issue at triage (linking the GitHub thread); commits reference Forgejo numbers exclusively; the GitHub thread is closed with a link to the landing commit. Full URLs for any cross-system reference in commit bodies.
AUR package is aqomui (source build from release tarball) — -bin is wrong, nothing prebuilt ships. Existing in-repo PKGBUILD becomes aqomui-git (provides/conflicts aqomui).
No Flatpak: the root service + polkit policy don't fit the sandbox. Distro packages are the path (ties into #19 — packages as the root service's update channel).

Checklist:

Forgejo push mirror → GitHub (tags included; releases need manual/scripted re-publish — mirror doesn't carry them)
Minimal GitHub Actions workflow so mirror PRs run tests (Forgejo runner can't see them)
CONTRIBUTING additions: issue numbers refer to the canonical tracker here; triage-inbox flow; note that rebased/squashed PRs show "closed" not "merged" on GitHub (only fast-forwarded exact SHAs get the merged badge)
SECURITY.md with a private reporting contact — root service, vuln reports stay off the public tracker
Tag a handful of good first issue candidates
Publish aqomui to AUR against the 1.0 tarball; rework in-repo PKGBUILD into aqomui-git
Debian packaging lands via #44 (already tracked, gated on Debian CI job)
Announce: issue on corrad1nho/qomui ("maintained hard fork, cgroup v2 split-tunneling"), AlternativeTo entry, a post when 1.0 tags

SECURITY.md and the AUR groundwork can land any time; the rest waits on 1.0.

Tracking issue for making the project publicly accessible and contributable at 1.0. Registration on this Forgejo is closed (OAuth-only), so outsiders currently have no way to file or contribute — the public surface has to live elsewhere. **Decisions already made (don't re-litigate):** - Forgejo stays canonical: code, CI, and the working issue tracker. GitHub gets a push mirror as the public front door (audience is there — qomui's fork network and search). Optional second mirror to Codeberg; issues/PRs accepted in one place only (GitHub). - Push mirrors carry git data only — issues, PRs, releases, wiki stay home. GitHub is an **inbox**: accepted external reports get a one-line Forgejo issue at triage (linking the GitHub thread); commits reference Forgejo numbers exclusively; the GitHub thread is closed with a link to the landing commit. Full URLs for any cross-system reference in commit bodies. - AUR package is `aqomui` (source build from release tarball) — `-bin` is wrong, nothing prebuilt ships. Existing in-repo PKGBUILD becomes `aqomui-git` (`provides`/`conflicts` `aqomui`). - No Flatpak: the root service + polkit policy don't fit the sandbox. Distro packages are the path (ties into #19 — packages as the root service's update channel). **Checklist:** - [ ] Forgejo push mirror → GitHub (tags included; releases need manual/scripted re-publish — mirror doesn't carry them) - [ ] Minimal GitHub Actions workflow so mirror PRs run tests (Forgejo runner can't see them) - [ ] CONTRIBUTING additions: issue numbers refer to the canonical tracker here; triage-inbox flow; note that rebased/squashed PRs show "closed" not "merged" on GitHub (only fast-forwarded exact SHAs get the merged badge) - [ ] SECURITY.md with a private reporting contact — root service, vuln reports stay off the public tracker - [ ] Tag a handful of `good first issue` candidates - [ ] Publish `aqomui` to AUR against the 1.0 tarball; rework in-repo PKGBUILD into `aqomui-git` - [ ] Debian packaging lands via #44 (already tracked, gated on Debian CI job) - [ ] Announce: issue on corrad1nho/qomui ("maintained hard fork, cgroup v2 split-tunneling"), AlternativeTo entry, a post when 1.0 tags SECURITY.md and the AUR groundwork can land any time; the rest waits on 1.0.

mysticalsoap added the

packaging

docs

labels

2026-08-28 01:31:36 -04:00

mysticalsoap referenced this issue

2026-08-30 12:23:21 -04:00

Release smoke test: clean-VM checklist per supported distro #213