On Fri, May 31, 2013 at 12:05:56AM -0700, Jessica Tomechak wrote:
> On Thu, May 30, 2013 at 1:59 PM, Chip Childers 
> <chip.child...@sungard.com>wrote:
> 
> > On Thu, May 30, 2013 at 01:12:40PM -0700, Jessica Tomechak wrote:
> > > Now Urgent!! Gregg will be starting in just a couple of weeks. Last year,
> > > we churned for several weeks after his arrival. Let's avoid that this
> > time.
> > >
> > > What do we want?
> > > Education videos from Sebastien's list?
> > > How-to videos left over from last year's Video Plan?
> > >
> > > Need to know in the next few days, so the correct person can attend the
> > > Mentor Orientation from Gregg's sponsoring organization.
> > >
> > > Mathias/Sebastien, if you want to use Gregg for education videos, please
> > > speak up and make some materials available. We'll need outlines and
> > > storyboards. Gregg can help generate those if all you have so far is
> > ideas.
> > >
> > > If you're not going to be ready to take advantage of Gregg's presence, I
> > > will plan to work with him as I did last year. We still have a list of
> > > video requests that we didn't get around to last time.
> > >
> > > Jessica T.
> >
> > Perhaps you can run with this Jessica?
> >
> 
> Chip,
> I am totally on board to run with this. I am just looking to collaborate
> with the community on which direction to go. From much previous discussion
> on this list, I've seen that showing up with a finished work item and
> "throwing it over the wall" is frowned upon. We're intended to develop in
> the open, and get feedback on proposed projects.

Absolutely true!  But your email above is asking for someone to "take
point".  I was asking if you wanted to do it yourself.

> 
> Perhaps if I throw out some more specific suggestions, people can vote or
> respond.
> 
> I just want to get some suggestions of what topics would be most helpful to
> cover. I don’t want to waste the short time that Gregg has to act as a
> contributor to the project.
> 
> Some Visual Styles:
> 
> Whiteboard talk
> 
> "Talking head" interview
> 
> Screencast
> 
> Animation
> 
> Tongue in cheek animation (xtranormal?)
> 
>  Sketchnotes (hand drawn animation with narration)
> 

IMO, style depends on the topic.

> 
> Some Possible Technical Topics:
> 
> What's new in 4.1, in 4.2

I think that longevity of a video about the releases is too short.  -0
on that one.

> 
> How to install (quick install, or advanced install)
> 

We already have some of these floating around, so -0.

> Hypervisor installation (for each supported hypervisor)
> 

-0

> How to set up networking
> 

+0 - It's really complex though, so I'd be curious how it would be put
into video form.

> Top 10 interesting clouds people have set up
> 

+100 - if we have users willing to do it.

> Conceptual overview of Cloudstack deployment (zones, pods, etc)
> 

+1 on this one too.  Conceptual constructs aren't likely to change
dramatically in the short term.


> Datacenter concepts (what is a datacenter, what hardware will you need, how
> does a rack correlate to a cloudstack pod, etc)
> 
> Overview of Cloudstack implementation architecture (code modules and their
> relationships) – this one might be fairly short shelf life
> 

-0 on the two above

> Networking:
> http://cloudstack.org/forum/8-storage-and-networking/10370-an-advanced-networking-video-or-webinar-is-sorely-needed.html
> 

I'd actually suggest that a webinar is the right way to do a networking
video, so that it's interactive if required...  and more easily produced
than a finished video product.

> 
> (1)    A video that shows someone installing a host with a single ethernet
> card that is going to be shared with the the managment and guest network
> and public networks. How the VLANS would be setup on the sell or cisco
> switch to accomplish this, or
> 
> (2)    A video showing someone installing a zone with the hosts having
> separate nics for management/guest, public, and storage networks and an
> example of setting up the VLANS, or
> 
> (3) A video showing different scenarios of setting up the VLANS with
> different amount of nics in the hypervisor hosts.
> 
>  Jessica T.

Reply via email to