public inbox for insight@sourceware.org
 help / color / mirror / Atom feed
From: Christopher Faylor <cgf-no-personal-reply-please@cygwin.com>
To: "'Th.R.Klein'" <Th.R.Klein@web.de>,
	insight@sources.redhat.com, Jon Beniston <jbeniston@compxs.com>
Subject: Re: [RFC] syntax highlighting
Date: Thu, 25 Aug 2005 18:34:00 -0000	[thread overview]
Message-ID: <20050825183411.GA32066@trixie.casa.cgf.cx> (raw)
In-Reply-To: <20050825180548.A35334A8054@cgf.cx>

On Thu, Aug 25, 2005 at 07:05:20PM +0100, Jon Beniston wrote:
>On Thu, Aug 25, 2005 at 07:56:33PM +0200, Th.R.Klein wrote:
>>Sorry but I do not understand where I've done something that violates
>>the existing copyright.
>
>You haven't.
>
>>As far as I'm interpreting this, I'm allowed to modify the source e.g.
>>by adding the syntax highlighting stuff to it.
>
>You are.  If you want to take all the source and start your own fork
>that's fine.
>
>>Red Hat itself might have a set of rules which kind of modification
>>they accept and which they will reject.
>
>The only reason I can see why you need to assign copyright is so that
>Red Hat can license Insight under a different (non-free) license.  But
>maybe I'm being a tad cynical.

Yes, just a tad.

The FSF requires similar license transferrals for gdb and no one ever
accused them of trying to provide things under a non-free license.

In the Insight case, I believe that Red Hat wants to make sure that all
of the code ownership is clear so that there will be no claims where a
company insists that they own some snippet of code added by an employee.
I believe that this is the same reason that the FSF requires similar
transfer of ownership for major changes to gdb, gcc, binutils, etc.

Additionally, since insight intertwines itself with gdb, I don't believe
you could sell it as non-free anyway since gdb's GPL would trump any
other license.

cgf

  parent reply	other threads:[~2005-08-25 18:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-03 21:12 Th.R.Klein
2005-08-03 21:49 ` Steven Johnson
2005-08-04  6:13 ` Steven Johnson
2005-08-04 10:25   ` Dave Korn
2005-08-23 20:31 ` Keith Seitz
2005-08-23 22:12   ` Steven Johnson
2005-08-24  3:51     ` Christopher Faylor
2005-08-25 17:49   ` Th.R.Klein
2005-08-25 18:05     ` Jon Beniston
     [not found]     ` <20050825180548.A35334A8054@cgf.cx>
2005-08-25 18:34       ` Christopher Faylor [this message]
2005-08-25 19:06         ` Jon Beniston
     [not found]         ` <20050825190632.D45444A8059@cgf.cx>
2005-08-25 19:13           ` Christopher Faylor
2005-08-25 19:59             ` Jon Beniston
     [not found]             ` <20050825195933.041274A805F@cgf.cx>
2005-08-25 20:54               ` Christopher Faylor
2005-08-04 17:35 Th.R.Klein
     [not found] <200508251805.j7PI5q4A015633@mx1.redhat.com>
2005-08-25 18:33 ` Keith Seitz
2005-08-25 21:23   ` Steven Johnson
2005-08-26 10:02     ` Dave Korn
2005-08-26 20:22       ` Christopher Faylor

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=20050825183411.GA32066@trixie.casa.cgf.cx \
    --to=cgf-no-personal-reply-please@cygwin.com \
    --cc=Th.R.Klein@web.de \
    --cc=insight@sources.redhat.com \
    --cc=jbeniston@compxs.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).