unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Felix Lechner <felix.lechner@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Proposing commit access for 'unmatched-paren'
Date: Tue, 15 Nov 2022 15:55:16 -0500	[thread overview]
Message-ID: <87fseklyyz.fsf@gmail.com> (raw)
In-Reply-To: <CAFHYt57z--zu30aiR3J+iU+=-g=4HL_eUy7YDwFXOKRizr=Rgg@mail.gmail.com> (Felix Lechner's message of "Tue, 15 Nov 2022 10:32:45 -0800")

Hi Felix,

Felix Lechner <felix.lechner@gmail.com> writes:

> Hi,
>
> As a new user, I needed lots of help. I also use software that is not
> packaged in Guix.
>
> In preparing my patches for submission I relied extensively on the
> guidance so generously offered by the IRC user 'unmatched-paren'. I
> thoroughly appreciated their advice, both on the technical as well as
> on the human level.
>
> Now I learned that 'unmatched-paren' would like to request commit
> access to the Guix repository, but they were humbled by their own
> uncertainty on how to illustrate their value. I then offered to write
> this letter.
>
> Please consider 'unmatched-paren' for commit access. Thank you!
>
> Kind regards,
> Felix Lechner
>
> P.S. Anyone who reads this and agrees with me, please chime in by
> replying to this message. Thanks!

There's a process in place for that: see info '(guix) Commit Access'.

Note that it doesn't involve publicly voicing support for a person,
although it won't hurt.

-- 
Thanks,
Maxim


      parent reply	other threads:[~2022-11-15 20:56 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-15 18:32 Proposing commit access for 'unmatched-paren' Felix Lechner
2022-11-15 20:23 ` bokr
2022-11-15 20:39   ` (
2022-11-15 20:55 ` Maxim Cournoyer [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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=87fseklyyz.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=felix.lechner@gmail.com \
    --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 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).