zsh-workers
 help / color / mirror / code / Atom feed
From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: move to sourceforge.net in progress
Date: Tue, 28 Mar 2000 01:28:21 +0100	[thread overview]
Message-ID: <20000328012821.A32467@thelonious.new.ox.ac.uk> (raw)
In-Reply-To: <E12ZgvH-0005Cr-00.2000-03-27-22-19-43@mail1.svr.pol.co.uk>; from pws@pwstephenson.fsnet.co.uk on Sun, Mar 26, 2000 at 11:19:42PM +0100

Peter Stephenson (pws@pwstephenson.fsnet.co.uk) wrote:
> Adam Spiers wrote:
> > ----- Forwarded message from Drew Streib <ds@varesearch.com> -----
> > 
> > I've looked at this and it doesn't appear to conflict with any part of the
> > OSI definition. I would approve the license on this. :)
> 
> Oh, hell.  That means we've run out of excuses.

Mission accomplished ;->

> Does someone else, such as Adam, want to set this up?

'Tis done.  I'll let you know when the SourceForge admins have
approved the request (assuming they do).  It should be within 24 hours
or so.  In the meantime, it would be good if everyone who hasn't
already got one creates themselves a SourceForge account.  Don't
worry; this is a remarkably painless operation and takes hardly any
time.  Just go to

  https://sourceforge.net/account/register.php

I presume everyone has access to an SSL-enabled browser?

Peter, once you've got an account I'll transfer the relevant project
administrator privileges to you.  Bart, I presume you won't want to
bother making a CVS tree for 3.0.x available, but if you do, let me
know and I'll give you admin privileges too.  Of course, once we have
the repository up and running smoothly, there's no technical
limitation preventing us from having several developers with commit
access to the development tree, but I'll assume that we want to carry
on with Peter as the sole "patch pumpking" unless I hear otherwise.

By the way, the home page is at 

  http://sourceforge.net/ 

if you want to have a look round, although I'm sure you already
figured that out.

> Clint's right that the licence details in the source code needing
> tidying up.

Yep, we definitely need to move all the individual copyrights into
LICENSE or Etc/LICENSE or something.  That's going to be a fun job for
someone :-/

Adam


  reply	other threads:[~2000-03-28  0:28 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-03-26  0:50 zsh license preventing move to sourceforge.net? (fwd) Adam Spiers
2000-03-26 19:06 ` Clint Adams
2000-03-26 22:19 ` Peter Stephenson
2000-03-28  0:28   ` Adam Spiers [this message]
2000-03-27 21:24     ` move to sourceforge.net in progress Peter Stephenson
2000-04-01 11:11       ` sourceforge.net CVS tree ready for use Adam Spiers
2000-04-01 20:51         ` Peter Stephenson
2000-04-02  0:44           ` Bart Schaefer
2000-04-02  0:45           ` Adam Spiers
2000-04-02  4:37             ` Bart Schaefer
2000-04-02  6:02               ` Geoff Wing
2000-04-02 22:02                 ` Adam Spiers
2000-04-02 23:16                   ` Bart Schaefer
2000-04-02 10:10         ` Andrej Borsenkow
2000-04-02 10:35           ` Geoff Wing
2000-04-02 23:29             ` Bart Schaefer
2000-04-03  8:50               ` Geoff Wing
2000-04-03 10:30         ` Oliver Kiddle
2000-04-03 13:06           ` Adam Spiers
2000-03-28  1:46     ` move to sourceforge.net in progress Bart Schaefer
2000-03-28 11:45     ` Andrej Borsenkow
2000-03-28 16:51       ` Bart Schaefer

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=20000328012821.A32467@thelonious.new.ox.ac.uk \
    --to=adam@spiers.net \
    --cc=zsh-workers@sunsite.auc.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).