Any chance of putting this wonderful app on F-Droid store?

[tinylucid]

I would really appreciate it (and I am sure many others).

[fibelatti]

Hi @defphil, thanks for the suggestion. I will look into doing it.

[grrrrr]

I'll second this request, it would be very useful to have on f-droid given that the other android app, pindroid has stalled in development

[grrrrr]

Hi @fibelatti

If f-droid is not an options, would it be possible to release APK on gitbub? It might allow for inclusion with @IzzySoft's repo which can be used with f-droid https://apt.izzysoft.de/fdroid/

[IzzySoft]

Would fit from what I see – if the signed APK were available here (preferably with releases being tagged and the APK files attached to their corresponding release).

[fibelatti]

Hi @fibelatti

If f-droid is not an options, would it be possible to release APK on gitbub? It might allow for inclusion with @IzzySoft's repo which can be used with f-droid https://apt.izzysoft.de/fdroid/

Hey @grrrrr, thanks for suggesting this alternative, I know it's been a good while since adding the app to F-Droid was first suggested. I've looked into it a while back but never managed to go through the full setup required, so this alternative might facilitate things.

I still need to make a few changes to the app because I'm use some play services (to auto-update and prompt for app store reviews). I'll either have to remove those or build a different app flavour that's specific to F-Droid. I'll prioritise this and see what it takes to add it to the repo

[fibelatti]

@IzzySoft I have just released v2 which should be suitable for your repository. I have attached the signed .apk to the release on GitHub, is there anything else I should be doing to have it listed?

[IzzySoft]

I have just released v2 which should be suitable for your repository.

Confirmed: it is 😃

is there anything else I should be doing to have it listed?

Just to wait until it shows up here with the next sync around 6 pm UTC 😃 If you want to define how your app is presented, you could establish Fastlane structures here in your app's repo (be welcome to use my Fastlane Cheat Sheet for guidance with that). And of course you're also welcome to pick a badge to link to your app's new presence 😉

Thanks a lot!

[fibelatti]

@IzzySoft awesome, thank you! I'll look into setting up fastlane and adding a badge to the repository later today 🚀

[IzzySoft]

Fantastic! Please givve me a ping here once Fastlane is ready – so I cross-check, enable it on my end and (if you link me that RFP I saw a few hours again) also kick the issuebot for another scan at F-Droid.org 😉

[fibelatti]

@IzzySoft I've setup the metadata for fastlane now and published a new release just in case since F-Droid doesn't build from HEAD. This new tag should also fix the Gradle wrapper issue from the RFP 👀

I'm gonna look into the badges next, thanks for your support

Edit: the Gradle wrapper changes messed up my GHA CI, so let me figure that out
Edit 2: it should be sorted now

[grrrrr]

@fibelatti & @IzzySoft this is fantastic, thank you both for getting this available via f-droid clients.

[IzzySoft]

Oof, got no notification for the edits – so thanks @grrrrr for causing this ping 🙈 Bot is triggered now at the RFP.

[fibelatti]

@IzzySoft no problem! As always, thanks a mil for your support!

[fibelatti]

Hey @IzzySoft, I've got two questions and couldn't think of a better way to reach out!

1. I have setup the metadata, could you please enable that on your side so that my listing on IzzyOnDroid is automatically updated?
2. I'm about to include com.google.android.gms:play-services-oss-licenses as a dependency to help listing all other OSS libraries I've used. That's the dependency for this plugin and their license points to https://developer.android.com/studio/terms. Do you reckon that would be a problem for IzzyOnDroid/F-Droid because it's a Play Services dependency? If so I'd much rather find an alternative

[IzzySoft]

couldn't think of a better way to reach out!

Totally fine this way 😃

could you please enable that on your side

That was already done on 2023-10-02. Changes on your end would be pulled along with new releases.

I'm about to include com.google.android.gms:play-services-oss-licenses

Bad idea. The "oss" in that name is misleading: it only processes FOSS-licenses but is not fully FOSS itself (but will drag in proprietary dependencies like GMS) – those AS-terms are proprietary, too (limiting freedoms). So yes, I'd say that is a problem. Mind to pick one of the alternatives I've collected for you? 😉

[fibelatti]

@IzzySoft you're a gentleman sir! Thanks for enabling the metadata change and for linking the alternatives! I'll look into them before submitting the next update.

I've also released a new app this weekend but it already contains the play library so I'll remove it first before submitting it to IzzyOnDroid as well.

Thanks a mil Izzy!

[IzzySoft]

You are very welcome! Just give me a ping when your new app is ready. Don't be surprised if I then respond that it's already listed 🙈

Some background:

• there's a quality check script running here once a month, a.o. checking if some repo has Fastlane added while it's not available here, or whether it is available on both ends but not fully enabled here. That's how your fastlane structures were already added in October: my tool reported it to me.
• I have some other tool watching out for new apps on Codeberg, Gtihub, GitLab which are neither listed at F-Droid nor in my repo. That's how many apps come to my repo.
• there are several more things automated here. Like, had you added that library, as soon as the new APK was pulled here an alert had popped up notifying me. That's e.g. how one app got removed from my repo today, for exceeding those thresholds by far (7 offending libraries is simply too much)

Not all is automated, though. So don't you worry I'd get bored – I won't 🙈