unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
To: "Jérémy Korwin-Zmijowski" <jeremy@korwin-zmijowski.fr>
Cc: guile-user <guile-user@gnu.org>
Subject: Re: Setup a remote pair-programming environment
Date: Thu, 24 Feb 2022 14:51:05 -0800	[thread overview]
Message-ID: <CA+XASoWbL5-U+5GCJ2AoV1QV_4MmqA1TchugVSozeOkfzOKGEw@mail.gmail.com> (raw)
In-Reply-To: <5823f89b-d06c-7a4c-28b2-158ccc61faf2@korwin-zmijowski.fr>

Thanks for sharing!

On Wed, Feb 23, 2022 at 2:23 PM Jérémy Korwin-Zmijowski <
jeremy@korwin-zmijowski.fr> wrote:

> Dear Guixters,
>
> I realised I have not shared my last blog post about Guix with you here.
>
> It's about how I used Guix to set up a remote pair-programming
> environment (mostly to hack with Guile). I mean somewhere I could hack
> with another person.
> For example:
> - I introduced people to Guile and Test Driven Development.
> - Simon introduced me to Guix contribution through bug fixing !
>
> Our setup was pretty experimental but we were able to pull Guix sources,
> compile, edit in Emacs, etc.
> We were using Jitsi to talk to each other.
>
> That was fun, really fun (at least for me haha).
> I enjoy this way to share knowledge, demonstrate, mentor, etc. More than
> reading or watching content from you all.
>
> And I hope some of you will enjoy doing remote pair-programming as much
> as I did.
>
> Here is the link of the blog post:
>
> https://tiny.write.as/jeko/how-to-setup-a-remote-pair-programming-environment-with-gnu-guix
> Here is the like of my repo with my setup:
> https://framagit.org/Jeko/pair-programming-vm
>
> Love you, take care !
>
> Jérémy
>
>


      parent reply	other threads:[~2022-02-24 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-23 22:12 Setup a remote pair-programming environment Jérémy Korwin-Zmijowski
2022-02-23 22:38 ` Jérémy Korwin-Zmijowski
2022-02-24 22:51 ` Aleix Conchillo Flaqué [this message]

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://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+XASoWbL5-U+5GCJ2AoV1QV_4MmqA1TchugVSozeOkfzOKGEw@mail.gmail.com \
    --to=aconchillo@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=jeremy@korwin-zmijowski.fr \
    /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).