Open Stack

Here's a suggestion of format for your consideration. How about we have three people with experience in this, and have a session moderated by someone. 

I'm happy to volunteer to be that moderator, I have experience doing that kind of thing both in my professional capacity and as <cough>an elected politician. Yes, no kidding, my elected title is "Town Moderator" :)

To do something like this, I'll put out a call for questions to the community, as well as come up with some questions of my own, and I'll organize this video session just as one would a panel discussion.

I'm also happy to help with arranging something like this, in any way that may be appropriate.

Thanks,

-amrith

> -----Original Message-----
> From: Shamail [mailto:itzshamail at gmail.com]
> Sent: Friday, March 25, 2016 1:25 PM
> To: Ed Leafe <ed at leafe.com>
> Cc: openstack-tc at lists.openstack.org
> Subject: Re: [openstack-tc] Design Summit video advice for session
> moderators
> 
> Hi,
> 
> > On Mar 25, 2016, at 11:53 AM, Ed Leafe <ed at leafe.com> wrote:
> >
> > On 03/25/2016 08:29 AM, Flavio Percoco wrote:
> >
> >>> We could do it as a free-form discussion across a limited set of
> >>> people, all recorded (using Google Hangouts on Air like for the
> >>> Bootstrapping Hour). However I fear that would result in a long
> >>> video that could be missing critical points.
> >>>
> >>> Alternatively we could think about it and lay out the points we want
> >>> to make on an Etherpad, and then have people sign up to pick one
> >>> they are comfortable with and speak about it for one minute. We can
> >>> still use a collective session on hangouts as a way to collect and
> >>> build the common video, but we would build the script in advance.
> >>
> >>
> >> Collecting points on an etherpad or a hangout session sounds good to
> me!
> >> I think
> >> having an organized format (even if somewhat informal) is better than
> >> a free-form discussion. A free-form discussion is likely to miss
> >> important info, as you also pointed out.
> >
> > Yes, an organized format will probably be much better. A discussion
> > format will likely end up with points being made with assumed tribal
> > knowledge, and that's exactly the thing we *don't* want. We want to
> > pass on that tribal knowledge explicitly.
> 
> I'll be glad to volunteer to help take the discussion and turn into bullet
> points or even update the project guide with the recommendations after the
> fact.
> 
> >
> > --
> >
> > -- Ed Leafe
> >
> > _______________________________________________
> > OpenStack-TC mailing list
> > OpenStack-TC at lists.openstack.org
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc
> 
> _______________________________________________
> OpenStack-TC mailing list
> OpenStack-TC at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-tc