From: unobe@cpan.org
To: 9front@9front.org
Subject: [9front] 9front Committers (Was Re: [9fans] Software philosophy)
Date: Thu, 19 Aug 2021 11:53:52 -0700 [thread overview]
Message-ID: <84BB69110DA4209EC08080E265045F4F@smtp.pobox.com> (raw)
In-Reply-To: <7A5C8F1F-58D0-4BEE-96EE-06168FEF5930@pixelheresy.com>
Quoth Keith Gibbs <k@pixelheresy.com>:
> In fact, 9front development is highly decentralized in authority and everyone seems to spot, review, critique, and gatekeep each other, rather than any person having a single final say.
So commit bits are handed out freely to anyone who asks?
Some background: I used to be involved in Perl 6 development (Raku)
and Autrijius did just that--anyone who wanted a commit bit got one.
Highly decentralized, but by necessity there was some centralization
in terms of where the repo was hosted.
P.S. Posting to 9front in case this is too off-topic for 9fans.
next parent reply other threads:[~2021-08-19 18:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7A5C8F1F-58D0-4BEE-96EE-06168FEF5930@pixelheresy.com>
2021-08-19 18:53 ` unobe [this message]
2021-08-19 19:00 ` Kurt H Maier
2021-08-19 19:16 ` ori
2021-08-19 20:55 ` hiro
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=84BB69110DA4209EC08080E265045F4F@smtp.pobox.com \
--to=unobe@cpan.org \
--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).