From: Oliver Kiddle <okiddle@yahoo.co.uk>
To: Adam Spiers <adam@spiers.net>, zsh-workers@sunsite.dk
Subject: Re: issues with sourceforge
Date: Mon, 12 Nov 2001 17:59:20 +0000 [thread overview]
Message-ID: <3BF00DF8.797F8AF1@yahoo.co.uk> (raw)
In-Reply-To: <20011112170508.A23272@thelonious.new.ox.ac.uk>
Adam Spiers wrote:
>
> http://fsfeurope.org/news/article2001-10-20-01.en.html
>
> I haven't looked at this closely enough to decide whether it should
> affect us, but I thought I should bring it up just in case.
I don't think it is anything to worry about. The article is probably
just the FSF exerting pressure on VA, fearing this might be the thin
edge of the wedge.
The only risk to us is with the tracker which we don't use extensively
anyway - a few bugs and 3.0.8 patches. If the services provided by
Sourceforge were to rely on commericial software, we could not move to
an alternative like Savannah because the alternative would need to use
the commercial software. We'd in theory be locked in to Sourceforge
unless we converted our data to a free alternative. CVS is not at risk
and that is our main use of Sourceforge.
The only thing we should do is ensure we have a backup of everything we
have on Sourceforge (or anywhere else for that matter). We can download
a tarball of the CVS repository. The best way to backup the 3.0.8
patches might actually be to release a 3.0.9/3.0.8a. The Solaris 9
preview still comes with 3.0.8 and there might be places where people
are still using 3.0 intentionally but want bug fixes.
Oliver
_____________________________________________________________________
This message has been checked for all known viruses by the
MessageLabs Virus Scanning Service. For further information visit
http://www.messagelabs.com/stats.asp
prev parent reply other threads:[~2001-11-12 17:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-12 17:05 Adam Spiers
2001-11-12 17:59 ` Oliver Kiddle [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3BF00DF8.797F8AF1@yahoo.co.uk \
--to=okiddle@yahoo.co.uk \
--cc=adam@spiers.net \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).