Write a charter

[jmwingenroth]

We need to frame our goals as a team.

My plan is to create a Markdown document with a first draft, open a PR, and request review from everyone. Typically having that many reviewers can be a little chaotic, but I suggest we treat this (meta) case as an exception in line with our trial-by-fire, learning-by-doing approach.

Hilariously, Copilot is going to be weighing in first since we turned on auto-review 😂

[gmcdonald-sfg]

Thanks so much for getting this started, @jmwingenroth !

Before diving into the specifics, I had one overarching question for the team @jmwingenroth @traceybit @danielleferraro @cullen-molitor - I thought our primary mandate for this team was focused around developing code review standards; not code review standards and AI standards?

Of course there are some AI tools to help with code review. But I think developing AI standards is a much broader topic that extends well beyond the realm of code review, and is more the focus of the AI task force.

I got a little confused, because the PR related to this is called Add Code Review & AI Standards Charter. But maybe that's just Claude getting overzealous with scope creep? haha

So just clarifying that our team here is focused only on developing code review standards, and only including AI guidance as it specifically pertains to effective code review (e.g., using copilot or Claude to review PRs)? I think that distinction would make a lot of sense, and would clarify our role and scope

[traceybit]

@gmcdonald-sfg i agree that the scope of AI seems like it should be narrow/focused for this task

[jmwingenroth]

Great point! I changed the PR title for a start. I’ll keep that narrower scope in mind when I go over the text of the charter and suggestions on the PR on Wednesday.

[jmwingenroth]

@traceybit @gmcdonald-sfg

The outline linked to in #20 has come a long way. Maybe a charter isn't necessary? We could close this issue as not planned.