[XML-SIG] Moving PyXML CVS tree to SourceForge?

[Paul Prescod]

"Andrew M. Kuchling" wrote:
> 
> What do people think of the idea of moving the PyXML CVS tree to
> SourceForge?  That makes adding new people with commit privileges is
> easier, and we wouldn't need to bug Greg Stein (who currently hosts
> the CVS tree) when that happens.  Downsides are, we're putting more
> eggs in the SourceForge basket -- but then we're hardly alone in
> that.

I think that there is an interesting philosophical and social issue
here. If we give them our data, shouldn't we be able to get it back in a
manner that is easy to back up and re-locate?

Perhaps people should start demanding that SourceForge make all
information associated with a project available as a big tarfile of
source, web pages, and XML-ized database metadata. That data could be
backed up by anyone who wanted to do so -- even someone setting up a
SourceForge competitor.

I mean doesn't it seem odd to swap closed source for information hostage
on someone else's computer system? Of course SourceForge doesn't stop
you from getting at your source code but there is a lot of content and
metadata around it (mailing lists and so forth) that is also valuable
and I don't think that there is any easy way to back that all up. If
there were, there would be very little danger in putting all of our eggs
in the SourceForge basket.

We would just install SourceForgeSource.tgz and then do an 

import python-xml-everything.tgz 

using some import feature.

Okay, this doesn't solve any immediate problems, but it is worth
thinking about as SourceForge users.

-- 
 Paul Prescod  - ISOGEN Consulting Engineer speaking for himself
At the same moment that the Justice Department and the Federal Trade 
Commission are trying to restrict the negative consequences of 
monopoly, the Commerce Department and the Congress are helping to 
define new intellectual property rights, rights that have a 
significant potential to create new monopolies. This is the policy 
equivalent of arm-wrestling with yourself.
	- http://www.salon.com/tech/feature/2000/04/07/greenspan/index.html