9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri+ml-9front@sirjofri.de
To: 9front@9front.org
Subject: The 9 Documentation Project
Date: Mon, 27 Jul 2020 09:09:44 +0000 (UTC)	[thread overview]
Message-ID: <f8d547cd-70be-46e6-84fc-755089be5187@sirjofri.de> (raw)

Hello all,

I thought about this some time and think we can do documentation better. Of course we have the very good fqa (which is 9front "only") and the official man pages as well as other documentation sources and guides. Most of these guides are distributed in various personal blogs and contribution to man pages and the fqa takes time (patch creation, review).

Since many of us users do happily provide information and guides as well as write ups I think we can create one active place for documentation that's too much for the fqa and the man pages as well as highly dynamic with changes everyday. (I want to mention the arch wiki as an example.)

My dream is something like a publicly available wiki system (wikifs?) with good structure where every nine user can contribute to without review. It would be interesting to have real authenticated accounts for write access, but that might be too much.

Here are some points I thought about and we can discuss:


- the documentation is publicly available, readable for everyone
- only plan 9 users can write (to prevent spamming)
- users need only plan 9 board tools to access the wiki (no extra software needed)
- discussion board for pages/page sections (no email needed)
- discussion chat for real-time discussions about the wiki (like hubchat/ants, documentation related content preferred)
- multi-distribution support. Most users use 9front, but it's worth mentioning differences between systems. This should happen in a structured manner.
- documentation download: users can download pages for offline reading. Maybe typeset and/or different formats.
- having authenticated user access would be interesting to see how a public auth server can work. This is not necessary, but I think it's worth it (and it can be used for other future fileserver projects)

These are just some ideas we can discuss. Keep in mind I don't want to create another distributed source for documentation, but a central "wiki" you can use to share information with other users, so we can collect all undocumented knowledge in one place.

I know there are other wiki places, for example:

9gridchan wiki, with focus on ANTS tools and the public grid project. I don't think people go there for general plan 9 advise.

9p.io wiki, which is more like an archive for the original plan 9 wiki. I don't know who owns this and how actively it's used.

Also this is _not_ meant as a replacement for the man pages and the fqa. The project should also encourage users (and developers) to contribute to the man pages. There are programs that don't even have a man page, as well as missing important information.

With this I want to open the discussion, feel free to share your ideas and comments. I hope we can make some good documentation together.

sirjofri



             reply	other threads:[~2020-07-27  9:09 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-27  9:09 sirjofri+ml-9front [this message]
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=f8d547cd-70be-46e6-84fc-755089be5187@sirjofri.de \
    --to=sirjofri+ml-9front@sirjofri.de \
    --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).