From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: org-bbdb-anniversaries-future
Date: Wed, 01 Mar 2017 15:34:38 +0100 [thread overview]
Message-ID: <874lzdrrpd.fsf@gmx.us> (raw)
In-Reply-To: 87o9xlw0u2.fsf@luisa.c0t0d0s0.de
Michael Welle <mwe012008@gmx.net> writes:
> Hello,
>
> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> Michael Welle <mwe012008@gmx.net> writes:
>>
>>> Even if we assume its quality is high enough to integrate it into Org,
>>
>> If code quality was a concern, Org would still be in alpha release ;)
> thank you for your kind words, Nicolas ;).
>
>
>>> there might or might not be another problem: I haven't signed the FSF
>>> papers. I would like to see the functionality in Org, too. Perhaps
>>> someone can sneak it in ;). I can repost the code, stating that it is
>>> licensed under the GPL or is even in the public domain, if that helps.
>>
>> I don't think it helps. IIRC, code integration in Emacs is pretty
>> strict. You could simply sign FSF papers.
> Yes. Trouble is nobody could explain to me what I have to sign and what
> that means in the legal system I'm in. My last attempt to find that out
> was in #emacs. It's about 'transfer of copyright' to the FSF. If I
> translate 'copyright' to the corresponding construct in our legal
> system, the transfer isn't possible. I can't give away the copyright.
> Maybe 'transfer of copyright' isn't what signing the FSF papers mean, I
> don't know. And IANAL ;).
You might want to discuss this with the FSF copyright clerk
copyright-clerk@fsf.org
They will also be able to tell you if you can use e.g. the FSFE
assignments.
Rasmus
--
The second rule of Fight Club is: You do not talk about Fight Club
next prev parent reply other threads:[~2017-03-01 14:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <qf8k5dxnqs.ln2@news.c0t0d0s0.de>
2016-07-14 22:22 ` org-bbdb-anniversaries-future Marco Wahl
2017-03-01 9:19 ` org-bbdb-anniversaries-future Alan Schmitt
2017-03-01 9:30 ` org-bbdb-anniversaries-future Michael Welle
2017-03-01 10:39 ` org-bbdb-anniversaries-future Marco Wahl
2017-03-01 13:38 ` org-bbdb-anniversaries-future Nicolas Goaziou
2017-03-01 14:03 ` org-bbdb-anniversaries-future Michael Welle
2017-03-01 14:30 ` org-bbdb-anniversaries-future Alan Schmitt
2017-03-01 14:40 ` org-bbdb-anniversaries-future Michael Welle
2017-03-01 14:34 ` Rasmus [this message]
2017-03-05 17:28 ` org-bbdb-anniversaries-future Nicolas Goaziou
2017-03-07 9:19 ` org-bbdb-anniversaries-future Michael Welle
2017-03-12 12:47 ` org-bbdb-anniversaries-future Nicolas Goaziou
2017-03-13 8:22 ` org-bbdb-anniversaries-future Michael Welle
2017-03-13 8:31 ` org-bbdb-anniversaries-future Michael Welle
2017-03-17 7:29 ` org-bbdb-anniversaries-future Nicolas Goaziou
2017-03-01 10:35 ` org-bbdb-anniversaries-future Marco Wahl
[not found] <ipa2rcx5nc.ln2@news.c0t0d0s0.de>
2016-03-08 9:25 ` org-bbdb-anniversaries, bbdb v3 Marco Wahl
[not found] ` <7hp2rcx89n.ln2@news.c0t0d0s0.de>
2016-03-08 13:08 ` Nick Dokos
2016-03-08 15:43 ` org-bbdb-anniversaries-future Georges
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=874lzdrrpd.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).