9front - general discussion about 9front
 help / color / mirror / Atom feed
From: Humm <hummsmith42@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] 9front Programmer's Manual
Date: Fri, 6 Aug 2021 17:00:55 +0200	[thread overview]
Message-ID: <YQ1Op7p9jIE7NcQ7@beryllium.local> (raw)
In-Reply-To: <11C4171FCBD89BCE076D20CB19C8B7CF@wopr.sciops.net>

> Are you volunteering?  As with other things, people propose then do 
> nothing.  It's annoying and comes up again and again.  It's already 
> great that we have so many articles written in the fqa, wiki and 
> elsewhere, but it's a difficult and time-consuming job for any one 
> person.  I'm trying to help a little bit by working on parts of the 
> fqa but it's taking forever.  Others do too.

I’m open for doing work on the manual.

> I doubt any contributions would ever be unwelcome.  A 9front 
> programmer's manual would be nice.  It would be great if you made 
> one.

We have one already.  With mostly fine man pages and some papers, some 
of them not quite up to date, with the potential of putting even more 
material in there.

I’m mostly talking about the framework around it, the “Programmer’s 
Manual” part, the title page and ToC, the notion of one manual.  And 
that, we already have (see tcp!9p.zone!9991 /humm/print.pdf).

If we do want to keep that, we could also migrate stuff from the FQA 
there or merge them completely or do whatever else with it.

-- 
Humm

  reply	other threads:[~2021-08-06 22:11 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 [this message]
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
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=YQ1Op7p9jIE7NcQ7@beryllium.local \
    --to=hummsmith42@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).