Kallithea issues archive

I agree something like this could be nice.

The next question would be how it should work. Should one of the reviewers be enough or must all approve? Who should get notifications? One or all ... or the active ones?

I think there are many different answers to that - no single solution fits everybody.

One solution (which I have opted for) is thus to customize the code. I made it so it fits the process in my organization ... but what worked for us is not something I would recommend for others.

The function that I want is to shorten the time and labor for each addition to be added individually. I think that everyone should receive notifications.

I just want to ease the registration work of the reviewer. For operation, I would like the same as when registering individually.

@export, see if you find the changes in pull request #226 useful. It's a customization we use.

At Collabora, we use Phab for reviews, and it supports group reviewers. It has a meta-group called Reviewers, in which everyone who’s done at least one review (I think) is automagically added. The change is considered approved as long as it’s approved by at least one reviewer — or more, depending on a specific case: Phab marks changes with at least one approval as Accepted, but it’s up to the project maintainers to require more or not.

I think it’s useful to have the tool not mandate the policy. Kallithea doesn’t have to necessarily require all reviewers to accept the change. It can be a behaviour to select per-repository, so that we have ‘permissive’ reviews (at least one reviewer acknowledges) or ‘strict’ reviews (every reviewer is required to ack it).

@kveretennicov, Thanks for your pull request information. I will try it.

@kiilerix, @andrew_shadura, Thanks for comment. I think that kallithea has a firm policy.