From: Attila Lendvai <attila@lendvai.name>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Guix wiki
Date: Tue, 11 Jan 2022 21:03:47 +0000 [thread overview]
Message-ID: <wx7mYHZ1ZapfCqQkatQGsBl4NLufurfofL1JLDUgtLQjnKDnWvCoqsvDURN-K56KVW7tCfL2oK4j04HVM7ZTIQX9lya4RX0wwSahMUXV1ok=@lendvai.name> (raw)
In-Reply-To: <17e49565b21.1285153a6259042.8278566905195778367@excalamus.com>
> > There is something here:
> > https://libreplanet.org/wiki/Group:Guix
[...]
> I was thrilled to see a wiki link on the homepage and disgusted to
> see that it didn't actually foster community. In fact, there's
> strife immediately within the "community" wiki, the simple fact it
> exists, let alone what it says. I think it would be better to have
> nothing linked from the homepage because 1) the current wiki is
> useless and 2) linking endorses what's there, including how it
> appears hostile to community.
FWIW, i had a similar experience when i came to Guix a few months ago:
i was thrilled that there was a wiki, and then i quickly got
disappointed that it's some shared something with little content
(which means that e.g. searching will bring up all kinds of unrelated
matches, etc).
i looked for the wiki because i wanted to add something useful to it
that i was searching for way too long, but then i ended up getting
dismayed and dropped the idea.
sending a patch to the manual is a way higher threshold than editing a
wiki, especially when it's someone's first contribution. and some
random, half-baked copy-paste doesn't belong in the manual, while it
may be very useful when found in a wiki using the search engine.
also note that i'm programming since i was a child, 30+ years now. at
least half of it was part of opensource projects, and yet i had quite
a learning curve getting to the point of submitting patches with any
level of confidence (but not yet comfort).
emails + debbugs + emacs + double-spaces + whatnot are all a cultural
thing, and not necessarily simple for aliens, not at all. if you want,
i can get into the details.
note that i'm not necessarily arguing for a wiki here, i understand
the concerns. i just want to draw attention that contributing to Guix,
and especially to the manual by a non-coder, is not at all as simple
as i see repeatedly expressed.
--
• attila lendvai
• PGP: 963F 5D5F 45C7 DFCD 0A39
--
Copying is not theft, and coercively excluding other humans from using knowledge is evil.
next prev parent reply other threads:[~2022-01-11 21:04 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
2022-01-12 15:26 ` Luis Felipe
2022-01-11 16:48 ` Luis Felipe
2022-01-11 21:03 ` Attila Lendvai [this message]
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='wx7mYHZ1ZapfCqQkatQGsBl4NLufurfofL1JLDUgtLQjnKDnWvCoqsvDURN-K56KVW7tCfL2oK4j04HVM7ZTIQX9lya4RX0wwSahMUXV1ok=@lendvai.name' \
--to=attila@lendvai.name \
--cc=guix-devel@gnu.org \
--cc=matt@excalamus.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).