Kiteworks launches ownCloud open source office

By AI, Created 10:21 AM UTC, May 20, 2026, /AGP/ – Kiteworks announced a formal Open Source Program Office for ownCloud on May 6, 2026, in Regensburg, Germany, pairing a governance overhaul with relicensing, a new AI-assisted contribution policy and a roadmap for the open-source file sync platform. The move is designed to make ownCloud’s community processes more transparent as the company expands its cloud-native and sovereign-infrastructure offerings.

Why it matters: - The OSPO gives ownCloud a formal governance structure for contributors, maintainers and community engagement. - The launch resets how ownCloud handles licensing, contributions and decision-making across more than 100 open-source projects. - The changes matter for contributors, commercial customers and public-sector evaluators that need clearer rules and more transparency.

What happened: - Kiteworks announced a formal Open Source Program Office under the ownCloud brand on May 6, 2026, in Regensburg, Germany. - The OSPO introduces structured governance, contribution policies and community commitments for the ownCloud open-source ecosystem. - Kiteworks is the parent company of ownCloud. - The company relicensed more than 100 projects to Apache 2.0. - Kiteworks retired the legacy Contributor License Agreement in favor of the Developer Certificate of Origin. - The company published a governance charter that defines contributor roles and decision-making processes. - Kiteworks also published an AI-assisted contribution policy that welcomes contributions developed with AI tools. - ownCloud Classic was upgraded to PHP 8.3. - Kiteworks released a migration tool to ownCloud Infinite Scale, the cloud-native platform written as microservices in Go.

The details: - David Walter, VP of the Open Source Program Office at Kiteworks, said the company is putting the terms of the open-source “social contract” in writing. - Walter said the shift to Apache 2.0, the end of the CLA, the adoption of DCO, the governance charter and AI-assisted contributions change how contributors, customers and the broader community engage with ownCloud. - The launch follows two years of engineering work with limited public communication. - During that period, ownCloud shipped quarterly releases and rebuilt its CI/CD pipeline on GitHub Actions. - ownCloud also delivered new desktop, Android and iOS clients. - The Classic platform moved from PHP 7.4 to PHP 8.3. - The OSPO formalizes the governance and communication commitments tied to that engineering work. - The move signals a more transparent posture toward the contributor community, commercial customers and public-sector evaluators. - oCIS, or ownCloud Infinite Scale, is licensed under Apache 2.0. - oCIS is deployed at scale in European public-sector environments, including a German federal states official school cloud serving millions of users. - oCIS also supports the European Open Science Cloud across cross-university research activities in Europe. - oCIS supports federation through Open Cloud Mesh and identity management through OpenID Connect. - ownCloud says oCIS can run entirely on sovereign infrastructures. - ownCloud Classic, also known as ownCloud 10, remains under active maintenance on PHP 8.3 and continues to receive security and maintenance releases. - The AI-assisted contribution policy requires disclosure of the tool used, contributor comprehension of all submitted code, adequate testing and licensing compliance. - Two oCIS web extensions have already been merged using that workflow. - The full developer methodology is published at ownCloud developer docs. - The governance charter creates a contributor-to-maintainer pathway, a Community Advisory Board and a public roadmap. - The charter is labeled v0.1 and is described as aspirational in parts. - A first annual OSPO report is scheduled for Q1 2027 and will cover governance activity, contribution volume, security program outputs and progress against the charter.

Between the lines: - The governance overhaul suggests ownCloud wants to look more like a mature open-source project with public processes and clearer accountability. - The AI contribution policy is notable because it accepts AI-generated help without lowering the quality bar, which could widen participation while keeping review standards intact. - The unusually candid v0.1 label on the charter signals that Kiteworks is treating the governance model as a work in progress rather than a finished framework.

What’s next: - Kiteworks plans to publish a first annual OSPO report in Q1 2027. - That report is expected to provide a public accounting of governance activity, contribution volume, security outputs and charter progress. - The company is likely to continue transitioning contributors and projects into the new governance model as the OSPO matures.

The bottom line: - Kiteworks is turning ownCloud’s open-source community into a more formal, more transparent and more permissive ecosystem, while keeping the platform positioned for public-sector and sovereign deployments.