-
-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fdroid version #15
Comments
Hi @alialbaali Are you ok with the inclusion of this app ? We could take care of the rest. |
I'm fine with publishing the app to F-Droid. However, In the next couple of releases, Noto will hopefully support internet data backup, and I'm not sure yet how it's going to be done. I'm looking for BaaS platforms such as Firebase and Appwrite and I still haven't decided yet (still researching). Note that, I probably won't go with Firebase since I want Noto to be degoogled. If you have any platforms you recommend, I'll be really glad to hear about them, as it would help a lot. From my knowledge, apps that use Google Services (such as Firebase) are not allowed in F-Droid. So, I want to finish implementing data backup first, then I will definitely publish to F-Droid if possible. |
There is no closed-source/non-free library allowed in apps that pretend to be on F-Droid, sorry :/ I never heard about a BaaS (Banking-as-a-Service) which is free and open-source, but maybe @IzzySoft heard about something like that? |
No. The only banking app we have at F-Droid is provided by a bank, but it's just the 2FA (not the banking itself). But sure you've interpreted BaaS correctly, @Poussinou? @alialbaali compares it to Firebase. And if it's a replacement for Firebase, I'd indeed have something to link to: Supabase. Or, if it's just Cloud Notifications you're after, there's @UnifiedPush (with existing F-Droid support already, see my list on Push Clients/Manager. UP gives a lot of flexibility, with the users being able to choose their preferred "cloud service". |
By BaaS, I meant Backend-as-a-Service |
Sorry I misunderstood... |
So my irritation was warranted 🤣 – and what's more important, the two hints given fully apply. Take a look at Supabase then – "backend" sounds like you need more than just notifications. PS: I love Bakery-as-a-Service. Especially when they deliver fresh-and-hot directly to the breakfast table. And if they can't make it in time, there's always Brewery-as-a-Service for the evening… 🙈 PPS: Unfortunately, more than those I daily see a lot of Bullshit-as-a-Service 🙊 💨 |
It's fine, I was trying to correct @Poussinou for considering the term as (Backend-as-a-Service), no biggie. I'm looking for something like Firebase but degoogled, since I want users to be able to backup their data to the cloud. You're suggesting Supabase, and there's also Appwrite, what do you think of both of them? Are there any other alternatives that worth to look at? Note that, the app business model might change depending on the implementation, If the implementation would be something like Firebase, then it would offer 3 options:
Otherwise, you have mentioned in the previous comment that there's an option to let users choose their preferred cloud service. Could you elaborate more on this, please? And is UP the only platform that supports that? Let me know also if any of that would interfere with publishing to F-Droid. |
Sure, I got that – I was just joking (couldn't help myself). @Poussinou knows me long enough to also know this was not making fun of him (at least I hope so).
I always tend to leave each task to its own app. If I want to backup stuff off-device, I have an app doing that (e.g. syncing the backup folder to my Nextcloud or other computer). Why should each app include the same functionality redundantly? Though I have to admit that currently, at least to my knowledge, no FOSS sync app for WebDAV/rsync exists. So should you think about a separate app for that, count me in: I'd definitely give that a try and might even "sign up" as tester!
Oh, didn't know about that – thanks for the pointer, added to my snippet right away! As for what I'm thinking about the two: good to have them 😄 I didn't take a deep look, haven't heard much from developers/users on them, and have no experiences with them myself. The options sound totally fine! Average Jane & Joe can have their care-free free variant – and who needs more can have it as well. Plus, you can cover your costs. A clear win for all.
I was talking about UnifiedPush, which is just for cloud notifications. There are several providers available for that, details behind the link I gave (which goes to my website). But with things like WebDAV, that would be true s well (at least for "cloud storage"), as there are many different services offering access via WebDAV. Nextcloud/ownCloud are just some of them.
Firebase would. I see no reason why Supabase or Appwrite would – but then, we didn't yet have an app using those, so I cannot yet tell about possible dependencies being dragged in. A quick look at Appwrite's |
May I recommend you my Fastlane Cheat Sheet and ask you to establish the described structure – then let me know when it's there? Then, once I've enabled that on my end, all future changes would be pulled along with their respective release 😉 |
Got it! Thank you so much :) |
Great! Then I'm waiting for your next ping when Fastlane is there, so I do my part of the job on my end 😃 |
Hey @IzzySoft, So, I decided to publish Noto to the main F-Droid repository. In the past few days, I managed to set up the metadata file, along with the fastlane structure. However, I have few questions, and I'd appreciate any answers before opening an MR on GitLab.
Sample of the metadata file:
In this case, do I create two locations, and copy everything manually or is there a specific tool to be used to separate the structures between Play Store and F-Droid?
Thank you, and sorry for bothering you with my questions 🙂 |
|
Thank you for the answers, really appreciate it! |
@IzzySoft, the repository now has the desired fastlane structure. 😃 |
Thanks! Integrating it here. Notes:
<b>Noto</b> is a simple note-taking app that lets you organize your notes into libraries with different colors and icons. You can create and manage your notes easily, Auto Save, Archive Notes and more.
* <b>Ad-free:</b> We all hate ads. Well, Noto doesn't have any, and it never will. Enjoy the full experience without any ads and free of cost.
* <b>Open source:</b> Noto is an open-source application. You can view its source code on GitHub at anytime using this <a href="https://www.github.com/alialbaali/Noto">link</a>
* … and so on (though it's quite stating the obvious for an app in a repository with only open source apps to state it's open source – but I guess you'll use the same for PlayStore, and that's why it's there?) All else is now enabled and will be pulled along with each new release from now on. For the full description, I wanted to wait for your decision on formatting. |
Are you suggesting I do it like this?
Correct. I have it there since I'm using it in the Play Store too.
Thank you! |
If you want to use HTML directly? <ul><li><b>Ad-free:</b> We all hate ads. Well, Noto doesn't have any, and it never will. Enjoy the full experience without any ads and free of cost.</li></ul> For F-Droid.org, ideally the entire description is in one line then, as there each |
Why aren't the new versions appearing on F-Droid? The latest version there is still 2.2.3 (54). |
UpdateCheckData: buildSrc/src/main/java/Dependencies.kt|VersionCode\s=\s(\d+)|.|VersionName\s=\s"(.+)" That file no longer exists, so the new versions cannot be found. Probably should be changed to UpdateCheckData: buildSrc/src/main/java/App.kt|VersionCode\s=\s(\d+)|.|VersionName\s=\s"(.+)" Done that here now. CI shows CheckUpdates now finds the latest release, so I've added that as well to speed up things (i.e. so we don't have to wait for the next CheckUpdates run as well). But now the build fails for the latest version. @alialbaali is that someone you can fix on your end? I'm no Android dev, so I'm lost with that:
Did you maybe switch to Java17? Oh, indeed:
OK, let me give that a try then (oops, my team mate just did that now 🙈 Which means I was on the right track). Builds now – but is no longer reproducible:
For consultation: HOWTO: diff & fix APKs for Reproducible Builds. Relevant details:
Can you please take care for that, @alialbaali? Once the PNGs are fixed, I guess the XML will be fixed automatically (guessing at checksums being stored there). |
The XML is different b/c upstream's APK has one more locale than the one from CI: <locale-config xmlns:android="http://schemas.android.com/apk/res/android">
<locale android:name="en-US" />
<locale android:name="ar" />
@@ -6,7 +6,6 @@
<locale android:name="de" />
<locale android:name="es" />
<locale android:name="fr" />
- <locale android:name="id" />
<locale android:name="in" />
<locale android:name="it" />
<locale android:name="ko" /> |
I'm still waiting for some feedback regarding this issue. |
It would be great if this app was also on Fdroid!
The text was updated successfully, but these errors were encountered: