all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: Matt <matt@excalamus.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Interest in "guix lint" Meetup?
Date: Mon, 11 Apr 2022 13:19:12 -0700	[thread overview]
Message-ID: <871qy3qsov.fsf@contorta> (raw)
In-Reply-To: <17f9ab7833f.c3b8103d507528.448063817992004480@excalamus.com>

[-- Attachment #1: Type: text/plain, Size: 764 bytes --]

On 2022-03-17, Matt wrote:
>  ---- On Thu, 17 Mar 2022 21:04:13 -0400 Vagrant Cascadian <vagrant@debian.org> wrote ----
>  > The description and synopsis fixes are generally pretty easy, so might
>  > make for good first steps for someone wanting to get familiar with the
>  > process of contributing without having to invest a whole lot of time and
>  > energy.
>
> I would like to look over the shoulder of or pair programming with
> someone working on Guixy things. Count me in. I think this is a great
> idea.

Well, not sure if there is other overly quiet interest lurking on the
sidelines, but would be happy to figure out a time to crank through a
few of these with you!

Would it also make sense to email guix-help about it as well?


live well,
  vagrant

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  reply	other threads:[~2022-04-11 20:20 UTC|newest]

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

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

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

  git send-email \
    --in-reply-to=871qy3qsov.fsf@contorta \
    --to=vagrant@debian.org \
    --cc=guix-devel@gnu.org \
    --cc=matt@excalamus.com \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.