Re: [PATCH] docs: update contributing guide to refer current bugs and feature requests

From: Carlo Marcelo Arenas Belón <carenas@gmail.com>
Date: Jan 8, 2025, 10:43 UTC
Message-ID: <cwkdvlhhfe6lrgx5pdcrgmgv7cfvkjflazo4k4yorzbuaixlpn@myd7rrdel3w6>
In-Reply-To: <pull.1867.git.git.1736080517950.gitgitgadget@gmail.com>

On Sun, Jan 05, 2025 at 12:35:17PM -0800, Rhythm Narula via GitGitGadget wrote:

Show 6 quoted lines

> From: Rhythm-26 <rhythm.narula26@gmail.com>
> 
> The contributing guide is updated to include references to the current
> open bugs and feature requests. This update aims to improve visibility
> for contributors on where to find open issues and features that need
> attention.

The commit message (as described in `Documentation/SubmittingPatches`) should explain the problem in the codebase and then describe (in imperative mode) how the patch proposes to fix it.

Subject line is also meant to be very short so maybe somethihg like:

  docs: mention source of tasks in MyFirstContribution

> +:mailinglist: git+subscribe@vger.kernel.org
> +
> +Here's where you can find bugs and feature requests existing in the system:

mentioning bugs with quotes might be a good idea, considering that GGG (your first link below) specifically mentions that only feature requests should be filed there.

something that encourages people to use the mailing list for reports and discussion probably worth adding as well.

> + - Unofficial bug trackers - https://github.com/gitgitgadget/git/issues, https://git.issues.gerritcodereview.com/

see #1432

Carlo

CC: +Emily as the original authour of "MyFirstContribution" for feedback