From: Jonathan Larmour <jifl@eCosCentric.com>
To: Subs <subs@divilment.com>
Cc: ecos-maintainers@ecos.sourceware.org
Subject: Re: Copyright assignment forms
Date: Sun, 21 Jan 2007 13:56:00 -0000 [thread overview]
Message-ID: <45B370F1.3080405@eCosCentric.com> (raw)
In-Reply-To: <20070121120636.GD21400@donkey.ma.tech.ascom.ch>
Andrew Lunn wrote:
> On Sun, Jan 21, 2007 at 11:58:20PM +1300, Subs wrote:
>
>>Hi there,
>>
>>I am running a free software project and would like to provide forms for
>>copyright assignment so that contributors assign the code for me. I have come
>>across your forms at the following link
>>
>>http://ecos.sourceware.org/assign.html
>>
>>Could I use these as a basis for my own forms as I can't find any stock
>>standard open source copyright assignment forms?
>
>
> The FSF has something similar. You might want to ask them. If you in
> future intend to become a GNU project it might be worth going that way
> from day 1.
>
> Is the eCos copyright assignment copyrighted? I don't see a copyright
> clause with in. [snake swallows its tail and creates Benzene] Jifl, a
> question for you i think.
The original text was written while we were at Cygnus/Red Hat, and co
copyright in the assignment text is probably held by them. The FSF
assignment text is probably safer.
You can look at:
http://ftp.xemacs.org/old-beta/FSF/assign.changes
or
http://ftp.xemacs.org/old-beta/FSF/assign.future
Depending on whether you wish the assignment to be a one-off, or to assign
all future changes as well.
Jifl
--
eCosCentric http://www.eCosCentric.com/ The eCos and RedBoot experts
Visit us at Embedded World 2007, Nürnberg, Germany, 13-15 Feb, Stand 11-336
Company legal info, address and number: http://www.ecoscentric.com/legal
------["The best things in life aren't things."]------ Opinions==mine
prev parent reply other threads:[~2007-01-21 13:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 10:54 Subs
2007-01-21 12:06 ` Andrew Lunn
2007-01-21 13:56 ` Jonathan Larmour [this message]
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=45B370F1.3080405@eCosCentric.com \
--to=jifl@ecoscentric.com \
--cc=ecos-maintainers@ecos.sourceware.org \
--cc=subs@divilment.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).