On Mon, 2016-04-11 at 05:54 -0400, John Trowbridge wrote: > Hola OOOers, > > It came up in the meeting last week that we could benefit from a CI > subteam with its own meeting, since CI is taking up a lot of the main > meeting time. > > I like this idea, and think we should do something similar for the > other > informal subteams (tripleoclient, UI), and also add a new subteam for > tripleo-quickstart (and maybe one for releases?). > > We should make seperate ACL's for these subteams as well. The > informal > approach of adding cores who can +2 anything but are told to only +2 > what they know doesn't scale very well.
+1 for some subteams. I think they make good sense for projects which are adopted upstream into projects like TripleO. I wouldn't say we have to go crazy and do it for everything but for projects like quickstart it seems fine to me. Dan > > - trown > > _____________________________________________________________________ > _____ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs > cribe > 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
