ownCloud has been forked twice.
\nThe first time, in 2016, a significant part of the community and engineering team left to build Nextcloud.
\nThe reasons were real: governance concerns, transparency gaps, disagreements about the relationship between company and community.
\nPeople left. The project continued.
\noCIS was already taking shape as a ground-up rewrite in Go, and ownCloud 10 kept shipping.<\/p>\n
The second fork, in 2025, was after the Kiteworks acquisition in late 2023.
\nDifferent context, different reasons, but the same underlying lesson: communication isn\u2019t just about what you say. It\u2019s about what the other person hears. Even well-intentioned decisions fracture communities if words, tone, or timing are off.<\/p>\n
What followed was two and a half years of building by a small, dedicated team.
\noCIS went from version 4.0 (the state at acquisition) through five production releases to 8.0.1 today.
\nThe Bavarian school cloud (ByCS) runs on it, serving millions of students.
\nThe Desktop Client went from version 4.x to the completely rewritten 6.0 line.
\nThe architecture proved itself at scale.<\/p>\n
There was a fear that the code would get closed off and that the community would get hollowed out after the Kiteworks acquisition.
\nWhile we kept shipping publicly to our open source repos, we were so focused on building, we did not find and commit the necessary resources into the community.<\/p>\n
We will publish a „Lessons Learned“ document as part of our OSPO manifesto suite.
\nIt will say, in public, that projects diverge when voices feel unheard and governance becomes unbalanced.
\nIt names what went wrong without blaming anyone.
\nBut more importantly, it commits to doing things differently, with specific mechanisms rather than vague intentions.<\/p>\n