From: Luis Felipe <sirgazil@zoho.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org
Subject: Re: Proposal: Differentiate products more clearly (Cycle 01)
Date: Thu, 12 Oct 2023 22:32:44 +0000 [thread overview]
Message-ID: <80ad6464-df1a-fa31-8a14-fc7871950063@zoho.com> (raw)
In-Reply-To: <87jzrskogh.fsf@elephly.net>
[-- Attachment #1.1.1: Type: text/plain, Size: 1702 bytes --]
Hi Ricardo,
El 12/10/23 a las 12:28, Ricardo Wurmus escribió:
> Hi,
>
>> 2018-01-17 · website: say what Guix is at the very top
>> https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00232.html
> Hey, that’s me! Naturally, I do agree that we need clearer product
> differentiation and your drafts are pretty and clear as always.
Glad to hear that.
> On the other hand I’ve always felt that the term “package manager” is so
> limiting. It primes people to expect a package manager, but none of
> the features in the “guix system” family of commands match that.
> Likewise, all that container stuff we do with “guix shell -C” lies just
> outside of what one would think of when hearing “package manager”.
Right. I agree.
> In my presentations I try to drive home the point that Guix is a
> solution for reproducible deployment at every level of scale. I have a
> set of slides similar to the “Reproducible Outputs” section in your
> home-page.pdf, going from package to environments to containers to
> systems to sites (via “guix deploy”).
Yeah, I've watched your presentations. I used "FOSDEM 2019 GWL: GNU
Workflow Language" as one of my references; any similarity to actual
slides is no coincidence :)
> I wonder if we should find a way to phase out the use of the term
> “package manager”, which seems to fire the wrong synapses and awaken
> associations with things that aren’t at all like Guix.
As with product renaming, I also avoided changing the purpose of Guix in
the proposal to reduce resistance to big changes, but I was tempted to.
Maybe this is a good time for redefining Guix as well.
[-- 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 --]
next prev parent reply other threads:[~2023-10-12 22:33 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 [this message]
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
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=80ad6464-df1a-fa31-8a14-fc7871950063@zoho.com \
--to=sirgazil@zoho.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
/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).