From: Tomas Volf <~@wolfsden.cz>
To: Steve George <steve@futurile.net>
Cc: help-guix@gnu.org, guix-devel@gnu.org
Subject: Re: You're invited to the first patch review session!
Date: Fri, 23 Feb 2024 20:13:22 +0100 [thread overview]
Message-ID: <ZdjuUotTJMk02Z2U@ws> (raw)
In-Reply-To: <wkb2fg4ucu336d4phpqfjovyw6qermqzdethp4cdwmouma7qjq@rl4uveuc363n>
[-- Attachment #1: Type: text/plain, Size: 1717 bytes --]
On 2024-02-22 23:27:31 +0000, Steve George wrote:
> Hi
>
> We're going to run some online patch review sessions. The first one is on *Thursday, 7th March* and you can sign-up here:
>
> https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024
>
> The background is that Guix has many fantastic contributions that are waiting to be reviewed and added to the archive. We have the QA system that does test builds, but each patch also needs to be evaluated and checked. Anyone can review patches, and reviews help to confirm that a patch is in good shape to be added to the archive.
>
> Doing patch reviews is also a great way to learn about Guix, the different packages and methods involved in packaging. To encourage new reviewers to step forward, and to have some fun we're going to run on-line patch review sessions. These will be informal, probably chaotic - but fun - with the aim that we learn as a group how to review packages.
>
> Each session will be hour 1:30 and they are rotating through the week, so there should be plenty of opportunities to come along. We're using the Guix London's Meet-up and the sessions run on Jitsi.
Will the Jitsi link be shared somewhere (here, irc, ...) for those of us who are
not able to sign up on the page? I am getting this error:
> Your IP address has been flagged as a source of spam and is blocked from
> Meetup.
Since meetup.com is a commercial, third-party service, I assume there is not
anything you can do about that, so I am curious if there are any alternatives
how to get into the review session.
Thank you and have a nice day,
Tomas Volf
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2024-02-23 19:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-22 23:27 You're invited to the first patch review session! Steve George
2024-02-22 23:53 ` Vagrant Cascadian
2024-02-23 6:11 ` Vivien Kraus
2024-02-23 14:59 ` Steve George
2024-02-23 19:13 ` Tomas Volf [this message]
2024-02-23 20:43 ` indieterminacy
2024-02-29 17:10 ` Daniel Littlewood
2024-02-29 17:35 ` Andreas Enge
-- strict thread matches above, loose matches on Subject: below --
2024-03-01 19:11 Suhail
2024-03-05 19:19 ` Etienne B. Roesch
2024-03-06 9:40 ` Andreas Enge
2024-03-06 11:28 ` Tomas Volf
2024-03-06 11:36 ` Etienne B. Roesch
2024-03-06 11:40 ` Tomas Volf
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=ZdjuUotTJMk02Z2U@ws \
--to=~@wolfsden.cz \
--cc=guix-devel@gnu.org \
--cc=help-guix@gnu.org \
--cc=steve@futurile.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).