all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: help-gnu-emacs@gnu.org
Subject: Re: What license to use for Emacs libraries?
Date: Tue, 18 Aug 2015 18:01:21 -0400	[thread overview]
Message-ID: <jwv8u98qn0l.fsf-monnier+gmane.emacs.help@gnu.org> (raw)
In-Reply-To: 87fv3gz2s1.fsf@russet.org.uk

> There are other options, I believe, including release under public
> domain which I you could do, although others can argue that this is a
> bad thing to do.

Few people find it bad to "release in the public domain".  Instead the
problem is that you can't do it.  Your work will/should fall into the
public domain at some point in the future (currently defined as
something like 75 years after your death, tho there are strong
commercial interests behind pushing this even further into the future),
but nobody (other than time itself) can do that.

Instead, you can release under a license that mimics the effects of
something being in the public domain (e.g. the CC0 license).


        Stefan




  reply	other threads:[~2015-08-18 22:01 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-18 21:06 What license to use for Emacs libraries? Marcin Borkowski
2015-08-18 21:48 ` Phillip Lord
2015-08-18 22:01   ` Stefan Monnier [this message]
2015-08-18 22:15     ` Phillip Lord
2015-08-18 23:46       ` Robert Thorpe
2015-08-19 14:12         ` Phillip Lord
2015-08-20  7:05         ` Steinar Bang
2015-08-18 23:16   ` Marcin Borkowski
2015-08-19 14:36     ` Tassilo Horn
2015-08-19 21:46       ` Robert Thorpe
2015-08-20  4:44         ` Tassilo Horn
2015-08-19 16:00     ` Phillip Lord
2015-08-18 21:53 ` Stefan Monnier
2015-08-18 23:21   ` Marcin Borkowski
     [not found]   ` <mailman.8593.1439940074.904.help-gnu-emacs@gnu.org>
2015-08-19  1:11     ` Stefan Monnier
2015-08-19 16:02       ` Phillip Lord

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=jwv8u98qn0l.fsf-monnier+gmane.emacs.help@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=help-gnu-emacs@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.