From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: schaefer@nbn.com
Cc: gjb@moa.cs.duke.edu, zsh-workers@math.gatech.edu
Subject: Re: Distribution terms
Date: Tue, 27 Aug 1996 21:25:28 +0200 (MET DST) [thread overview]
Message-ID: <199608271925.VAA08321@bolyai.cs.elte.hu> (raw)
In-Reply-To: <960827082850.ZM7886@candle.brasslantern.com> from Bart Schaefer at "Aug 27, 96 08:28:50 am"
> } Do you, Zoltan, or does anyone else know where I can find explicit
> } distribution terms for Zsh. I've looked the usual places, and not found
> } any information. I'm asking permission of the FSF to use the bit of
> } color_ls in zsh, but we need to let them know the distribution policy.
>
> Before you go through that hassle, perhaps we should have (a) a statement
> from Zoltan on whether he thinks the patches are worth including in the
> first place, and (b) a discussion on zsh-workers about that statement.
As Richard wrote the copyright policy can be found in each C source file.
I'll extract it to a separate COPYING file and add that that copiright
notice holds for all included file except where there is a different
copyright note in the file (i.e. COPYING will say that zsh is copyrighted
by P.F. but Makefiles, configure.in etc. are copyrighted by Richard. I do
not know who copyrights the texinfo documentation. It comes mostly from
the manual so PF maybe. I do not know anything about copyright law. If
one expert could write a good COPYING file based on the comments in C files
and the general ideas above I would happily include it in the distribution.
And about colorizes lists: first there will be a zsh-3.0.1 release. It
will definitely not be added before that. And in zsh-3.1 we have to find
out a portable way to use dynamically loadable modules. After that anyone
can write a plug-in for zsh and can implement any feature he wants. But
such features should not blow up zsh. It would be a good idea to better
modularise the existing zsh code, make a few things optional (fo rexample
zle and completion). I do not know how much is the ovehead caused by a big
executable. When zsh is used as a scipt interpreter on a demand-paged
system only the parts necessary run a script will be loaded so it may not
give any real improvement.
Zoltan
next prev parent reply other threads:[~1996-08-27 19:32 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-15 18:17 zsh-3.0.0 released Zoltan Hidvegi
1996-08-15 18:57 ` zsh-3.0.0 installed in the US Tom Kaczmarski
1996-08-16 4:18 ` Andrew Cosgriff
1996-08-16 11:55 ` Tom Kaczmarski
1996-08-20 1:32 ` Andrew Cosgriff
1996-08-20 12:55 ` Tom Kaczmarski
1996-08-15 19:56 ` zsh-3.0.0 released John Harres
1996-08-15 20:14 ` Richard Coleman
1996-08-15 20:27 ` John Harres
1996-08-15 21:22 ` Richard Coleman
1996-08-15 21:35 ` Wayne Davison
1996-08-27 14:25 ` Distribution terms Greg J. Badros
1996-08-27 15:28 ` Bart Schaefer
1996-08-27 15:37 ` Bruce Stephens
1996-08-27 17:04 ` Greg J. Badros
1996-08-27 18:58 ` Bart Schaefer
1996-08-27 19:04 ` Zefram
1996-08-27 19:25 ` Zoltan Hidvegi [this message]
1996-08-27 19:53 ` future of zsh Richard Coleman
1996-08-27 16:32 ` zsh: future and loadable modules Chip Salzenberg
1996-08-28 9:03 ` Bruce Stephens
1996-08-27 20:23 ` future of zsh Zoltan Hidvegi
1996-08-27 20:20 ` Distribution terms Zefram
1996-08-27 20:32 ` Zoltan Hidvegi
1996-08-27 16:37 ` Richard Coleman
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=199608271925.VAA08321@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=gjb@moa.cs.duke.edu \
--cc=schaefer@nbn.com \
--cc=zsh-workers@math.gatech.edu \
/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).