Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: new SourceForge terms
- X-seq: zsh-workers 16652
- From: Clint Adams <clint@xxxxxxx>
- To: Christopher Faylor <cgf@xxxxxxxxxx>
- Subject: Re: new SourceForge terms
- Date: Thu, 14 Feb 2002 20:03:04 -0500
- Cc: zsh-workers@xxxxxxxxxx
- In-reply-to: <20020215002030.GK6876@xxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- References: <20116.1013680497@xxxxxxx> <20020214110720.1405.qmail@xxxxxxxxxxxxxxxxxxxxxx> <a4gbcn$qb1$1@xxxxxxxxxxxxxxxxxxxxx> <1020214165115.ZM21918@xxxxxxxxxxxxxxxxxxxxxxx> <20020214173319.GA30891@xxxxxxxx> <20020214194259.GA3689@xxxxxxxxxx> <20020214220743.GA5776@xxxxxxxx> <20020214220913.GI6876@xxxxxxxxxx> <20020214222120.GA6035@xxxxxxxx> <20020215002030.GK6876@xxxxxxxxxx>
> Unfortunately, right now the addition of new keys isn't automated. It's
> been on my to-do for a while to automate things but, for now, it all
> goes through me, or one of the other "volunter sysadmins".
>
> I should mention that all of the maintenance of the site is done by
> volunteers. There is no professional staff other than that.
I'd have reservations about moving to such a system. With SF,
evil as it is, I can add and remove SSH1 and SSH2 keys by merely
suffering through a web GUI and then waiting for the next hit of the
cronjob. More importantly, I can use my password in lieu of any such
key, which is important since I only use keys on 2 of the 6 machines
from which I do zsh commits.
A quick look at Savannah reveals that the only support SSH1 keys, but
the cronjob is hourly.
cvs.debian.org would also be problematic in terms of lack of automation
for non-developers, and I think the same is true for any other alternate
I can imagine.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author