Skip to content
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

Inclusion in F-droid #26

Closed
Dragnucs opened this issue Jun 3, 2020 · 13 comments
Closed

Inclusion in F-droid #26

Dragnucs opened this issue Jun 3, 2020 · 13 comments

Comments

@Dragnucs
Copy link

Dragnucs commented Jun 3, 2020

Please consider submitting the application to F-droid.

Submission link: https://gitlab.com/fdroid/rfp/-/issues/1372

What is mostly required is a fastlane file structure and tagging releases. I might help with that.

Additionally, to enhance privacy respect, please provide a so called untainted build with no dependencies to crashlytics and firebase or other proprietary dependencies.

Keep up the good work! I am glad Morocco is releasing a foundational, quality, privacy reviewed, and FLOSS application.

@licaon-kter
Copy link

licaon-kter commented Jun 4, 2020

Additionally, to enhance privacy respect

It's not about that, the main F-Droid repo hosts only full free open-source apps. If it links to Google Services/Firebase/Crashlytics/etc libs, which are closed sourced, it can't be included.

@Dragnucs
Copy link
Author

Dragnucs commented Jun 4, 2020

F-droid hosts application that are at the same time FLOSS and privacy friendly. The application at hand lacks in the later.

Inclusion Policy

Instead of debating what it is about or not, lets contribute to make this even better, and privacy respecting.

@Abdelwahad
Copy link

Thank you very much for this interesting proposal, but as @licaon-kter pointed out, the use of Firebase is not allowed by F-droid.

@Dragnucs
Copy link
Author

Dragnucs commented Jun 7, 2020

Why is firebase used in this application anyway? Can't an alternative be used? Like knative or other databases.

@smege1001
Copy link

@licaon-kter

If it links to Google Services/Firebase/Crashlytics/etc libs, which are closed sourced, it can't be included.

It might get included, but with an anti-feature warning that says that the upstream source code is not free and some parts of source code may get rewritten or replaced to remove the non-free libraries or code

@licaon-kter
Copy link

licaon-kter commented Jun 27, 2020

@smege1001 nope, and if that was the case for older apps in the past it is no more.

The Wiki is obsolete since Dec 2018, there only 4 pages there, related to current build output, that are still updated.

@Dragnucs
Copy link
Author

@Abdelwahad can you reconsider this issue?
This will also solve other issues like #38.

@Abdelwahad
Copy link

@Dragnucs Sorry, we will not move from firebase in a near futur. Anyway, thanks a lot for your proposal.

@Dragnucs
Copy link
Author

Dragnucs commented Jul 3, 2020

I understand not wanting to move away from firebase, but can you please explain this choice? Using a proprietary library while you want to have a fully free and open source stack.

@licaon-kter
Copy link

@Abdelwahad is this about a database software or about having a dependency on Google Services?

@Dragnucs
Copy link
Author

Dragnucs commented Jul 3, 2020

Both. The stack starts from the what runs on the mobile, transport layers than what is used in the back-end server.
For example, even if this application is open source, it forces us to use proprietary privacy intrusive dependencies. Google services for instance.

@licaon-kter
Copy link

@Dragnucs I wasn't asking you, I wasn't asking that

@smege1001
Copy link

Using proprietary libraries absolutely ruins the point of being about privacy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants