@bb77 closest I’ve seen to a community LTS is @nextcloudpi offering their own release schedule, which can be bypassed at any time by updating yourself. Their offering includes automatic updates of the base software, automatic updates of apps, and a webui / cli interface for occ maintenance. Since it includes these different moving parts, it requires thorough bug testing and a slower cycle, which is great! Basic tldr, resist the urge to update major versions until bugs are addressed in stable. This addresses the move fast approach to an extent, but remains specific to this project.
Credit where credit is due, basically every major enterprise part of the software has been open sourced these last couple years: spreed high performance backend as an example. So, got to give them big kudos.
It does seem a bit of a bummer to see the employees always being called to join conversations both on the forum and github… just see it happening all the time and I do feel bad for those people who are treated as always on-call because they actually do respond to most of these posts once people get heated. Just my .02, but I’d love to hear more from the app maintainers who started this thread in a calm and collected manner… @marcelklehr and @stefan-niedermann
Right now there is a definite lack of knowing which apps are community apps. Actually, only a small number of apps are “official” and “core”… the number is much smaller than most any of us realize. E2E is a community app, which I had no idea about until someone on the team said so [looking for the exact quote either on forum or gh]… so there is no guarantee on it working across major version releases. I’d love to see the ability for us to resist updates that break X and Y apps we depend on.
On the Github side it is really difficult to track what is happening in regards to community contributions. Requests on Github will be eventually be closed to limit the number of open issues the core team will not be able to implement, but there is no “Nice to Have” label or similar that allows volunteer developers to track these github submissions the core team is not working on in the future…
Yes, it is a constant game of test for breakage and what is supported… that is why the missing features thread was created in addition to these:
Any apps not yet compatible with version 21 and php 8?
Any apps not yet compatible with version 22?
I apologize as this is all a big deviation from the original question of this thread, but I do see it related to how the community could better contribute. Unsure of how the Foundation branch of the community will develop, but I do see that we could really use a greater focus on encouraging the community to contribute quality documentation similar to the Arch Wiki. My suggestion is adding a category to this forum in which every post is user editable by default. Common courtesy will still apply, but it is easy enough to revert edits.
Totally true. I completely acknowledge that we are a very small percentage of the user base, so that is certainly important to keep in mind regardless of future developments.
I would love for this to happen any time!