unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed

From: zimoun <zimon.toutoune@gmail.com>
To: guix-devel@gnu.org
Cc: vagrant@debian.org
Subject: Re: Interest in "guix lint" Meetup?
Date: Fri, 18 Mar 2022 10:13:40 +0100	[thread overview]
Message-ID: <87a6dn8vy3.fsf@gmail.com> (raw)
In-Reply-To: 87pmmkt6k2.fsf@contorta

Hi,

> I haven't really done this sort of thing virtually before; Where would
> be a good place to host it?

We are definitively lacking a BBB instance or something for that. :-)
Depending on the numbers of participants, maybe Jami could be an
option.  IIRC, a service is around (an instance is even probably
available) and the client just works with Guix (last time I tried,
thanks Maxim! :-))

Well, I like the idea of one each day, for instance the traditional
"advent calendar" done by Debian Med.  Maybe it could also an option for
this housecleaning.  Say from now until April, 18th (Happy Birthday!
:-)), let clean as much as possible: lint fixes, close irrelevant
tickets, etc.  The most productive people win a drink next time we will
meet. :-)

Another option to embark people (or for motivation) is pair programming.
It could also ease the timezone constraint.  Jérémy (jeko) wrote a nice
blog post for a quick setup using Guix.

https://rednosehacker.com/how-to-setup-a-remote-pair-programming-environment-with-gnu-guix

(It appears to me being worth to turn it into a cookbook recipe, another
story. :-))


Cheers,
simon

next             reply	other threads:[~2022-03-18  9:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  9:13 zimoun [this message]
2022-03-18 13:27 ` Interest in "guix lint" Meetup? Maxime Devos
     [not found] <mailman.7411.1649757705.1276.guix-devel@gnu.org>
2022-04-12 12:06 ` Christopher Rodriguez
  -- strict thread matches above, loose matches on Subject: below --
2022-03-18  1:04 Vagrant Cascadian
2022-03-18  1:49 ` Matt
2022-04-11 20:19   ` Vagrant Cascadian
2022-04-12  9:38     ` Remco van 't Veer
2022-03-18 12:44 ` Matt

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=87a6dn8vy3.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=vagrant@debian.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

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