Hi Dmitry, It depends, but usually it takes half of working time to do reviews, I'm not sure if we can assume 25-30%, also finding a good reviewer usually is much harder than a person who can write the code, so it would be much more productive to encourage people to spend as much time as they can on making the project better and helping other contributors, than restricting them to review code for not more than 2.5 hours.
Thanks, On Thu, Jun 9, 2016 at 5:46 AM, Dmitry Klenov <dkle...@mirantis.com> wrote: > Hi Folks, > > From technical standpoint I fully support Arthur to become core reviewer. > I like thorough reviews that he is making. > > Although I have some concerns as well. Planned tasks for our team will not > allow Arthur to spend more than 25-30% of his time for reviewing. If that > is fine - my concerns are resolved. > > Thanks, > Dmitry. > > On Thu, Jun 9, 2016 at 12:57 PM, Sergey Vasilenko <svasile...@mirantis.com > > wrote: > >> +1 >> >> >> /sv >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: >> openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> >> > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev > >
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
