App: DetourApplication ID: dev.detour.appLicense: MITSource: GitHub - arttvad9r/detour: Android VPN/network client with per-app routing, Mihomo, ByeDPI, WARP and VLESS profiles. · GitHub Release: Release Detour 0.2.1 · arttvad9r/detour · GitHub
I am the upstream developer of Detour and would like to submit it to F-Droid.
The application has already been prepared for F-Droid:
upstream Fastlane metadata is available;
.fdroid.yml is prepared;Mihomo and ByeDPI native sources are pinned;
the native build works without build-time network access;
Go and Android NDK inputs are pinned;
F-Droid scanner findings are documented and handled narrowly;
fdroid readmeta, fdroid rewritemeta and fdroid lint pass;a full fdroid build --on-server passed in the official F-Droid buildserver environment.
F-Droid readiness documentation:
https://github.com/arttvad9r/detour/blob/main/docs/fdroid-readiness.md
Upstream tracking issue:
opened 09:55AM - 10 Sep 26 UTC
## Goal
Submit `dev.detour.app` to the official F-Droid `fdroiddata` repository… using the already validated upstream recipe.
## Upstream candidate
- Release tag: `v0.3.0`
- Version name: `0.3.0`
- Version code: `3000`
- Upstream recipe: `.fdroid.yml`
- Fastlane metadata: `fastlane/metadata/android/`
- Release: https://github.com/arttvad9r/detour/releases/tag/v0.3.0
- Source: https://github.com/arttvad9r/detour
## Validation already completed upstream
- [x] Native Mihomo and ByeDPI builds work with build-time network access disabled.
- [x] Go/toolchain and Android NDK inputs are pinned.
- [x] FLOSS/Anti-Features review completed upstream.
- [x] F-Droid scanner findings are handled with narrow, documented `scanignore` / `scandelete` entries.
- [x] `fdroid readmeta` passes.
- [x] `fdroid rewritemeta` passes.
- [x] `fdroid lint` passes.
- [x] `fdroid build --on-server` passes in the official `fdroidserver:buildserver` environment.
- [x] `v0.3.0` contains the upstream Fastlane metadata and changelog for versionCode `3000`.
- [x] The F-Droid buildserver CI job passed on the `v0.3.0` release commit (`a6ca68be`), including the new ZXing core dependency (Apache-2.0, no Play Services).
## Submission steps
1. Fork https://gitlab.com/fdroid/fdroiddata on GitLab.
2. Create a branch such as `dev.detour.app`.
3. Copy `.fdroid.yml` from Detour `main` to `metadata/dev.detour.app.yml` in the fdroiddata checkout.
4. Run the current F-Droid metadata/build checks again in that checkout.
5. Commit as `New App: dev.detour.app`.
6. Push the branch to the GitLab fork.
7. Open a merge request against `fdroid/fdroiddata` and apply the `New App` label if requested by the current contribution flow.
8. Link this issue and the upstream `v0.3.0` release in the MR description.
9. Respond to packager review comments and adjust Anti-Features/update policy only if requested by F-Droid maintainers.
Official quick-start: https://f-droid.org/docs/Submitting_to_F-Droid_Quick_Start_Guide/
## Done when
- [ ] `metadata/dev.detour.app.yml` is merged into official `fdroiddata`.
- [ ] The first Detour build appears in the official F-Droid repository.
- [ ] Upstream distribution docs are updated from “submission-ready” to “available on F-Droid”.
I cannot open the normal fdroiddata merge request because GitLab requires additional account verification. GitLab phone verification is unavailable for Russia and I do not have a supported foreign credit/debit card.
Could an F-Droid packager please help open the RFP / fdroiddata submission using the already prepared upstream metadata?
I can respond to any packaging or build questions and make upstream changes if required.