unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Sarthak Shah <shahsarthakw@gmail.com>, Guix Devel <guix-devel@gnu.org>
Subject: Re: A Forum for Guix Users
Date: Sat, 19 Aug 2023 13:54:49 +0200	[thread overview]
Message-ID: <86v8dbxn5i.fsf@gmail.com> (raw)
In-Reply-To: <CADBZEVn_DKTUdZ50typiCF=SsLcmbFtxTgXCP166cfawHNo_3g@mail.gmail.com>

Hi,

On Thu, 13 Jul 2023 at 19:22, Sarthak Shah <shahsarthakw@gmail.com> wrote:

> I think we should seriously consider having a user forum similar to
> Debian's User Forum or Nixos' Discourse.

Well, I shared my opinion in the other thread:

        A Forum for Guix Users
        from Distopico <distopico@riseup.net>
        Tue, 18 Jul 2023 06:45:16 -0500
        https://yhetil.org/guix/87bkg9wigq.fsf@riseup.net

with my message 86a5unz4ap.fsf@gmail.com. 


And to be explicit: do not count on me for interacting with Discourse.
For two reasons:

 1. Because I have never find the way to deal with it with intermittent
 internet connection.  How do you deal with such forum in batch-mode?

 More than often, I process (read and/or answer) the volume of Guix
 messages off-line.  As I am doing right now. :-) For example, before
 going to somewhere without internet connection (meeting or else) and
 because I know that I will have some slots of free time (boring meeting
 or else), well I just fetch the last messages, and then I process the
 messages.  Once back to some internet connection, I send all my
 replies.

 Without that batch-mode feature, I would not just read most of the
 messages and probably I would never answer.  For example, today I am
 not following Haskell or OCaml or Python because Discourse forces me
 the way of interaction.  Well, because I find that way so boring: open
 my web-browser, click, no filter, etc., I am scrolling only the
 Discourse of OCaml once per month or so.  Maybe I have missed the
 offline procedure because I have not checked Discourse features since
 last months (years?).

 2. Because I find insane to have such resource-hungry client/server
 configuration for only exchanging small pieces of text.

 Instead of calling to require more for doing the same (or sometimes
 even less) but using more resource, I am calling to the opposite: doing
 more with less.  I strongly think we must collectively reflect on how
 to do using less.  We have to drastically decrease the global CO2
 footprint and every gram counts.

Obviously, we have to be welcoming.  For sure we have to think and
re-think and think again and again about the best ways to be welcoming
and helpful.  However, I disagree that Discourse or similar will bring
something on the table.  Well, I will not bet that people currently
helping in mailing lists would continue to provide answers using
Discourse and I will not bet that instead new experienced users would
answer to question on Discourse.

There is a trade-off between newcomer’s expectations about the way to
get help and experienced users who provide such help.  I fear that
switching to Discourse could indeed meet newcomer’s expectations but
loosing those experienced users.

Cheers,
simon


  parent reply	other threads:[~2023-08-19 14:58 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
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 [this message]
  -- 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=86v8dbxn5i.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --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).