9front - general discussion about 9front
 help / color / mirror / Atom feed
From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: 9front@9front.org
Subject: Re: [9front] 9front Programmer's Manual
Date: Sat, 7 Aug 2021 04:52:22 +0000 (UTC)	[thread overview]
Message-ID: <f539a047-9c03-4612-b37f-85b54d5bfcd6@sirjofri.de> (raw)
In-Reply-To: <18BDAB449FBB20989093FC284E3A89F1@eigenstate.org>


06.08.2021 17:05:30 ori@eigenstate.org:
> Quoth Humm <hummsmith42@gmail.com>:
>>
>> So, what’s the situation?  Are there any plans other than continuing
>> to let it rot?
>
> Updates and fixes to manpages are always
> welcome and applied regularly. Improving
> and fixing the build system is also good.
>
> But papers are papers. It seems strange
> to modify them. I think for papers, it
> makes most sense to add a 'changes since
> publication' document.

Absolutely, maybe as an appendix to the other documents or to the whole 
collection.

> I'd also like more tutorial or 'theory of
> operation' style docs that supplement the
> manpages, and show how parts of the system
> fit together, but I'm not much of a writer,
> and haven't put much thought into this.

Some people started writing stuff for the wiki, also the fqa contains 
some info (eg. Upas theory). I planned to write some papers about that 
when I had more time, but then I didn't have that time...

Personally, I like writing, although my language might not be sufficient.

Slightly offtopic, but I made pdf versions of the man pages available on 
my 9front public web server, especially for ereaders. I generally wanted 
to mirror some stuff.

sirjofri

  parent reply	other threads:[~2021-08-07  8:25 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-06 12:08 Humm
2021-08-06 13:37 ` qwx
2021-08-06 15:00   ` Humm
2021-08-06 13:49 ` qwx
2021-08-06 15:05 ` ori
2021-08-06 19:30   ` Stuart Morrow
2021-08-07  4:52   ` sirjofri [this message]
2021-08-20 11:26   ` Stuart Morrow
2021-08-06 15:06 ` Stanley Lieber
2021-08-06 19:34   ` Stuart Morrow
2021-08-07 11:37   ` Humm

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=f539a047-9c03-4612-b37f-85b54d5bfcd6@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).