Re: [DISCUSS] Review Guide for the project

2025-01-19 Thread Bernardo Botella
Well, as a growing member on this community, I definitely see benefit on such a review style guide. I’d also be more than happy to participate on its creation with my “fresh eyes reviewer” hat, as someone that hasn’t been reviewing PR for as long as other members of the community. Having said t

Re: [DISCUSS] Review Guide for the project

2025-01-18 Thread Ekaterina Dimitrova
Having updated guides is great and probably we can also put links to them into the PR template, for convenience sake. Thus anyone who opens a PR will see them. On Sat, 18 Jan 2025 at 18:46, Jordan West wrote: > I generally support a guide we can point new contributors to as well. > > Jordan > >

Re: [DISCUSS] Review Guide for the project

2025-01-18 Thread Jordan West
I generally support a guide we can point new contributors to as well. Jordan On Sat, Jan 18, 2025 at 10:20 Dinesh Joshi wrote: > As a growing community with new committers and contributors, I would > support establishing a review guide to ensure consistency and uniformity of > feedback. > > On

Re: [DISCUSS] Review Guide for the project

2025-01-18 Thread Dinesh Joshi
As a growing community with new committers and contributors, I would support establishing a review guide to ensure consistency and uniformity of feedback. On Sat, Jan 18, 2025 at 5:21 AM Josh McKenzie wrote: > See thread "Checkstyle as style contract for Cassandra >

[DISCUSS] Review Guide for the project

2025-01-18 Thread Josh McKenzie
See thread "Checkstyle as style contract for Cassandra ". One area where we haven't formalized much guidance is around our code review culture as a project. I've worked with guides based on google's "How to do a code review