Re: TODO List?

[Robert Dewar <dewar@adacore.com>]

Rob Quill wrote:
> Qutoing the module website:
> 
> "Who owns my project intellectual property rights?

How about we just say "copyrights and patents", rather than use the
dubious term IPR, even if everyone else does in the world? This
phrase tends to agree that these are property (which is controversial)
and that they are rights (which is controlversial). Just saying
copyrights and patents is neutral, and simply refers to actual
statutory provisions.
> 
> You own them. If you are sponsored, you still own them unless you have
> explicitly signed a legal document transferring them to your sponsor.

That's not quite right, if you are a full time employee, no legal
document is needed for your employer to own them. Also if you sign
a consultant agreement with the magic words "work for hire", the
same reasoning applies (this is in the USA, laws differ from
one country to another). Also in some cases, universities claim
some interest in any work done by students using their facilities.
In the case of the university of Texas (at least this used to be
true, don't know if it still is in this age of universities trying
to make money from copyrights and patents), all software developed
using department facilities is by default released under the GPL.
> 
> 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."

Well that's certainly good advice, but it may not be quite sufficient.
> 
> 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?

Well these things are very tricky, and as I mention above, universities
these days are trying to maximize the dollar value of their copyright
and patent portfolios.

So check with anyone likely to assert a right of ownership.

I suppose this is off topic, but on the other hand, one of the vital
issues in gcc and gdb development is to try to make sure that the
GNU project can take advantage of the work that people contribute.