unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Steve George <steve@futurile.net>
To: guix-devel@gnu.org
Subject: Coordinators for patch review session on Tuesday
Date: Sun, 31 Mar 2024 22:58:46 +0100	[thread overview]
Message-ID: <ZgnclribWWMF4Cho@t25sg> (raw)

Hi all,

The next patch-review session is taking place on Tuesday 2nd of March [0] and I'd love to try pair-programming where groups can actively work on some patch reviews.

Is anyone willing to 'co-ordinate' a pair programming session?

Last time I set-up a cloud host and installed Upterm (https://upterm.dev/) so that everyone could ssh into a session. We could run 4-5 simultaneous sessions where people could 'pair' to do patch reviews together. 

To co-ordinate a session I'll give you SSH access and there are instructions on how to launch the Upterm session. We have written instructions on some basic tools to do the patch reviews - and as Guix is installed for each user you can add your own ;-)

Anyone up for it?

I'm also collecting simple patches for review onto a list so they can be assigned to each group:

https://debbugs.gnu.org/cgi-bin/pkgreport.cgi?tag=patch-review-hackers-list;users=guix

Feel free to add simple issues there!

Thanks,

Futurile / Steve

[0] https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024#Patch_Review_Sessions_2024


             reply	other threads:[~2024-03-31 21:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-31 21:58 Steve George [this message]
2024-04-02 10:09 ` Coordinators for patch review session on Tuesday Christina O'Donnell
2024-04-02 20:23   ` Steve George
2024-04-03 11:00     ` Christina O'Donnell
2024-04-03 23:01       ` Christina O'Donnell
2024-04-04 14:57       ` Steve George
2024-04-04 17:27         ` Christina O'Donnell
2024-04-05  7:54           ` 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=ZgnclribWWMF4Cho@t25sg \
    --to=steve@futurile.net \
    --cc=guix-devel@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).