unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Steve George <steve@futurile.net>
Cc: Arun Isaac <arunisaac@systemreboot.net>,
	Christopher Baines <mail@cbaines.net>, jgart <jgart@dismail.de>,
	Simon Tournier <zimon.toutoune@gmail.com>,
	guix-devel@gnu.org
Subject: Re: Committers available for Patch hacking/review meet-up?
Date: Wed, 14 Feb 2024 15:04:51 +0100	[thread overview]
Message-ID: <ZczIg6QL7131F7u7@jurong> (raw)
In-Reply-To: <d02eef04-46ba-42f0-9441-8b269c6fe7f7@futurile.net>

Hello,

thanks, Steve, for getting things going!

Am Tue, Feb 13, 2024 at 02:48:08PM +0000 schrieb Steve George:
> We said they'd be every 13 days, for 3 months to see if it has interest.
> Proposed calendar:
> 7th March (Thursday)

I will be around on this day.

> 2nd April (Tuesday)
> 15th April (Monday)
> 3rd May (Friday)
> 16th May (Thursday)
> 29th May (Wednesday)
> Each one held at 19:00 CET / 18:00 BST / 13:00 EST [0] for 1.5 hours.

For these, we will have the daylight savings time switch; so maybe we
should move to 19:00 CEST. Something we can do later.

> What I propose is that we'd do the following:
> 1 - 30 mins: a committer runs through their review process, and shows a
> recent patch or patches they've reviewed. Really informal showing what they
> do.

Well, I only ever look at simple packages, and do not think I have anything
resembling a process to share. But I will try to be around in any case :)

Andreas



  reply	other threads:[~2024-02-14 14:05 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-13 14:48 Committers available for Patch hacking/review meet-up? Steve George
2024-02-14 14:04 ` Andreas Enge [this message]
2024-02-15  8:34   ` Steve George
2024-02-14 14:20 ` Simon Tournier
2024-02-15  0:53 ` jgart
2024-02-15  8:36   ` Steve George

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=ZczIg6QL7131F7u7@jurong \
    --to=andreas@enge.fr \
    --cc=arunisaac@systemreboot.net \
    --cc=guix-devel@gnu.org \
    --cc=jgart@dismail.de \
    --cc=mail@cbaines.net \
    --cc=steve@futurile.net \
    --cc=zimon.toutoune@gmail.com \
    /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).