It’s easy to be tempted to draw a parallel between the recent fork of ownCloud by Nextcloud and The Document Foundation’s fork of OpenOffice six years ago. Slight differences are there, but they’re probably meaningless.
There are more than enough similarities between the recent forking of ownCloud to Nextcloud and the creation of LibreOffice out of OpenOffice six years ago to draw comparisons, but there are also many differences. As Yogi Berra might say, they are the same but different.
OpenOffice, if you’ll remember, was forked by a group of developers who had been frustrated for years by roadblocks to what they saw as necessary development by Sun Microsystems, which had created the open source project out of Star Office, a proprietary suite it purchased in the late 1990s. When the situation worsened after Oracle took ownership, the developers created The Document Foundation, forked OpenOffice and released it as LibreOffice under the GPL. Improvements became evident right away, with much of the early work centering on cleaning up the bloated code base.
On the surface at least, the recent forking of ownCloud was much the same. A group of developers unhappy with the project’s direction forked it to create Nextcloud. The developers also promised that functions in the enterprise edition that were non-free would be reimplemented as free software released under the AGPL. Similar to LibreOffice, less than a month after the initial forked release, an update was issued bringing improvements.
There are some differences, however. Unlike The Document Foundation fork, which was a group organized project, the Nextcloud fork appears to have been spurred primarily by Frank Karlitschek, ownCloud’s founder, with help from Jos Poortvliet, one time community manager for ownCloud and openSUSE. Just five weeks earlier, Karlitschek had resigned his position as CTO of ownCloud, Inc. By appearances, the move wasn’t entirely altruistic and was at least partly motivated by profit, which isn’t a problem in and of itself, as long as profit wasn’t the overriding motivation. For better or worse, this is a capitalistic world and bills must be paid, children must be fed and mortgages must be paid.
However, the new project did come with a commitment to FOSS. Unlike ownCloud, which required users of the enterprise edition to pay licensing fees for the use of included proprietary software, Nextcloud promised to adopt something similar to the Red Hat model, with a promise that all software would be free, with the company paying its bills through support subscriptions.
So far the company is standing behind these promises. The update to Nextcloud 9 announced on Tuesday returns many of the enterprise functions which had been proprietary in ownCloud as rewritten free and open source software. As Karlitschek explained to eWeek for an article published the same day as the update, “Nextcloud is building open-source replacements for the ownCloud closed-source enterprise-only features. With this release, 80 percent is done and the rest will be coming soon.”
Not only have previously proprietary functions been returned as open source, new capabilities have been added at the enterprise level. “At the moment, we have a new and super easy way to theme your Nextcloud installation with different colors and logos directly from within the Web interface,” Karlitschek also told eWeek.
The update also includes Security Assertion Markup Language (SAML) for Single Sign-On Authentication (SSO), which were developed in collaboration with several universities and research institutions. In addition, the company has become a participant in the Open Cloud Mesh initiative, which according to Nextcloud’s website, “aims to link researchers and universities in Europe, the Americas and Asia via a series of interconnected, secure private clouds.”
While it’s too soon to tell if this fork will be as beneficial to free tech as LibreOffice has been, so far it appears that Karlitschek and his team are making a good start.