9front - general discussion about 9front
 help / color / mirror / Atom feed
From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] Two errors in fqa
Date: Fri, 25 Jun 2021 20:39:21 +0200	[thread overview]
Message-ID: <CAFSF3XOq3k+BBZNHUn3Rxb3W0AOtH5NF2i5DJLS6bb8EN16HUA@mail.gmail.com> (raw)
In-Reply-To: <95397E6884143EA24CF6EC0563A09FE4@gmail.com>

The main problem is if there has to be as much documentation as there
is that might suggest the system is already too complex :D

more seriously:

I'm happy that kvik's wiki got stolen and put inside the tree of the
9front.org website, at least everything is more in one place than
before (even though it's still just a website).

I tend to complain about everything sl does, mainly bec. he is
involved in doing many things. maybe this will help revise my former
half-assed comments:

1) shitty best-effort documentation is better than no documentation.
2) maybe some person is running straight from a new 9front iso and has
no web or internet access, this should be rewarded not penalized, so
...
(also, copy&paste is easier when the docs are on the same machine)
3) the .iso should contain all possible best and worst effort
documentation that has been gathered so far
4) the 9front/cat-v websites should also include all the documentation
(e.g. that's why man pages are accessible via the web, too), bec. some
people have 2 computers, and one of them can be used to read the
documentation on the website

the rest, like how easy it is to find the wiki on the website,
shouldn't matter much in comparison, as it being web means it should
show up on google anyway, as even the guy in the youtube video found
out.

and maybe if morale improves and people like me also add some effort
to improve upon the content already there, the low quality or
duplicated scattered information will get more readable and more
efficient and shorter, too.

so far i revoked all attempts made by myself to improve upon
documentation as i wasn't happy with the inefficiency of my english
that i came up with.

On 6/25/21, Sigrid Solveig Haflínudóttir <ftrvxmtrx@gmail.com> wrote:
> Quoth Stanley Lieber <sl@stanleylieber.com>:
>> On June 24, 2021 6:26:05 PM EDT, Stuart Morrow <morrow.stuart@gmail.com>
>> wrote:
>> >This seems as good a place as any to point out that people apparently
>> >find the FQA hard to find...: https://youtu.be/rTQe3W37RBA?t=1276
>> >
>> >I think what has happened is: it used to be clear that 'FQA' was the
>> >FAQ, but now that we have the wiki on the front page *and the link is
>> >called 'docs'*, people are going to the wiki thinking it's the
>> >documentation, and since you don't keep looking for something once
>> >you've already found it (or think you have), they never find the
>> >actual documentation.
>> >
>>
>> maybe the docs wiki could link more prominently to the fqa.
>>
>> sl
>
> I added a note at the top of index to point out FQA is the way to go.
>
>

  parent reply	other threads:[~2021-06-25 23:38 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-19  7:29 sirjofri
2021-06-19 15:49 ` Stanley Lieber
2021-06-20  7:08   ` AW: " sirjofri
2021-06-20 15:19     ` Stanley Lieber
2021-06-20 16:33       ` cinap_lenrek
2021-06-21  1:33         ` sl
2021-06-20 20:06       ` AW: " sirjofri
2021-06-20 23:46         ` Stanley Lieber
2021-06-20 13:28   ` ori
2021-06-21  1:32     ` sl
2021-06-21  1:57       ` ori
2021-06-24 22:26   ` Stuart Morrow
2021-06-25  0:03     ` Stanley Lieber
2021-06-25 18:03       ` Sigrid Solveig Haflínudóttir
2021-06-25 18:35         ` Stanley Lieber
2021-06-25 18:39         ` hiro [this message]
2021-06-25  0:24     ` Kurt H Maier
2021-06-25 11:16       ` Stuart Morrow
2021-06-25 13:52         ` Sigrid Solveig Haflínudóttir
2021-06-25 18:09         ` Kurt H Maier
     [not found]           ` <fbbb68c4-8d65-4c08-a59f-0a73208dfb36@a-b.xyz>
2021-06-25 23:11             ` Stanley Lieber
2021-06-26  8:25               ` kvik
2021-06-28 18:12                 ` kvik
2021-06-28 18:21                   ` Kurt H Maier
2021-06-28 20:14                   ` sl

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAFSF3XOq3k+BBZNHUn3Rxb3W0AOtH5NF2i5DJLS6bb8EN16HUA@mail.gmail.com \
    --to=23hiro@gmail.com \
    --cc=9front@9front.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.
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 NNTP newsgroup(s).