Kiteworks launches ownCloud OSPO, relicenses 100 projects to Apache 2.0

By AI, Created 10:26 AM UTC, May 20, 2026, /AGP/ – Kiteworks has launched a formal Open Source Program Office for ownCloud, setting new governance rules, contribution policies and community commitments. The move also relicenses more than 100 projects to Apache 2.0 and signals a more transparent posture for the open-source file sync and share platform.

Why it matters: - The ownCloud OSPO formalizes how the project governs contributions, decisions and community participation. - Relicensing more than 100 projects to Apache 2.0 can make reuse and external participation simpler for developers and organizations. - The changes matter for customers, contributors and public-sector users that rely on ownCloud for self-hosted file sharing and collaboration.

What happened: - Kiteworks launched a formal Open Source Program Office under the ownCloud brand in Regensburg, Germany, on May 7, 2026. - The launch introduces structured governance, contribution policies and community engagement commitments for the ownCloud open-source ecosystem. - Kiteworks relicensed over 100 projects to Apache 2.0. - The company retired the legacy Contributor License Agreement in favor of the Developer Certificate of Origin. - Kiteworks published a governance charter defining contributor roles and decision-making processes. - The company issued an AI-assisted contribution policy that allows 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: - 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 through that workflow. - The full developer methodology is published at ownCloud developer docs. - The governance charter includes 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. - The first annual OSPO report is scheduled for Q1 2027. - The report is intended to cover governance activity, contribution volume, security program outputs and progress against charter commitments. - The launch follows two years of engineering work with limited public communication. - During that period, ownCloud shipped quarterly releases, rebuilt its CI/CD pipeline on GitHub Actions, delivered new desktop, Android and iOS clients, and upgraded ownCloud Classic from PHP 7.4 to PHP 8.3.

Between the lines: - The OSPO appears designed to turn a mostly engineering-focused effort into a more formal open-source operating model. - The governance charter’s v0.1 label suggests Kiteworks is signaling that the process will evolve publicly instead of presenting a finished framework. - The AI contribution policy lowers the barrier for some contributors, while still setting quality and compliance standards. - The timing suggests Kiteworks is trying to align commercial stewardship, community trust and public-sector expectations around the ownCloud platform.

What’s next: - Kiteworks plans to publish its first annual OSPO report in Q1 2027. - ownCloud’s governance and contribution processes are expected to continue evolving as the charter moves from v0.1 toward a more mature framework. - The migration path from ownCloud Classic to ownCloud Infinite Scale is likely to remain a key focus as the newer platform grows in use.

The bottom line: - Kiteworks is putting formal governance around ownCloud and pairing it with permissive licensing, AI-friendly contribution rules and a public accountability plan.