all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Vagrant Cascadian <vagrant@debian.org>
To: guix-devel@gnu.org
Subject: Interest in "guix lint" Meetup?
Date: Thu, 17 Mar 2022 18:04:13 -0700	[thread overview]
Message-ID: <87pmmkt6k2.fsf@contorta> (raw)

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

Hey folks, was wondering if there would be interest in doing a virtual
meetup where we try and fix issues revealed by "guix lint".

On a fairly recently pulled guix:

  $ guix lint --checkers=description > guix-lint-description
  $ guix lint --checkers=synopsis > guix-lint-description
  $ wc -l guix-lint
  365 /home/vagrant/guix-lint-description
  169 /home/vagrant/guix-lint-synopsis
  534 total

That's over 500 mostly trivial issues to fix!

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.

For someone looking for slightly more adventurous things, one could try
fixing other issues guix lint knows about, or fix all issues of a
particular package, or incorporating guix lint knowledge directly into
importers, etc.!


It would be a nice bit of housecleaning. :)

Anyone interested?


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


live well,
  vagrant

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

             reply	other threads:[~2022-03-18  1:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-18  1:04 Vagrant Cascadian [this message]
2022-03-18  1:49 ` Interest in "guix lint" Meetup? Matt
2022-04-11 20:19   ` Vagrant Cascadian
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=87pmmkt6k2.fsf@contorta \
    --to=vagrant@debian.org \
    --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 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.