unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Csepp <raingloom@riseup.net>
To: Robby Zambito <contact@robbyzambito.me>
Cc: Sarthak Shah <shahsarthakw@gmail.com>, guix-devel@gnu.org
Subject: Re: A Forum for Guix Users
Date: Thu, 13 Jul 2023 17:21:33 +0200	[thread overview]
Message-ID: <87sf9rygb7.fsf@riseup.net> (raw)
In-Reply-To: <87sf9r6gmp.fsf@robbyzambito.me>


Robby Zambito <contact@robbyzambito.me> writes:

> Hi Sarthak,
>
>> As of now, it's a bit difficult for beginners to find answers to their problems in the mailing list or in IRC logs as they aren't very
>> easy to navigate compared to forum threads.
>
> I personally think that it would be wiser to improve the documentation
> relating to the mailing lists and IRC logs, rather than fragmenting the
> places that someone should look for answers. Maybe a new / additional
> frontend that is more approachable for new users would also be good.

Sourcehut has full-time employees working on making these accessible, so
it really boggles my mind why we aren't using that instead of Savannah
and Debbugs.
We could also bridge IRC to Matrix (even though the company behind it
has some people who... let's say like the taste of leather too much).
Pine64 has a great chat setup actually, their channels are bridged to a
whole bunch of services.  Not saying we must also bridge with Discord,
but at least the libre options should be considered.

> I have never found myself participating in distro-specific forums; I
> have always used them as read-only sources of information. Yet here I am
> participating in the Guix mailing lists :). I bet I am not alone in this
> experience.
>
> Also FWIW, Guix was basically my introduction to participating in
> mailing lists. So I wouldn't say I am biased in my old ways of doing
> things - I just genuinely think it's a good way to handle communication.
>
> Robby

Guix is also the first project I contributed to in a major way over
mailing lists and my experience is that if you don't keep up to date
with the list, the lackluster search and linking will be a major pain in
the buttocks.  It is usable for experts, but is absolutely not
beginner-friendly.
But even experts would benefit from a better workflow.


  reply	other threads:[~2023-07-13 15:37 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-13 13:52 A Forum for Guix Users Sarthak Shah
2023-07-13 14:05 ` Robby Zambito
2023-07-13 15:21   ` Csepp [this message]
2023-07-14 11:31     ` Msavoritias
2023-07-15 13:43       ` Attila Lendvai
2023-07-15 21:00         ` MSavoritias
2023-07-16  5:55           ` Julien Lepiller
2023-07-15  2:45     ` kiasoc5
2023-07-15 13:59       ` Attila Lendvai
2023-07-15 13:14     ` Tobias Geerinckx-Rice
2023-07-14 21:10   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-15 13:27     ` Attila Lendvai
2023-07-16 10:33     ` Pjotr Prins
2023-07-16 23:30       ` Csepp
2023-07-17 17:41         ` Attila Lendvai
2023-07-17  7:37       ` Ricardo Wurmus
2023-07-17  8:17         ` MSavoritias
2023-07-17 20:29           ` Csepp
2023-07-13 14:40 ` Andrea Rossi
2023-07-13 22:38 ` vidak
2023-07-17  7:58   ` Etienne B. Roesch
2023-08-19 12:47     ` Simon Tournier
2023-07-18  1:52 ` Wilko Meyer
2023-07-18 16:39   ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-07-18 21:12     ` Ricardo Wurmus
2023-08-19 11:54 ` Simon Tournier
  -- strict thread matches above, loose matches on Subject: below --
2023-07-14 20:19 Andy Tai
2023-07-14 21:17 ` Sarthak Shah
2023-07-14 21:26   ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-07-14 22:12     ` Wojtek Kosior via Development of GNU Guix and the GNU System distribution.
2023-07-14 23:50   ` Nguyễn Gia Phong via Development of GNU Guix and the GNU System distribution.
2023-07-21 13:30   ` 宋文武
2023-07-18 11:45 Distopico
2023-07-21  8:37 ` Etienne B. Roesch
2023-07-23 16:17 ` Ahmed Khanzada
2023-07-24  2:41   ` Csepp
2023-08-19 10:59 ` Simon Tournier

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=87sf9rygb7.fsf@riseup.net \
    --to=raingloom@riseup.net \
    --cc=contact@robbyzambito.me \
    --cc=guix-devel@gnu.org \
    --cc=shahsarthakw@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 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).