unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: indieterminacy <indieterminacy@libre.brussels>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, GNU Guix maintainers <guix-maintainers@gnu.org>
Subject: Re: Teams
Date: Sun, 05 Jun 2022 12:30:52 +0200	[thread overview]
Message-ID: <1d4ecb08a874ff46368110f3e8bb3724@libre.brussels> (raw)
In-Reply-To: <87a6as62r2.fsf@elephly.net>

FWIW,

I just want to commend whoever is packaging TexLive.

My last update covered March of this year - no mean feat given that it 
is a 3.4GB package aggregate.

(sorry I cant do more direct contributions for Guix atm, looking forward 
to such an honour eventually)

On 04-06-2022 14:07, Ricardo Wurmus wrote:
> Hi Guix,
> 
> this is not a new idea[1]: let’s add a page to the website that lists 
> teams
> and a mail alias for each of the teams.
> 
> For example, the “R team” consists of people familiar with how R
> packaging works in Guix, e.g. Simon and myself.  There would be an 
> alias
> “guix-team-r@gnu.org”.  People with questions about R in Guix could
> write an email to that alias.
> 
> Mumi could also send email to guix-team-r@gnu.org to remind them about
> patches relating to R / Bioconductor / CRAN, etc.
> 
> Maintainers could write to these teams before releases to ask if there
> are any obstacles to a release.
> 
> As a first step I’d suggest collecting teams, setting up the email
> aliases, and updating the website to show the existing teams.  Here’s
> a draft of three teams:
> 
> * R team
> Simon Tournier
> Ricardo Wurmus
> 
> * Java team
> Julien Lepiller
> 
> * Rust team
> Efraim Flashner
> Aleksandr Vityazev
> Arun Isaac
> John Soo
> Maxim Cournoyer
> Nicolas Goaziou
> Tobias Geerinckx-Rice
> 
> What do you think?

-- 
Jonathan McHugh
indieterminacy@libre.brussels


  parent reply	other threads:[~2022-06-05 10:31 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-04 12:07 Teams Ricardo Wurmus
2022-06-04 13:00 ` Teams Maxime Devos
2022-06-04 13:19 ` Teams Ekaitz Zarraga
2022-06-04 14:50 ` Teams Tobias Geerinckx-Rice
2022-06-04 15:52   ` Teams Maxime Devos
2022-06-04 15:56   ` Teams david larsson
2022-06-05  9:10   ` Teams pelzflorian (Florian Pelz)
2022-06-07  4:11     ` Teams Thiago Jung Bauermann
2022-06-05  8:19 ` Teams Josselin Poiret
2022-06-06 21:21   ` Teams Ludovic Courtès
2022-06-14 11:31   ` Teams Andrew Tropin
2022-06-14 18:52     ` Teams Blake Shaw
2022-06-15  6:19       ` how to write services (was: Re: Teams) catonano
2022-06-15 13:53         ` Ricardo Wurmus
2022-06-15 17:01           ` Blake Shaw
2022-06-15 17:32             ` Maxime Devos
     [not found]               ` <CAKjmbcA56WL8ude232fz_5_G9U2RfoNNf4gqMHu5tft5kMbjFQ@mail.gmail.com>
2022-06-15 22:04                 ` Maxime Devos
2022-06-15 22:13                 ` Maxime Devos
2022-06-15 22:28                 ` Maxime Devos
2022-06-15 23:20                   ` Blake Shaw
2022-06-16  8:27                     ` Maxime Devos
2022-06-16  5:14             ` catonano
2022-06-16  6:46               ` Ricardo Wurmus
2022-06-16 13:09               ` Brian Cully via Development of GNU Guix and the GNU System distribution.
2022-06-18 11:53                 ` how to write services indieterminacy
2022-06-18 12:23                   ` Maxime Devos
2022-06-18 13:33                     ` indieterminacy
2022-06-15 10:53       ` How to write a service (was: Re: Teams) catonano
2022-06-05  9:31 ` Teams Lars-Dominik Braun
2022-06-05  9:51 ` Teams zimoun
2022-06-05 10:00   ` Teams Julien Lepiller
2022-06-07 17:49   ` Teams Efraim Flashner
2022-06-05  9:51 ` Teams Andreas Enge
2022-06-09  4:39   ` Teams Eric Bavier
2022-06-05 10:30 ` indieterminacy [this message]
2022-06-05 17:59 ` Teams Mathieu Othacehe
2022-06-06 21:26   ` Teams Ludovic Courtès
2022-06-06 14:12 ` Teams Maxim Cournoyer
2022-06-07  0:28 ` Teams Ryan Prior
2022-06-07 19:06 ` Teams Vagrant Cascadian
2022-06-08 21:30   ` Teams Ludovic Courtès
2022-06-09  2:21     ` Teams Thiago Jung Bauermann
2022-06-09 19:28 ` Teams Arun Isaac
2022-06-13 13:38   ` Teams Blake Shaw
2022-06-13 22:33     ` Teams raingloom
2022-06-21 15:21 ` Teams: first draft list zimoun
2022-06-21 17:28   ` bokr
2022-06-21 22:21     ` zimoun
2022-06-22  6:56       ` Efraim Flashner
2022-06-22 16:19         ` bokr
2022-06-22  7:59   ` Ricardo Wurmus
2022-06-22  9:19     ` zimoun
2022-06-22 12:30       ` Josselin Poiret
2022-06-22 13:10         ` Maxime Devos
2022-06-22 13:49     ` Ludovic Courtès
2022-06-22 14:18       ` Blake Shaw
2022-07-01 10:28       ` Ricardo Wurmus
2022-07-01 17:36         ` Liliana Marie Prikler
2022-07-01 19:08           ` Ricardo Wurmus
2022-07-03 13:04             ` Teams: please add yourself to etc/teams.scm.in Ricardo Wurmus
2022-07-03 14:51               ` Andreas Enge
2022-07-01 20:53   ` Teams: first draft list Leo Famulari
     [not found] <mailman.14592.1655210857.1233.guix-devel@gnu.org>
2022-06-15  2:26 ` Teams jgart

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=1d4ecb08a874ff46368110f3e8bb3724@libre.brussels \
    --to=indieterminacy@libre.brussels \
    --cc=guix-devel@gnu.org \
    --cc=guix-maintainers@gnu.org \
    --cc=rekado@elephly.net \
    /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).