On Wed, Aug 28, 2013 at 03:43:21AM +0000, Joshua Harlow wrote: > Why not a rotation though, I could see it beneficial to say have a > group of active developers code for say a release then those > developers rotate to a reviewer position only (and rotate again for > every release). This allows for a flow of knowledge between reviewers > and a different set of coders (instead of a looping flow since > reviewers are also coders). > > For a big project like nova the workload could be spread out more > like that.
I don't think any kind of rotation system like that is really practical. Core team members need to have the flexibility to balance their various conflicting workloads in a way that maximises their own productivity. Regards, Daniel -- |: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :| |: http://libvirt.org -o- http://virt-manager.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :| _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev