From: Ian Eure <ian@retrospec.tv>
To: "Sergio Pastor Pérez" <sergio.pastorperez@outlook.es>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Request for assistance maintaining LibreWolf
Date: Sat, 17 Aug 2024 12:43:11 -0700 [thread overview]
Message-ID: <87h6bi6g5a.fsf@meson> (raw)
In-Reply-To: <PAXP251MB0348FCF488DA71284D05F70FF3822@PAXP251MB0348.EURP251.PROD.OUTLOOK.COM>
Hi Sergio,
Sergio Pastor Pérez <sergio.pastorperez@outlook.es> writes:
> Hello Ian.
>
> I cannot help you since I don't have commit access. But I want
> to thank
> you for your hard work, I'm currently using your package.
>
Thank you for the kind words, they truly mean a lot to me.
Whatever the state of Guix proper, you can always find the current
version of LibreWolf in my personal channel[1], though I don’t
have a public substitute server, so long build times will await
you if you choose this route.
> We should try to come up with a solution that alleviates the
> burden on
> the maintainers. Given how often this issue arises, what if we
> try, as
> a collective, to suggest new mechanisms that would improve the
> situation?
>
> If I recall correctly, someone suggested having a development
> branch in
> which, once the QA passes, the patches get automatically
> merged. I know
> some people rose concerns about the slowness of the QA system
> for this
> to be an effective solution, and there is also the issue
> ordering the
> patch application.
>
> If the previous solution is ruled out, I would like to know the
> opinion
> of the Guix community on a voting system. I'm imagining a system
> where
> we reuse the mailing infrastructure we have, where each accepted
> mail in
> the guix devel mailing list has 1 vote for a given patch, that
> way we
> avoid multiple votes from the same entity and would allow people
> without
> commit access, but active on the Guix development, to
> participate. So,
> we could set up a threshold where if a patch gets 10 votes from
> non-committers the merge would be done; preferably automated,
> but if it's
> not possible, committers would know what is ready to be merged
> without
> effort and what the community wants.
>
I’m not sure this would be effective, because the QA service is
unreliable. I regularly see patches which simply don’t get picked
up by it, including many of my own. At other times, it lags very
far behind. I don’t think it’s reliable enough to be in the
critical path for anything. Guix is supposed to be a
rolling-release distro, so it feels strange to have a develop
branch which moves even faster.
Thanks,
— Ian
[1]: https://codeberg.org/ieure/atomized-guix
next prev parent reply other threads:[~2024-08-17 20:37 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 [this message]
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
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=87h6bi6g5a.fsf@meson \
--to=ian@retrospec.tv \
--cc=guix-devel@gnu.org \
--cc=sergio.pastorperez@outlook.es \
/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.