From: Steve George <steve@futurile.net>
To: help-guix@gnu.org
Subject: Patch review meetup on Tuesday
Date: Sun, 31 Mar 2024 23:07:11 +0100 [thread overview]
Message-ID: <ZgnejxvHalsu4O99@t25sg> (raw)
Hi,
Our next online patch review is on:
Tuesday 17:00 UTC; 18:00 London; 19:00 Paris; 13:00 New York
Hopefully, we'll be able to have a few different rooms so that people can pair and work on patches together. Last time we used Upterm (https://upterm.dev/) so that everyone could ssh into a cloud host and take part. We can have more than two people in a session - so it will be more of a huddle!
If you'd like to take part in a room I've added a table to the Wiki so you can add yourself:
https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024
We'll need one co-ordinator for the room, and then multiple others can take part. I'll give the details of the hosts and passwords at the start of the session.
The Wiki also has the reports that I'm using to collect issues together and mark them as reviewed, and instructions on how to do reviews - check it all out if you'd like to take part!
Look forward to seeing you there!
Steve / Futurile (on behalf of the Guix London Team)
reply other threads:[~2024-03-31 22:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=ZgnejxvHalsu4O99@t25sg \
--to=steve@futurile.net \
--cc=help-guix@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.
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).