From: Ricardo Wurmus <rekado@elephly.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 15549@debbugs.gnu.org, christophe.jarry@ouvaton.org
Subject: bug#15549: hydra.gnu.org uses nontrivial and nonfree javascript
Date: Mon, 09 Oct 2017 23:17:46 +0200 [thread overview]
Message-ID: <87lgkkm35x.fsf@elephly.net> (raw)
In-Reply-To: <87zjqkvoht.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> AFAICS it’s actually the case. However, all this lacks the right tags
> for LibreJS to recognize it.
>
> Could you tell us what’s needed to make it work?
>
> I can then submit a patch for Hydra itself. It would be neat if someone
> else would submit the JQuery/Bootstrap parts, though.
Has our version of hydra diverged from upstream, or are we just using an
old version?
We need to add license comments to the JavaScript files and to
non-trivial embedded script blocks.
I would like to do this, but I don’t know where the code is that I
should edit, or if this should just be done on our single
soon-to-be-obsolete hydra.gnu.org instance.
--
Ricardo
GPG: BCA6 89B6 3655 3801 C3C6 2150 197A 5888 235F ACAC
https://elephly.net
next prev parent reply other threads:[~2017-10-09 21:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-07 7:43 bug#15549: hydra.gnu.org uses nontrivial and nonfree javascript christophe.jarry
2013-10-07 20:02 ` Ludovic Courtès
2017-10-09 21:17 ` Ricardo Wurmus [this message]
2017-10-10 6:55 ` Ludovic Courtès
2017-10-18 23:48 ` Ricardo Wurmus
2017-10-22 21:54 ` Maxim Cournoyer
2017-10-23 21:06 ` Ludovic Courtès
2017-11-10 22:35 ` Ricardo Wurmus
2014-08-28 19:02 ` Christophe Jarry
2017-10-19 15:15 ` Thompson, David
2017-10-23 5:46 ` Ricardo Wurmus
2017-11-10 0:20 ` Adonay Felipe Nogueira
2017-03-16 20:47 ` bug#15549: hydra.gnu.org needs to declare its javascript licenses for Joshua Branson
2018-12-17 10:36 ` bug#15549: hydra.gnu.org needs to declare its javascript licenses for LibreJS swedebugia
2018-12-18 11:23 ` Ludovic Courtès
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=87lgkkm35x.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=15549@debbugs.gnu.org \
--cc=christophe.jarry@ouvaton.org \
--cc=ludo@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/guix.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.