guix-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Simplify contribution by using user-friendly bug tracker and git int


From: Steve George
Subject: Re: Simplify contribution by using user-friendly bug tracker and git interface
Date: Sun, 1 Sep 2024 17:13:00 +0100

Hi Jan,

There are multiple ways to set-up for creating and dealing with patches. We've 
been organising 'monthly' online meetups to review patches. As part of that I 
spent some time writing a 'how-to' with bulleted instructions. It might be 
useful *in addition* to the manual:

https://libreplanet.org/wiki/Group:Guix/PatchReviewSessions2024

As I say, there are many ways to do this, this is one way and I tried to make 
it very 'direct'. 

Jgart also did a video on how to use a different interface Mumi, which was 
created for Guix:

https://youtu.be/8m8igXrKaqU

Hope this helps!

Steve / Futurile



On 31 Aug, Ekaitz Zarraga wrote:
> Hi
> 
> On 2024-08-31 15:44, Jan Wielkiewicz wrote:
> > 
> > I apologize for my emotional and not constructive reply at first, I'll
> > try making more constructive replies next time.
> 
> No, don't worry about it. It is a normal reaction and I'm glad you started
> there because we were able to create something from it.
> 
> > As for help, now I'm good because I managed to send patches
> > correctly-ish. I'll probably end up looking for another email provider.
> > The issue that needs to be addressed however is the documentation, this
> > page to be precise:
> > https://guix.gnu.org/en/manual/devel/en/html_node/Sending-a-Patch-Series.html
> > I propose turning it into numbered list of things a contributors needs
> > to do in order to successfully sending 1) a single patch or 2) a patch
> > series, with clearly visible headers. Then as I mentioned in the
> > previous reply, sections such as "Canceling Issue", "Adding More
> > Patches", "Updating/Changing the Patch Series" and "Troubleshooting"
> > should be added. This should make the guide easier to follow and more
> > friendly. The "Troubleshooting" section should cover typical
> > mistakes/errors and mention the issue we were having.
> > That way possible contributors will at least have a hint what could be
> > wrong with their setup, which should limit the level of frustration.
> > You could also add "make sure to ask on the IRC or mailing list first
> > if you can't resolve the issue".
> > 
> > That should do.
> 
> Good, I'll get to it. I'll send you the patch for review :)
> 
> Thanks for the guidance, it will be helpful for newcomers. I'm sure.
> 
> Best,
> Ekaitz
> 
> 



reply via email to

[Prev in Thread] Current Thread [Next in Thread]