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

Re: [TOPIC 07/11] New Contributors and Discord

From
Junio C Hamano <gitster@pobox.com>
Date
Sep 24, 2024, 19:15 UTC
Message-ID
<xmqqmsjwsw1q.fsf@gitster.g>
In-Reply-To
<20240924-sawfish-of-exotic-fantasy-b6abdb@meerkat>
Konstantin Ryabitsev <konstantin@linuxfoundation.org> writes:
Show 17 quoted lines
> On Mon, Sep 23, 2024 at 02:31:07PM GMT, Junio C Hamano wrote:
>> > I can chime up and offer bugspray bot integration for the list. This is a new
>> > tool I've been developing for integrating the mailing list with bugzilla. I've
>> > been using it on the tools mailing list over the past year with reasonable
>> > success.
>> 
>> Intriguing.  Everybody loves to hate bugzilla, but would bugzilla
>> become less smelly with bugspray enough to make it palatable to all
>> of us?
>
> I'm happy to enable it for this list if you'd like to try this out. It doesn't
> really create any obligation to use it, but it may end up being something
> useful.
>
> To enable it, I only need a list of people who are allowed to trigger bugspray
> via the "bugspray track" trigger phrase. I assume it's going to be more than
> just you?

Now we'll have to come up with and maintain an official list of trusted contributors. Which at first may sound like such a list may alianate those who did not make the list, but when deciding which topics are ready to hit 'next', such a "selection" is implicitly made to choose whose opinion weigh more anyway.

It might make the process more transparent to formalize the "more trusted contributors" list.

I suspect that the list of folks who can operator bugspray do not necessarily have to be with deep technical knowledge of the innards of Git. They have to be able to dedicate the time to read and understand what was said in the discussion threads, recognise when a problem is identified ("bugspray track"), have been long enough to know or able to use "git blame / git log" to see who likely has useful insight into the issue than others ("bugspray tag"?), and have good enough taste to recognise irrelevant "bugs" that are opened by those with worse taste. In a sense, it is very different from the earlier "list of those whose opinion weigh more in assessing topic's doneness". Competent "project secretaries" are the kinds of people we want.

If I misunderstood the nature of "allow-list" for trigger phrase, please correct me. Also it would be very welcome to hear from those listening in from the sidelines who want to see different kinds of people to be on the trigger phrase list.

Thanks.
Previous: Konstantin RyabitsevNext: Konstantin Ryabitsev
Message 25 of 38 in “Notes from the Git Contributor's Summit, 2024”
  1. Taylor BlauSep 20, 2024
  2. 01/11 RustTaylor Blau, Sep 20, 2024
  3. rsbecker@nexbridge.comSep 20, 2024
  4. Sean AllredSep 23, 2024
  5. rsbecker@nexbridge.comSep 23, 2024
  6. Phillip WoodSep 24, 2024
  7. rsbecker@nexbridge.comSep 24, 2024
  8. Sean AllredSep 27, 2024
  9. rsbecker@nexbridge.comSep 27, 2024
  10. rsbecker@nexbridge.comSep 27, 2024
  11. 02/11 Top-level lib/ directoryTaylor Blau, Sep 20, 2024
  12. 03/11 Structured Error HandlingTaylor Blau, Sep 20, 2024
  13. 04/11 Platform Support PolicyTaylor Blau, Sep 20, 2024
  14. 05/11 : SHA 256 / Git 3.0Taylor Blau, Sep 20, 2024
  15. Junio C HamanoSep 20, 2024
  16. 06/11 Git and Software Freedom ConservancyTaylor Blau, Sep 20, 2024
  17. 07/11 New Contributors and DiscordTaylor Blau, Sep 20, 2024
  18. Junio C HamanoSep 20, 2024
  19. Kousik SanagavarapuSep 21, 2024
  20. Junio C HamanoSep 22, 2024
  21. Junio C HamanoSep 22, 2024
  22. Konstantin RyabitsevSep 23, 2024
  23. Junio C HamanoSep 23, 2024
  24. Konstantin RyabitsevSep 24, 2024
  25. Junio C HamanoSep 24, 2024
  26. Konstantin RyabitsevSep 24, 2024
  27. Phillip WoodSep 27, 2024
  28. Junio C HamanoSep 27, 2024
  29. Phillip WoodOct 1, 2024
  30. 08/11 Modern Build SystemsTaylor Blau, Sep 20, 2024
  31. Eli SchwartzSep 23, 2024
  32. Patrick SteinhardtSep 24, 2024
  33. 09/11 Bundle-URI on fetch / resume-able cloneTaylor Blau, Sep 20, 2024
  34. 10/11 Project TrackingTaylor Blau, Sep 20, 2024
  35. Junio C HamanoSep 20, 2024
  36. Junio C HamanoSep 20, 2024
  37. Phillip WoodSep 23, 2024
  38. 11/11 git-scm.com state of the siteTaylor Blau, Sep 20, 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.