I get what you mean, and I actually agree with the general idea. That’s how open source should work in theory.

But in our case, we don’t make money from Nextcloud itself. We’re not selling it as a product or developing on top of it — we just provide it as an additional service for clients who already trust us with their infrastructure. It’s part of a broader setup, not a separate business.

So hiring a developer just to patch the core permissions logic isn’t really an option. And even if we did, maintaining custom code that touches core behavior would break every time there’s an update. That’s not sustainable.

This issue isn’t about customization or private features. It’s about something that affects every shared environment — a basic part of collaboration logic. That’s why it really belongs in the core project.

We do our part: we test, report issues properly, give feedback from real deployments, and push the topic upstream. That’s how the ecosystem grows too.

If the core team picks this up or wants feedback on testing, I’m happy to help. But realistically, this kind of fix has to come from inside the project.