ClashForAndroid
ClashForAndroid copied to clipboard
Kr328
[Feature Request] Include this app in F-Droid app store
Is your feature request related to a problem? Please describe. I think this could be a good idea to provide this app in the F-Droid repo. It only serves free and open source apps build from source, and could help people without Google Play to find, download ans use this app, and more important, stay up to date with the updates.
Describe the solution you'd like The first would be to open a Request For Packaging on F-Droid side if you think that adding this app in F-Droid is a good idea, and you'll probably get some help.
Describe alternatives you've considered Putting this app in F-Droid or not, I think it's a good idea to keep the different apks in the release section with appropriate tags.
Additional context You can ping me if you have any question.
https://gitlab.com/fdroid/fdroiddata/-/merge_requests/9010
@Kr328 Needs your endorsement :)
@proletarius101 Clash for Android isn't stable enough to release on F-Droid
I'll probably release it in the next major version
What does your "release" mean? Would you do it yourself, or you ask us to wait for the next release?
BTW, since you replied, would you switch the NDK to the latest LTS or stable which could be included in F-droid?
Any ETA? Looks like OP is quite eager to get this listed :wink:
PS: Would it be possible to establish Fastlane structure here in the app's repo, so you stay in full control of how your app will be presented?
@Kr328 the current RFP just popped up on the triage. Are you still on it? Will Fastlane be added here?
I'll probably release it in the next major version
I thought we need to wait for version 3.0.0. So let's be patience.
@linsui what you quote was 1 year ago. The RFP was never answered to (apart from me asking for a status multiple times) and now due to enter the closure pipeline, as defined by our process. So if there's not even an answer to an expected ETA (not even a rough one like "maybe in 6 months") I must assume there won't be an answer and it might take indefinitely.
I'll now lift the due-date for another 2 weeks before entering closure to give another chance for an estimate. But if we don't get any answer, the process is to close the RFP. It can still be reopened, or a new RFP be opened when the app finally is ready for that. But not getting an answer looks like that day might be in the far future :wink:
Now entering the closure phase, which gives another 4 weeks for at least a simple reply. If that's asked too much, I'm afraid hope is gone.
Looks like there's no interest: despite prolonging the due date, no activity here or on the RFP itself. As thus we cannot include the app, the RFP will be closed now. Should interest come up, we can reopen or have a fresh start.