Can’t really forcefully assign work, including review work, to volunteers.
So I’m not sure what we can do here, other than perhaps create some sort of dashboard to show tickets with unassigned reviewers, and tickets with overdue reviews. Both can be easily done as JIRA filters, however. As an individual volunteer committer, you just pick JIRAs you want to work on/review, if they aren’t taken. If they are taken, you talk to the current assignee and ask them to take over. Usually if they aren’t far in, they’ll happily yield, in my experience. -- AY On 28 August 2016 at 23:49:23, mck (m...@apache.org) wrote: http://cassandra.apache.org/doc/latest/development/index.html This is fantastic. Thanks heaps and heaps for doing this. Stefan i believe you get some of the credit for this! The top level 'Community' link now seems a bit superfluous. I guess there are plans for this? There's also no docs on how which tickets get reviewed. As far as i know DS has an internal system for this, which is fair enough. But it would be nice to know more (and see formalised/documented) about how the tickets to review are pulled, how they'll split into different areas of code to make it easier for committers to review, and how tickets don't get forgotten along the way. I've had a number of tickets where the reviewer just 'disappeared' and many months went by. This is a potential source of frustration for contributors. Mick.
