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

Re: [PATCH v2] MyFirstContribution: add avenues for getting help

From
SZEDER Gábor <szeder.dev@gmail.com>
Date
Nov 19, 2019, 18:49 UTC
Message-ID
<20191119184919.GM23183@szeder.dev>
In-Reply-To
<20191118214519.GH22855@google.com>
On Mon, Nov 18, 2019 at 01:45:19PM -0800, Emily Shaffer wrote:
Show 27 quoted lines
> On Sat, Nov 16, 2019 at 12:05:45PM +0900, Junio C Hamano wrote:
> > > +==== https://public-inbox.org/git[git@vger.kernel.org]
> > > +
> > > +This is the main Git project mailing list where code reviews, version
> > > +announcements, design discussions, and more take place. If you fail to receive
> > > +help via the channels above, you can ask your question here. The Git list
> > > +requires plain-text-only emails and prefers inline and bottom-posting when
> > > +replying to mail; you will be CC'd in all replies to you. Optionally, you can
> > > +subscribe to the list by sending an email to majordomo@vger.kernel.org with
> > > +"subscribe git" in the body.
> > 
> > Sounds good; I agree with Denton, especially with the mention of
> > "you must join" on the other mailing list, that it is a good idea to
> > explicitly say that subscription is optional in this entry.
> > 
> > You can ask questions even if you haven't tried other avenues and
> > failed, but this entry makes it sound as if an earlier failure
> > elsewhere is a prerequisite for asking for help here.
> 
> I envision an exchange sort of like this:
> 
> Newbie to git@vger.kernel.org: "I'm having trouble compiling Git and I
> want to write a patch, I'm getting X error"
> 
> Veteran to Newbie, cc git-mentoring, bcc git@vger.kernel.org:
> "Please build with blah flag and paste console output, plus let us know
> system information blah blah blah"

That won't work if the veteran is not registered to the mentoring list, and we can't assume that the newbie is registered there either. I don't think that we should send anyone who asked a question here to somewhere else, especially if that elsewhere requires registration.

Show 10 quoted lines
> I don't mind the idea of pushing folks to ask on the mentoring list
> first. It's pretty well attended already - just now I count 16 list
> members, a pretty significant majority of which are project veterans. I
> have no problem suggesting newbies ask their questions, which others
> probably had and solved before them, in a space separate from the main
> mailing list.
> 
> Of course if you want to encourage newbies to ask in any of these three
> venues, weighted equally, I can change the language. But suggesting the
> main list as a last resort was intentional.

git@vger is the ultimate source of all wisdom :) and it is openly accessible for anyone for writing, reading, and searching. Therefore these three venues cannot be weighted equally, but git@vger should be the explicitly preferred venue. Only if the newbie has some other preferences should the other two be considered; e.g. if more interactive, chatty communication is preferred, then try #git-devel.

Previous: Junio C HamanoNext: Johannes Schindelin
Message 10 of 44 in “MyFirstContribution: add avenues for getting help”
  1. MyFirstContribution: add avenues for getting helpEmily Shaffer, Nov 15, 2019
  2. Denton LiuNov 15, 2019
  3. Emily ShafferNov 15, 2019
  4. MyFirstContribution: add avenues for getting helpEmily Shaffer, Nov 15, 2019
  5. Johannes SchindelinNov 15, 2019
  6. Jonathan NiederNov 16, 2019
  7. Junio C HamanoNov 16, 2019
  8. Emily ShafferNov 18, 2019
  9. Junio C HamanoNov 19, 2019
  10. SZEDER GáborNov 19, 2019
  11. Johannes SchindelinNov 19, 2019
  12. SZEDER GáborNov 19, 2019
  13. Eric WongNov 20, 2019
  14. Johannes SchindelinNov 20, 2019
  15. SZEDER GáborNov 20, 2019
  16. Kerry, RichardNov 20, 2019
  17. Junio C HamanoNov 20, 2019
  18. SZEDER GáborNov 19, 2019
  19. MyFirstContribution: add avenues for getting helpEmily Shaffer, Dec 13, 2019
  20. Derrick StoleeDec 13, 2019
  21. Emily ShafferDec 13, 2019
  22. MyFirstContribution: add avenues for getting helpEmily Shaffer, Dec 13, 2019
  23. Junio C HamanoDec 13, 2019
  24. Emily ShafferDec 13, 2019
  25. Junio C HamanoDec 13, 2019
  26. MyFirstContribution: add avenues for getting helpemilyshaffer@google.com, Jan 24, 2020
  27. Junio C HamanoJan 24, 2020
  28. Emily ShafferJan 24, 2020
  29. Emily ShafferJan 24, 2020
  30. Junio C HamanoJan 24, 2020
  31. MyFirstContribution: add avenues for getting helpEmily Shaffer, Jan 24, 2020
  32. Junio C HamanoJan 24, 2020
  33. Emily ShafferJan 24, 2020
  34. MyFirstContribution: add avenues for getting helpEmily Shaffer, Jan 24, 2020
  35. SZEDER GáborJan 24, 2020
  36. Junio C HamanoJan 24, 2020
  37. SZEDER GáborFeb 6, 2020
  38. Junio C HamanoFeb 6, 2020
  39. Emily ShafferFeb 6, 2020
  40. Emily ShafferFeb 6, 2020
  41. MyFirstContribution: rephrase contact infoEmily Shaffer, Feb 14, 2020
  42. Jonathan NiederFeb 14, 2020
  43. Junio C HamanoFeb 14, 2020
  44. Junio C HamanoJan 24, 2020

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.