From: hiro <23hiro@gmail.com>
To: 9front@9front.org
Subject: Re: [9front] The 9 Documentation Project
Date: Tue, 28 Jul 2020 16:16:42 +0200 [thread overview]
Message-ID: <CAFSF3XMQRBSiRH=3jDWSu77pF2y-KHAMB4J5P5oADnJPg7BrfA@mail.gmail.com> (raw)
In-Reply-To: <7A5765F50E02CC5A77A31E80F4D0D3CF@sirjofri.de>
we need a clear, sane, documented process how to contribute.
what you are describing sounds like it could become that. of course
once we tested it out we need to also decide to start enforcing it,
too. somehow last time the part of the system that i knew about didn't
feel like it made enough sense to force it on anybody.
and yes, for some things sometimes you're the only one, i'm sure you
will be joined by others.
let's just hope sl agrees! :)
On 7/28/20, sirjofri+ml-9front@sirjofri.de
<sirjofri+ml-9front@sirjofri.de> wrote:
>> it seems to me we might profit from making you boss of documentation,
>> and whatever process you find will just have to become mandatory for
>> the rest of us.
>
> I don't know. That's exactly why I'm asking. I'm happy to help, eg I
> can set up a 9front wikifs server including auth and handle user
> registrations as well as structuring the wiki and editing it. I can
> also help managing changes and user feedback as well as asking
> original authors to contribute to the wiki.
>
> I can also try collecting wiki content and format it for inclusion
> into official 9front, if wanted, as well as sending patches to the
> fqa, but I want to encourage people to also do that.
>
> I hope we find a good and helpful process for all users and devs, and
> support developers so they don't need to handle everything. Also I
> hope I don't need to do everything alone, but I guess that's often the
> case in an open source world where no money is involved.
>
>
> sirjofri
>
>
next prev parent reply other threads:[~2020-07-28 14:16 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 [this message]
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
[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='CAFSF3XMQRBSiRH=3jDWSu77pF2y-KHAMB4J5P5oADnJPg7BrfA@mail.gmail.com' \
--to=23hiro@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).