[Campus-hartnell-staff] Focus of event / workshop details

[Katie Cunningham]

Hi all,

I discussed some variations on the workshop setup with Shauna earlier.
While I had been thinking of focusing on more advanced students and
contributions, due to some internal reasons there will be a larger
percentage of students who are at a beginner level.

Here is my breakdown of the expected attendees. The reason I can make this
prediction is because I work so closely with computer science students in
special cohort programs. While cohort students are not required to attend,
they are generally the most enthusiastic about extracurricular events.

   - *Population 0* (5): students taking ~3rd programming class who use
   git/command line extensively in personal projects.
   - *Population 1* (5-10): students taking ~3rd programming class who have
   used the command line and git a bit, but not that much.
   - *Population 2* (30): students taking ~1.25th programming class who
   don’t have much command line experience or version control experience.
   - We will work with most of these students to get them slightly more
      familiar with the command line / git before OSCTC

Many students from 0 and 1 will have attended an OSCTC before. They are
really excited that it is happening again (and really looking forward to
seeing the mentors from last time). My sense is that while they learned a
good amount last semester, a review of the material would be welcome to
most.

While students will certainly learn a lot of great skills from this
workshop, it’s perhaps just as importantly a sort of *cultural exchange*.
It’s an exposure to concepts, jargon, and mannerisms/approaches that aren’t
really a part of the CS curriculum or experience here in our somewhat
isolated, low-tech location. I believe events like OpenHatch help our
students become acculturated enough to feel comfortable sitting at the
table and participating in tech culture.

Due to the above, here is my first draft of a schedule:
(Note: two rooms are reserved, so we'll have room to run parallel
activities)

   - Morning
      - *Setup* - should be quick, because I'll have worked with students
      on getting things installed beforehand.
      - *Basics of open source, less emphasis on code, more emphasis on
      concepts*
         -
*Intro to Open Source / Communications Tools, more in-depth *
         -  More advanced students will likely be happy to sit through a
         review on these topics, especially if we emphasize “*how it all
         fits together*”. But the option of having advanced students start
         on contributions during this time could also be good.


   - Lunch --* I propose something different than regular OSCTC events*
   - *Networking session with mentors and older students seeking
      internships*
         - We'd like to maximize the networking time of our students who
         are seeking internships for this summer. If possible, we'd like these
         students to sit down to lunch with our mentors to talk more one on one.


   - Early afternoon
      - *Version control / git subgroups*. Students choose a group based on
      their comfort / level, and work on something with a small group and a
      mentor.


   - Advanced git
   - Intro to git (git add, rm, commit, push, pull, status)
   - Concepts of version control


   - Later afternoon
      - *Contributions workshop*
         - I think it would be nice to have a lot of issues / bugs lined up
         for students to jump into.

Thoughts?

-Katie
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/campus-hartnell-staff/attachments/20141103/f73d1de6/attachment.html>