all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ian Eure <ian@retrospec.tv>
To: Suhail Singh <suhailsingh247@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Request for assistance maintaining LibreWolf
Date: Sat, 17 Aug 2024 21:07:54 -0700	[thread overview]
Message-ID: <87v7zy4gk0.fsf@meson> (raw)
In-Reply-To: <87ikvyvjcb.fsf@gmail.com>


Suhail Singh <suhailsingh247@gmail.com> writes:

> Ian Eure <ian@retrospec.tv> writes:
>
>> The initial patch to update the version to 127.x was submitted 
>> on June
>> 29th; updated to 128.x on July 17th; and I’ll be sending the 
>> patch
>> updating it to 129.x later today, after I’ve finished building 
>> and
>> testing it.
>
> Thank you for your continued commitment to this despite the lack 
> of
> timely review.
>

I appreciate your kind words; thank you.


>> I’m stuck in an impossible situation.  I can’t apply for 
>> committer access until
>> I have more accepted contributions, but can’t build those 
>> contributions unless
>> my patches are reviewed.  It’s frustrating and demoralizing.
>
> I can empathize.  I decided to take a step back from posting
> contributions earlier this year for similar reasons.  I am 
> hopeful this
> can improve in the (near) future.
>

I’m feeling very similarly, and have been biasing to maintaining 
my own channel lately.


>> A second, and smaller question, is: is there a mechanism to 
>> direct others’
>> contributions to LibreWolf to me for review, without 
>> subscribing to every patch
>> sent to Guix?  I have seen some patches, and participated, but 
>> I have to go look
>> for those, and it’d be more convenient if they were directed to 
>> me in the first
>> place.
>
> I believe the usual way of doing something like this is via 
> teams (see
> ./etc/teams.scm ).
>

I’m not sure whether/how well this mechanism works for 
non-committers.

Thanks,
  — Ian


  reply	other threads:[~2024-08-18  4:11 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-17 16:44 Request for assistance maintaining LibreWolf Ian Eure
2024-08-17 18:00 ` Sergio Pastor Pérez
2024-08-17 19:43   ` Ian Eure
2024-08-18  8:35   ` Christopher Baines
2024-08-18 16:50     ` Ian Eure
2024-08-19  1:53       ` Suhail Singh
2024-08-19  8:53       ` Christopher Baines
2024-08-19 23:14         ` Ian Eure
2024-09-12  1:01           ` Maxim Cournoyer
2024-08-19 17:01     ` Sergio Pastor Pérez
2024-08-18  8:37   ` Attila Lendvai
2024-08-18  9:07     ` Lars-Dominik Braun
2024-08-17 20:36 ` Ian Eure
2024-08-17 23:08 ` Suhail Singh
2024-08-18  4:07   ` Ian Eure [this message]
2024-08-18 21:17     ` Tomas Volf
2024-08-21 20:54       ` Ludovic Courtès
2024-08-22 15:00         ` Ian Eure
2024-08-28 20:48           ` Ludovic Courtès
2024-08-28 23:15             ` Ian Eure
2024-08-29  7:30               ` Tobias Geerinckx-Rice
2024-08-29 20:24                 ` [Browser-Team] " André Batista
2024-08-30 20:14                   ` Ludovic Courtès
2024-08-22 16:37         ` André Batista
2024-08-28 20:46           ` Ludovic Courtès
2024-08-30 20:18             ` Defining the role of teams Ludovic Courtès
2024-08-28 23:16           ` Request for assistance maintaining LibreWolf Ian Eure
     [not found] <mailman.5970.1723926982.21382.guix-devel@gnu.org>
2024-08-18  0:11 ` Andy Tai
2024-08-18  0:48   ` Ian Eure

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=87v7zy4gk0.fsf@meson \
    --to=ian@retrospec.tv \
    --cc=guix-devel@gnu.org \
    --cc=suhailsingh247@gmail.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.