all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bengt Richter <bokr@bokr.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: “guix --help” should point to https://guix.gnu.org/help/
Date: Fri, 15 May 2020 22:22:01 +0200	[thread overview]
Message-ID: <20200515202201.GA5536@LionPure> (raw)
In-Reply-To: <CAJ3okZ1j7fV+5J77ftxN7wzrPjodRveGkFK9z9pGU8YtmmAKDw@mail.gmail.com>

Hi zimoun, et al,

On +2020-05-15 13:00:58 +0200, zimoun wrote:
> Hi Ricardo,
> 
> On Fri, 15 May 2020 at 12:20, Ricardo Wurmus <rekado@elephly.net> wrote:
> 
> > annoyed by the fact that people turn to Reddit for help with Guix — a
> > venue only very few of us frequent — I wondered if our help channels are
> > visible enough.
> 
> Maybe it is "cultural" or/and "generational" thing and we cannot do
> really better. Maybe some people prefer channels as Reddit because
> they are a bit "afraid" by email and/or IRC, especially maybe on
> official channels.  Maybe because when someone has a problem, the
> first thing they does is a query to popular search engines and then

Habits are habits, but I don't think people specifically needing guix info
would go to popular search engines if they had an obvious better alternative.

I suspect people e.g. go to https://duckduckgo.com/ and type
"site:gnu.org some clues 2020" in the slot because it can be faster
that way to get a good selection of URLS to choose from.

I.e., faster than navigating from the top of http://www.gnu.org/gethelp/
(BTW wondering why the link is not
   https://www.gnu.org/software/gethelp.html
which works fine).

So, shame at having been outperformed in a search? Or an opportunity to extend the
cooperative FLOSS ethos, and maybe contact duckduckgo.com so as to help them
suceed well in helping us, and creating a mesh benefiting all?

Likewise with Arch and Debian and other wikis or forums that can have
useful search capability that it would be helpful for guix.gnu.org to point to.

You may say that users usually know about their own distros' help sites,
but sometimes it can help to know e.g. that a sibling debian descendant does
not have the problem you are experiencing.

> browse some Reddit-kind of channels, so maybe they feels like it is a
> good entry point.  Maybe some people appreciate the voting system
> (upvote, Discourse, etc.) to be "rewarded". Etc..
>

Good point, I definitely think some kind of rating system would help.
Especially if tied into the search data base so that you can easily
sift out information authored by people who typically post the
final authoritative and correct "fixes" with nice succinct rationale :)

> Well, I am not convinced it is an issue about visibility. :-(
>
Well, I am :)
At least visible things are easier to find when you need them.
Of course, in the dark, audible things may be easier to find,
which may be very important to some.

Of course, in a familiar room, touch may be sufficient to
keep your mental model of the room in sync with reality,
and to navigate through it. Touch is easy to overlook, but
really important, whether typing, reading braille,
playing an instrument, or just playing around :)

So an accessible site map, to build that mental model that
makes it a familiar room, is probably a good thing.

> 
> > “guix --help” prints this:
> >
> >   Report bugs to: bug-guix@gnu.org.
> >   GNU Guix home page: <https://guix.gnu.org>
> >   General help using GNU software: <http://www.gnu.org/gethelp/>

Some people might not like to click on http[^s] and wonder why gnu
is not practicing what it preaches, or suspect that their isp is playing
surveillance middle man^H^H^Hperson^H^H^H^H^H^Hagent for some reason?

I'll repeat from above:
(BTW wondering why the link is not
   https://www.gnu.org/software/gethelp.html
which works fine).

> >
> > I think it should explicitly point to https://guix.gnu.org/help/, maybe
> > right before “General help using GNU software”.
>
+1 :)

Also, I think it would be nice if there were a link from https://guix.gnu.org/help/
to a search page with some category checkboxes and radio buttons, so that
you could get rapidly to the _kind_ of search you need or want. E.g.,

"[x] Troubleshooting" ought to be one check-box IMO, for me the most important :)
I think with that checked searches should lead to info re recent regressions
and "popular" troubleshooting topics, and notices of security issues and realease news.
NOT 2017 bikeshed threads or fixes for problems of long-gone generations :)
(unless of course they sadly are still dead-on relevant ;-/ )

Also, ISTM guix.gnu.org should not try to be the only source of information, but rather
help people to get to other GNU-friendly sources of info that may have extra relevant
info for their particular distribution and use case. Links for pursuing that would help.

Sometimes going to duckduckgo.com and typing "site:gnu.org what you want" in the slot
can get you useful urls faster than navigating down from https://guix.gnu.org/help/

I don't think there's any shame in suggesting that :)

 > Yes, it cost nothing and could improve.

I think that's way too unassertive :)

> 
> 
> All the best,
> simon
> 

-- 
Regards,
Bengt Richter


  parent reply	other threads:[~2020-05-15 20:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 10:18 “guix --help” should point to https://guix.gnu.org/help/ Ricardo Wurmus
2020-05-15 11:00 ` zimoun
2020-05-15 15:54   ` Diego Nicola Barbato
2020-05-17 23:01     ` Ludovic Courtès
2020-05-18  9:10       ` Pierre Neidhardt
2020-05-15 20:22   ` Bengt Richter [this message]
2020-05-17 23:03 ` Ludovic Courtès
2020-05-20 15:36 ` zimoun
2020-05-24 21:10   ` Ludovic Courtès
2020-05-25  6:40     ` Efraim Flashner
2020-05-25  9:17     ` zimoun
2020-05-25 21:24       ` Ludovic Courtès

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=20200515202201.GA5536@LionPure \
    --to=bokr@bokr.com \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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.