From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 30992 invoked from network); 6 Aug 2021 22:12:55 -0000 Received: from 1ess.inri.net (216.126.196.35) by inbox.vuxu.org with ESMTPUTF8; 6 Aug 2021 22:12:55 -0000 Received: from mimir.eigenstate.org ([206.124.132.107]) by 1ess; Fri Aug 6 11:12:27 -0400 2021 Received: from abbatoir.myfiosgateway.com (pool-74-108-56-225.nycmny.fios.verizon.net [74.108.56.225]) by mimir.eigenstate.org (OpenSMTPD) with ESMTPSA id 085bb157 (TLSv1.2:ECDHE-RSA-AES256-SHA:256:NO) for <9front@9front.org>; Fri, 6 Aug 2021 08:05:31 -0700 (PDT) Message-ID: <18BDAB449FBB20989093FC284E3A89F1@eigenstate.org> To: 9front@9front.org Date: Fri, 06 Aug 2021 11:05:30 -0400 From: ori@eigenstate.org In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 8bit List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: overflow-preventing advanced realtime enhancement Subject: Re: [9front] 9front Programmer's Manual Reply-To: 9front@9front.org Precedence: bulk Quoth Humm : > > 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. 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.