From: "Ethan Gardener" <eekee57@fastmail.fm>
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Sat, 01 Aug 2020 16:42:37 +0100 [thread overview]
Message-ID: <95dce504-fe7e-4c29-b05f-26eadfcc2424@www.fastmail.com> (raw)
In-Reply-To: <16BE402B539CD2C5067BAE84CFE71F56@a-b.xyz>
On Fri, Jul 31, 2020, at 2:44 PM, kvik@a-b.xyz wrote:
> For the past few days I procrastinated on a school project, which
> resulted in what you are free to call a wiki. [1]
>
> It is proudly a dumping ground for 9-adjacent information, some of which
> you could call documentation.
>
> The intention and hope for it is to house information that might not
> neatly fit the finite purpose of a manual page, the book format of the
> FQA, or the importance and outdatedness of a /sys/doc paper. I also see
> it reasonably serving the role of a working bench for documents that
> might become a part of the above forms of documentation.
>
> This is a lot of results to hope for from making and hosting some
> software — hope that I would have lost without the enthusiasm shown by
> the few people already making contributions in code and content.
>
> Some technical details behind this are described at [2].
>
> Not much is set in stone just yet, and I'd love making a system people
> will enjoy using, so feel free to drop concrete suggestions if you have
> some.
>
> [1] http://docs.a-b.xyz
> [2] http://docs.a-b.xyz/this.html
Good to see something's being done!
I find I'm curiously pleased to see rc-httpd is not involved. Must be my love for diversity.
next prev parent reply other threads:[~2020-08-01 15:42 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
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 [this message]
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=95dce504-fe7e-4c29-b05f-26eadfcc2424@www.fastmail.com \
--to=eekee57@fastmail.fm \
--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).