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

Re: [DISCUSSION] Growing the Git community

From
Jeff King <peff@peff.net>
Date
Nov 14, 2019, 06:06 UTC
Message-ID
<20191114060650.GC10643@sigill.intra.peff.net>
In-Reply-To
<20191114023100.GD22855@google.com>
On Wed, Nov 13, 2019 at 06:31:00PM -0800, Emily Shaffer wrote:
Show 9 quoted lines
> Christian's suggestion of a Google Group list was good enough for me.
> For now, the permission settings are as follows:
> 
>  - Group visibility: Anyone. (So it can be easier to discover and
>    advertise.)
>  - View topics: Group members only. (Maybe we want to open this up so
>    it's easier for non-member Git contributors to take a look at what's
>    going on.... but maybe if they're interested they can just join the
>    group :) )

I think it makes sense to stay closed for now. One of the reasons to have a separate group is to make it less daunting to post to. Having a public archive may work against that.

>  - Post: Group members only. (My thinking is that once you're asking for
>    someone's time and effort to help mentor you, you can volunteer the
>    time and effort needed to push the join button and optionally filter
>    your inbox ;) )

It also cuts down on spam (I moderate the git-security google group, and the spam-blocking is far from perfect).

It is annoying if things get cross-posted to git@vger (whoever replies with the cc intact will get an annoying "you can't post here" bounce). But I'd try it this way for a while and see.

>  - Join group: Anyone. (Let's make the barrier to entry low.)
Makes sense. I just joined.
-Peff
Previous: Emily ShafferNext: Junio C Hamano
Message 33 of 45 in “[DISCUSSION] Growing the Git community”
  1. Derrick StoleeSep 19, 2019
  2. Denton LiuSep 19, 2019
  3. Emily ShafferSep 19, 2019
  4. Jeff KingSep 19, 2019
  5. Junio C HamanoSep 20, 2019
  6. Garima SinghSep 20, 2019
  7. Junio C HamanoSep 20, 2019
  8. Klaus SembritzkiSep 19, 2019
  9. Klaus SembritzkiSep 19, 2019
  10. Klaus SembritzkiSep 19, 2019
  11. Klaus SembritzkiSep 20, 2019
  12. Klaus SembritzkiSep 20, 2019
  13. Klaus SembritzkiSep 20, 2019
  14. Klaus SembritzkiSep 20, 2019
  15. Klaus SembritzkiSep 20, 2019
  16. Mike HommeySep 19, 2019
  17. Johannes SchindelinSep 23, 2019
  18. Jakub NarebskiOct 1, 2019
  19. Jeff KingSep 19, 2019
  20. Derrick StoleeSep 20, 2019
  21. Jeff KingSep 20, 2019
  22. Elijah NewrenSep 19, 2019
  23. Pierre TardySep 25, 2019
  24. Derrick StoleeSep 25, 2019
  25. Jakub NarebskiOct 4, 2019
  26. Philip OakleySep 25, 2019
  27. Jakub NarebskiOct 4, 2019
  28. Emily ShafferNov 12, 2019
  29. Johannes SchindelinNov 12, 2019
  30. Christian CouderNov 13, 2019
  31. Thomas GummererNov 13, 2019
  32. Emily ShafferNov 14, 2019
  33. Jeff KingNov 14, 2019
  34. Junio C HamanoNov 15, 2019
  35. Pratyush YadavNov 14, 2019
  36. Thomas GummererNov 14, 2019
  37. Philip OakleySep 20, 2019
  38. brian m. carlsonSep 20, 2019
  39. Randall S. BeckerSep 20, 2019
  40. Jakub NarebskiOct 4, 2019
  41. Garima SinghSep 20, 2019
  42. Junio C HamanoSep 20, 2019
  43. Junio C HamanoSep 20, 2019
  44. Derrick StoleeSep 23, 2019
  45. Johannes SchindelinSep 23, 2019

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.