From: Stefan Kangas <stefankangas@gmail.com>
To: rms@gnu.org
Cc: monnier@iro.umontreal.ca, 58856@debbugs.gnu.org
Subject: bug#58856: Non-free license CC-BY-ND on GNU ELPA web pages
Date: Mon, 31 Oct 2022 07:14:59 -0700 [thread overview]
Message-ID: <CADwFkmnq4wu1P-40cCkZ=3oH3iyx7ZRQ6pdQ-p98An_CYB3H5g@mail.gmail.com> (raw)
In-Reply-To: <E1opTKT-00084W-Q8@fencepost.gnu.org>
Richard Stallman <rms@gnu.org> writes:
> In the GNU Project we use CC-BY-ND for publications that
> state our views. Most articles on www.gnu.org carry CC-BY-ND.
>
> However, for documentation of software, we use free licenses.
>
> 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.
Stefan M, could you please update the static web pages too?
diff --git a/elpa-admin.el b/elpa-admin.el
index f8f8fcabb6..c804612516 100644
--- a/elpa-admin.el
+++ b/elpa-admin.el
@@ -1307,7 +1307,7 @@ readme file has an unconventional name"
<p>Design provided by <a
href=\"https://nicolas.petton.fr\">Nicolas Petton</a></p>
<p>
This website is licensed under the
- <a
href=\"https://creativecommons.org/licenses/by-nd/4.0/\">CC BY-ND
4.0</a>
+ <a
href=\"https://creativecommons.org/licenses/by-sa/4.0/\">CC BY-SA
4.0</a>
International License.
</p>
<p><a href=\"/jslicense.html\"
data-jslicense=\"1\">JavaScript Licenses</a></p>
next prev parent reply other threads:[~2022-10-31 14:14 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 [this message]
2022-11-01 16:49 ` Richard Stallman
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='CADwFkmnq4wu1P-40cCkZ=3oH3iyx7ZRQ6pdQ-p98An_CYB3H5g@mail.gmail.com' \
--to=stefankangas@gmail.com \
--cc=58856@debbugs.gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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.