From: Adam Spiers <adam@spiers.net>
To: zsh workers mailing list <zsh-workers@sunsite.auc.dk>
Subject: Re: zsh license preventing move to sourceforge.net? (fwd)
Date: Sun, 26 Mar 2000 00:50:31 +0000 [thread overview]
Message-ID: <20000326005031.A18407@thelonious.new.ox.ac.uk> (raw)
----- Forwarded message from Drew Streib <ds@varesearch.com> -----
Date: Wed, 22 Mar 2000 11:05:02 -0800 (PST)
From: Drew Streib <ds@varesearch.com>
To: Adam Spiers <adam@spiers.net>
Cc: dtype@users.sourceforge.net
Subject: Re: zsh license preventing move to SF?
X-Parp-Accepted: sourceforge.net
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. :)
-drew
-------
Drew Streib <d@valinux.com> 408.542.5725
Sr Developer, Community Liason, SourceForge | <dtype@sourceforge.net>
System Administrator, Linux International | <dtype@li.org>
Information Architect, VA Linux Systems | <dtype@valinux.com>
Admirer, Occasional Programmer, Linux.com | <dtype@linux.com>
On Wed, 22 Mar 2000, Adam Spiers wrote:
> Hi there,
>
> I sent this question to dlb but got no response. Maybe
> you're a more suitable victim ;-)
>
> The zsh developers would like to move our codebase to
> sourceforge. However, while zsh is released under a license
> entirely within the spirit of free software (similar to the
> GPL, see below), it's not technically OSI approved. Would
> this be a problem? A swift response would be most
> appreciated!
>
> Adam
>
> #
> # Copyright (c) 1995-1997 Richard Coleman
> # All rights reserved.
> #
> # Permission is hereby granted, without written agreement
> and without
> # license or royalty fees, to use, copy, modify, and
> distribute this
> # software and to distribute modified versions of this
> software for any
> # purpose, provided that the above copyright notice and the
> following
> # two paragraphs appear in all copies of this software.
> #
> # In no event shall Richard Coleman or the Zsh Development
> Group be liable
> # to any party for direct, indirect, special, incidental, or
> consequential
> # damages arising out of the use of this software and its
> documentation,
> # even if Richard Coleman and the Zsh Development Group have
> been advised of
> # the possibility of such damage.
> #
> # Richard Coleman and the Zsh Development Group specifically
> disclaim any
> # warranties, including, but not limited to, the implied
> warranties of
> # merchantability and fitness for a particular purpose. The
> software
> # provided hereunder is on an "as is" basis, and Richard
> Coleman and the
> # Zsh Development Group have no obligation to provide
> maintenance,
> # support, updates, enhancements, or modifications.
> #
>
>
----- End forwarded message -----
next reply other threads:[~2000-03-26 0:50 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-26 0:50 Adam Spiers [this message]
2000-03-26 19:06 ` Clint Adams
2000-03-26 22:19 ` Peter Stephenson
2000-03-28 0:28 ` move to sourceforge.net in progress Adam Spiers
2000-03-27 21:24 ` 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=20000326005031.A18407@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).