unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
* Setup a remote pair-programming environment
@ 2022-02-23 22:14 Jérémy Korwin-Zmijowski
  2022-02-24  2:19 ` Maxim Cournoyer
  0 siblings, 1 reply; 3+ messages in thread
From: Jérémy Korwin-Zmijowski @ 2022-02-23 22:14 UTC (permalink / raw)
  To: Help Guix


[-- Attachment #1.1.1: Type: text/plain, Size: 1063 bytes --]

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


[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 2525 bytes --]

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 665 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Setup a remote pair-programming environment
  2022-02-23 22:14 Setup a remote pair-programming environment Jérémy Korwin-Zmijowski
@ 2022-02-24  2:19 ` Maxim Cournoyer
  2022-04-28  8:33   ` zimoun
  0 siblings, 1 reply; 3+ messages in thread
From: Maxim Cournoyer @ 2022-02-24  2:19 UTC (permalink / raw)
  To: Jérémy Korwin-Zmijowski; +Cc: Help Guix

Hi Jérémy,

Jérémy Korwin-Zmijowski <jeremy@korwin-zmijowski.fr> writes:

> 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.

It sure sounds fun!

> 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-guixn
> Here is the like of my repo with my setup:
> https://framagit.org/Jeko/pair-programming-vm

Working in pair from a VM is an interesting idea.
Near the end of your blog post, you wrote:

> One the communication side, Jitsi is fine. But there could be something
> more suited for remote pair-programming sessions. I read about a Jami
> service…

As the jami-service-type implementer, I'd be happy to help you with
that, if you have any question setting it up, or issues after.

Thanks for sharing!

Maxim


^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: Setup a remote pair-programming environment
  2022-02-24  2:19 ` Maxim Cournoyer
@ 2022-04-28  8:33   ` zimoun
  0 siblings, 0 replies; 3+ messages in thread
From: zimoun @ 2022-04-28  8:33 UTC (permalink / raw)
  To: Maxim Cournoyer, Jérémy Korwin-Zmijowski; +Cc: Help Guix

Hi Maxim,

I am late to the party. :-)

On Wed, 23 Feb 2022 at 21:19, Maxim Cournoyer <maxim.cournoyer@gmail.com> wrote:

>> 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.
>
> It sure sounds fun!

It was really fun! :-)

It is a really good way to learn both sides and also discuss some
workflow tips barely discussed otherwise.

However, it requires some time.  I would recommend slots of 2h every
week.  From one session to the other, we “forgot” what we already did
and weekly seems enough for not forgetting too much. ;-)  And 2h means
more or less only 1h of productive work, all the other is about tiny
technical issues, resume, discuss tips, etc.

I am really happy with the experience!  Thanks Jérémy for the
proposition! :-)


>> One the communication side, Jitsi is fine. But there could be something
>> more suited for remote pair-programming sessions. I read about a Jami
>> service…
>
> As the jami-service-type implementer, I'd be happy to help you with
> that, if you have any question setting it up, or issues after.

At the time, the jami-service-type did not exist. ;-)

Well, I know you are hosting a rendezvous point.  Maybe it could be nice
to add to the Cookbook both (how to setup a pair programming VM and how
to setup a Jami rendezvous) could be really worth.

Bah I have started to convert the Jérémy’s blog post to texi but then I
have forgotten to submit the patch.  Maybe I will resume… if no one
beats me. ;-)

It could be nice to have this “how to setup Jami” in the Cookbook.
WDYT?



Cheers,
simon


^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2022-04-28  8:41 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-02-23 22:14 Setup a remote pair-programming environment Jérémy Korwin-Zmijowski
2022-02-24  2:19 ` Maxim Cournoyer
2022-04-28  8:33   ` zimoun

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).