From: Oleg Pykhalov <go.wigust@gmail.com>
To: myglc2@gmail.com
Cc: guix-devel@gnu.org, Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: [RFC] A simple draft for channels
Date: Fri, 26 Jan 2018 21:53:57 +0300 [thread overview]
Message-ID: <87inbosb7e.fsf@gmail.com> (raw)
In-Reply-To: <86o9lgedpb.fsf@gmail.com> (myglc2@gmail.com's message of "Fri, 26 Jan 2018 12:23:44 -0500")
[-- Attachment #1: Type: text/plain, Size: 1098 bytes --]
myglc2@gmail.com writes:
[...]
> I don't think you should call them "channels." Why? Only advanced Nix or
> Conda users will know what it means. For anyone familiar with Chrome,
> Red Hat, or TV channels, the "channels" label works against you: they
> have to learn and remember that a Guix channel works differently. These
> labels might work better: "Guix Sources" (ala Debian sources list[1]),
> "third party sources" or "third party repos".
>
> WDYT?
>
> [1] https://wiki.debian.org/SourcesList
"Sources" is a very bad name. Especially for search engines. And it
also bad for the reference. You will need to specify what is the 'Guix
source' all the time you mention it. I think about '~/src/guix' Git
repository as I see this.
I think the best for understand phrase is a "third party package
repository" or "package repositories" for short. Is it too general or
could we stick with it?
I also like Ricardo's mention 'Guix package collection' on the IRC.
Maybe 'Guix collections' will be a good candidate? It's unique unlike
'package repositories', which is good for search.
Oleg.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
next prev parent reply other threads:[~2018-01-26 18:54 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 8:24 [RFC] A simple draft for channels Ricardo Wurmus
2018-01-19 8:55 ` Jelle Licht
2018-01-19 11:30 ` Pjotr Prins
2018-01-19 13:41 ` Ludovic Courtès
2018-01-19 13:56 ` Pjotr Prins
2018-01-23 6:38 ` Ricardo Wurmus
2018-01-23 8:54 ` Pjotr Prins
2018-01-23 23:01 ` Carlo Zancanaro
2018-01-23 16:03 ` myglc2
2018-01-23 16:50 ` ng0
2018-01-24 5:44 ` myglc2
2018-01-24 12:33 ` ng0
2018-01-24 15:04 ` Konrad Hinsen
2018-01-23 20:39 ` Ricardo Wurmus
2018-01-23 20:37 ` Ricardo Wurmus
2018-01-24 12:01 ` Pjotr Prins
2018-01-20 5:45 ` 宋文武
2018-01-24 14:08 ` Ludovic Courtès
2018-01-24 17:55 ` myglc2
2018-01-24 18:20 ` Ricardo Wurmus
2018-01-26 17:23 ` myglc2
2018-01-26 18:53 ` Oleg Pykhalov [this message]
2018-03-19 12:46 ` ng0
2018-01-27 12:10 ` Chris Marusich
2018-03-19 12:04 ` [Orchestration][RFC] " Pjotr Prins
2018-03-19 12:36 ` ng0
2018-03-19 18:21 ` myglc2
2018-03-19 18:31 ` Pjotr Prins
2018-03-19 20:18 ` myglc2
2018-03-19 20:29 ` Pjotr Prins
2018-03-20 7:02 ` Pjotr Prins
2018-03-20 10:41 ` Ricardo Wurmus
2018-03-20 13:10 ` Pjotr Prins
2018-03-20 13:41 ` Ricardo Wurmus
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=87inbosb7e.fsf@gmail.com \
--to=go.wigust@gmail.com \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=ricardo.wurmus@mdc-berlin.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.