Re: Pain points in Git's patch flow

From: Bagas Sanjaya <bagasdotme@gmail.com>
Date: Apr 14, 2021, 07:22 UTC
Message-ID: <b562e614-add7-575f-3013-1dbc667bc5bf@gmail.com>
In-Reply-To: <YHaIBvl6Mf7ztJB3@google.com>

On 14/04/21 13.13, Jonathan Nieder wrote:

> Those four are important in my everyday life.  Questions:
> 
>   1. What pain points in the patch flow for git.git are important to
>      you?

There is no lists of "beginner-friendly" issues that can be worked on by new contributors. They had to search this ML archive for bug report issues and determine themselves which are beginner-friendly.

>   2. What tricks do you use to get by with those existing pain points?
> 
>   3. Do you think patchwork goes in a direction that is likely to help
>      with these?

No, unrelated to beginner-friendly issues above.

>   4. What other tools would you like to see that could help?

Some sort of bug tracker systems like Bugzilla (used by Linux kernel and many other projects) and Debbugs [1] (which is mail-centric and used by Debian for its BTS).

[1]: https://bugs.debian.org/debbugs-source/

-- 
An old man doll... just what I always wanted! - Clara