Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: "Rob Quill" <rob.quill@gmail.com>
To: gdb@sourceware.org
Subject: Re: TODO List?
Date: Sun, 14 May 2006 15:06:00 -0000	[thread overview]
Message-ID: <baf6008d0605140341g2823e424j4353cf10e0979696@mail.gmail.com> (raw)
In-Reply-To: <4466DD5C.4030008@adacore.com>

Qutoing the module website:

"Who owns my project intellectual property rights?

You own them. If you are sponsored, you still own them unless you have
explicitly signed a legal document transferring them to your sponsor.

We would strongly discourage you from signing any contract or other
document assigning any rights to your sponsor without seeking advice
from us. Please contact the project organisers in the first instance."

So it should be fine. As I see it, it should be nothing to do with the
University, beyond the fact that I implemented some research that was
done by other people there. Right?

Thanks,
Rob

On 14/05/06, Robert Dewar <dewar@adacore.com> wrote:
> Daniel Jacobowitz wrote:
>
> > [If you intend for your research work to be usable by and incorporated
> > into mainline GDB some day, you may want to work on copyright
> > assignment paperwork.  Since this is university research work, the
> > university would have to submit some paperwork too - this can take ages
> > to sort out, so if you want it done, it's good to start early :-)]
>
> Right, and it is often very hard to convince universities to yield the
> "intellectual property rights" involved. But please try hard. An
> interesting little note here is that the government contract for gnat
> required the copyright to be assigned to the FSF (this contract
> actually had the entire text of the GPL and required release under
> the GPL, a quite interesting provision for such a contract). At the
> end of the period of support, NYU initially balked at assigning the
> copyright, but I pointed out they had signed a contract requiring
> them to do so, and they finally did.
>
> If anyone has trouble negotiating with university authorities in
> this regard, I am happy to try to help out (since I have had quite
> a bit of experience in doing this in a university environment).
>
> Robert Dewar
>


  reply	other threads:[~2006-05-14 10:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-13 14:54 Rob Quill
2006-05-13 17:14 ` Daniel Jacobowitz
2006-05-13 21:57   ` Rob Quill
2006-05-14  5:34     ` Daniel Jacobowitz
2006-05-14 15:02       ` Robert Dewar
2006-05-14 15:06         ` Rob Quill [this message]
2006-05-14 15:10           ` Daniel Jacobowitz
2006-05-14 19:34           ` Robert Dewar
2006-05-14 21:22             ` Daniel Jacobowitz
2006-05-15 18:41     ` PAUL GILLIAM

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=baf6008d0605140341g2823e424j4353cf10e0979696@mail.gmail.com \
    --to=rob.quill@gmail.com \
    --cc=gdb@sourceware.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