From: Richard Stallman <rms@gnu.org>
To: Zhu Zihao <all_but_last@163.com>
Cc: emacs-devel@gnu.org
Subject: Re: Show the license of package in ELPA website.
Date: Sat, 07 May 2022 19:08:44 -0400 [thread overview]
Message-ID: <E1nnTXY-0003wS-3e@fencepost.gnu.org> (raw)
In-Reply-To: <861qx6q6sy.fsf@163.com> (message from Zhu Zihao on Sat, 07 May 2022 12:48:02 +0800)
[[[ 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. ]]]
> > But statements of facts witnessed, views, positions, and opinions
> > don't have to be free. Those reasons don't apply to them, and
> > CC-BY-ND is fine for them. (Likewise for art.)
> IIUC the style and design(CSS & JS) of the website is not a part of you
> mentioned here.
I am not sure what that sentence means. But I think I understand the question.
CSS is a kind of style markup for the text or other contents. We
treat it as part of the contents. It should have a license like the
page contents, or else a license compatible with the page contents.
As for Javascript, that is software code. We reject any nonfree software.
So all Javascript code in a page must be free.
And really you should avoid using Javascript code for anything substantial.
--
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)
prev parent reply other threads:[~2022-05-07 23:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 6:18 Show the license of package in ELPA website Zhu Zihao
2022-05-04 12:58 ` Stefan Monnier
2022-05-05 18:36 ` Richard Stallman
2022-05-07 5:01 ` Zhu Zihao
2022-05-07 13:32 ` Stefan Monnier
2022-05-05 18:36 ` Richard Stallman
2022-05-07 4:48 ` Zhu Zihao
2022-05-07 23:08 ` Richard Stallman [this message]
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=E1nnTXY-0003wS-3e@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=all_but_last@163.com \
--cc=emacs-devel@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.