Bringing back the Open in Open Source: (Re-)Building Community after forks and acquisition (froscon2026)

Open source projects get forked. They get acquired. They lose contributors, fracture communities, and sometimes quietly stop being open in a meaningful sense. This talk uses ownCloud's history as an honest case study in what goes wrong and what it actually takes to fix it. We'll cover the real lessons from operating a major project without proper open governance, what prompted a course correction, and the concrete steps taken since, in trying to rebuild contributor trust without hiding behind community-washing language. The phrase "open source" carries a lot of weight, and not all of it is as open and honest as it should be. A project can be open source by license and still be effectively closed in every way that matters to contributors: opaque roadmaps, decisions made behind closed doors, community input that gets acknowledged and ignored. ownCloud knows some of this firsthand. This talk is a case study, not a redemption arc. We'll start with ownCloud's origins and the context that led to the 2 forks (one of the more significant splits in the self-hosted software space), then trace what a decade of incomplete open governance actually costs a project: contributor drift, community distrust, and the kind of reputational debt that doesn't show up on any balance sheet until you try to spend it. The second and thrid parts are about what changed. Kiteworks took on commercial stewardship of ownCloud and faced a choice that a lot of companies in similar positions avoid making clearly: keep doing what wasn't working, or build something more honest. This section will also cover the Community Advisory Board model we're building toward. This isn't a talk for people who want reassurance that open source is fine. It's for developers, OSPO practitioners, and anyone involved and intersted in open source projects that have gone through acquisition or a fork and are trying to figure out what "working in the open" actually means when there's a commercial entity at the center. The lessons from ownCloud are specific and sometimes unflattering. That's the point. Licensed to the public under http://creativecommons.org/licenses/by/4.0 about this event: https://programm.froscon.org/2026/events/3654.html