From: John Gilmore <gnu@toad.com>
To: Daniel Jacobowitz <daniel.jacobowitz@gmail.com>
Cc: Stan Shebs <stanshebs@earthlink.net>, gdb@sourceware.org
Subject: Re: Licencing policy for gdb Python plugins
Date: Wed, 11 Jul 2012 17:43:00 -0000 [thread overview]
Message-ID: <201207111743.q6BHhRmw020236@new.toad.com> (raw)
In-Reply-To: <CAN9gPaHgt_gbrxysKnaJNDLW9j3=APtz2Zw2UeYmCEskY3=vGQ@mail.gmail.com>
Since we aren't sure, howabout publishing something that says, "If
your plugin is public domain or licensed under GPLv3+, it's compatible
with GDB's licensing. If you want to do something different, come
talk with us and we'll work something out." That way we can make a
decision in a context that's informed by an actual plugin - while
enabling anybody who doesn't mind PD or GPL.
John
next prev parent reply other threads:[~2012-07-11 17:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-10 13:33 Joachim Protze
2012-07-10 14:19 ` Stan Shebs
2012-07-11 12:18 ` Daniel Jacobowitz
2012-07-11 17:43 ` John Gilmore [this message]
2012-07-11 21:34 ` Frank Ch. Eigler
2012-07-11 21:52 ` Doug Evans
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=201207111743.q6BHhRmw020236@new.toad.com \
--to=gnu@toad.com \
--cc=daniel.jacobowitz@gmail.com \
--cc=gdb@sourceware.org \
--cc=stanshebs@earthlink.net \
/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).