all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Luis Felipe <sirgazil@zoho.com>
To: Simon Tournier <zimon.toutoune@gmail.com>,
	guix-devel <guix-devel@gnu.org>
Subject: Re: Proposal: Differentiate products more clearly (Cycle 01)
Date: Thu, 12 Oct 2023 21:52:58 +0000	[thread overview]
Message-ID: <00e2b17b-75d1-81b0-d2a5-8215b96bd9f6@zoho.com> (raw)
In-Reply-To: <86bkd4clha.fsf@gmail.com>


[-- Attachment #1.1.1: Type: text/plain, Size: 2475 bytes --]

Hi Simon,

El 12/10/23 a las 8:07, Simon Tournier escribió:
> Hi,
>
> On Thu, 12 Oct 2023 at 00:15, Luis Felipe <luis.felipe.la@protonmail.com> wrote:
>
>> This is a proposal to help differentiate Guix, the package manager,
>> from Guix System.
> I agree with this proposal.
>
> For what it is worth, I remember a discussion past year at 10 Years of
> Guix with researchers – interested by reproducible research and not
> really knowing what Guix is – and after some search engine queries, they
> ended on the website guix.gnu.org.  From the information there, 1. they
> did not get what Guix is and 2. they had the feeling that Guix is not
> for their tasks.  Your proposal really helps here!

Glad to hear that :)


>> Mockup:
>> https://luis-felipe.gitlab.io/downloads/temp/guix-website-2023-09-21-LF/home-page.pdf
> Well, comments.
>
> 1.
> Instead of replicate or reproduce that have different meaning depending
> on communities, I prefer to use the weak-defined ’redeploy’ which cover the
> idea.
>
>      “and make these eaiser to redeploy in one or many devices, and over time.”
>
> For instance, the word “replicate” could confuse this community who
> expect the word “reproduce”.
>
> “What’s the difference between replication and reproduction?“
> https://rescience.github.io/faq/
>
> Well, for instance:
>
> “Reproducibility vs. Replicability: A Brief History of a Confused Terminology”
> https://www.ncbi.nlm.nih.gov/pmc/articles/PMC5778115/

Thanks, I'm taking note of this.


> 2.
> I would not write “without superuser privileges” since you need at least
> once – for installing.  Hum, I have no alternative wording.

Right. I've been living in the Guix System for so long now...


>
> 3.
> I would not write “50 years later”.  Instead, just “Get the same
> environment in the future”.

The reason I used the specific number was to make it clearer that Guix 
should allow reproducible outputs for generations to come, instead of 
just some near future.


> 4.
> How to go from “Guix Package Manager” to “Guix System” and vice-versa?

I don't think I understand. Do you mean how would people go from the 
package manager home page to the operating system page?


>> Looking forward to your comments,
> Well, from my perspective, your proposal makes clearer information about
> the different Guix.
Thanks for checking it out, Simon :)

[-- 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 --]

  reply	other threads:[~2023-10-12 21:53 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 [this message]
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

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=00e2b17b-75d1-81b0-d2a5-8215b96bd9f6@zoho.com \
    --to=sirgazil@zoho.com \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.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 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.