unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Ludovic Courtès" <ludo@gnu.org>
To: L p R n d n <guix@lprndn.info>
Cc: guix-devel@gnu.org
Subject: Re: Communication and Design at Guix
Date: Tue, 08 Jan 2019 18:37:53 +0100	[thread overview]
Message-ID: <87k1jfuk26.fsf@gnu.org> (raw)
In-Reply-To: <cuc5zuzaybu.fsf@lprndn.info> (L. p. R. n. d. n.'s message of "Tue, 08 Jan 2019 17:49:57 +0100")

Hello,

L  p R n  d n    <guix@lprndn.info> skribis:

> After taking some time learning Guix and trying to get some new packages
> in, I wanted get involved in a slightly different way. I'm not good at
> programming and I think my time might be better used participating in
> tasks a little more inline with my skills.
> The thing is that I find "design" and "communication" (take it in a very broad
> way) often a little more complex and delicate to tackle in a group
> project. This is why I'm introducing the idea with this mail.

This is one of the non-programming activities where Guix needs help so
I’m glad you’re offering to contribute!

> I think the Guix project could benefit a lot from dealing with the
> "rest of the world" and how it wants to show itself. It might even help
> clarify some technical decisions if needed. Bonus is that next release
> will probably be 1.0 and that it means Guix will get extra attention.
>
> I have a few things I would like to talk about but, as I don't want to
> force aniything on anyone, I wanted to first have your thoughts about this and
> eventually what you guix people think would be nice to tackle on. (I
> think I saw something about a wiki somewhere for example etc.)

I’m not sure we need a wiki.  :-)

A very concrete task that could be of interest to you is the “name
change” (a bit of a strong word) that we’d like to implement by 1.0.
I’ll try to summarize.  Currently we have “Guix” and “GuixSD”, and that
confuses things: people visit the web site, they see a “GuixSD” logo and
get confused because they were just looking for a package manager, not a
whole distro, or they think “GuixSD” is a storage device ;-), things
like that.

The idea is to bring everything under the “Guix” name.  Most of the
time, writing “Guix” is good enough—after all, one can run ‘guix system’
on a foreign distro, too.  When we really need to make the distinction,
for instance in the manual, we would write “Guix System” to designate
what we currently call “GuixSD”.

This has implications mostly on the web site and on the manual.  Ricardo
sketched web site modifications here:

  https://lists.gnu.org/archive/html/guix-devel/2018-01/msg00300.html

It would probably have further implications on how we present
Guix/GuixSD.

WDYT?

> By the way, I wanted to start working on the documentation. 
> IMHO, it might benefit from a little graphical enhancement for
> newcomers. The thing is that it's currently hosted on
> gnu.org so it's probably not possible to modify the design. So I wanted
> to ask, first, if that's something that would be welcome? What could be
> the possibilities? And what would be the technical limitations?

The HTML pages at gnu.org/s/guix/manual are generated from Texinfo.  The
CSS there is shared with all the GNU manuals, which is nice for
consistency.  Ideally modifications of the CSS would be submitted to the
GNU webmaster or bug-gnulib@gnu.org (I forgot which one).  However, be
aware that you may encounter misplaced conservatism if you take that
route, so don’t lose your hair on it.

Thanks,
Ludo’.

  reply	other threads:[~2019-01-08 17:38 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-08 16:49 Communication and Design at Guix L p R n d n
2019-01-08 17:37 ` Ludovic Courtès [this message]
2019-01-09  6:11   ` swedebugia
2019-01-09 21:45     ` Ludovic Courtès
2019-01-10 12:09       ` L p R n d n
2019-01-10 13:20         ` swedebugia
2019-01-10 14:34         ` Ricardo Wurmus
2019-01-13 21:45           ` Ludovic Courtès
2019-01-14 15:02             ` L p R n d n
2019-01-15 10:36               ` zimoun
2019-01-15 18:03                 ` nly
2019-01-15 22:08                   ` Ricardo Wurmus
2019-01-16 11:00                     ` Giovanni Biscuolo
2019-01-15 22:28               ` Ludovic Courtès
2019-01-14 23:25             ` swedebugia
2019-01-15 13:56               ` Ricardo Wurmus
2019-01-15 17:39                 ` Julien Lepiller
2019-01-15 22:30                   ` Ludovic Courtès
2019-01-10 12:17     ` L p R n d n
2019-01-10 12:57   ` L p R n d n
2019-01-10 14:30     ` Ricardo Wurmus
2019-01-13 21:50     ` Ludovic Courtès
2019-01-14 14:36       ` L p R n d n
2019-01-15 22:31         ` Ludovic Courtès
2019-01-16 16:31       ` George Clemmer
2019-01-17  0:10         ` swedebugia
2019-01-17 10:58         ` L p R n d n
2019-01-17 11:10           ` Ricardo Wurmus
2019-01-17 14:08             ` swedebugia
2019-01-17 16:24               ` L p R n d n

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=87k1jfuk26.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=guix@lprndn.info \
    /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).