From: Steve George <steve@futurile.net>
To: Ekaitz Zarraga <ekaitz@elenq.tech>
Cc: Jan Wielkiewicz <tona_kosmicznego_smiecia@interia.pl>,
guix-devel@gnu.org
Subject: Re: Simplify contribution by using user-friendly bug tracker and git interface
Date: Sun, 1 Sep 2024 17:13:00 +0100 [thread overview]
Message-ID: <ovfldmoyd5xg2dl725urzkjpykofbqwyy7dqpbzi74yf6ifmac@6f3i2usi4n2v> (raw)
In-Reply-To: <9b96a142-d319-4cd0-c676-6f227431ad25@elenq.tech>
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
>
>
next prev parent reply other threads:[~2024-09-01 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 22:35 Simplify contribution by using user-friendly bug tracker and git interface Jan Wielkiewicz
2024-08-30 23:45 ` Ekaitz Zarraga
2024-08-31 12:05 ` Jan Wielkiewicz
2024-08-31 13:05 ` Ekaitz Zarraga
2024-08-31 13:44 ` Jan Wielkiewicz
2024-08-31 21:14 ` Suhail Singh
2024-08-31 21:42 ` Ekaitz Zarraga
2024-09-01 16:13 ` Steve George [this message]
2024-08-31 19:26 ` Attila Lendvai
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=ovfldmoyd5xg2dl725urzkjpykofbqwyy7dqpbzi74yf6ifmac@6f3i2usi4n2v \
--to=steve@futurile.net \
--cc=ekaitz@elenq.tech \
--cc=guix-devel@gnu.org \
--cc=tona_kosmicznego_smiecia@interia.pl \
/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.