unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Laura Lazzati <laura.lazzati.15@gmail.com>
To: "Gábor Boskovits" <boskovits@gmail.com>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: New topic: asking for help
Date: Thu, 14 Feb 2019 16:37:04 -0300	[thread overview]
Message-ID: <CAPNLzUPbdPncUdnDeUGehkb0U7o+56dTvWGEqh4wcrZ9PjZnZw@mail.gmail.com> (raw)
In-Reply-To: <CAE4v=phACrj2=ZnhR_jZN19azRKZnU9uSA4PnejDam_+LbpHAA@mail.gmail.com>

Hi!
> > * First entry maybe is the homepage as such.
Guix site?
> > * Then show the documentation [or: are we here already assuming that
> > someone found that?].
We are adding in every video the link to the full documentation in the
last slide.
> > * 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.
uhm but isn't the idea of the video "hi, I'm new, I am trying to use
GNU Guix, how can I ask for help?" That was what I had in mind, or at
least what I understood. Maybe if there is enough time, we can add it,
but I feel it is kind of advanced for the video.
> >
>
> 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 agree with this, we can show a screenshot of that part of the site :)

>
> 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 mentioned that the videos show at the end a slide with the link for
the documentation, but does not harm adding it again.
> I guess I would skip the dev list here
OK, just help. is it fine taking snapshots?
> 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.
Here we need to show like in cli sessions or just explain it?
> 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.
Already mentioned my idea about debbugs. Don't know what mumi is :/

Regards :)
Laura

  reply	other threads:[~2019-02-14 19:38 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
2019-02-14 19:37     ` Laura Lazzati [this message]
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

  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=CAPNLzUPbdPncUdnDeUGehkb0U7o+56dTvWGEqh4wcrZ9PjZnZw@mail.gmail.com \
    --to=laura.lazzati.15@gmail.com \
    --cc=boskovits@gmail.com \
    --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 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).