all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: How to present Guix to a wider audience
Date: Wed, 08 Jan 2020 17:32:38 +0100	[thread overview]
Message-ID: <87sgkpzz6h.fsf@elephly.net> (raw)
In-Reply-To: <8736cqarof.fsf@ambrevar.xyz>


Pierre Neidhardt <mail@ambrevar.xyz> writes:

> As Ricardo said, I believe such a general presentation would be very
> welcome on Guix' front page.
>
> Anyone interested in writing such a text?

We discussed website changes extensively in the past.  Here’s a thread:

    https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00232.html

It also includes the suggestion to deemphasize the distro “Guix System”
and only keep text on the home page that applies to Guix itself.

In my last FOSDEM talk on the GWL I showed how Guix operates on
ever-growing “scenes”: packages, environments composed of multiple
packages, containers composed of environments, and even full-blown
systems.

Maybe there’s something in the old discussions that would still be
useful today for concrete change proposals.

--
Ricardo

  reply	other threads:[~2020-01-08 16:32 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-02 10:03 How to present Guix to a wider audience Pierre Neidhardt
2020-01-02 18:18 ` zimoun
2020-01-08 15:33   ` Pierre Neidhardt
2020-01-08 16:32     ` Ricardo Wurmus [this message]
2020-01-08 20:18     ` zimoun
     [not found]       ` <24DdUL_0dCHlf-Jsotb_z0Mxz7kuUpI_FeBoRrbgJUypYRxvic9u3GhPfBwAiz5ZGjRxITivscu59w_-BPA2cIY_wSbypis89M7Jb8AglBM=@protonmail.com>
     [not found]         ` <CAJ3okZ1CQ1zvbHnFT6EmB+yYFwcAszZ0baroyj03LzTK7AhBXw@mail.gmail.com>
2020-01-10  9:52           ` wisdomlight--- via
2020-01-10 12:19             ` Pierre Neidhardt
2020-01-02 19:20 ` Ricardo Wurmus
2020-01-08 15:26   ` Pierre Neidhardt
2020-01-14 11:23 ` Pierre Neidhardt
2020-01-14 15:58   ` Jack Hill
2020-01-14 17:00     ` Pierre Neidhardt
2020-01-14 21:01       ` Jack Hill
2020-01-14 23:44   ` Dimakakos Dimos
2020-01-15  0:07   ` Vagrant Cascadian
2020-01-15  8:52     ` Pierre Neidhardt
2020-01-15  0:20   ` Josh
2020-01-15  8:57     ` Pierre Neidhardt
2020-01-15  5:59   ` Arun Isaac
2020-01-15  8:53     ` Pierre Neidhardt
2020-01-15  8:59   ` Pierre Neidhardt
2020-01-15 17:44     ` sirgazil
2020-01-19 11:03       ` Todor Kondić
2020-01-19 15:57         ` wisdomlight
2020-01-21 21:49   ` ndre
2020-01-22 11:00     ` Pierre Neidhardt
2020-01-22 17:35       ` Pierre Neidhardt
2020-01-23 14:44         ` Kelsang Sherab
2020-01-23 21:25           ` Pierre Neidhardt
2020-02-11  7:45   ` Pierre Neidhardt
2020-02-11 17:38     ` Josh Marshall

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=87sgkpzz6h.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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.