I’d say that providing up to date packages is a great idea and I’d like to invite distributions to do that.
So distributions with a rolling model or a short release cycle like Arch, openSUSE Tumbleweed, Fedora or Debian Unstable/Testing could easily include Nextcloud packages and - please, guys and girls, do. Anything we can do to help, ask us!
For a more LTS focused distribution there are two problems:
- long term bug and security fixes are something very few volunteers want to work on (most barely fix bugs in the stable release but only in development versions…).
- Nextcloud can’t skip upgrades. And I don’t think it is OK running people through 5-10 upgrades at once at the end of the period.
It won’t be easy to find people willing to do bug and security fixes for 10 years. I sure won’t be willing to force volunteer developers to backport every fix for that long. A low barrier to contribution to Nextcloud is important to us.
We want to make it possible to skip releases, so that concern might go away in a future release, but we’re talking at least 2-3 releases from now, I think. An alternative would be to built a hacky way to skip upgrades which risks users’ data - something we would get very upset about (again). Users’ data is holy, not risking it is rule 1 of Nextcloud.