From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Tue, 28 Jul 2020 14:14:53 +0200 [thread overview]
Message-ID: <CAFSF3XPsEYrLnS+zSyGnhBOzBEwK+75GbPPD9K9sO2NWosX6VQ@mail.gmail.com> (raw)
In-Reply-To: <69ca4492-7a1f-48fb-ba59-4f226277042c@sirjofri.de>
it seems to me we might profit from making you boss of documentation,
and whatever process you find will just have to become mandatory for
the rest of us.
sounds like you are also providing useful reasoning why your process
is the right one and i'm happy to try and adopt it.
On 7/28/20, sirjofri+ml-9front@sirjofri.de
<sirjofri+ml-9front@sirjofri.de> wrote:
> Hello,
>
> the project is not only about creating a wiki space, this is just one part
> that's especially useful for the information that's distributed over many
> blogs or hidden behind long chat logs. I often find myself interviewing
> kvik, burnzez or mycroftiv (and others) about how to do things that are
> never written anywhere else. Most of the time I try to understand this and
> then write an article about exactly that (on my personal blog or on
> 9gridchan wiki). Imo this information is good in a wiki, because other users
> can easily add missing information and link to other sources.
>
> The other parts of the project (if you want to call it like that) are:
> improving man pages, fqa and maybe even debug messages. These are all more
> static because there's a review and merge process. On the other hand,
> collected information in a wiki can help authors to select content for the
> fqa.
>
> Also don't forget /sys/doc and maybe /sys/lib/wiki. /sys/doc is a possible
> place to be extended with updated information. The dead /sys/lib/wiki can be
> revived with snapshots from the wiki. I can also think about a separate
> update process that automatically fetches data from the wiki and includes it
> into the system wiki (offline snapshot).
>
> You see, there are many possibilities and I'd like to provide a place where
> plan9 users can provide useful information (guides, notes etc) that do not
> fit in the book styled fqa or the highly implementation specific manpages or
> the highly technical /sys/doc, also these articles can change quickly
> (sometimes daily or weekly) which would be a lot for reviewers to approve
> before including it into the main distribution.
>
> Also I don't expect things to be so complex. Having a plan9 usable small and
> simple system (eg an official wikifs) makes more sense than hiding
> everything in a browser that can't even edit the pages because there's too
> much webshit or something like that. Also we are a small community, so
> providing information should be more in focus than providing nice UI and a
> modern web browsing experience.
>
> sirjofri
>
>
next prev parent reply other threads:[~2020-07-28 12:14 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 [this message]
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
[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=CAFSF3XPsEYrLnS+zSyGnhBOzBEwK+75GbPPD9K9sO2NWosX6VQ@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).