From: Matt <matt@excalamus.com>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix wiki
Date: Tue, 11 Jan 2022 22:51:16 -0500 [thread overview]
Message-ID: <17e4c694e6f.12069c91d373945.5617779756099828199@excalamus.com> (raw)
In-Reply-To: <87mtk2qn1b.fsf@nckx>
---- On Tue, 11 Jan 2022 10:30:22 -0500 Tobias Geerinckx-Rice <me@tobias.gr> wrote ----
> Hullo Matt,
>
> Matt 写道:
> > I feel like it also says that community isn't important to us.
>
> I understand how you could reach a flawed conclusion from a flawed
> assumption:
>
> > Wikis are synonymous with community.
>
> But it's still circular, wrong, and frankly quite offensive.
I didn't mean to say that you or the broader Guix community doesn't care. I can see how what I said was unclear and accused people of that. I'm sorry for that.
What I tried to say was *not* if someone values community that they must have a wiki. Instead, that a wiki is inherently based around community. If there's a wiki, there is implied community. Of course, it's technically possible for someone to create, host, and maintain a wiki just for themselves. But given the options of not hosting, or using some other format (e.g. blog), the choice of a wiki strongly implies collaboration (which is the essence of community).
I was under the impression that the wiki linked to from the main page was *not* editable by non-FSF members. I was mistaken about that. If that were the case (non-editable), then I think it would reflect poorly.
I tried to make the wiki more clear. I still think it's confusing for it to be there.
> Guix cares about community very much. Many of us care very little
> for wikis, having seen how they attract much outdated and
> incorrect information and spam. Wikis are high-maintenance.
Given this situation, I see why.
> I must say, the proponents of wikis have done an exceptionally
> poor job of representing them. Yet we're supposed to be convinced
> that we're missing countless valuable contributions by people who
> can't be bothered to send a mail.
The reality is that wikis can be helpful and they can be misleading. I don't think anyone is under the impression that they will write and maintain themselves.
I'm not advocating for a wiki. I'm saying, there is one currently linked to from the homepage. What should be done with it?
I'm willing to help maintain it.
next prev parent reply other threads:[~2022-01-12 3:52 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-09 21:14 Guix wiki Matt
2022-01-09 21:32 ` Vagrant Cascadian
2022-01-11 13:02 ` Matt
2022-01-11 18:29 ` Jonathan McHugh
2022-04-13 14:46 ` Aurora
2022-01-09 23:55 ` Vincent Legoll
2022-01-11 13:31 ` Matt
2022-01-11 15:17 ` Ricardo Wurmus
2022-01-12 2:52 ` Matt
2022-01-11 15:30 ` Tobias Geerinckx-Rice
2022-01-11 17:15 ` zimoun
2022-01-11 17:27 ` Tobias Geerinckx-Rice
2022-01-11 18:21 ` André A. Gomes
2022-01-11 18:50 ` zimoun
2022-01-12 2:06 ` Tobias Geerinckx-Rice
2022-01-12 8:55 ` zimoun
2022-01-12 9:22 ` André A. Gomes
2022-01-12 3:51 ` Matt [this message]
2022-01-12 15:26 ` Luis Felipe
2022-01-11 16:48 ` Luis Felipe
2022-01-11 21:03 ` Attila Lendvai
2022-01-11 23:18 ` Ricardo Wurmus
2022-01-12 3:28 ` Matt
2022-01-18 14:34 ` Ludovic Courtès
2022-04-11 6:49 ` Attila Lendvai
2022-04-11 8:42 ` Maxime Devos
2022-04-13 15:01 ` Attila Lendvai
2022-04-11 8:47 ` Maxime Devos
2022-01-12 11:19 ` Attila Lendvai
2022-01-12 11:52 ` Ricardo Wurmus
2022-01-12 12:00 ` André A. Gomes
2022-01-10 8:29 ` Josua Stingelin
2022-01-12 1:57 ` Matt
2022-01-12 9:19 ` Ricardo Wurmus
2024-01-10 9:55 ` Attila Lendvai
2024-01-17 19:17 ` Maxim Cournoyer
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=17e4c694e6f.12069c91d373945.5617779756099828199@excalamus.com \
--to=matt@excalamus.com \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).