From: David Kastrup <dak@gnu.org>
Cc: Drew Adams <drew.adams@oracle.com>, Emacs-Devel <emacs-devel@gnu.org>
Subject: Re: tutorial or guidebook text for some complex topics
Date: Tue, 24 Oct 2006 00:08:37 +0200 [thread overview]
Message-ID: <85mz7mfzx6.fsf@lola.goethe.zz> (raw)
In-Reply-To: <17725.14365.503609.516302@kahikatea.snap.net.nz> (Nick Roberts's message of "Tue\, 24 Oct 2006 10\:46\:05 +1300")
Nick Roberts <nickrob@snap.net.nz> writes:
> > GNU won't use my text, because my employer won't sign papers.
>
> But presumably if you contribute in your own time from a separate
> e-mail address they wouldn't need to sign papers.
Your employee contracts might preclude something like "your own time".
If you think of just not telling the FSF: the assignment contract
holds you accountable for making wrong statements. You'd have to pay
the damage.
So better make sure that everything is as it should be.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
next prev parent reply other threads:[~2006-10-23 22:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-23 18:35 tutorial or guidebook text for some complex topics Drew Adams
2006-10-23 19:59 ` Stefan Monnier
2006-10-23 21:14 ` Drew Adams
2006-10-23 21:46 ` Nick Roberts
2006-10-23 21:58 ` Drew Adams
2006-10-23 22:54 ` Nick Roberts
2006-10-23 23:24 ` Drew Adams
2006-10-24 0:13 ` Nick Roberts
2006-10-24 7:06 ` David Kastrup
2006-10-24 7:44 ` David Kastrup
2006-10-24 20:46 ` Drew Adams
2006-10-24 20:45 ` Drew Adams
2006-10-23 23:33 ` Robert J. Chassell
2006-10-24 17:42 ` Richard Stallman
2006-10-24 20:51 ` Drew Adams
2006-10-23 22:08 ` David Kastrup [this message]
2006-10-24 17:42 ` Richard Stallman
2006-10-24 23:49 ` Stefan Monnier
2006-10-23 20:01 ` Eli Zaretskii
2006-10-23 21:19 ` Drew Adams
2006-10-24 17:42 ` Richard Stallman
2006-10-24 19:31 ` Drew Adams
2006-10-25 18:03 ` Richard Stallman
2006-10-25 18:21 ` Drew Adams
2006-10-26 8:52 ` Richard Stallman
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=85mz7mfzx6.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.