9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sl@stanleylieber.com
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Wed, 29 Jul 2020 21:02:20 -0400	[thread overview]
Message-ID: <20200730010220.ddI5h253rq63Jl6vdRhTCCDk-qudVlofJgsh7BPfBpc@z> (raw)
In-Reply-To: <20200727224744.GA61790@wopr>

> I put up code.9front.org/wiki mostly so we can demonstrate that large
> swaths of time go by with no changes, and the changes that show up are
> generally from a handful of people.  I don't really like wikis as
> documentation and/or knowledge bases because they only work when a
> preponderance of users contribute.

i have to apologize because 1.) i forgot this was even there, and 2.)
i didn't know people had added anything to it, at all.


> 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.


> The problem with the current introductory garden path is that each piece
> of advice reults in roadblocks to future pieces of advice, e.g. "set up
> a terminal that can accept cpu connections, now set up these services on
> another machine, now tear down step one and rebuild it in step two's
> image" etc.  It works for "zero to running" but it sucks as a
> pedagogical approach, as not all learners do well with the "draw the
> rest of the fucking owl" approach.
> 
> Old electronics manuals (specifically, here thinking of Textronics
> oscilloscope manuals) used to have a section entitled "Theory of
> Operation" which went over at a high level what each component and/or
> panel button did and why, culminating in an explanation of how they
> worked together in common scenarios.  Such a document explaining what
> these services (ndb, factotum, secstore, rpcu, etc) do without getting
> distracted by administration instructions may be a valuable document.
> 
> "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.

sl


  parent reply	other threads:[~2020-07-30  1:02 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [not found] <98A6B5A900B5E1660221CE63074D0920@ewsd.inri.net>
2020-07-30  2:14 ` ori
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

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=20200730010220.ddI5h253rq63Jl6vdRhTCCDk-qudVlofJgsh7BPfBpc@z \
    --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).