From: Nils Gillmann <ng0@n0.is>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>,
"myglc2@gmail.com" <myglc2@gmail.com>
Subject: Re: Roadmap for Guix 1.0
Date: Sat, 1 Sep 2018 10:09:40 +0000 [thread overview]
Message-ID: <20180901100940.rybu6tmqjib7jtnd@abyayala> (raw)
In-Reply-To: <20180901092726.lvgm5i7u2s7jxajy@thebird.nl>
Pjotr Prins transcribed 466 bytes:
> On Sat, Sep 01, 2018 at 07:36:35AM +0000, rchar01 wrote:
> > As an example, PureOS had a similar idea for the name.
> >
> > - https://www.pureos.net/
> > - from https://www.gnu.org/distros/free-distros.en.html
>
> We should have some flavours:
>
> FunGuixOs
> SeriousGuixOs
> VerySeriousGuixOS
> VerySeriousGuixOSIndeed
>
> Just kidding. GuixOS sounds fine to me. How will be distinguish
> between Linux and Hurd?
We don't have to. Why would you want this?
Simply give a download a descriptive name, and put the details in
parens behind it or a proper description box.
Imagine we get support for one of the BSD kernels in the future. And
then a variant which builds our own BSD-based GuixSD/OS.. you don't
need to come up with a new name every time.
GuixOS (Linux-libre)
GuixOS (Hurd)
GuixOS (obsd)
easy as that
> GuixLinuxOS
> GuixHurdOS
>
> or simplify to
>
> GNU Guix Linux
> GNU Guix Hurd
>
> Pj.
>
next prev parent reply other threads:[~2018-09-01 10:09 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-29 15:18 Roadmap for Guix 1.0 Ludovic Courtès
2018-07-30 1:23 ` Pjotr Prins
2018-07-30 9:02 ` Nils Gillmann
2018-07-30 12:47 ` Pierre Neidhardt
2018-08-19 11:06 ` LVM support Ludovic Courtès
2018-08-29 16:12 ` Roadmap for Guix 1.0 Amirouche Boubekki
2018-08-30 11:46 ` Pierre Neidhardt
2018-08-30 12:04 ` Ludovic Courtès
2018-08-30 12:57 ` Ricardo Wurmus
2018-08-30 14:20 ` Tobias Geerinckx-Rice
2018-08-30 15:17 ` Nils Gillmann
2018-08-30 19:13 ` George Clemmer
2018-08-30 20:12 ` Gábor Boskovits
2018-08-31 14:25 ` George Clemmer
2018-08-31 15:45 ` Vincent Legoll
2018-08-31 15:54 ` Amirouche Boubekki
2018-09-01 7:36 ` rchar01
2018-09-01 9:27 ` Pjotr Prins
2018-09-01 10:09 ` Nils Gillmann [this message]
2018-08-30 15:36 ` George Clemmer
2018-08-30 17:11 ` Hartmut Goebel
2018-08-30 18:17 ` Jan Nieuwenhuizen
2018-08-30 21:45 ` Taylan Kammer
2018-07-30 5:08 ` Chris Marusich
2018-07-30 7:33 ` Pierre Neidhardt
2018-08-19 11:19 ` Ludovic Courtès
2018-08-19 11:11 ` Ludovic Courtès
2018-08-20 1:12 ` Chris Marusich
2018-08-30 19:34 ` Ricardo Wurmus
2018-08-19 21:52 ` Amirouche Boubekki
2018-08-20 7:44 ` Ricardo Wurmus
2018-08-29 16:05 ` Amirouche Boubekki
2018-09-04 22:55 ` fis trivial
2018-09-04 23:09 ` Adam Van Ymeren
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=20180901100940.rybu6tmqjib7jtnd@abyayala \
--to=ng0@n0.is \
--cc=guix-devel@gnu.org \
--cc=myglc2@gmail.com \
--cc=pjotr.public12@thebird.nl \
/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).