Which Nextcloud apps are default in /e/OS and differences in the forks

Using /e/OS murenacloud
1

I love that /e/OS has a lot of Nextcloud functionality already baked in.

But what complicates things for someone like me, who used Nextcloud on their phone before, is that I’d really want to know:

  • which Nextcloud(-related) apps are already integrated into /e/OS by default; and
  • what are the changes in the /e/’s forks of the original Nextcloud apps.

Regain your privacy! Adopt /e/ the unGoogled mobile OS and online servicesphone

1 Like
2

not many - you can gauge the origin of an /e/-App fork from the repository description at https://gitlab.e.foundation/e/apps

for what the differences are - check out both Repositories to somehow same versions before they diverge to much and rename classes / move folders, then do recursive folder diff.

For Nextcloud related content, what keeps Contacts (Aosp version), Calendar (Etar) and Tasks (opentasks) in sync is the work of davx5-ose (formerly Davdroid). So it’s really the protocols (Web-/Cal-/CardDAV) doing the interfacing.

Edit: I took a stab at how to compare App forks in [HOWTO] Oneliner to Diff an /e/-app Fork to its Upstream

1 Like
3

Thanks, that’s useful.

What I wonder whether it’s worth maintaining a fork for most of these. Especially since its already seems some /e/-apps are missing features from its upstream (e.g. Sms app misses features from QKSMS).

I don’t know how else to create a more uniform UI though …so just throwing this in as a question. It may very well be worth it.

4

I think there is no other choice to forking if a handful of people try to quickly make their case and show their vision as it allows for more control. The /e/-Team made excellent picks in what to fork. But then you’re also on the hook for running the bugtrackers and having divided the userbase.

Longterm the user benefits if there’s close collaboration. If you fund both projects, it’s also a more efficient use of resources.

1 Like