From: "Ludovic Courtès" <ludo@gnu.org>
To: Luis Felipe <luis.felipe.la@protonmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Proposal: Differentiate products more clearly (Cycle 01)
Date: Thu, 16 Nov 2023 15:37:00 +0100 [thread overview]
Message-ID: <87pm09wyr7.fsf@gnu.org> (raw)
In-Reply-To: <FyiPnZvXS3omJ7zWhb3XVTlw-PKblDUni7J7_7K7G4631vuGiMARxDeumhjPMr9CiiL5iak_uZm7p5I50XyWBZClOWp6Ie4MhzHflSirYCE=@protonmail.com> (Luis Felipe's message of "Thu, 12 Oct 2023 00:15:00 +0000")
Hi Luis,
I’m big fan of what you propose, both graphically in terms of how we
present things!
I love the “cubes” that represent the different levels of Guix
(reminiscent of the hexagons Ricardo had in some of his presentations);
we could add a “systems” (plural) cube that I didn’t see here, but
that’s a detail. I love that the mockups insist on “User Control” and
“User Autonomy” too.
Like Ricardo, I’m less enthusiastic about the term “package manager”,
but we should be able to work around it.
We should also make sure IMO that Guix System is not perceived as a
completely independent/separate beast, and instead insist on that notion
of a continuum.
Luis Felipe <luis.felipe.la@protonmail.com> skribis:
> I can help implement several of the proposed changes.
>
> Subsequent changes (hinted in the mockups) with the same goal of product differentiation could be:
>
> 5. Guix Features section in the manual: Improve it.
> + Separate in sections to make it easier to browse
> + List forgotten functional features (if any)
> + List non-functional features
> + Compare with similar products
> 6. Guix System Features section in the manual: Add it.
> 7. Guix System Configurations page: A collection of configurations, ideally of real systems currently used in production environments.
Makes sense to me. This something those of us less into design and more
into coding can help with.
Thank you!!
Ludo’.
prev parent reply other threads:[~2023-11-16 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 0:15 Proposal: Differentiate products more clearly (Cycle 01) Luis Felipe
2023-10-12 1:54 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-10-12 21:23 ` Luis Felipe
2023-10-13 7:24 ` Simon Tournier
2023-10-12 8:07 ` Simon Tournier
2023-10-12 21:52 ` Luis Felipe
2023-10-12 12:28 ` Ricardo Wurmus
2023-10-12 16:58 ` Simon Tournier
2023-10-12 22:32 ` Luis Felipe
2023-10-12 20:30 ` pinoaffe
2023-11-01 16:01 ` Luis Felipe
2023-11-02 13:18 ` pinoaffe
2023-10-13 9:41 ` Wilko Meyer
2023-10-15 13:11 ` Luis Felipe
2023-10-26 15:07 ` Luis Felipe
2023-11-16 14:37 ` Ludovic Courtès [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
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=87pm09wyr7.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.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).