Talk:Code review/Patch board

Who are the intended reviewers?
People with +2 only? Everyone? Goats?

I'd like to contribute, but don't posses +2 in significant repositories (and lack a drive to acquire them anytime soon). (Meaninglessly adding +1 when +2 are required should probably be avoided if nothing of value is to be gained, it'd just add noise) &mdash; Mainframe98 talk 21:39, 1 February 2023 (UTC)


 * Its primarily intended for people who have +2 in the repo the patch is in. Of course you're welcome to give helpful feedback to patches regardless of if you have +2. The primary intention is to get stuck things "unstuck" by either merging or giving the creator concrete steps they can do to get it merged. If you can do that without having +2, by all means, but in most cases I think you would need +2. Bawolff (talk) 22:09, 1 February 2023 (UTC)

Awesome idea
I don't have any patches that I'm ready to add here yet, but I must say this is an awesome idea. * Pppery * it has begun 22:37, 1 February 2023 (UTC)

What about using hashtags?
Just an idea. Gerrit has hash tag functionality. Something to consider is if it might be easier (for reviewers and people needing reviews) to tag Gerrit patches with a hash tag and to link that here ? We could also auto-tag patches listed here.

We did this during the wishathon event and I thought it was pretty effective: https://gerrit.wikimedia.org/r/q/hashtag:wishathon Jdlrobson (talk) 20:35, 2 February 2023 (UTC)
 * Boldly picked "" TheresNoTime (talk) 00:37, 9 February 2023 (UTC)
 * Bookmarked! Jdlrobson (talk) 17:03, 10 February 2023 (UTC)