m4-discuss
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: M4 1.5 development


From: Nick Etson
Subject: RE: M4 1.5 development
Date: Tue, 6 Apr 2004 11:56:26 -0400

Cool, well give me the info and I'll get the paperwork going through
immediately.

Nick Etson
UNIX Systems Administrator
Swales Aerospace
(301) 902-4946 (Voice)
address@hidden

-----Original Message-----
From: Gary V. Vaughan [mailto:address@hidden
Sent: Tuesday, April 06, 2004 11:37 AM
To: Nick Etson
Cc: address@hidden; M4
Subject: Re: M4 1.5 development

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Nick,

Nick Etson wrote:
| What do you mean by copyright assignment?  I don't want to do any
non-GPL'ed
| work so I'd be more than happy to sign anything to that effect.  I do a
| limited amount of development here at work, most of which is specific to
our
| infrastructure and engineering services and isn't worth opensourcing even
if
| I was allowed to do so.

Just that.  The FSF asks us to collect copyright assignments for
contributions
to GNU projects.  The idea is that when you contribute code to (say) GNU m4,
you assign the copyright for that code to the FSF to better allow them to
defend the program code in court if someone violates the license (among
other
things).

Would you be willing to sign paperwork that says that you assign the
copyright, for any patches you contribute to M4, to the FSF?

The employer disclaimer is because many (most) programmers are employed with
a
contract that gives their employer copyright of any code they write,
including
code you write in your own time on your own hardware that has no business
value to your employer.  I believe it is not unprecedented for employers to
claim that they have intellectual property rights over past free software
contributions made by former employees!!!  To protect themselves and you
from
that, the FSF also asks us to collect copyright disclaimers from
programmers'
employers.  The paperwork has good advice on how to approach this, but
basically it asks your employer to promise not to say that your
contributions
actually belong to them at any point in the future.  I simply had them sign
a
form that said "We disclaim copyright of all GPL code written by Gary V.
Vaughan until further notice".  If your job is not substantially programming
then there will be no need for you to get this signed.

If you are happy to go ahead, I'll look up the address of the copyright
clerk,
and you can mail him for the paperwork.

Sorry this is a little onerous, but it is unfortunately necessary to keep
our
software free in a world populated by the likes of SCO and Microsoft :-(

Thanks again for your interest in M4 :-)

Cheers,
        Gary.
- --
Gary V. Vaughan      ())_.  address@hidden,gnu.org}
Research Scientist   ( '/   http://tkd.kicks-ass.net
GNU Hacker           / )=   http://www.gnu.org/software/libtool
Technical Author   `(_~)_   http://sources.redhat.com/autobook
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFAcs6uFRMICSmD1gYRAoK/AJ47Y+cbMq72sGV7jtadN035R9IaAQCfWep3
Kluzj/0usjPHDAo+v++1ZQs=
=T3WZ
-----END PGP SIGNATURE-----






reply via email to

[Prev in Thread] Current Thread [Next in Thread]