emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Marcin Borkowski <mbork@wmi.amu.edu.pl>
To: emacs-orgmode@gnu.org
Subject: Re: AUCTeX key bindings within Org documents
Date: Sat, 28 Sep 2013 12:36:38 +0200	[thread overview]
Message-ID: <20130928123638.6cbe894f@aga-netbook> (raw)
In-Reply-To: <l26b31$7e1$1@ger.gmane.org>

Dnia 2013-09-28, o godz. 12:30:01
Achim Gratz <Stromeko@Nexgo.DE> napisał(a):

> Am 28.09.2013 11:56, schrieb Suvayu Ali:
> > I think "Public Domain" is the most open you can go.
> 
> It isn't, simply because there is no way to put something into the 
> public domain in many jurisdictions and what exactly is meant by
> "public domain" differs by jurisdiction as well.
> 
> >  Otherwise "GPL v2" is always good.
> 
> CC0 probably comes closest to "public domain" for most intents and 
> purposes, although I don't think it has been tested in court as the
> GPL variants have been.  For Emacs, (L)GPL would be more appropriate
> and if integration into Emacs proper is desired, then you actually
> need to assign copyright to the FSF.

BTW: what are exactly the legal consequences of assigning copyright to
the FSF, especially (but not limited to) concerning copyright of future
works?  Is there any document on the web summarizing this?  (I'm asking
because there is at least one person around here who got very
dissatisfied with his FSF copyright assignment, and I'd prefer to know
what the pitfalls might be.)

And for the record: you might consider the LPPL (LaTeX Project Public
Licence), which is more liberal than GPL, but more restrictive than
PD (and need not be restricted to LaTeX-related works).

> Achim.

Best,

-- 
Marcin Borkowski
http://octd.wmi.amu.edu.pl/en/Marcin_Borkowski
Adam Mickiewicz University

  reply	other threads:[~2013-09-28 10:36 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-27 11:21 AUCTeX key bindings within Org documents Fabrice Niessen
2013-09-27 12:08 ` Nicolas Richard
2013-09-28  8:15   ` Fabrice Niessen
2013-09-28  9:56     ` Suvayu Ali
2013-09-28 10:04       ` Marcin Borkowski
2013-09-28 10:30       ` Achim Gratz
2013-09-28 10:36         ` Marcin Borkowski [this message]
     [not found]     ` <86a9ixgy5b.fsf-oHC15RC7JGTNLxjTenLetw@public.gmane.org>
2013-09-29 18:47       ` Fabrice Niessen
2013-10-01 15:08         ` Suvayu Ali
2013-10-01 20:38           ` Marcin Borkowski
2013-10-02 11:36             ` Nicolas Richard
2013-10-02 20:41               ` Marcin Borkowski
2013-10-05  6:10     ` Joseph Vidal-Rosset
2013-10-05  7:58       ` Fabrice Niessen
2013-10-05 13:51         ` Joseph Vidal-Rosset
2013-10-05 20:52       ` Nicolas Richard
2013-10-05 21:22         ` Joseph Vidal-Rosset
2013-09-27 12:24 ` Marcin Borkowski
2013-09-28  8:16   ` Fabrice Niessen
     [not found]     ` <8661tlgy2w.fsf-oHC15RC7JGTNLxjTenLetw@public.gmane.org>
2013-10-21 20:06       ` Fabrice Niessen
2013-10-01 20:26 ` AW
2013-10-02 11:37   ` Nicolas Richard

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=20130928123638.6cbe894f@aga-netbook \
    --to=mbork@wmi.amu.edu.pl \
    --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).