On Fri, Apr 8, 2016 at 1:42 PM, Dmitry Tantsur <divius.inside at gmail.com> wrote: > > 2016-04-08 19:26 GMT+02:00 Davanum Srinivas <davanum at gmail.com>: > >> Team, >> >> Steve pointed out to a problem in Stackalytics: >> https://twitter.com/stevebot/status/718185667709267969 > > > There are many ways to game a simple +1 counter, such as +1'ing changes > that already have at least 1x +2, or which already approved, or which need > rechecking... > > >> >> >> It's pretty clear what's happening if you look here: >> >> https://review.openstack.org/#/q/owner:openstack-infra%2540lists.openstack.org+status:open >> >> Here's the drastic step (i'd like to avoid): >> https://review.openstack.org/#/c/303545/ >> >> What do you think? >> > > One more possible (though also imperfect) mitigation is to make exception > from the usual 2x +2 rule for requirements updates passing gates and use > only 1x +2. Then requirements reviews will take substantially less time to > land, reducing need/possibility of having such +1's. > > Many projects (including Keystone) already go with a single core +2/+A for Proposal Bot changes. This definitely helps them land faster (which is why the policy is there). -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160408/94a9a127/attachment.html>