9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] 9front Committers (Was Re: [9fans] Software philosophy)
Date: Thu, 19 Aug 2021 15:16:41 -0400	[thread overview]
Message-ID: <E2545BBEB37A31190E473CBF0D61BC5F@eigenstate.org> (raw)
In-Reply-To: <YR6qMNUeJ4bDduMY@wopr>

Quoth Kurt H Maier <khm@sciops.net>:
> On Thu, Aug 19, 2021 at 11:53:52AM -0700, unobe@cpan.org wrote:
> > 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.
> > 
> 
> There was never a formal process for getting commit access to
> code.9front.org.  Generally someone would ask for it in the irc channel,
> and if nobody objected after a little while I'd just add them.  Ori's
> currently hosting the git repo, so I'll let him chime in on that if he
> wants.
> 
> khm
> 

Nothing's changed, beyond the people you ask. I run
the file server, sl runs the auth server, so we both
need to create accounts with a matching username.

I'd prefer to see patches before handing out commit
access, but so far everyone that's asked has gotten
a commit bit.


  reply	other threads:[~2021-08-20  9:08 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
2021-08-19 19:00   ` Kurt H Maier
2021-08-19 19:16     ` ori [this message]
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=E2545BBEB37A31190E473CBF0D61BC5F@eigenstate.org \
    --to=ori@eigenstate.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).