[Ccsf-campus-staff] checking in

Tue Mar 18 23:33:26 UTC 2014

Hi Katherine,

I'd be happy to go over the "communication tools" section! Although it
sounds like that talk really consists of two topics: one on how to
initially screen for open source projects using OpenHatch / OhLoh / etc,
and another one about reaching out to people on interesting OS projects
using different communication tools. I'm not sure how much advice I have on
the former (aside from "OpenHatch / OhLoh / Google it"). So if another
mentor's got a better approach to screening for projects, perhaps they
could take over that part of the session. (Otherwise, I will dispense what
knowledge I have.)

On Tue, Mar 18, 2014 at 4:08 PM, Katherine Moloney
<kmoloney at mail.ccsf.edu>wrote:

> Hello,
>
> *) None of the mentors beyond Geoff are on this ccsf-campus-staff list:
>
> veronica.l.ray at gmail.com maria.pacana at gmail.com alex.gaynor at gmail.com
> jlewi at google.com
>
>
> ...should I just directly add everyone (and then they can unsubscribe<http://lists.openhatch.org/mailman/listinfo/ccsf-campus-staff>after the event is over)?
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > B)  Each section needs a presenter who is comfy with presenting it.
>
> I've made a spreadsheet 20140322 OSCTC Presentation Scheduling<https://docs.google.com/a/mail.ccsf.edu/spreadsheet/ccc?key=0Av9oxqSu1j8mdFVySnRDQldOcmZkdXRpQ1BNamktM3c#gid=0>,
> so everyone can be on the same page about how the day will be broken up.
> *Geoff* & *Asheesh*, edit this to match what you've been talking about.
>
>
>    - For whoever takes the *'irc introduction'*, the key is to *not go
>    too fast*. This is the first section of the day, and, for many of the
>    students, this will be a foreign country.
>    - This is a nice summary to use & to share with the students:
>       http://www.ircbeginner.com/ircinfo/ircc-commands.html
>       - One thing that worked really well last time (the first time we
>       ran this workshop) was sharing links with students via irc -- so they
>       couldn't ignore it altogether
>
> ...if this section goes slowly & repetitively that seems to work out okay,
> advanced users joke around, and novices get the hang of it.
>
>
>    - *Maria*, I queued you up for the *'Communications Tools'* section
>    since you could talk about how you came to Parsoid, and how you first
>    learned about the project, how you first immersed yourself in it, etc.  I
>    saw on your Tumblr -- mariapacana.tumblr.com -- that you had several
>    nice posts about this process:
>
>
> http://mariapacana.tumblr.com/post/66509721444/dont-try-to-understand-the-whole-thing
>
> http://mariapacana.tumblr.com/post/67473860470/hacker-school-weeks-6-7-retrospective (Contributing
> to Parsoid)
>
> http://mariapacana.tumblr.com/post/71338780796/my-opw-internship-getting-started
> http://mariapacana.tumblr.com/post/73515099315/meeting-my-mentor
> http://mariapacana.tumblr.com/post/74985090833/coding-by-consensus
> http://mariapacana.tumblr.com/post/78260425415/the-never-ending-patch
>
> I figure in the process you can organically touch on exploring the project
> website, bug tracker, irc channel vs email vs mailing lists, etc.  And then
> summarize these communication tools at the end of the presentation:
>
>
> https://openhatch.org/wiki/OSCTC/Tools
>
>
> Relatedly, these might be useful:
>
> *http://opensource-events.com/#project-setup
> <http://opensource-events.com/#project-setup>*
>
> http://www.pyvideo.org/video/513/pyohio-2010--teach-me-python-bugfixing
>
>
> ...in thinking about what you'd want to say, but really just speak from
> your experience.
>
>
>    - ...then we flow into the *Career Panel  (Geoff, Veronica, Maria,
>    Alex, Jeremy
>    <https://docs.google.com/a/mail.ccsf.edu/document/d/1E3ejH2UEG0NxzgTzESSqeOrUMouGV7u0JcRFTqNVOIw/edit>)*
>    - ...and then into *Lunch <http://palmyrasf.com/menu/>*
>    - *Veronica*, does 'Refuge Restrooms<https://github.com/tkwidmer/refugerestrooms/issues>'
>    have any bite-sized bugs or features that could be dealt with during the
>    workshop?
>       - If so, you could lead the '*Git/GitHub introduction*'
>          - either with a bite-size bug that you can continue working on
>          during the workshop, in the modeling section of the contribution workshop
>          (see below for that discussion)
>          - or with a walk-thru of an already completed bug/feature, a la:
>             -
>             http://www.pyvideo.org/video/513/pyohio-2010--teach-me-python-bugfixing
>             - Just by looking at the issue names, the following look
>          intelligible to new eyes:  #79, #53, #41, #39, #34, #11, #10, #4
>       - If not, does anyone else have a project with a bite-sized bug?
>          - I'm going to the Python hack night tomorrow to recruit
>          additional mentors, so maybe one of them will.
>       - Or does Open Hatch have one?
>    - ...and then on to the *Contribution workshop*
>       - While students can work on their own, it seems essential for
>       there to be one mentor leading a guided session.  This could go a number of
>       ways:
>          - one or alternating student(s) could "drive" and then the group
>          (with guidance/hints from the mentor) can call out what they think the
>          "driver" should do, or
>          - mentor can "drive" and talk about what they're doing and why,
>          and seek student input where possible
>
> Whoever just read all of that is a champion -- thank you.
>
> Now Geoff, Asheesh, Maria, Veronica and anyone else please change up that
> whole plan as you see fit.
>
> I am a student, so I am certainly not the expert here in the subject or
> how to organize the workshop.
>
> (I have a sense of the pacing that would server our average current skill
> set, and what worked & didn't work last time.)
>
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Last I looked we had 57 students registered<https://docs.google.com/a/mail.ccsf.edu/spreadsheet/ccc?key=0AlYlN3mu5OJbdFVsQnFyTHFQM2ZFUzZ4cTR0SXJuVEE&usp=drive_web#gid=0>.
> Assuming the same attendance rate as last time, that averages out to 45
> students, so I'm still attempting to recruit more mentors.  If you know
> anyone who would be interested & available, please invite them.
>
> Regards,
>
> Katherine
>
>
>
>
> On Tue, Mar 18, 2014 at 1:11 PM, Shauna Gordon-McKeon <shaunagm at gmail.com>wrote:
>
>> Hi CCSF organizers,
>>
>> Just wanted to check in and see how everything's going.  I've been
>> operating on the "if they need anything from OpenHatch, they'll ask"
>> principle, but I wanted to let you know/remind you of a few things:
>>
>> A)  For projects time, it's generally a good idea to have a few specific
>> projects prepped for people to work on.  It looks like, from the volunteer
>> emails I've seen, there are a few volunteers coming who maintain open
>> source projects.  We should invite them to feature them at the event!  If
>> you/they want help getting their projects set up, just contact me/Asheesh
>> via this ccsf-campus-staff list.
>>
>> B)  Each section needs a presenter who is comfy with presenting it.  If
>> you don't have that, let us know, so we can do some targeted recruitment.
>>
>> C)  Asheesh will be around evenings this week to meet with people, online
>> or in person, to answer questions/go over curriculum/etc.
>>
>> I think that's all.  Let me know if there's anything else I can help with!
>>
>> ~ Shauna
>>
>> _______________________________________________
>> ccsf-campus-staff mailing list
>> ccsf-campus-staff at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/ccsf-campus-staff
>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/ccsf-campus-staff/attachments/20140318/959885d4/attachment.html>