From: Julien Lepiller <julien@lepiller.eu>
To: guix-devel@gnu.org, MSavoritias <email@msavoritias.me>,
Attila Lendvai <attila@lendvai.name>
Subject: Re: A Forum for Guix Users
Date: Sun, 16 Jul 2023 07:55:39 +0200 [thread overview]
Message-ID: <E34FB6F1-6717-47E9-8C7F-98FA549279BB@lepiller.eu> (raw)
In-Reply-To: <87edl8anr5.fsf@fannys.me>
Le 15 juillet 2023 23:00:43 GMT+02:00, MSavoritias <email@msavoritias.me> a écrit :
>
>Attila Lendvai <attila@lendvai.name> writes:
>
>>> Regarding the forum I dont think any forum would have much traction.
>>> I agree that either matrix or xmpp could be considered instead for that
>>> purpose.
>>> As a more approachable chat mechanism compared to IRC.
>>
>>
>> it's an essential role of a forum that latecomers find the earlier
>> questions/discussions, typically through a websearch. a forum's
>> primary user-story is very much not that of a chat, i.e. a real-time,
>> ephemeral, linear flow of text, sometimes with multiple overlapping
>> discussions, and as such not very well processed by the search engine
>> crawlers...
>>
>> i think it all boils down to this:
>>
>> mailing list archives (and IRC logs) are stuck in time. their underlying data model is inadequate for efficient indexing/searching, and often lack structure even to conveniently present the archive to the user.
>
>Good point.
>My thinking is that next we miss too things for that:
>
>1. Easy search and indexing of our docs. Which already exists for the
>most part. Searching for occurunces of words like grep or a full blown
>wiki like gentoo or arch would be an interesting future approach.
>2. We need something easier than gnu info to contribute docs. As I have
>read a lot in irc for it to be a barrier. And personally its one of the
>main reasons i havent contributed yet. That I need time to learn
>it. That and I can't easily change or add Docs. I have to do pull
>requests and such.
At least for the cookbook, we can accept other formats, and a commiter will convert to the proper info format. What matters is the content, and you don't even have to create a patch, just send a chapter to the ML :)
>
>Thats why I was also aggreeing with Sourcehut in the other email. (Which
>already has guix ci support.) Guix would benefit from less NIH imo. At
>least in places where there already better solutions.
>
>Msavoritias
>
>> --
>> • attila lendvai
>> • PGP: 963F 5D5F 45C7 DFCD 0A39
>
>
next prev parent reply other threads:[~2023-07-16 5:57 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 [this message]
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=E34FB6F1-6717-47E9-8C7F-98FA549279BB@lepiller.eu \
--to=julien@lepiller.eu \
--cc=attila@lendvai.name \
--cc=email@msavoritias.me \
--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).