[Smaug] Is SourceForge the right place for SMAUG ?

Rick Moen rick@linuxmafia.com
Mon Jan 28 10:29:24 2002


Out of curiosity, I looked up Patrick McGovern's comments.  They were
first posted to Advogato in October, and then (as mentioned) to the
related discussion on Slashdot:

http://advogato.org/article/376.html#9

One interesting portion was this:

> Eight months ago we did have a[n] XML API that allowed project admins
> to download bug report data. The API broke earlier in the year when we
> enhanced the SF.NET code (version 2.5) to include the tracker (a tool
> that unifies all 'ticket-related' systems). Until recently, we didn't
> receive a lot of interest from the community to re-introduce the
> feature... so we have been focusing on other aspects of the site. We
> are now re-examining the issue. In the mean time, there are
> third-party programs which will collect the content directly from the
> site and extract that data. 

This is in apparent attempt to respond to Loïc Dachary's rather vague
charges here:

> The move to non-free software was the culmination of a series of steps
> designed to lock users in. There never was a way to fully extract
> projects from SourceForge, but efforts were made in this
> direction--then this year they were removed. At present the only
> things you can get are the CVS tree and tracker data
> /export/sf_tracker_export.php.

As noted, Duchary's claim is, from an objective analysis, overblown at
the very minimum:  100% of a SourceForge.net project's public contents
can be sucked down at any time by anyone, using cvs and wget.  (The
contents marked private, if any, are available to all project admins
using the same tools.)  But how immediately useful that would be depends
on what you intend to do with it.

A SourceForge.net project may contain some combination of Mailman mailing
lists, Web pages, a CVS repository, tasks, Tracker items (a simple Web-based
comment system for bug reports and such, news flashes, a patch
repository, a document manager, and file releases.  (Almost all of these
are disabled in project Smaug-Web, because we don't use them.)

Dachary's beef on the cited matter, to the extent he has one, and
cutting through all the rhetoric, seems to be "Well, there's no simple
tool for exporting all data from all of those features, so that it could
be easily re-imported somewhere else."

Well, duh.

If you assemble a complex and diverse project-hosting system from
Mailman, exim, cvs, PHP, Apache, a back-end database, and so on, storing
away about nine different kinds of project data, giving people a simple
export all of that such that it can be easily re-exported elsewhere is 
no joke.  And even then, people will probably bitch that they don't like
the export format, or it doesn't meet their needs.  According to McGovern,
SourceForge nonetheless had such a mechanism in 2001, but it broke when
the horrid bug-tracking mechanism got replaced by Tracker, and the
broken script was removed rather than fixed because nobody seemed to 
be using it.

Dachary cites this as exemplifying "steps designed to lock users in".
Reasonable?  You decide.


Noted without comment:  http://savannah.gnu.org/ seems to lack any "way
to fully extract projects" of the sort that Savannah head & founder
Dachary complains about being lacking at SourceForge.net.

-- 
Cheers,
Rick Moen                     Emacs is a decent operating system,
rick@linuxmafia.com           but it still lacks a good text editor.
(speaking for himself, alone)