From: 宋文武 <iyzsong@envs.net>
To: Sarthak Shah <shahsarthakw@gmail.com>
Cc: Andy Tai <atai@atai.org>, guix-devel@gnu.org
Subject: Re: A Forum for Guix Users
Date: Fri, 21 Jul 2023 21:30:30 +0800 [thread overview]
Message-ID: <87jzut75op.fsf@envs.net> (raw)
In-Reply-To: <CADBZEV=LAmEiz1zdG5-kRnLsdXPEriuaDGqKWZiK_25oBwmZbQ@mail.gmail.com> (Sarthak Shah's message of "Sat, 15 Jul 2023 02:47:09 +0530")
Sarthak Shah <shahsarthakw@gmail.com> writes:
> The reason why I'm suggesting a move away from mailing lists is that it is a lot easier to follow threads on forums.
> You have all the replies on the same page, compared to clicking on the link of each reply, realizing it doesn't have the answer, clicking
> another link and so on...
Well, I could not image we'd move away from mailing lists (for patches,
issues)... For QA forum we have the help-guix list, it has an
unofficial public-inbox instance at https://yhetil.org/guix-user/ ,
which show replies in one page, and can be clicked to reply by email...
Maybe we can write a more polished web interface for public-inbox.
Also today I learned there exist fediverse reddit like sites using
lemmy/kbin, where you can get a modern forum experience. eg:
https://kbin.social/m/guix@lemmy.ml (not much people there though...)
If we can bridge mailing lists with those fediverse sites, that will be
cool! 🤔
next prev parent reply other threads:[~2023-07-21 13:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 20:19 A Forum for Guix Users 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 ` 宋文武 [this message]
-- strict thread matches above, loose matches on Subject: below --
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
2023-07-13 13:52 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
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=87jzut75op.fsf@envs.net \
--to=iyzsong@envs.net \
--cc=atai@atai.org \
--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).