unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: guile-devel@gnu.org
Subject: Re: Quasisyntax broken?
Date: Mon, 27 Jul 2009 00:06:04 +0200	[thread overview]
Message-ID: <878wibgkvn.fsf@gnu.org> (raw)
In-Reply-To: m3hbwztnjj.fsf@pobox.com

Hi,

Andy Wingo <wingo@pobox.com> writes:

> Hm. I have no idea what this means for Guile. It seems we need either a
> disclaimer or an assignment.

My understanding is that it's OK if we have bits of code not copyright
FSF, if there's a good reason to do so (and there is one, here).

After some reading, I see this (info "(maintain) Copying from Other
Packages"):

     When you are copying code for which we do not already have papers,
  you need to get papers for it.  It may be difficult to get the papers
  if the code was not written as a contribution to your package, but
  that doesn't mean it is ok to do without them.  If you cannot get
  papers for the code, you can only use it as an external library (*note
  External Libraries::).

But later on (info "(maintain) External Libraries") basically says that
it's easy to incorporate free third-party code like this.

At any rate we already have precedents for this (`psyntax' and `match')
so I'm not worried.  Maybe we can ask Karl Berry and RMS just to make
sure.

(Note that the so-called "GNU" Bazaar doesn't have a single line
copyright FSF.)

Thanks,
Ludo'.





  reply	other threads:[~2009-07-26 22:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-03  0:04 Quasisyntax broken? Andreas Rottmann
2009-07-23 21:31 ` Andy Wingo
2009-07-23 22:35   ` Andreas Rottmann
2009-07-23 22:48     ` Andy Wingo
2009-07-25 21:30       ` Andreas Rottmann
2009-07-26 13:15         ` Ludovic Courtès
2009-07-26 16:30         ` Andy Wingo
2009-07-26 22:06           ` Ludovic Courtès [this message]
2009-07-27 22:51             ` Neil Jerram
2009-08-20 21:19         ` Ludovic Courtès

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=878wibgkvn.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guile-devel@gnu.org \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).