[Ccsf-campus-staff] how did the event go?

[Katherine Moloney]

Just for context, I asked Maria to touch upon her journey into open source
that she described here:

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


...as part of handling this section:

https://openhatch.org/wiki/OSCTC/Tools


...for me, how to use irc and git/GitHub seemed to be handled elsewhere
naturally, so I was hoping that this section ("Communication Tools") would
focus on discovering projects, reading thru their materials, and then get
into which communication channels for which types of communication.

I'd love to see a training module added on how to log irc conversations (I
guess this is called an 'irc bouncer') for catching up with what happened
when you are not online -- see next message which I am forwarding for that
conversation.

Regards,

Katherine


On Thu, Apr 10, 2014 at 2:17 AM, Maria Pacana <maria.pacana at gmail.com>wrote:

> Did you use any of the activities in our curriculum (for instance, getting
>> students onto IRC, the bug comprehension exercise)?
>>
> I didn't do either of those activities. We'd just had the 30-min IRC
> workshop, so I figured that we'd already done enough IRC-ing for the day,
> and I had an activity idea of my own (see below).
>
>  If there's anything new you did that you think went over well I'd love
>> to hear about it.  :)
>>
> I didn't quite have enough time to execute my activity idea perfectly; I
> squeezed it into the last 20m. Ideally students would probably spend at
> least an hour doing this activity. Here's how I'd suggest structuring it,
> in an ideal world:
>
> 1) Ask students to brainstorm OS projects they want to contribute to. Show
> them how to explore and evaluate projects on OpenHatch, GitHub, OhLoh, etc.
> (does the project involve languages / topics I am familiar with or
> interested in? are people actively contributing to it? etc.)
>
> 2) Once students have a specific project in mind, have them look for a bug
> / issue that they want to work on.
>
> 3) Once they have a bug in mind, have them draft an email or IRC message
> to the maintainers, in which they introduce themselves and ask a couple of
> questions about the project or the bug they're working on. Slightly
> contrived, but it helps get the ball rolling. The message was based on the
> following criteria (which I took from Mel Chua <http://blog.melchua.com/>
> ):
>
>    - Can this person independently navigate the resources my project has
>    on the website? (base level initiative)
>    - Is this person trying to do something that would be helpful to me?
>    - Is there a specific ask I could help with?
>    - Is there a way I can publicly respond to this person? (not
>    bottlenecking)
>
>
> 4) Have students critique each other's draft messages before sending them
> off.
>  _______________________________________________
>
>>  ccsf-campus-staff mailing list
>>> ccsf-campus-staff at lists.openhatch.org
>>> http://lists.openhatch.org/mailman/listinfo/ccsf-campus-staff
>>>
>>>
>>
>> _______________________________________________
>> ccsf-campus-staff mailing list
>> ccsf-campus-staff at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/ccsf-campus-staff
>>
>>
>
> _______________________________________________
> 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/20140410/91f5cfec/attachment.html>