Gnus development mailing list
 help / color / mirror / Atom feed
From: Hrvoje Niksic <hniksic@srce.hr>
Subject: Re: timezone.el patterns in emacs 19.34
Date: 04 May 1997 21:55:23 +0200	[thread overview]
Message-ID: <kigd8r7j9lg.fsf@jagor.srce.hr> (raw)
In-Reply-To: Ken Raeburn's message of 03 May 1997 23:03:59 -0400

Ken Raeburn <raeburn@cygnus.com> writes:

> as the lisp or yacc versions?  Maybe.  Would it be worth spending the
> time?  I doubt it, at least for right now.  If you want to do it
> anyways, go for it....

I will not do it, unless a good speedup in Gnus (and possibly other
packages, but my focus is on Gnus, which uses the routine heavily) is
the result.  I don't consider it a particular fun thing to write, but
if it's a good point for speed optimization -- why not?

> > > > Then, there are copyright problems with it.
> > > No, there aren't.
> > Yes, there are.  The public domain code is not to be introduced in
> > important parts of Emacs, as it is compromisable.
> 
> "Compromisable?"  Why, because the FSF might not be able to get
> paperwork saying it really is PD?  They could try, and I suspect such
> paperwork would be enough.

No.  By definition, PD software is the software that is not
copyrighted -- it does not have a legal owner (which should be the
person or persons signing the papers).  From www.fsf.org:

Public domain software 
    Public domain software is software that is not copyrighted. It is
    a special case of non-copylefted free software, which means that
    some copies or modified versions may not be free at all.
    Sometimes people use the term ``public domain'' in a loose fashion
    to mean ``free'' or ``available gratis.'' However, ``public
    domain'' is a legal term and means, precisely, ``not
    copyrighted''.  For clarity, we recommend using ``public domain''
    for that meaning only, and using other terms to convey the other
    meanings.

Stallman considers PD programs unsafe to use in GNU.

    * Public domain.

    If you put the program in the public domain, we prefer to have a
    signed piece of paper--a disclaimer of rights--from you confirming
    this.  If the program is not very important, we can do without
    one; the worst that could happen is that we might some day be
    forced to stop using it.

    The law says that anyone can copyright a modified version of the
    public domain work.  (This doesn't restrict the original, which
    remains in the public domain; only the changes are copyrighted.)
    If we make extensive changes, we will probably do this and add our
    usual copyleft.  If we make small changes, we will leave the
    version we distribute in the public domain.

> (Actually, I'd be surprised if there weren't some other GNU programs
> using a date parser already.  For example, GNU date in sh-utils.)

Yes, there are pieces of public-domain software in GNU, but they are
either dispensable, or there is not yet a free replacement (as in the
case of `getdate.y').

-- 
Hrvoje Niksic <hniksic@srce.hr> | Student at FER Zagreb, Croatia
--------------------------------+--------------------------------
Oh lord won't you buy me a color TV...


  reply	other threads:[~1997-05-04 19:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <199705020844.EAA06520@kr-laptop.cygnus.com>
1997-05-03  1:14 ` Hrvoje Niksic
1997-05-03  3:07   ` Ken Raeburn
1997-05-03  4:04     ` Hrvoje Niksic
1997-05-03 23:44       ` Ken Raeburn
1997-05-04  0:41         ` Hrvoje Niksic
1997-05-04  3:03           ` Ken Raeburn
1997-05-04 19:55             ` Hrvoje Niksic [this message]
1997-05-04 20:49               ` Johan Danielsson
1997-05-04 20:55                 ` Hrvoje Niksic
1997-05-04 22:22                   ` Public domain (was: timezone.el patterns in emacs 19.34) Johan Danielsson
1997-05-05  6:52                     ` Lars Magne Ingebrigtsen
1997-05-04 22:55                   ` timezone.el patterns in emacs 19.34 Stainless Steel Rat
1997-05-08 12:37         ` Lars Magne Ingebrigtsen
1997-05-03 22:41   ` Ken Raeburn
1997-05-02 23:18 Ken Raeburn

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=kigd8r7j9lg.fsf@jagor.srce.hr \
    --to=hniksic@srce.hr \
    /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.
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).