9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] Two errors in fqa
Date: Fri, 25 Jun 2021 19:11:39 -0400	[thread overview]
Message-ID: <3C238F5A-DD4B-4050-998F-3545DB8670CC@stanleylieber.com> (raw)
In-Reply-To: <fbbb68c4-8d65-4c08-a59f-0a73208dfb36@a-b.xyz>

On June 25, 2021 6:40:44 PM EDT, kvik <kvik@a-b.xyz> wrote:
>The name 'docs' is unfortunate.
>I did not (neccessarilly) hope for it to be a The Documentation thing.
>It was primarily to be a dumping ground for articles that can't be manual pages or aren't, under my interpretation, a fit for the FQA, or aren't /sys/doc-worthy (yet?) -- most people would call it a wiki...
>
>25 Jun 2021 23:16:38 Kurt H Maier <khm@sciops.net>:
>
>> On Fri, Jun 25, 2021 at 12:16:22PM +0100, Stuart Morrow wrote:
>>> On 25/06/2021, Kurt H Maier <khm@sciops.net> wrote:
>>>> What is wrong with people finding the wiki, anyway?
>>> 
>>> Nothing is "wrong" with it, but it's called docs when it's really the
>>> documentation equivalent of /extra.  So it's called docs and linked to
>>> from the front page when it's really the furthest thing from *the*
>>> documentation.
>> 
>> I don't think the intention is for that wiki to be /extra-like.  I can't
>> speak for kvik but I always thought the goal was to be comprehensive.
>> 
>> People complained that the FQA was considered 'the' documentation when
>> nobody voted for sl, now people are complaining that other efforts are
>> masquerading as 'the' documentation.  Unless and until the project
>> develops a watery tart to lob scimitars at people I don't see the
>> advantage in promoting one best-effort documentation project over
>> another, even if I happen to prefer one.
>> 
>> khm
>

maybe we could rename it to wiki?

sl

  parent reply	other threads:[~2021-06-27  8:44 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
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 [this message]
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=3C238F5A-DD4B-4050-998F-3545DB8670CC@stanleylieber.com \
    --to=sl@stanleylieber.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).