On Feb 3, 2017, at 14:54, Davide Michelino notifications@github.com wrote:
It would be great to have the jitsi meet build released on F-Droid http://f-droid.org/. Is there any plan to release it there?
Hi,
I don’t think we have considered it. Do you happen to have a link to some documentation on how the process would go?
--
Saúl
Thanks! I'll check those out.
Meet Jitsi on F-Droid : Very good suggestion.
Or even have a link to download the APK. (I had to download it like warez, WTF)
Or even have a link to download the APK. (I had to download it like warez, WTF)
Yes, same here... a very bad process of getting an open source app.
Someone has asked the F-droid maintainers to include Jitsi in the repository. The issue is here:
https://gitlab.com/fdroid/rfp/issues/73
It would be appreciated if you could assist with any issues which come up, for instance dependencies, binary blobs, build scripts, etc.
Cheers,
Robin
@robinpaulson Thanks for doing that Robin! I left a comment in case they need our help.
@lanodan @Tony-il-Capo We currently only provide it via the Play store, but of course you can compile it yourself.
@saghul
Downloading via Google is not a solution. (specially if you don’t have Google installed)
Building android apps is a horrible mess, specially if your OS/distro is not like debian/ubuntu. (And I’m used to compile things)
Seriously I fail to see how that can be considered okay, I hope I misunderstood.
@lanodan Time is not infinite, so we do what we can given time constraints. "It never rains to everyone's taste", I'm afraid.
Our currently supported distribution mechanism is the Play Store. Period. F-Droid is in the works, as you read above, but that's out of our control. I did volunteer to help in any capacity required but I haven't been contacted back. You can try to download the APK from one of those APK mirrors, though I cannot recommend one. And last, you can compile it yourself.
If none of the above work for you, I'm sorry, but there is nothing I can do to help you.
lanodan, you can also use gplaycli on Linux or yalp from F-Droid to download apk-s.
@saghul Thanks for your work, I hope F-Droid guys or enthusiasts will reply to you in time. I personally stick to F-Droid and have a very, very limited number of apps outside of F-Droid. This is because fdroid is a serious and respected review stage, passing which means the app is compatible with a lot of requirements (_all_ of which I agree to).
@saghul I appreciate you getting in touch on the f-droid issues page. As you may have worked out, there is a bit of a backlog for adding apps to f-droid. If you are interested in helping out, there is a process to speed things along, I will see if I can find the links and post them here.
@vn971 I didn't know about gplaycli, it looks useful, thanks! Also, I don't disagree with anything you said :-)
@robinpaulson Thanks! What kind of help would be needed?
@saghul
How to add the app yourself - actually, anyone can do this.
https://gitlab.com/fdroid/fdroiddata/blob/master/README.md
https://gitlab.com/fdroid/fdroiddata/blob/master/CONTRIBUTING.md
@robinpaulson Sweet! I'll give it a try this weekend if time allows!
@saghul Are you getting on OK with the inclusion in gitlab? If you need help, do ask!
Alas I'm quite swamped right now, so I never got the chance to look at it... yet!
+1
On 09/28/2017 03:36 PM, Lyubomir Marinov wrote:
Dear F-Droid proponents,
The desire to have Jitsi Meet for Android released in F-Droid has been
duly noted at https://github.com/jitsi/jitsi-meet/issues/1290. I'd
encourage you to please "react" there with "+1" so that it's easier
for us to track how hot a feature request is.Why is Jitsi Meet for Android not released in F-Droid yet? Because:
(1) We're releasing on both Android and iOS so taking on a third
release process requires additional and repetitive involvement on our
side.
(2) Having F-Droid build our young source code base in which builds
are not reproducible yet and (3) which also links with
Fabric/Crashlytics are not trivial matters.(I personally want Jitsi Meet for Android on Amazon Appstore as well.)
Best regards,
Lyubo Marinov
+1 !
+1
+1
+1
+1
+1
+1
Guys, there is a "react with emoji" action instead of +1. Even though I completely agree with the need to have an F-Droid build.
+1
please please please. A friend did not want to install jitsi on Android because she doesn't want to give private data. We were disappointed to not find it on f-droid :(
F-Droid is in the works, as you read above, but that's out of our control. I did volunteer
to help in any capacity required but I haven't been contacted back.
They won't contact you back; there are so many requests and so few maintainers, anything which requires even the tiniest effort beyond an app with a simple process gets put to one side. Not ideal, but their time is limited and there are 276 open requests for app inclusion.
As I understand it, now that you have been made aware of the requirements, they will expect you (or someone else) to make pull requests for the app list repository on gitlab.
I get that your time is limited though, particularly with Play Store, iOS, etc. pressures. Unless someone here prepares the pull requests, it's likely not going to happen.
@strk
please please please. A friend did not want to install jitsi on Android because she doesn't want to give private data. We were disappointed to not find it on f-droid :(
Circumvention: use Yalp Store instead of the Play Store https://f-droid.org/en/packages/com.github.yeriomin.yalpstore/
No Google account needed.
Tried to install Jitsi with Yalp on Cyanogenmod 12.1 but environment tools (Trebuchet, Catapult, Yalp itself) crashed completely.
Luckily I could open a terminal to remove with:
pm list packages | grep jitsi
pm uninstall org.jitsi...
Any updates on this?
I am currently working on a build recipe for F-Droid and I have a few questions:
The instructions at https://github.com/jitsi/jitsi-meet/blob/master/doc/mobile.md tell me to use react-native run-android to build the APK, install it on a connected Android device and launch it. How can I just build an unsigned release APK, without installing or launching anything? (And where would I then find the APK?) I have tried cd'ing to the android subdir and running gradle there, but this fails with:
* Where:
Build file '/builds/mvglasow/Navit-fdroid/fdroiddata/build/org.jitsi.meet/android/build.gradle' line: 73
* What went wrong:
A problem occurred configuring project ':react-native-background-timer'.
> Failed to notify project evaluation listener.
> /builds/mvglasow/Navit-fdroid/fdroiddata/build/org.jitsi.meet/node_modules/react-native-background-timer/package.json (No such file or directory)
(Tested with 10624e87.)
Also, how can I tell which git commits correspond to an official release (i.e. one that would go on the Play Store)? Are they tagged in some way? I see two types of tags, nnnn (number) and jitsi-meet_nnnn, do any of those tags correspond to releases? Or is there another way to tell automatically?
/builds/mvglasow/Navit-fdroid/fdroiddata/build/org.jitsi.meet/node_modules/react-native-background-timer/package.json (No such file or directory)
It looks like NPM dependencies were not installed.
You might want to have a look at how we build other React Native apps on F-Droid.
We don't use the react-native command and instead do something like this manually:
npm install
cd android
gradle assemble
(But Jitsi Meet might have some additional build steps.)
@Rudloff great to see you here! Do you happen to have any examples of other React Native apps on F-Droid? (I wasn’t even aware Jitsi Meet was not the only one…)
You can check the following build recipes:
For all intents and purposes our use of React Native can be counted as anecdotal. It's an implementation detail. You can build it as a regular Android package. The extra step you need to fllow is installing all dependencies with npm i.
If you make a debug build, however, you'd need to start the React Native packager, but you don't need that.
We currently have no tag for mobile releases but are about to start doing it (next release will have one).
Anecdotal… well, you do need React Native installed to build it :-)
Re tags for mobile releases, will they follow a particular pattern? F-Droid can do some regex-based filtering, so if there were e.g. a prefix used for all mobile releases (and only for those), that would be quite easy.
@Rudloff I tried one of those build recipes. I had to run npm install with sudo or else it would fail. The truncate/rm operations fail because the respective files are not found, so I just appended || true to see what happens afterwards. After that, the build process fails with the same error as above.
This might be related to my CI setup, I’ve documented details at https://gitlab.com/mvglasow/fdroiddata/issues/1 and would be grateful if you could take a look.
I just noticed the app uses several non-free libraries: https://github.com/jitsi/jitsi-meet/blob/54df0f5d0fe1565c93118df8aa1bc981dd738c43/android/app/build.gradle#L85
This will prevent the app from being included in F-Droid as we require included libraries to be FOSS.
Is there any way to build Jitsi Meet without FCM? If not, that would be a blocker.
Anecdotal… well, you do need React Native installed to build it :-)
Not really, you need all npm dependencies installed, and RN is distributed in as an npm package, so I don't see the problem there. Can you clarify?
Re tags for mobile releases, will they follow a particular pattern? F-Droid can do some regex-based filtering, so if there were e.g. a prefix used for all mobile releases (and only for those), that would be quite easy.
Yes. We haven't decided exactly on the pattern, but it will be a consistent one.
Is there any way to build Jitsi Meet without FCM? If not, that would be a blocker.
Yes and no. FCM is not a hard requirement, so a build time toggle to disable it would be ok. I wonder if we can do it with this variable: https://github.com/jitsi/jitsi-meet/blob/6190173ea74be8f070f9a8334ce699f22570ac51/android/app/build.gradle#L3
Then here: https://github.com/jitsi/jitsi-meet/blob/master/android/app/src/main/java/org/jitsi/meet/MainActivity.java#L194 we'll need to use the full package notation to avoid the imports.
I think that would be all.
I'll keep this in mind and take care of it as time allows, but if someone wants to send a PR, that would be most welcome.
Would be very welcome for me as well, yalp needs a google account here and gplaycli don't work for me on ubuntu bionic and I've got a google-free smartphone.
Thanks!
@webmind offtopic, but Yalp certainly doesn't require a personal google account. There were some occasions when it was laggy, but otherwise it works just fine (using built-in accounts). Retrying later helps at times.
Could we have an F-Droid version without Google Crashlytics and Firebase Analytics? See https://reports.exodus-privacy.eu.org/en/reports/37219/
I've made some progress on this. https://github.com/jitsi/jitsi-meet/pull/4155 allows to build Jitsi Meet without any analytics nor Google Play Services.
If I can get this landed by in the next Jitsi Meet version (19.2.0) it would be the right time to restart the F-Drop release effort, by taking that tag and rebuilding it with the LIBRE_BUILD env var.
For reference: https://gitlab.com/fdroid/rfp/issues/73#note_188026138
I think, this is one to announce on social media, reddit, irc, etc.
Most helpful comment
https://f-droid.org/en/packages/org.jitsi.meet/ 🚀