unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Bruno Félix Rezende Ribeiro" <oitofelix@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Help needed for screenshots
Date: Mon, 17 Nov 2014 17:50:43 +0100	[thread overview]
Message-ID: <877fytydng.fsf@gnu.org> (raw)
In-Reply-To: <20141117133535.7647c0ef@freedom-laptop> ("Bruno Félix Rezende Ribeiro"'s message of "Mon, 17 Nov 2014 13:35:35 -0200")

Bruno Félix Rezende Ribeiro <oitofelix@gnu.org> skribis:

> Em Mon, 17 Nov 2014 16:13:16 +0100
> ludo@gnu.org (Ludovic Courtès) escreveu:
>
>> I’d rather remove the table altogether, unless LibreJS really uses it.
>
> LibreJS *really* needs it.  JavaScript License Web Labels is the
> preferred, and practical, method for labeling third party scripts as
> free [0].
>
>> And even if LibreJS uses it, I’d rather make it invisible.
>
> Wouldn't that defeat one of the purposes of the method's design?
> People should have easy access to the source code of the programs they
> are running.  If we hide the table, people won't easily find the source
> code.  So, what would be the purpose of stating them as free in the
> first place?

Yes, you’re right.  I knew of the @licstart tags, but not JS labels;
indeed, it makes sense to make software distribution more visible in
this way.  javascript-labels-rationale.html explains it very well.

> I think the best solution is to make a separate page
> 'javascript.html' with the table, and put a small, but prominent,
> LibreJS logo linking to that page, like I did for my personal web site. 
>
> What do you think?

Well, in hindsight, you’re right.  Let’s just leave it as is.

We still need a fix so LibreJS actually uses it, though.

Thanks!

Ludo’.

  reply	other threads:[~2014-11-17 16:50 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-14  9:38 Help needed for screenshots Ludovic Courtès
2014-11-14 19:35 ` Bruno Félix Rezende Ribeiro
2014-11-14 21:47   ` Ludovic Courtès
2014-11-14 23:02     ` Bruno Félix Rezende Ribeiro
2014-11-15 15:18       ` Felipe López
2014-11-15 15:30         ` Bruno Félix Rezende Ribeiro
2014-11-15 16:34           ` Felipe López
2014-11-15 17:57         ` Ludovic Courtès
2014-11-15 19:03           ` Felipe López
2014-11-16 17:19             ` Ludovic Courtès
2014-11-16  5:19           ` Bruno Félix Rezende Ribeiro
2014-11-17 13:26             ` Ludovic Courtès
2014-11-17 13:32               ` Ludovic Courtès
2014-11-17 13:49               ` Felipe López
2014-11-17 14:43               ` Bruno Félix Rezende Ribeiro
2014-11-17 15:00                 ` Bruno Félix Rezende Ribeiro
2014-11-17 15:13                 ` Ludovic Courtès
2014-11-17 15:35                   ` Bruno Félix Rezende Ribeiro
2014-11-17 16:50                     ` Ludovic Courtès [this message]
2014-11-17 18:44                       ` Bruno Félix Rezende Ribeiro
2014-11-17 20:37                         ` Ludovic Courtès
2014-11-18 13:51                     ` David Thompson
2014-11-18 16:08                       ` Felipe López
2014-11-18 20:45                       ` Ludovic Courtès
2014-11-19  4:33                         ` Bruno Félix Rezende Ribeiro
2014-11-19  8:55                           ` 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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=877fytydng.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=oitofelix@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 public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).