[Ccsf-campus-staff] Curriculum / Structure

[Shauna Gordon-McKeon]

> After reading some of the threads about curriculum and post-workshop
> self-assessments, I wanted to throw some ideas in the ring:
>
>    - First, I wanted to point out that currently we have a single large
>    room booked -- many of the debriefs of other workshops seemed to suggest
>    that many events were held in multiple rooms.
>
> This is not particularly the case.  We like having two rooms so that folks
can eat & socialize without disturbing others but that's usually not a
problem - and especially not with this event, where we may be working
through lunch.  Is that a definite, that we can't get the room until 5?


>    - Possibly push the "Ethics & History of Free Software" module to
>    lunchtime
>       - first 30-mins of lunch hour:  "Ethics & History of Free Software"
>       - 2nd 30-mins of lunch hour:  "career panel" [which I take to mean
>       that presenters/TAs talk about developing open source at work & how they're
>       inspired by OS]
>
>
It's a bit intense to work through the whole of lunch though.  People need
a bit of a break... maybe let's pick one or the other?




>
>
> ...I think:
>
>
>    - this gets the day started off on a sharper note -- newbies are less
>       likely to be excited about an "interactive discussion" first thing in the
>       morning
>       - this would let us jump right into the skill modules first thing
>       in the morning (this is what everyone is most excited about)
>       - the history module right before the wider presenter (and possibly
>       attendee) comments might "prime the pump" so to speak
>
>
So generally, our schedule goes:

- intro & laptop setup
- intro to open source tools (includes demos of IRC, bug trackers, using
diff() and patch())
- intro to git/version control
- career panel
- lunch
- history & ethics of free software
- demo/group walkthrough of pull requests on git
- workshop

So we do usually do skills in the morning.  History & Ethics sometimes gets
cut or greatly shortened due to time constraints.



>
>    - How about training missions instead of lectures?
>       - there can be a recommended flow (starting the newbies off with a
>       command line tutorial, more advanced users can jump ahead, etc)
>       - presenters/TAs can wander around helping folks
>       - attendees will be maximally engaged as they are working on what
>       they want to (need to), when they want to
>       - if there are video portions, we can ask folks to bring headphones
>       (and we can borrow a whole bunch from our CS dept computer lab as long as
>       we make sure they all come back)
>
>
Which lectures would you want to supplant by training missions?  I'm
assuming version control w/ git, but maybe also the "intro to open source
tools"?  To clarify, we often do the missions after the lectures as a
follow up.  This is especially true of the git lecture, which over time has
grown shorter and more concise in favor of letting attendees move on to the
git training mission.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/ccsf-campus-staff/attachments/20130606/521d3b3d/attachment.html>