From: Bastien <bzg@altern.org>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: #+PROPERTY documentation
Date: Tue, 22 Jan 2013 14:19:37 +0100 [thread overview]
Message-ID: <87a9s1xsly.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87libl7mob.fsf@Rainer.invalid> (Achim Gratz's message of "Tue, 22 Jan 2013 07:32:20 +0100")
Achim Gratz <Stromeko@nexgo.de> writes:
> Nick Dokos writes:
>> I believe that just as with code changes, doc changes also need FSF
>> copyright assignment.
>
> The FSF owns the copyright to all of Org, including the
> documentation.
More precisely, the FSF owns the copyright of GNU Emacs, and
assignments are signed but the contributors for contributions
to GNU Emacs.
Since Org is part of GNU Emacs, the FSF owns the copyright
for the Org manual that is part of GNU Emacs.
It does not own the copyright for changes that are ahead of
GNU Emacs and not yet merged.
But we ask contributors to proceed with the assignment ahead
of the merge, that's easier.
> So yes, anything over 20 lines non-trivial chnages needs to be assigned
> to FSF.
Indeed.
--
Bastien
next prev parent reply other threads:[~2013-01-22 13:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-21 18:41 #+PROPERTY documentation Daimrod
2013-01-21 22:21 ` John Hendy
2013-01-21 22:35 ` Daimrod
2013-01-21 22:47 ` John Hendy
2013-01-21 22:49 ` Daimrod
2013-01-22 0:21 ` Thomas S. Dye
2013-01-22 0:36 ` Daimrod
2013-01-22 5:27 ` Nick Dokos
2013-01-22 6:32 ` Achim Gratz
2013-01-22 13:19 ` Bastien [this message]
2013-01-22 10:19 ` Daimrod
2013-01-22 13:20 ` Bastien
2013-01-22 0:43 ` [PATCH] " Daimrod
2013-01-22 13:23 ` Bastien
2013-01-22 14:09 ` Daimrod
2013-01-22 14:34 ` Bastien
2013-01-24 12:20 ` Daimrod
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
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a9s1xsly.fsf@bzg.ath.cx \
--to=bzg@altern.org \
--cc=Stromeko@nexgo.de \
--cc=emacs-orgmode@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 public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).