Hi, On Thu, Oct 21, 2021 at 1:57 PM Johannes Schindelin <Johannes.Schindelin@xxxxxx> wrote: > > This session was led by Johannes "Dscho" Schindelin. Supporting cast: > brian "Bmc" carlson, Jeff "Peff" King, Taylor Blau, CB Bailey, Ævar > Arnfjörð "Avarab" Bjarmason, Jonathan "Jrnieder" Nieder, Derrick Stolee, > Lessley Dennington, Glen Choo, Philip Oakley, Victoria Dye, and Jonathan > "Jonathantanmy" Tan. > > Notes: > ... > > 5. Git the community is still overwhelmingly male, white - what can we do? > ... > > 19. Stolee: When we moved from MS to GH, we received quick feedback that we > weren’t communicating well - too direct and unemotional. Maybe Git > community communicates that way, but that’s not how most people interact; > that makes me think that our “efficient and effective” communication is > actually too aggressive, and easily interpreted as attacks on > contributors. Basically… let’s all lighten up? :) > > 20. Taylor: Yep, my “talking to GitHubbers at GitHub” voice is different from > my “talking to Gitters on Git list” voice. New contributors, are we on the > right track here? > ... > > 34. Avarab: I think it’s a good thing to work on; we need to be really careful > about what guidelines we pick and choose. Need to ensure an easy path for > new contributors so they don’t need to read hours of documentation for a > typo fix. Plus we need to ensure that this doc is accessible for folks who > have different first language than English. > > 35. Bmc: on git-lfs we have a contributor with very little English, so when we > did the review I’d offer an alternative text, and we would work together. > That process was useful to come up with readable documentation in a > helpful way. That is, proposing a solution instead of pointing out the > problem and saying “fix it” can help a lot in scenarios like this. > > 36. Dscho: Yep, this is important and will help us be more accessible to > contributors whose English is not super top notch Cambridge exam :) Yes, thanks for mentioning the non-English speaking community. I have been an avid reader of the Git Mailing List for the past years and can't help but notice contributions from folks working in Alibaba(China) have been taking a lot more iterations to get to final reviews than usual contributions. I would recommend, on top of having a guideline document, to have a Valve check (1) setup as a commit-msg hook and run it as part of GitGitGadget CI to help folks shorten the feedback loops in some basic cases. Cheers, Son Luong. (1): https://docs.errata.ai/vale/styles
