Hi folks, One of our team goals for Grizzly was to distribute management across more members of the Quantum community using sub-teams.
In trying to realize this, we've been reworking how team meetings work to have a more sub-team focused agenda. So far, we've been slicing off sections of the meeting for some subteams that correspond to different projects (e.g., quantum + horizon, or quantum + tempest) but not within sub-teams that contribute primarily to the main quantum project. I'd like to try going with completely sub-team focused design. As a result, I reworked the agenda from today's meeting to match the design i'm proposing: http://wiki.openstack.org/Network/Meetings If you're a sub-team lead, lease take a look at this proposed design and let me know if you have suggestions. Basically, we have a sub-team report for any non-plugin subteam, which covers any "high" issues in detail (as we do already), but also let's the sub-team lead provide quick updates on any other blueprints or active discussion topics, as well as touching on any doc bugs related to that sub-team. We then end with opportunity for other sub-teams to report (e.g., a plugin specific sub-team) as well as open discussion when people can bring up issues that didn't quite fall into any of the sub-team buckets. The model here would be that each sub-team lead updates their portion of the agenda prior to the meeting, and leads discussion for the meeting during their section (now you can see why i'm so interested in this approach!). Keep in mind that with 9 sub-teams, plus announcements and open discussion, the goal is that each sub-team report is on average under 5 minutes. Let's give this a try for next week and we'll see how it goes. Thanks, Dan -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Dan Wendlandt Nicira, Inc: www.nicira.com twitter: danwendlandt ~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- Mailing list: https://launchpad.net/~quantum-core Post to : quantum-core@lists.launchpad.net Unsubscribe : https://launchpad.net/~quantum-core More help : https://help.launchpad.net/ListHelp
