Hi,
I am very late to the party. :-)
On Thu, 04 Aug 2022 at 00:59, Nicolas Graves via wrote:
> I've some patches waiting to be merged, and was thinking about how to
> deal with that. (I understand that maintainers are few and probably
> overworked, I'm not criticizing anyone.)
I sympathize.
Hi,
Nicolas Graves skribis:
> Is there a requirement to help with patch reviewing? I feel I can tackle
> python or rust packages unless they are weird, I need not to spend too
> much time on that, but if it's just advising new beginners (I'm myself
> a 9 month old Guix user but went cold turkey
On 2022-08-09 22:54, Ludovic Courtès wrote:
> This was discussed recently on guix-devel and I hope we can collectively
> improve on that. The new teams that we devised (see ‘etc/teams.scm’)
> should help, though we have yet to document them and publicize them.
Thanks for your answer, I'll check
Hello Nicolas,
Thanks for your message. Patch review is overall rather slow due to a
mixture of Guix being a victim of its success and (perhaps more
importantly) having too few people devoting time to patch review, and
too few committers committing.
This was discussed recently on guix-devel and
Hi!
I've some patches waiting to be merged, and was thinking about how to
deal with that. (I understand that maintainers are few and probably
overworked, I'm not criticizing anyone.)
There are actually two problems in one :
1) how to manage and track series of patches one makes in his local
