Re: Increase CAB meeting to 1.5 or 2 hours?

Steven Benario

One of the things we've started going in the Runtime-specific meetings is
asking that individual team status updates are provided ahead of time, and
then we use the time in the meeting for Q&A only, instead of reading those
notes aloud.

I'm a big fan and recommend this model.


On Sun, Feb 14, 2016 at 11:19 AM, Dr Nic Williams <drnicwilliams(a)>

Since we started the CAB calls in late 2013 the size of Cloud Foundry
community, the number of engineering teams, and the number of code bases
(both core & community) has grown.

There was a time when community projects might get to be introduced once
during a CAB meeting; and shared discussion of what was going on amongst
the community.

Recently, due to the hard limit of 1 hour - there is only just time for
core team projects to discuss their status.

With increased number of CF office locations, the tread will continue to
create more teams, which in turn will create more repositories & tracker
roadmaps, and will create more demand on the limited CAB call time slot.

I like the name "Community Advisory Board meeting". It seems like a good
goal for the meeting.

Could we increase the CAB meeting to 1.5 or 2 hours?

Or could the summaries by PMs be delivered before the meeting (I have the
feeling many of them are organized and have notes that they are reading).
This might give us more time to discuss the projects, and discuss
non-core/community projects and ambitions.

It might also allow time for the community to chat with itself and bond as
a community.

with valentine's love
Dr Nic

Dr Nic Williams
Stark & Wayne LLC - consultancy for Cloud Foundry users
cell +1 (415) 860-2185
twitter @drnic

Join to automatically receive all group messages.