Open Stack

I'm hesitant to do more meetings as well, but we do need some coordination. I will leave the one for Monday on the board for now.  Lets have one meeting with the goal being to never need another one. I'm sure we can come up with an alternate way to communicate.

IDEA: We could have a "status" etherpad that everyone could keep updated each week with current tasks, important blueprints, concerns etc.

Vish

On Dec 8, 2011, at 8:42 AM, Trey Morris wrote:

> Weekly status emails sent to whom? I think it could be a good idea but my worry is that while the mailing list is efficient in terms of information per second, it's an inefficient place for coordinating. Solve this and I'm on board.
> 
> On Thu, Dec 8, 2011 at 7:26 AM, Soren Hansen <soren at linux2go.dk> wrote:
> 2011/12/8 Thierry Carrez <thierry at openstack.org>:
> > Soren Hansen wrote:
> >> 2011/12/7 Vishvananda Ishaya <vishvananda at gmail.com>:
> >>> 1) Weekly meeting for team leads. This is a time for us to discuss blueprint
> >>> progress, multiple-team-related issues, etc. Going to shoot for Mondays at
> >>> 2100 for this one.  I really need the subteam leads to commit to making this
> >>> meeting. We can discuss at the first meeting and decide if there is a better
> >>> time for this to occur.
> >> I have a conflict in that time slot every other week, and frankly, I'd
> >> really like to avoid more meetings. I'd by far prefer keeping to
> >> e-mail, and if we (over e-mail) find something that warrants more
> >> real-time discussion, we can put it on the agenda for our regular
> >> openstack team meeting on Tuesdays.
> > The problem is the general meeting has less and less time to dedicate to
> > each project, so Vish identified that he could not get efficient subteam
> > feedback and inter-subteam coordination from it... hence the need for a
> > new meeting slot. It could be a short one (30min) at start.
> 
> I hear that, but I'd like us to at least *try* and get it to work
> without stealing yet another one of my precious evenings for another
> horribly inefficient meeting. There are lots and lots and lots of
> thing we can do to avoid meetings that we haven't even tried. As a
> start, team leads could send a weekly report about what the team has
> been up to, what the challenges have been, and what they'll be doing
> the next week.
> 
> When I say "horribly inefficient meeting" I'm not implying that our
> meetings are more inefficient than anyone else's, but just that
> meetings in general are horribly inefficient. The amount of
> information per second is tremendously low, and everyone has to sit
> through the whole thing even if they only care about a tiny fraction
> of the agenda (if they're even so lucky to have a proper agenda).
> 
> Can we try to identify what sort of information we want from the
> various teams and *then* figure out how to extract and distribute it
> rather than just throwing a meeting slot at it?
> 
> --
> Soren Hansen        | http://linux2go.dk/
> Ubuntu Developer    | http://www.ubuntu.com/
> OpenStack Developer | http://www.openstack.org/
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~openstack
> Post to     : openstack at lists.launchpad.net
> Unsubscribe : https://launchpad.net/~openstack
> More help   : https://help.launchpad.net/ListHelp

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20111208/bb31c6ec/attachment.html>