all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Stefan Kangas <stefankangas@gmail.com>
Cc: 58856@debbugs.gnu.org
Subject: bug#58856: Non-free license CC-BY-ND on GNU ELPA web pages
Date: Tue, 01 Nov 2022 12:49:29 -0400	[thread overview]
Message-ID: <E1opuS9-0000yy-IU@fencepost.gnu.org> (raw)
In-Reply-To: <CADwFkmnq4wu1P-40cCkZ=3oH3iyx7ZRQ6pdQ-p98An_CYB3H5g@mail.gmail.com> (message from Stefan Kangas on Mon, 31 Oct 2022 07:14:59 -0700)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > > Which of those categories do these pages fall in?  (Or are theh in
  > > neither one?)  That is the crucial question here.  If these pages are
  > > software documentation -- that includes brief descriptions of packages
  > > -- then it should have a free license.

  > It is software documentation, yes.  Thanks for confirming.  So I
  > installed the below change in the elpa-admin repository.

Thanks for bringing it up.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  reply	other threads:[~2022-11-01 16:49 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-29  3:00 bug#58856: Non-free license CC-BY-ND on GNU ELPA web pages Stefan Kangas
2022-10-31 11:51 ` Richard Stallman
2022-10-31 14:14   ` Stefan Kangas
2022-11-01 16:49     ` Richard Stallman [this message]
2022-11-12 20:45     ` Stefan Kangas
2022-11-12 22:37       ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-11-13  4:01         ` Stefan Kangas

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=E1opuS9-0000yy-IU@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=58856@debbugs.gnu.org \
    --cc=stefankangas@gmail.com \
    /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.