unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Jonathan McHugh" <indieterminacy@libre.brussels>
To: "Blake Shaw" <blake@nonconstructivism.com>,
	"Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Formalizing teams
Date: Thu, 23 Dec 2021 21:51:21 +0000	[thread overview]
Message-ID: <5a1d9f608e098648daf3b34f173818ea@libre.brussels> (raw)
In-Reply-To: <87lf0bwe07.fsf@nonconstructivism.com>

December 23, 2021 4:13 PM, "Blake Shaw" <blake@nonconstructivism.com> wrote:

> Ludovic Courtès <ludo@gnu.org> writes:
> 
>> One idea that I like is to bring structure to the group, or rather to
>> make structure visible, so that newcomers know who they can talk to to
>> get started on a topic, know who to ping for reviews, and so that each
>> one of us can see where they fit. Rust has well-defined teams:
>> 
>> https://www.rust-lang.org/governance
> 
> Definitely! Perhaps this an aesthetic matter, but keeping-with the
> community spirit of Guix, and the existing nomenclature where the
> 'core' maintainers are called a "collective", perhaps we should avoid
> some of the more corporate "team" language of Rust/Mozilla and stick to
> "collectives"?
> 

I reckon 'coterie' is more elegant a term:
```
: an intimate and often exclusive group of persons with a unifying common interest or purpose
```


====================
Jonathan McHugh
indieterminacy@libre.brussels


  reply	other threads:[~2021-12-23 21:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 15:13 Formalizing teams Blake Shaw
2021-12-23 21:51 ` Jonathan McHugh [this message]
2021-12-24 12:23   ` Hartmut Goebel
2021-12-24 15:37     ` indieterminacy
  -- strict thread matches above, loose matches on Subject: below --
2021-12-22 15:46 Ludovic Courtès
2021-12-22 16:04 ` Jack Hill
2021-12-22 16:22   ` indieterminacy
2021-12-22 19:43 ` Filip Łajszczak
2022-01-03 15:09   ` Ludovic Courtès
2021-12-27  5:17 ` Maxim Cournoyer
2021-12-28 10:52   ` Lars-Dominik Braun
2021-12-28 15:44     ` Kyle Meyer
2021-12-28 18:03       ` Ricardo Wurmus
2021-12-29 21:04         ` Lars-Dominik Braun
2021-12-28 14:44   ` Ricardo Wurmus
2021-12-29  9:05     ` Efraim Flashner
2022-01-03 15:22     ` Ludovic Courtès
2022-01-03 15:57       ` Ricardo Wurmus
2022-01-04 22:35       ` adriano
2022-03-31 21:15       ` david larsson
2022-04-01  9:14         ` Ludovic Courtès

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5a1d9f608e098648daf3b34f173818ea@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=blake@nonconstructivism.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).