This site is an archive; learn more about 8 years of OpenHatch.

[Campus-hartnell-staff] [MENTORS] planning for Saturday

Katie Cunningham kcunningham at csumb.edu
Sat May 3 05:41:40 UTC 2014 

Thanks Asheesh! I'm so glad to be able to work with you guys.

Here are a couple last pointers to make things more convenient:

Here's a link to a Google map of the event building:
https://goo.gl/maps/9kqSC. We're in the middle of a lot of nothing on a
former army base, so don't worry if you feel like you're in the middle of
nowhere or see abandoned army barracks :)

Parking permits are required on campus. I'll have a few on hand, so please
come get one from me to take back to your car.

If you have any issues, feel free to call me at 831 717 7971. I'll get to
the building around 10a I think.

Thanks so much again to everyone, and have a safe drive!

-Katie



On Fri, May 2, 2014 at 9:40 PM, Asheesh Laroia <lists at asheesh.org> wrote:

> FWIW, *Jesse*, I think your project is super cool. As I was reading this
> thread, to catch up, I happened to say out loud: "Whoa! This reddit
> brackets thing is so cool!"
>
> *Katie*, if there's still time, and it makes the pizza situation simpler,
> I'm happy to provide an OpenHatch card to use for the pizza. I will bring
> the card tomorrow.
>
> *Shauna*, huge thanks for all the work you have done in organizing. I'll
> prepare some bitesize bugs in the OpenHatch project. There is always room
> for improvement on openhatch.org.
>
> For everyone -- http://openhatch.org/missions/git is the git tutorial
> we'll be using. Given that, it's extremely helpful if you personally work
> through it at least one time, before you work through it with a student. It
> makes a *world* of a difference if you're familiar with it.
>
> *Katie*, I am so excited that you put this event together, and so happy
> to be helping tomorrow.
>
>
> re: quailjs: It would be so great if we could get someone interested in
> mentoring students who want to work on qualjs! It seems like a great
> project. It'd be fantastic if one of the local mentors could see if it were
> feasible to set up a development environment for students; quailjs actually
> seems supremely well-suited to this event, since it is in Javascript (from
> what I can tell) and therefore would require minimal dependencies other
> than a text editor and a web browser.
>
> https://github.com/quailjs/quail/issues/211 might be a fun first-task for
> a quailjs contributor. It might require a mentor to explain what a
> bookmarklet is, but I think that's fine.
>
>
> *Jonathan*, since you won't be mentoring on any particular project, I
> wonder if I can get you to be a mentor for the OpenHatch website itself,
> and/or to see what the setup process for quailjs is like. If you want to
> try mentoring students to work on OpenHatch itself,
> http://openhatch.readthedocs.org/en/latest/ is our documentation on how
> to set up the development environment.
>
> I see that I'm on the hook for Introduction / Open Source Communication
> Tools -- I'll deliver this based on the current
> https://openhatch.org/wiki/OSCTC/Tools document. (Shauna, please correct
> me if this is not the right link.)
>
>
>
> *Katie*, if you're going to be leading students through Wikipedia edits,
> I recommend looking for a few pages that need fixes before you ask students
> to do it. That way, you'll have specific things for them to work on. If I
> were leading that, I would do the following things:
>
> 1. Read https://en.wikipedia.org/wiki/Help:Getting_started yourself
> (Katie) to prep, and use clarity gleaned from that to lead a 10 minute
> group conversation where you ask people what they know about editing
> Wikipedia, and see what misconceptions you can address, then
>
> 2. Group them in pairs, and ask them to take 8 minutes to read about
> various Wikipedia "rule"s, picking one to focus on; then after the 8
> minutes, explain that rule to one other student:
> http://en.wikipedia.org/wiki/Wikipedia:Policies_and_guidelines (my
> favorite is probably "Break All Rules")
>
> 3. https://en.wikipedia.org/wiki/Wikipedia:Training/Newcomers is a
> plausible-looking newcomers tutorial, for students who want more practice
> with the technical details.
>
> 4. Have them work in pairs to make the specific fixes to specific pages
> you found while prepping for this.
>
> 5. You could pick some WikiProject, like
> http://en.wikipedia.org/wiki/Wikipedia:WikiProject_North_Americaspecifically, and scroll down to the "tasks you can do" link, and have them
> all work on different tasks in there, perhaps by working together in pairs.
>
> For those that I don't know, so nice to meet you all!  All of you, see you
> tomorrow.
>
>
>
> On Fri, May 2, 2014 at 7:26 PM, Katie Cunningham <kcunningham at csumb.edu>wrote:
>
>> This is fantastic! Thank you so much Shauna for all your hard work to
>> bring this together. I can't believe the event is here already!
>>
>> I have a big box of local strawberries from the guy who sells them down
>> the street, and I've scoped out the room. I'm an a student award ceremony
>> right now, but I'll send out an email with a map of the building and any
>> other advice I can think of.
>>
>> Also, Shauna, is the pizza lunch a reimbursement situation?
>>
>> Thanks again!
>> Katie
>> On May 2, 2014 10:09 AM, "Shauna Gordon-McKeon" <shaunagm at gmail.com>
>> wrote:
>>
>>> Great.  So we're pretty much set, except for having someone take
>>> pictures.
>>>
>>> For the contributions workshop, the set up will be thus:
>>>
>>> * The "Finding a Projects demo":  Asheesh will demo, at the front of the
>>> room, doing this activity with the whole room as his "small group":
>>> https://openhatch.org/wiki/Open_Source_Comes_to_Campus/Curriculum/Finding_a_Project
>>> Then, you'll break off into small groups and go through the activity in
>>> small groups.  By the end of 20 min to half an hour, students should have
>>> contacted in some way at least one project.
>>>
>>> * Students will then pause for the rest of the workshop to be
>>> introduced.  Students will be given the option of continuing to investigate
>>> the project they found, or joining a small group:
>>>   - Asheesh working on OpenHatch
>>>   - Katie working on Wikipedia
>>>   - Ryan working on Python tickets
>>>   - Jesse working on the bracket manager
>>>
>>> What's key in this second part of the workshop is being attentive to
>>> students and helping them solve their own problems, not immediately knowing
>>> the answers to their questions.  Some questions you can ask to help provoke
>>> thought/further exploration:
>>> * Do you know what this project does?  What interests you about it?
>>> * Have you said hello to the community?  Does it have an IRC
>>> channel/have you joined it?
>>> * Does the project have a guide for contributors?  Have you read it?  Is
>>> there stuff you don't understand?
>>> * Have you tried installing the project/getting it running on your
>>> computer?
>>> * Have you looked through the bug tracker?  Have you found a couple
>>> issues that seem interesting?  (If yes: can you explain what you think is
>>> happening?  Are there parts that you find confusing?)
>>>
>>> The contributions workshop should not be framed as an activity with a
>>> set process and a clear solution, the way the earlier activities are.  It
>>> is a process of exploration.  In some ways it's better if you're not an
>>> expert on a project, as you can role model the process of exploration.  If
>>> you can show them how to explore, and show them how much fun you have doing
>>> it, then you'll be successful.  :)
>>>
>>> best
>>> Shauna
>>>
>>>
>>> On Thu, May 1, 2014 at 2:39 PM, Katie Cunningham <kcunningham at csumb.edu>wrote:
>>>
>>>> Sorry, I was preoccupied with my organizer hat and forgot my mentor hat
>>>> :)
>>>>
>>>> 1) I believe I can lead a git group with the mission's guidance. I
>>>> don't have much experience beyond git basics, so if one of those
>>>> showstopping git errors pops up I may need assistance.
>>>>
>>>> 2) I think all but 3 of the attendees know about my job, so probably no
>>>> on the career panel.
>>>>
>>>> 3) I have edited pages on MediaWiki, so I may be in a solid spot to
>>>> help guide Wikipedia contributions.
>>>>
>>>> I just talked to a technology staff member here at CSUMB who works on a
>>>> project called Quail <http://quailjs.org/>. It's a tool to check if a
>>>> website you've designed has everything needed proper accessibility
>>>> (pictures have alt-text for blind users, color scheme doesn't cause
>>>> problems for colorblindness, etc). If a student were to be involved in this
>>>> project, it seems they could get a lot of local mentorship. Do you think it
>>>> would be appropriate to mention this project at some point on Saturday?
>>>>
>>>> Thanks!
>>>> -Katie
>>>>
>>>>
>>>> On Thu, May 1, 2014 at 9:36 AM, Ryan Compton <rcompton at ucsc.edu> wrote:
>>>>
>>>>> 1) Yes I can lead a group on Git
>>>>>
>>>>> 2) Yes I can be on the career panel
>>>>>
>>>>> 3) No projects that would be good for contributions since they are
>>>>> very specific to some research projects. But I can take a look at the
>>>>> Python Tickets project and see if I can familiarize myself with it well
>>>>> enough before Saturday.
>>>>>
>>>>>
>>>>> On Thu, May 1, 2014 at 8:48 AM, Shauna Gordon-McKeon <
>>>>> shaunagm at gmail.com> wrote:
>>>>>
>>>>>> Thanks for the feedback, everyone.  I've updated the responsibilities
>>>>>> sheet, which is now mostly filled out, although it would still be quite
>>>>>> helpful for Katie and Ryan to answer the questions above and/or take a look
>>>>>> at the sheet.  We can definitely use more mentors for various things.
>>>>>>
>>>>>> For people leading small groups teaching git, the current git
>>>>>> activity is this one: http://openhatch.org/missions/git
>>>>>>
>>>>>> For the contributions workshop, here are some projects that have good
>>>>>> documentation about how to contribute.  Would anyone be interested in
>>>>>> taking a little time to familiarize themselves with the project and then
>>>>>> leading contributions to them?
>>>>>>
>>>>>> Python - https://openhatch.org/wiki/Triaging_Python_tickets
>>>>>> Wikipedia - https://en.wikipedia.org/wiki/Wikipedia:Community_portal
>>>>>> (non-programming tasks)
>>>>>> Mozilla - http://www.mozilla.org/en-US/contribute/
>>>>>>
>>>>>> It's okay that you're not expert at these projects - the key is to be
>>>>>> able to role model a good approach for contributing to a new project.  :)
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Thu, May 1, 2014 at 3:27 AM, Chas Leichner <chas at chas.io> wrote:
>>>>>>
>>>>>>> Yes to git. Yes to career. No to current project, though I have
>>>>>>> participated in the google summer of code and I could explain that process.
>>>>>>>
>>>>>>>
>>>>>>> On Wednesday, April 30, 2014, Jesse Gunsch <j at qxlp.net> wrote:
>>>>>>>
>>>>>>>> 1) Yes to leading a group through Git.
>>>>>>>>
>>>>>>>> 2) Yes to being on the career panel.
>>>>>>>>
>>>>>>>> 3) I work semi regularly on chromium but that's not really feasible
>>>>>>>> for introductory contributions.
>>>>>>>>
>>>>>>>> I did run a college basketball bracket manager for reddit this year
>>>>>>>> (http://brackets.qxlp.net) which has all its code on github, and
>>>>>>>> could manage some small contributions to that pretty easily.
>>>>>>>> On Apr 30, 2014 9:55 AM, "Shauna Gordon-McKeon" <shaunagm at gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> Hi folks,
>>>>>>>>>
>>>>>>>>> I've updated the "day of responsibilities" with times for each
>>>>>>>>> activity.  It would be great if all of our volunteer mentors could respond
>>>>>>>>> to this email and answer:
>>>>>>>>>
>>>>>>>>> * Would you feel comfortable leading a small group of students
>>>>>>>>> through how to use git, by following our git activity?
>>>>>>>>>
>>>>>>>>> * Would you be interested in being on the career panel/history and
>>>>>>>>> ethics panel?
>>>>>>>>>
>>>>>>>>> * Do you have an open source project that you maintain and/or
>>>>>>>>> would feel comfortable helping students contribute to?
>>>>>>>>>
>>>>>>>>> best
>>>>>>>>> Shauna
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Campus-hartnell-staff mailing list
>>>>>>>>> Campus-hartnell-staff at lists.openhatch.org
>>>>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>>>>>>>>
>>>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Campus-hartnell-staff mailing list
>>>>>>> Campus-hartnell-staff at lists.openhatch.org
>>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Campus-hartnell-staff mailing list
>>>>>> Campus-hartnell-staff at lists.openhatch.org
>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>>>>>
>>>>>>
>>>>>
>>>>> _______________________________________________
>>>>> Campus-hartnell-staff mailing list
>>>>> Campus-hartnell-staff at lists.openhatch.org
>>>>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Campus-hartnell-staff mailing list
>>>> Campus-hartnell-staff at lists.openhatch.org
>>>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>>>
>>>>
>>>
>>> _______________________________________________
>>> Campus-hartnell-staff mailing list
>>> Campus-hartnell-staff at lists.openhatch.org
>>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>>
>>>
>> _______________________________________________
>> Campus-hartnell-staff mailing list
>> Campus-hartnell-staff at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>>
>>
>
> _______________________________________________
> Campus-hartnell-staff mailing list
> Campus-hartnell-staff at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/campus-hartnell-staff
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/campus-hartnell-staff/attachments/20140502/3dd2e796/attachment-0001.html>

More information about the Campus-hartnell-staff mailing list