This issue might have popped up in the previous repo, but there are still people out there with custom ROMs and don't have Google services installed. Some can't access Google due to region-locking or just don't want to use the Playstore.

The thing that prevented it last time for it to be on the Open source store was that fdroid/rfp#97 the Cordova build required a Play-services fragment to be available during build. Maybe with the RN version it could be different.

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Minds/mobile-native/issues/1, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1XyMTdpD6UN2bru_LDAnc5wZ5JmNVDks5tjkH4gaJpZM4TBwSh .

Maybe the builds can be automated with a CI. Or is it blocked, due to internal credentials for build?

The apps need to be signed so I dont think that would be possible.

On Wed, May 2, 2018, 5:26 PM Serkan-devel notifications@github.com wrote:

Maybe the builds can be automated with a CI. Or is it blocked, due to internal credentials for build?

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/Minds/mobile-native/issues/1#issuecomment-386126756, or mute the thread https://github.com/notifications/unsubscribe-auth/AAz97FVCG13VzP4eUAMBfn1gY35If-bZks5tuiSPgaJpZM4TBwSh .

Why though?

You can place your keys into a .gitignore entry to hide it

Gitignore stops files from being commited so is unrelated.

The CI server would need the signing credentials. Right now the security risk here outweighs the benefits it woulf bring.

On Sat, May 5, 2018, 8:48 AM Serkan-devel notifications@github.com wrote:

You can place your keys into a .gitignore entry to hide it

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/Minds/mobile-native/issues/1#issuecomment-386803447, or mute the thread https://github.com/notifications/unsubscribe-auth/AAz97NYLXBFYnYfyCmqAF4bQp8SJyznCks5tvZ-egaJpZM4TBwSh .

How do other open source projects commit to F-Droid? Isn't your CI private?

Can't the signing be the only thing hidden and release the source code for the CI as proof?

Hello, I'm a F-Droid contributor. We build every app from source on our build server and sign it with our own key. Does that answer your question?

@Rudloff they are trying to make their CIs public. But if the CI is completely public, one could see their private key when signing

@markharding I think this could help https://youtu.be/2uaTPmNvH0I

Any updates on this?

Could at least be a public apk available for download, officially from minds?

fdroid/rfp#97 (comment 80322175)

The app does not have any tagged release: https://github.com/Minds/mobile-native/releases This would make packaging easier.

Created by: trymeouteh

Could at least be a public apk available for download, officially from minds?

I would be OK with this too. This is what Gab does for their Andriod app. If you do offer a APK download please add a feature in the app that will notify the user when a new version of the app is available.

But an F-Driod release will be nice since it will also update the app when updates roll out.

Would it be possible to have a maintainer be responsible for managing Minds APK on f-droid? I don't have experience with f-droid but it seems like it could be an interesting project to work on.

@msantang78

assigned to @msantang78

changed milestone to %sprint: Wire

added 1 - High scoped label

added S - Backlog scoped label

mentioned in issue #677 (closed)

changed milestone to %sprint: X

changed milestone to %sprint: Zero

changed milestone to %sprint: Aspiring Albatross

changed milestone to %sprint: Boisterous Buffalo

changed milestone to %sprint: Clever Chipmunk

added S - InProgress scoped label and automatically removed S - Backlog label

added S - Backlog scoped label and automatically removed S - InProgress label

mentioned in issue front#1338 (closed)

@markeharding, Thank you for informing me about this ticket within ticket #1338.

However you (or any other staff member) have yet to provide the information that I requested within the previous ticket regarding the Google PlayStore agreement.

Could the requested information be either posted to this ticket or #1338? (also, please remember to tag me to your reply so that I can be notified in a timely and efficient fashion. Thanks.)

I believe we would be in violation of the following clause:

4.5 You may not use Google Play to distribute or make available any Product that has a purpose that facilitates the distribution of software applications and games for use on Android devices outside of Google Play.

(https://play.google.com/about/developer-distribution-agreement.html#non-compete)

Cc. @medworthy (I suggest modifying your gitlab notifications to include tickets you've interacted with(

@markeharding,
Thank you for the information. I can see that the 4.5 clause is the real issue here (which is really disappointing).

Something that I think that I mentioned to @jotto141 at the time that I was writing my "The many faces of the minds app" blog article (see URL below) was the suggestion of providing information within the minds.com/mobile page about Android's "install from unknown sources" security option. I think that some further instructions about installing the unfettered version of the Minds APK being included within the minds.com/mobile page would help a lot of users out.

I also took your advice and activated the "receive notifications about your own activity" tick-box within Gitlab's settings section and also set the "global notification level" to the "watch" status.

(Note that I have included information about the clause to the bottom of my article).

Reference:

The Many Faces Of The Minds App
https://www.minds.com/blog/view/979482529691869184

changed milestone to %sprint: Hipster Hedgehog

The F-Droid client would update the app.

Anyway, I see a custom maven repo and google services used in build.gradle and these are the real blockers for integration in F-Droid (the subject of this issue), not point 4.5 of some others store user agreement. :-(

changed milestone to %sprint: Interesting Iguana

changed weight to 2

changed title from Release it on F-Droid to Release on F-Droid

changed the description

added Platform::Mobile scoped label

added Platform::Mobile::Android scoped label

changed milestone to %sprint: Jolly Jellyfish

added Squad::Green scoped label

changed milestone to %sprint: Kilted Koala

@msantang78 can you write up your findings about google services.

@brianhatchet as Licaon_Kter wrote above the terms of F-droid forbid to have the google play services inside the app https://f-droid.org/es/docs/Inclusion_Policy/ We can't build the app without it because it is required by the Jitsi SDK.

Checking the code of the new release of the Jitsi SDK it now seems to have an option to build it without the google sign-in feature (removing the need of the play services)

But update the SDK into the app will not be a trivial task. I have forked the Jitsi SDK and the package react-native-jitsi-sdk because we needed custom features and I also updated the react-native version of the Jitsi SDK to prevent some conflicts and fixed the sdk for 64bits builds.

Release on F-Droid

Related issues 0

Related issues
0