git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] RFC: add MAINTAINERS file

From
Taylor Blau <me@ttaylorr.com>
Date
Apr 1, 2024, 21:33 UTC
Message-ID
<ZgsoOnle3CC8DqUR@nand.local>
In-Reply-To
<ZgPIEgFGVokYWc-H@tanuki>
On Wed, Mar 27, 2024 at 08:17:38AM +0100, Patrick Steinhardt wrote:
Show 24 quoted lines
> On Sun, Mar 24, 2024 at 07:51:03PM -0700, Junio C Hamano wrote:
> > Junio C Hamano <gitster@pobox.com> writes:
> >
> > > I am more worried about how the file is used and maintained.  Some
> > > things to think about while in the "spurred discussion" I can think
> > > of are:
> > > ...
> > >  - Is the project big enough to require this (especially for the
> > >    purpose of (1)), or would
> > >
> > >    $ git shortlog -n --no-merges --since=24.months -- path-to-file
> > >
> > >    be sufficient and more importantly the value that it will keep
> > >    current automatically outweigh the benefit of having this file
> > >    that can go stale?  To answer this question, we'd need to know
> > >    the turnover rates of past project contributors, of course.  If
> > >    it is too high, having such a list may help for (1) and (3)
> > >    above.
>
> I don't think of this as "big enough to require this". I rather think
> about the onboarding experience for new folks here. Sure, we can ask
> them to "Please run git-shortlog(1) to figure out whom to Cc". But if we
> instead provide a nice script that does it for them then we make their
> lifes easier.

Do you think that the script in contrib/contacts does a sufficient job at this?

I admit that I am not a frequent user of it (mostly because I end up either having a good sense of who I want to review patches ahead of time, and/or I end up just running 'shortlog'), so I can't vouch for its accuracy.

But from running it on a handful of patches just now locally while replying to your email, it seems to do a reasonable job at identifying a good set of candidate reviewers.

Perhaps we haven't been as good at advertising this script as we could be, and that's why it isn't as widely used as it could be? I'm not sure.

Thanks, Taylor

Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 23 in “RFC: add MAINTAINERS file”
  1. RFC: add MAINTAINERS fileLinus Arver via GitGitGadget, Mar 23, 2024
  2. Junio C HamanoMar 23, 2024
  3. Junio C HamanoMar 25, 2024
  4. Linus ArverMar 27, 2024
  5. Patrick SteinhardtMar 27, 2024
  6. Linus ArverMar 30, 2024
  7. Junio C HamanoMar 30, 2024
  8. Taylor BlauApr 1, 2024
  9. Junio C HamanoApr 1, 2024
  10. Linus ArverApr 2, 2024
  11. Patrick SteinhardtApr 2, 2024
  12. Eric SunshineApr 2, 2024
  13. Patrick SteinhardtApr 2, 2024
  14. Linus ArverMar 26, 2024
  15. Taylor BlauMar 26, 2024
  16. Junio C HamanoMar 27, 2024
  17. Linus ArverMar 27, 2024
  18. Junio C HamanoMar 27, 2024
  19. Linus ArverMar 30, 2024
  20. Patrick SteinhardtApr 2, 2024
  21. Linus ArverApr 4, 2024
  22. Patrick SteinhardtApr 2, 2024
  23. Junio C HamanoApr 2, 2024

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.