Copyright assignment

View: New views
5 Messages — Rating Filter:   Alert me  

Copyright assignment

by David Stubbs-5 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,

I'd like to contribute back some work I've done. My employer has already
provided a copyright disclaimer to the FSF.

Back in June I received a form that I filled in and sent to
fsf-records@.... I never received a response from this. I was a bit
lax in chasing it up, but eventually I discovered that a colleague had
been provided with a subtly different form and instructed that it should
be sent to assign@.... I've now also sent this form to the new
address.

I sent the latter form on October 5th, and haven't yet received a
response. Please can someone look into this and check if it's been
received, or if there are any problems with it?

Many thanks,
David Stubbs.


Re: Copyright assignment

by Nick Clifton :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi David,

> I sent the latter form on October 5th, and haven't yet received a
> response. Please can someone look into this and check if it's been
> received, or if there are any problems with it?

You can send an email directly to fsf-records@... asking about this.

According to the latest version of the copyright list your personal
assignment is not it, but the corporate one for Icera is there:

   BINUTILS Icera Semiconductor Inc. 2008-10-15
   Assigns Past and Future Changes
   Steven Chandler (Vice President Legal and Intellectual Property)
   chandler@...

So if the work you wish to contribute was created as part of your job at
Icera then you are free to submit it now.

Cheers
   Nick


RE: Copyright assignment

by David Stubbs-5 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi Nick,

Thanks for the response. I'll email them directly.

Is there a guide somewhere on the steps to go through when submitting
changes? I've had a quick search and not really found anything. We're
still using 2.19, so I guess the first step is to update to 2.20...

Thanks again,
Dave.

> -----Original Message-----
> From: Nick Clifton [mailto:nickc@...]
> Sent: 06 November 2009 12:59
> To: David Stubbs
> Cc: binutils@...
> Subject: Re: Copyright assignment
>
> Hi David,
>
> > I sent the latter form on October 5th, and haven't yet received
> a
> > response. Please can someone look into this and check if it's
> been
> > received, or if there are any problems with it?
>
> You can send an email directly to fsf-records@... asking
> about this.
>
> According to the latest version of the copyright list your
> personal
> assignment is not it, but the corporate one for Icera is there:
>
>    BINUTILS Icera Semiconductor Inc. 2008-10-15
>    Assigns Past and Future Changes
>    Steven Chandler (Vice President Legal and Intellectual
> Property)
>    chandler@...
>
> So if the work you wish to contribute was created as part of your
> job at
> Icera then you are free to submit it now.
>
> Cheers
>    Nick


Re: Copyright assignment

by Ian Lance Taylor-3 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

"David Stubbs" <stubbs@...> writes:

> Is there a guide somewhere on the steps to go through when submitting
> changes? I've had a quick search and not really found anything. We're
> still using 2.19, so I guess the first step is to update to 2.20...

I don't think there is a guide, but you should really submit patches
against the CVS head, not against any release.  The
http://sourceware.org/binutils/ page tells you how to check out CVS.

Thanks for your interest.

Ian

Re: Copyright assignment

by Nick Clifton :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi David,

> Is there a guide somewhere on the steps to go through when submitting
> changes?

Actually yes, there is:

http://et.redhat.com/~rjones/how-to-supply-code-to-open-source-projects/

Also, please make sure that your code follows the GNU Coding Standard:

http://www.gnu.org/prep/standards/

> I've had a quick search and not really found anything. We're
> still using 2.19, so I guess the first step is to update to 2.20...

Or even better the current head of the mainline development sources.

Cheers
   Nick