From: Steve George <steve@futurile.net>
To: help-guix@gnu.org, guix-devel@gnu.org
Subject: Thanks for attending the first patch review session!
Date: Thu, 7 Mar 2024 22:54:39 +0000 [thread overview]
Message-ID: <acb0a382-9ee3-4add-acf2-861fbd6d3a49@futurile.net> (raw)
Hi everyone,
Just wanted to say thanks to everyone who came along to Guix London's
first patch review session!
Along with a special thanks to Andreas Enge for jumping in as our first
committer showing how he reviews and answering a host of questions.
Arun, Chris, Fabio and I were really excited to see you all!
I hope you'll allow a little bit of chaos as it's the first time we've
tried this - plus my 'robot voice' when I demo'd!
Next time we'll split into some breakout rooms much faster so that
everyone can work together and help each other at the right level.
If you have time to dig-in and review some patches before next time,
check out the 'step-by-step' instructions on the Wiki:
https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024
Would love your feedback or edits.
There are also links to the patch-review-hackers-list list [0] and
explanations of the other usertags reports.
Our next session is on Wednesday March 20th - this is a mixed session -
if you're in London you can join Arun, Chris and Fabio in person. Or you
can be virtual and with a robot voice, like me!
We're looking for feedback on how to make the sessions work for everyone
- if you'd like to help in any way give us a shout!
Steve (on behalf of the Guix London team)
p.s. we haven't forgotten about the questions that were asked, we'll
collect those together into an FAQ and add them to the wiki page.
[0]
https://debbugs.gnu.org/cgi-bin/pkgreport.cgi?tag=patch-review-hackers-list;users=guix
reply other threads:[~2024-03-07 22:55 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=acb0a382-9ee3-4add-acf2-861fbd6d3a49@futurile.net \
--to=steve@futurile.net \
--cc=guix-devel@gnu.org \
--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.
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).