9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Wed, 29 Jul 2020 19:14:23 -0700	[thread overview]
Message-ID: <FD283C54550F5AFB8868CA988B557E43@eigenstate.org> (raw)
In-Reply-To: <98A6B5A900B5E1660221CE63074D0920@ewsd.inri.net>


>> I would much prefer thet see
>> specific sections of the FQA overhauled in a thoughtful manner, but I
>> sure do not have free time for that at the moment.
> 
> fqa7 needs help.

What in particular do you want help with?

>> "What does this tool do and when do I use it" is a fundamentally
>> different question than "how do I operate this tool" and I think mixing
>> them in the FQA may be doing a disservice to some segment of the
>> readership.  I personally prefer the mixed approach, but I'm not
>> everyone.  Yet.
> 
> i agree we need something like this. i've dabbled with every piece
> except assembling a narrative.

I think there are a few different kinds of docs that are
worth having.

I mentioned some of this on gridchat, but I'll repeat i
here for posteriority.

- Reference manuals. Covering all the options that a
  program has, as well as describing what it does.
  This is covered by our manpages.

- Theory of operation documents. These should give an
  overview of how the parts of the system fit together,
  and the design considerations that went into it.
  We've got hints of this in /sys/doc, but it's spotty.

- Tutorials. Hand holding on how to get tasks accomplshed
  end to end, in detail, explaining both steps and how
  to do things. This is mostly notes scattered over
  the web.

- Cheat sheets: Quick references and summaries of how
  to do things. The FQA, basically.

The divisions are fuzzy -- the synopsis and examples
of manpages, for example, also act as a cheat sheet
if you already know what you're looking for. But some
duplication is fine (and, in fact, good).

As far as most projects go, we're actually in really good
shape -- compare to, say, kubernetes, which is basically
just a bucket of half-assed examples.

The biggest gaps I see are around some theory of operation
documents, as well as some tutorials. I keep referring to
/sys/doc/comp.ps as an example of what I'd like, so here's
one more mention of it.

And, of course, if people want to look over the manpages
and fqa, and submit patches for those: while they're
pretty good, that would also be welcome.



       reply	other threads:[~2020-07-30  2:14 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <98A6B5A900B5E1660221CE63074D0920@ewsd.inri.net>
2020-07-30  2:14 ` ori [this message]
2020-07-30  3:06   ` Stanley Lieber
2020-07-30  3:12     ` Michael Misch
2020-07-30  8:19       ` hiro
2020-07-30  8:58         ` Kurt H Maier
2020-07-30 12:03       ` Ethan Gardener
2020-07-27  9:09 sirjofri+ml-9front
2020-07-27  9:56 ` [9front] " hiro
2020-07-27 15:10 ` Amavect
2020-07-27 15:54   ` Stanley Lieber
2020-07-27 15:58 ` ori
2020-07-27 17:01   ` William Gunnells
2020-07-27 17:29     ` Stanley Lieber
2020-07-27 18:09       ` William Gunnells
2020-07-27 20:01       ` ori
2020-07-27 21:22         ` Ethan Gardener
2020-07-28 19:10           ` cinap_lenrek
2020-07-29 22:36             ` Ethan Gardener
2020-07-27 22:06         ` Anthony Martin
2020-07-27 22:21           ` Stanley Lieber
2020-07-27 23:46             ` ori
2020-07-27 22:17         ` Stanley Lieber
2020-07-27 22:47           ` Kurt H Maier
2020-07-27 23:50             ` ori
2020-07-28  4:56               ` sirjofri+ml-9front
2020-07-28 10:18                 ` hiro
2020-07-28 11:27                   ` sirjofri+ml-9front
2020-07-28 12:14                     ` hiro
2020-07-28 13:08                       ` sirjofri+ml-9front
2020-07-28 14:16                         ` hiro
2020-07-28 15:01                           ` Stanley Lieber
2020-07-28 15:12                             ` ori
2020-07-28 15:46                               ` Stanley Lieber
2020-07-28 17:25                                 ` hiro
2020-07-28 17:37                                 ` ori
2020-07-28 17:43                                   ` Kurt H Maier
2020-07-28 15:11                         ` ori
2020-07-28 11:29                   ` sirjofri+ml-9front
2020-07-29 17:10                     ` ori
2020-07-30  1:02             ` sl
2020-07-28  9:48           ` hiro
2020-07-30 18:12 ` magma698hfsp273p9f
2020-07-30 18:48   ` kvik
2020-07-30 18:54   ` ori
2020-07-30 19:28     ` Eckard Brauer
2020-07-30 19:59     ` Romano
2020-07-31 13:44       ` kvik
2020-07-31 13:51         ` Stanley Lieber
2020-08-01 15:42         ` Ethan Gardener
2020-07-30 19:15   ` Kurt H Maier
2020-07-31 10:59     ` Ethan Gardener
2020-08-03 18:50       ` magma698hfsp273p9f
2020-08-04 17:13         ` Ethan Gardener

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=FD283C54550F5AFB8868CA988B557E43@eigenstate.org \
    --to=ori@eigenstate.org \
    --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).