all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: "Björn Höfling" <bjoern.hoefling@bjoernhoefling.de>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New topic: asking for help
Date: Thu, 14 Feb 2019 15:55:12 +0100	[thread overview]
Message-ID: <CAE4v=phACrj2=ZnhR_jZN19azRKZnU9uSA4PnejDam_+LbpHAA@mail.gmail.com> (raw)
In-Reply-To: <20190213100621.6e9754f1@alma-ubu>

Hello,

> * First entry maybe is the homepage as such.
> * Then show the documentation [or: are we here already assuming that
> someone found that?].
> * Then mailing list (dev/help).
> * IRC channel is also quite a help, I would mention that too.
> * There is the debbugs bug tracker
> (https://debbugs.gnu.org/cgi/pkgreport.cgi?pkg=guix) where you could
> search for problems. It is maybe not the most obvious interface and
> explaining it a bit would be nice.
>

This ordering looks fine to me.

I would add some emphasis to finding the
documentation and the contact page on the website, but that might be obvious.

I would spilt up showing documentation, and first refer to the
location with the other videos,
then to the manual, the rationale being is that someone who is already
watching a documentation
video might be more interested in documentation videos in the first place.

I guess I would skip the dev list here. I feel it would result in
better distribution of messages. If the
question seems to be dev related, the  either we can redirect the
thread to dev, and most devs will
come across the list of mailing lists on the contact page, and post
there in the first place, so I
guess this would not cause any real concern.

I also believe that the IRC channel is quite important. On thing to
consider here is to mention the
things related to nickname registration and logging in. It is
unfortunate that we were forced to
making registration required, but this is how things are right now.

We might also propose the mumi as the primary issue tracking
interface, and mention debbugs in
case more advanced stuff is needed. No strong opinion here.

Best regards,
g_bor

  reply	other threads:[~2019-02-14 14:55 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11 14:29 New topic: asking for help Laura Lazzati
2019-02-11 15:38 ` znavko
2019-02-11 15:49   ` Laura Lazzati
2019-02-13  3:02   ` Laura Lazzati
2019-02-13  9:06 ` Björn Höfling
2019-02-14 14:55   ` Gábor Boskovits [this message]
2019-02-14 19:37     ` Laura Lazzati
2019-02-16 18:58       ` Alex Vong
2019-02-17  8:26         ` swedebugia

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='CAE4v=phACrj2=ZnhR_jZN19azRKZnU9uSA4PnejDam_+LbpHAA@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=bjoern.hoefling@bjoernhoefling.de \
    --cc=guix-devel@gnu.org \
    /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.