LWN Weekly Edition
Front pageSecurity
Kernel development
Distributions
Development
Announcements
->One big page
This page
Previous weekFollowing week
| |||||||||||||
DevelopmentWhat's next for BerliOS projects?It's been a good run, but after more than 11 years in service BerliOS will be shutting down. Users and projects have until the end of this year to move their data off BerliOS. The good news is, there are plenty of alternatives, though the shutdown highlights the problems of moving from one forge to another. BerliOS is providing clear instructions on getting data out but migrating to another forge is an exercise left to the project or developer. BerliOS is operated by the Fraunhofer FOKUS institute in Berlin, Germany. In June, the BerliOS project conducted a survey to see whether there was support in the community to help fund the site. According to the announcement on September 30th, there is not enough support in the community to "put the project on a sustainable financial basis." Efforts to find a partner or sponsors to help host BerliOS that would be compatible with its open source roots were also unsuccessful. It is unclear just how much of an effort was made to keep BerliOS afloat. Surveying users, instead of simply announcing the need for support, is a non-optimal way to try to garner support. The survey published by BerliOS was not terribly well publicized, and it's likely that many users of BerliOS were unaware of the situation until it was announced that BerliOS is closing. More successful fund-raising efforts in the open source community generally consist of making the community aware of the problem and providing specific targets for fundraising. But BerliOS may also lack enough support, even if FOKUS had been more aggressive about fundraising. BerliOS is home to some popular projects, like avidemux, SuperTux, and Fetchmail. However, it doesn't host a lot of heavy-hitting projects. The final numbers for BerliOS are impressive, but somewhat anemic if compared to larger forges. According to the announcement, BerliOS has more than 50,000 users and 4,710 projects. It sees more than 1.6 million file downloads each month. While an impressive achievement, BerliOS hasn't seen nearly as much traffic as some of the alternatives. SourceForge lists upwards of 313,000 projects and claims nearly 3 million downloads in one day on the banner on its front page. GitHub claims more than two million repositories and more than one million users as of September 21. Naturally, that's not an apples to apples comparison. GitHub is not solely focused on open source, nor is it a free service. GitHub claims Gists (text snippets stored in a Git repository as a Pastebin type service) as repositories. But even discounting some of the numbers as fluff, it's clear there's a lot more activity going on at GitHub or SourceForge than BerliOS. A more apt comparison might be GNU Savannah, which claims more than 53,000 users and 3,384 projects. BerliOS has also had its share of troubles that hint that its support staff were overmatched by the challenge of maintaining an active "forge" site. Last year in January, a compromise dating back to 2005 was discovered — but never adequately investigated. Jörg Schilling, who is employed by FOKUS to work on BerliOS, said he'd seen no sign of damage from the intrusion aside from the defacement of the site. "Therefore, I don't currently don't see a reason to issue a warning." No details about the intrusion were ever supplied. Alternatives and migration toolsWhen BerliOS was founded in 2000, hosting services for free software projects were not quite as abundant as they are today. SourceForge had been up since November of 1999. The GNU Project's Savannah also launched in 2000, initially based on code from SourceForge — though SourceForge's move to proprietary software caused the GNU Project to part ways. Since then, there's been an explosion of open source software hosting repositories. There's the aforementioned GitHub, SourceForge, GNU Savannah, and Gna for non-GNU but Libre Software projects. Developers can also migrate to Gitorious, which is a favorite for projects that are looking for a free software platform that's similar to GitHub. If a project is feeling particularly adventurous, it can host its own instance using Gitorious's software which is licensed under the AGPL. The interoperability problemThe BerliOS folks have provided a migration guide for moving everything from project Web sites to bug trackers, databases, mailing lists, and repositories out of BerliOS. Developers are then left to their own devices to migrate those resources into another hosting facility. This highlights the problem of interoperability between various forges, something that was highlighted by Olivier Berger at the Open World Forum in 2010. Berger writes that while we have the rights to fork and patch source code, forking a project is much more difficult:
Having the possibility to export/backup contents of all the artefacts and
relations that constitute a project in a forge is quite important. Even
more important is the ability to restore these into another set of tools on
another forge.
We're not quite there yet. There is a ForgePlucker project that is supposed to be building tools to migrate from "data jails" in forge systems. However, it doesn't seem to have made enough progress to be widely useful. Berger says the BerliOS shutdown may be "an [opportunity] for improvement of forgeplucker, although I don't have a clue about the maturity of its BerliOS support." Even though BerliOS is providing tools to migrate away from the project, there will be some loss when it goes dark. Of the 4,710 projects on BerliOS, not all of them are actively maintained or will be transitioned. For example, the developer of a project called SimVis4, Jörg Rädler, said "since my activities with SimuVis are already on hold, I decided not to move to another hosting platform." Rädler says he may move to GitHub, but in the meantime, unless someone else decides to move the code to another repository it may simply disappear into the ether when the plug on BerliOS is pulled for good. One semi-serious comment on Reddit is to have a project called "SourceMorgue" to host dead open source projects. The end for BerliOS is a bit sad, but not the end of the world. It will be an inconvenience to many projects, but not insurmountable to those that have an active community. It also highlights the need for projects to have a transition plan, and backups, no matter how stable a service looks today. No doubt many of BerliOS users were shocked to hear that the service was closing shop. Luckily, in this instance, there's plenty of notice before the doors close.
Brief items Quotes of the week
But if there's one thing free software has taught me, it's that you
can not tell people something is a bad idea and have any
expectation they will believe you.
-- Adam Jackson
So you need another heuristic to handle that, and of course
"heuristic" is an ancient african word meaning "maybe bonghits will
make this problem more tractable".
-- Matthew Garrett
In keeping with ducks, you were looking for one, didn't find
anything which quacked or looked like a duck. The fallback protocol
kicks in, you get something with feathers which you found near
water and went "good enough". Now you drop it from 10000m because
you're looking into the efficiency of a duck's flight starting
airborne, and observe your quite dismayed penguin barreling towards
the ground.
-- "Masklinn"
A few seconds later, you find yourself not with additional experimental data but with a small indentation in the earth and a big mess all over it.
However, it's the kind of situation that's part and parcel of duck
typing - you try things and see if they work and the occasional
penguin gets it in the neck. If that's inadequate for a given use
case, you define an ABC and register only things you've already
checked and found to behave correctly (although beware if you
register Bird rather than FlyingBird - the penguins, emus and
friends may still be in trouble at that point)
-- Nick Coghlan
Denemo 0.9.2Version 0.9.2 of the Denemo music notation editor is available. This release features improved score checking capabilities, a new set of fonts, and more.
FVWM 2.6.3 releasedSome users have expressed their dislike for recent releases by the major desktop environment projects; others never liked the earlier releases either. For that select group, the FVWM 2.6.3 release is available. It adds some new style commands, tweaks to the "Move" command, better control over the direction in which windows are resized, and more.
The FSF fixes missing source files in GDBThe Free Software Foundation has sent out two separate notices for GDB 6.0 to 6.6 and versions 6.7 to 7.3 granting permission to distribute those releases despite the fact that they do not contain the source files for "certain CPU descriptions."
Hugin 2011.2.0 releasedHugin is a tool for the creation of panoramic images; it was reviewed here in 2009. The 2011.2.0 release is available; significant changes include a new lens calibration tool and a Python scripting/plugin interface.
OfflineIMAP v6.4.0OfflineIMAP is a tool for the synchronization of mail directories using the IMAP protocol. The 6.4.0 release adds per-account locking, RFC 2595 LOGINDISABLED support, more robust synchronization, non-experimental SQLite backend support, and more.
Newsletters and articles Development newsletters from the last week
Interview with Michael Monty Widenius (ODBMS Industry Watch)The ODBMS Industry Watch site has an interview with Michael "Monty" Widenius. "I want to ensure that the MySQL developers have a good home where they can continue to develop MySQL in an open source manner. This is important as if the MySQL ecosystem would lose the original core developers there would be no way for the product to survive. This is also in hindsight proven to be important as Oracle has lost almost all of the original core developers, fortunately most of them has joined the MariaDB project."
Page editor: Jonathan Corbet |
|||||||||||||