From: pinoaffe <pinoaffe@gmail.com>
To: Luis Felipe <sirgazil@zoho.com>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: Differentiate products more clearly (Cycle 01)
Date: Thu, 02 Nov 2023 14:18:13 +0100 [thread overview]
Message-ID: <87bkccfdrl.fsf@gmail.com> (raw)
In-Reply-To: <25b8b762-892f-7191-f216-e00a9ab1b7f6@zoho.com>
Hello!
Luis Felipe <sirgazil@zoho.com> writes:
> El 12/10/23 a las 20:30, pinoaffe escribió:
>> I think it's important to clarify what Guix is (and I really like your
>> mockups/some of the concrete proposed changes), but I don't quite agree
>> with the idea behind your proposal.
>>
>> I think it would be more useful to produce and maintain a clear list of
>> what guix can do than to bifurcate guix into a package manager and an
>> operating system, especially since many of the aspects of Guix don't
>> cleanly fall in either of those two categories.
>
> In this proposal, that clear list of what Guix can do would be the
> feature list, linked early in the home page, right after Guix's
> definition. The features list already exists in the manual, but I
> think it could provide more information.
>
> Regarding the separation of both products, as I see it, it already
> exists, it is just that it is not that clear. There are separate
> downloads for both products and the manual, for example, has specific
> sections for the package manager and the operating system.
It kind-of exists, but it kind-of doesn't either - guix and guix system
are developed as one joint project, you interact with both through a
common interface, there is no clear division between what is part of
what, etc
>
> Now, I do agree that "package manager" and "operating system" don't
> quite make potential users picture the whole range of features
> provided by Guix... Would you still disagree with the differentiation
> of both products if the definition of Guix changed from "package
> manager" to, say, "a tool for reproducible deployment at every level
> of scale", as Ricardo suggest
> (https://lists.gnu.org/archive/html/guix-devel/2023-10/msg00142.html)?
> Or something along those lines?
I personally really like that definition, though "guix system" could
also fall under that definition, so that may be an issue or a benefit
depending on your point of view :)
[omitted]
> I may be misreading you, but I think your points are in line with the
> idea of changing the definition of Guix to better communicate its many
> other features, instead of simply calling it a "package manager".
My points are very much in line with that, my opposition is solely with
categorizing Guix/Guix System into a package manager and an operating
system
> If I read you correctly, I think having an additional presentation and
> definition for the Guix System (the OS), as suggested in this
> proposal, would not conflict with a possible change to Guix's
> definition.
Yeah, I really support that
[omitted]
Kind regards,
pinoaffe
next prev parent reply other threads:[~2023-11-02 14:10 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 [this message]
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
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=87bkccfdrl.fsf@gmail.com \
--to=pinoaffe@gmail.com \
--cc=guix-devel@gnu.org \
--cc=sirgazil@zoho.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).