From: "Jon Beniston" <jbeniston@compxs.com>
To: <duane_ellis@franklin.com>, <sjohnson@sakuraindustries.com>
Cc: <insight@sources.redhat.com>
Subject: RE: Insight and Licencing of TCL/TK Code
Date: Mon, 16 May 2005 13:39:00 -0000 [thread overview]
Message-ID: <004c01c55a1c$9708af00$0dbda8c0@Kindrogan> (raw)
In-Reply-To: <200505161330.j4GDUaFL020683@monster.franklin.com>
>
>
> >> Certainly if I were to submit TCL/TK code (which the way
> im going, im about to), i would not be assigning it's
> copyright to Redhat.
>
> See:
>
> http://www.fsf.org/licensing/licenses/why-assign.html
>
Maybe he'd be happy to assign it to the FSF, but not to RedHat.
Cheers,
Jon
next prev parent reply other threads:[~2005-05-16 13:39 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 22:13 Current Status of Insight Paul Schlie
2005-05-16 5:35 ` Steven Johnson
2005-05-16 13:18 ` Insight and Licencing of TCL/TK Code Steven Johnson
2005-05-16 13:31 ` Duane Ellis
2005-05-16 13:39 ` Jon Beniston [this message]
2005-05-16 14:15 ` Steven Johnson
2005-05-16 16:12 ` Christopher Faylor
2005-05-17 19:33 ` Current Status of Insight Fernando Nasser
2005-05-16 16:10 ` Christopher Faylor
2005-05-16 17:18 ` Paul Schlie
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='004c01c55a1c$9708af00$0dbda8c0@Kindrogan' \
--to=jbeniston@compxs.com \
--cc=duane_ellis@franklin.com \
--cc=insight@sources.redhat.com \
--cc=sjohnson@sakuraindustries.com \
/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).