From: Luis Felipe <sirgazil@zoho.com>
To: "pelzflorian (Florian Pelz)" <pelzflorian@pelzflorian.de>
Cc: Luis Felipe <luis.felipe.la@protonmail.com>,
guix-devel <guix-devel@gnu.org>
Subject: Re: Proposal: Differentiate products more clearly (Cycle 01)
Date: Mon, 12 Aug 2024 14:47:18 +0000 [thread overview]
Message-ID: <32b8eac5-2be0-4092-9a9b-6635b621aadf@zoho.com> (raw)
In-Reply-To: <87sevi54m4.fsf@pelzflorian.de>
[-- Attachment #1.1.1: Type: text/plain, Size: 1335 bytes --]
El 6/08/24 a las 10:26, pelzflorian (Florian Pelz) escribió:
> Hello Luis.
>
> I very much like your Guix download page mock-ups that make the download
> pages give clear instructions. They avoid referring to the manual; this
> is better at least to many users (who currently probably download the
> Guix tarball before they learn it was useless).
Thanks for the feedback, Florian. I'll consider sending patches for
these then.
> The question of wording is if it would be an improvement to use terms
> popularized elsewhere. I have opinions, but perhaps I’m wrongly
> conservative in this regard.
>
> Guix is all about packages, therefore it is a package manager. I
> believe the shell and container and system, home support are still about
> packages. Despite other package managers not doing it.
Yeah... Well, and I guess there's not much interest in changing the
definition anyways. So :)
> Also you write in the system download page mock-up, Guix System were a
> distribution of the GNU operating system. I believe this is wrong; Guix
> (not Guix System) is a distribution of the GNU operating system.
>
> The definition of OS should not be something like Windows, running on
> top of an IBM Bios or Intel Management Engine.
Thanks, I'll take that into account for the patches.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2881 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
prev parent reply other threads:[~2024-08-12 14:48 UTC|newest]
Thread overview: 21+ 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
2024-07-26 23:18 ` Luis Felipe
2024-08-06 10:26 ` pelzflorian (Florian Pelz)
2024-08-06 12:17 ` Marek Paśnikowski
2024-08-06 16:09 ` pelzflorian (Florian Pelz)
2024-08-12 14:47 ` Luis Felipe [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=32b8eac5-2be0-4092-9a9b-6635b621aadf@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=luis.felipe.la@protonmail.com \
--cc=pelzflorian@pelzflorian.de \
/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.