Publish on F-Droid?

[IzzySoft]

Being an open source app, it would be great to have TORGI available on F-Droid. A raw glance at your gradle files seems to show (to a non-dev like me) there are no show stoppers (proprietary libs), though I might have missed something.

Would you support that?

To make it easier for you, I already opened a request for packaging with F-Droid. For the builds (F-Droid builds from your source code), it would be great if the tags and versions on the releases/ page (currently 1.2.2) match those in your gradle/manifest (currently 1.2) :wink:

Until it becomes available at F-Droid (provided you accept), could you have signed .apk files at your releases? Then I could offer to provide your app via my repo immediately.

Thanks in advance!

[ianblenke]

@IzzySoft, thanks for the involvement!

@tabinfl and @scottlandis are really the primary devs of this project at the moment. I'll reach out to them on our sofwerx slack and see if we have any reservations of doing so. There may be some reservations as we're iterating toward making these apps more user friendly.

[IzzySoft]

Thanks Ian! Looking forward to your update then. The RFP is stalled anyway until I mark your approval there – so nothing will happen with it until then.

[IzzySoft]

@ianblenke The F-Droid bot just checked your repo and found an insecure gradle. Regardless of how you decide about "going F-Droid", you might wish to fix that :wink:

[ianblenke]

@IzzySoft Ouch! Thanks! Seems like a simple fix there. PRs are always welcomed :grin:

[IzzySoft]

Yepp, should be easy to fix from what I've heard. I'm no Android dev, so I prefer not to tamper with the code, though :wink:

[ianblenke]

@IzzySoft PR #31 should address this. I'll just need @tabinfl or @scottlandis to give this a +1 before merging.

[tabinfl]

Let’s pause this please until I return, we are going to have some fast-moving updates coming out of this week’s experiments, I’d prefer to avoid any distractions (e.g. from wider app distribution) until after those are addressed. @ianblenke & @scottlandis, I will fill you in offline.

[IzzySoft]

@ianblenke thanks!

@tabinfl No problem. Just give me the "Go" when it's ready, so I mark the RFP at F-Droid accordingly then. Thanks to you as well!

[Grossdm]

Just a comment:

This looks like an awesome project!

Doug®

[IzzySoft]

@tabinfl are you returned? Can we get this running?

[IzzySoft]

Unfortunately you only offer unsigned and debug releases here, else I had at least added it to my repo meanwhile. Hope that's not because you fell into Google's trap of having them sign your packages, and your signing key is only there?

[IzzySoft]

@tabinfl any news?

[IzzySoft]

@tabinfl @ianblenke where is this stuck? The RFP is still waiting on F-Droid's end, but looks dead on yours.

[tabinfl]

My primary reservation is that the RFI/EW detection algorithm has not been validated, and in fact our testing showed some significant deficiencies in an adversarial scenario. Unfortunately I haven't had the bandwidth to dive into the testing & analysis required to improve that.

There is a warning to that effect on the app's main screen, and as long as that could also be communicated in the description on F-Droid it's OK with me.

[IzzySoft]

@tabinfl The description can be completely in your hands! Simply use fastlane or triple-t (see e.g. here) to maintain them on your end. That way you can even add screenshots – and use the very same stuff for Play Store as well if you have your app there, no double work.

[IzzySoft]

@tabinfl any status update? Just triaging issues at our end and again came on the one asking to package TORGI. Got impregnated with metadata 9 months ago, time for it to give birth!

[IzzySoft]

@ianblenke @tabinfl any news? We already missed this issue's 1st anniversary now…

[ianblenke]

Neither @tabinfl or I are employed by Sofwerx any longer. As such, we wouldn't be authorative for publishing the app. Seems like something potentially worth forking on github.

[IzzySoft]

Thanks @ianblenke – but who can then? Or shall I close the RFP because noone wants to say either yes or no? Would be a pity, wouldn't it? The license would permit, so it's rather a formality we're stuck at.

[IzzySoft]

It's a real pity, but it seems like I have to withdraw my RFP at F-Droid then. Here development looks stalled, noone to contact, noone having declared a "successor fork" (I'm still no Android dev, so I could not even do so if I had the time for it). Sounded so promising :cry:

I'm leaving this issue open here. Should someone take over the project, please contact me (a comment on this issue will do fine) and we can pick up again.

[tabinfl]

Thank you for your efforts @IzzySoft, unfortunately none of the original developers have had the bandwidth to follow through with additional development that would be needed for it to be releasable as an app. It’s not forgotten, just on a back burner for now.

[IzzySoft]

Quite the rearmost back burner, considering when this issue was opened :speak_no_evil:

I'd suggest we close the RFP then for now on F-Droid's end (I'm trying to tighten things there to have a better chance for a clear overview of tasks). It's still linked from here and thus can be found easily. Once you're ready, we can reopen and continue (or have a "fresh start", whichever seems more appropriate then).

Thanks a lot, all the best for your current projects – and hope to hear from you when we can pick up again!

PS: I already closed the RFP 2 weeks ago. Just updated it with the "back-burner hint" now.