unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Luis Felipe via Guix-patches via <guix-patches@gnu.org>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Julien Lepiller <julien@lepiller.eu>,
	"43871@debbugs.gnu.org" <43871@debbugs.gnu.org>
Subject: [bug#43871] [PATCH website] Add community page
Date: Thu, 05 Nov 2020 00:36:24 +0000	[thread overview]
Message-ID: <qsZoE8aBNX_OnIKFcj3O8mu8CKAElOarZcYD0pI6l7PfBIVfHJe4W9YeGgTIWKpf2Sqy-oE8cLuDHUd_L7pfSn7wxiZCsf4kIPFrYrzexm8=@protonmail.com> (raw)
In-Reply-To: <CAJ3okZ3nrNT9qEF2kT9R9MJhqaX2CsfNoV83zz3vDb54KmF4aA@mail.gmail.com>

‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐
On Wednesday, November 4, 2020 6:31 PM, zimoun <zimon.toutoune@gmail.com> wrote:

> Dear,
>
> On Wed, 4 Nov 2020 at 17:12, Luis Felipe luis.felipe.la@protonmail.com wrote:
>
> > Or maybe add it to the Packages menu item? For example:
> > Packages (/LANG/packages/)
> > Channels (/LANG/packages/channels/ or /LANG/channels/)
>
> Ok. Maybe it is better.
>
> > Also, the Packages page could also mention that that list of packages comes from the Guix channel, but more packages are available from other channels (and link to the new list of channels).
>
> You mean add one sentence in the header of:
>
> http://guix.gnu.org/en/packages/
>
> right?

I mean, modify the introductory paragraph. For example:

···
GNU Guix provides 15,183 packages transparently available as pre-built binaries. These pages provide a complete list of the packages IN GUIX CHANNELS. Our continuous integration system shows their current build status (updated November 4, 2020). CHECK THE CHANNELS PAGE TO LEARN ABOUT OTHER CHANNELS THAT PROVIDE ADDITIONAL FREE SOFTWARE NOT INCLUDED IN THE GUIX CHANNEL.
···

Or something like that. And maybe the first use of the term "channel" in that paragraph should be linked to the definition of a channel in the manual.



> > I don't know about the "Community" part because I think the Guix community [is | will be] split into "Libre Only Community" and "Open Source with Proprietary Comunity", so maybe each community should build their own websites that better reflect their own goals? I don't know...
>
> I do not understand this last statement. The websiteguix.gnu.org is
> "Libre Only"; because it is GNU. Therefore, the channels will be
> FSDG-compliant packages only (often variants) and other channels
> (often named 'nonfree') will be not listed here. For example, even on
> hpc.guix.info which is more permissive, nonfree channels contributed
> by Ludo and/or Ricardo) about specific HPC tools are not listed
> overthere. What do you have in mind about "Open Source with
> non-free"?

Well, the thing is, when I read the word "Community" I think of the whole group of GNU Guix users, contributors, and enthusiasts (including people who use Guix with non-free software or who promote channels with non-free packages). So I don't like the word "community" because it would not include the whole Guix community (the group of people who use/promote non-free stuff would be excluded from the list).






  reply	other threads:[~2020-11-05  0:37 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-08 22:38 [bug#43871] [PATCH website] Add community page Julien Lepiller
2020-10-08 23:16 ` zimoun
2020-10-12 16:41 ` Ludovic Courtès
2020-10-12 19:45   ` Brett Gilio
2020-10-13 12:47   ` Luis Felipe via Guix-patches via
2020-10-13 20:06     ` Ludovic Courtès
2020-10-13 20:46       ` Julien Lepiller
2020-11-04 10:38 ` zimoun
2020-11-04 16:12   ` Luis Felipe via Guix-patches via
2020-11-04 18:31     ` zimoun
2020-11-05  0:36       ` Luis Felipe via Guix-patches via [this message]
2021-05-25 14:55 ` Luis Felipe via Guix-patches via
2021-05-25 15:07   ` Julien Lepiller
2021-07-01 13:31   ` Luis Felipe via Guix-patches via
2021-11-19 14:36 ` bug#43871: " Julien Lepiller

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='qsZoE8aBNX_OnIKFcj3O8mu8CKAElOarZcYD0pI6l7PfBIVfHJe4W9YeGgTIWKpf2Sqy-oE8cLuDHUd_L7pfSn7wxiZCsf4kIPFrYrzexm8=@protonmail.com' \
    --to=guix-patches@gnu.org \
    --cc=43871@debbugs.gnu.org \
    --cc=julien@lepiller.eu \
    --cc=luis.felipe.la@protonmail.com \
    --cc=zimon.toutoune@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 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).