9front - general discussion about 9front
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9front@9front.org
Subject: Re: [9front] Questions about community dynamics
Date: Sun, 24 Sep 2023 12:10:04 -0400	[thread overview]
Message-ID: <AB8856CD6456E7C4532F41567DBE7DF7@eigenstate.org> (raw)
In-Reply-To: <AEF211ACAE287093255CC425BDAB7D68@eigenstate.org>

Quoth ori@eigenstate.org:
> Quoth ieliedonge@wilsonb.com:
> > How do things generally get decided around here: e.g. patches merged, meetings
> > planned, etc?
> 
> Someone decides they want to do something. They do it.
> 
> To commit, either run git/push or find someone that
> can. If uncertain about committing, ask for feedback.
> As a rule of thumb, talking about designs is a good idea.
> Getting some miles on big changes before committing is
> another.
> 
> There's no formal process. Use your judgement.
> 

this also goes for meetings and hackathons; someone says
"hey, want to hang out?" or "hey, want to talk about X?",
and drops a link to a jitsi; we hang out on the jitsi a
while, people come and go.

hackathons are a bit more involved, since you actually
need a space and people travel, but the principle is the
same -- "hey, I want a hackathon, who's in?", and then
stepping up to make it happen.

This is a hobby project.


      reply	other threads:[~2023-09-24 16:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-23 22:53 ieliedonge
2023-09-23 23:05 ` hiro
2023-09-23 23:19 ` Jacob Moody
2023-09-24  0:02   ` ieliedonge
2023-09-24  0:37     ` sl
2023-09-24  1:18     ` Kurt H Maier
2023-09-27  3:04       ` ieliedonge
2023-09-24 15:43 ` ori
2023-09-24 16:10   ` ori [this message]

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=AB8856CD6456E7C4532F41567DBE7DF7@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).