[Campus-uofa-staff] getting mentors for the event

Thu Feb 6 21:05:47 UTC 2014

I'll send out the reminder emails when I get out of class today

Z.

On Thu, Feb 6, 2014 at 1:53 PM, Shauna Gordon-McKeon <shaunagm at gmail.com>wrote:

> For the remote career panel:
>
> - I shouldn't have a problem finding 3 mentors (I wouldn't recommend more,
> as each person additional increases the likelihood of technical issues).
>  The key is figuring out what time the career panel will be, so we can ask
> people to keep a specific time free. Once you get me that, I'll send out
> emails.
>
> - With only a few days notice, I think it makes sense to limit the remote
> mentors to OpenHatch.  From past experience, it would be useful to arrange
> about 5 minutes for Asheesh and/or myself to talk to the attendees before
> the contributions workshop starts, so we can explain a bit about what we
> have for them to work on.  (We recommend that mentors with open source
> projects also prepare a 3-5 minute explanation of what they have to work
> on.)
>
> ~ Shauna
>
>
> On Thu, Feb 6, 2014 at 3:46 PM, Shane Gianelli <shanejgianelli at gmail.com>wrote:
>
>> Sorry, yes to both, I really like the idea of giving students a chance to
>> chat directly with mentors.
>>
>> Let me know what we will need to set up for that portion.
>>
>> Thanks,
>>
>> Shane
>>
>>
>> On Thu, Feb 6, 2014 at 1:43 PM, Kate Maroney <
>> katemaroney at email.arizona.edu> wrote:
>>
>>> If you can get remote mentors, that would be great, I know last minute
>>> is difficult.
>>>
>>> Food will be ordered today, and I've looked at the list of attendees
>>> with dietary needs. We're all set up with equipment, and I'll take care of
>>> taking photos and notes.
>>>
>>>
>>> On Thursday, February 6, 2014, Shauna Gordon-McKeon <shaunagm at gmail.com>
>>> wrote:
>>>
>>>> Shane:  I'm going to assume the answer to those questions is no, unless
>>>> I hear otherwise from you.  (At which point I'll do what I can to make them
>>>> happen, but I can't promise anything.)
>>>>
>>>> Zuoming:  Usually about 2-3 days out from the event, we send out a
>>>> reminder email asking people to confirm that they're coming.  If you
>>>> haven't yet, you should consider doing so.  :)  From past experience, 90%
>>>> of sign ups that confirm they're coming will come, and about 30% of
>>>> attendees that never respond will show up.
>>>>
>>>> Kate:  Are you all set with food?  Make sure to check the attendee
>>>> signup list for allergies and vegetarians/vegan.  There's also the second
>>>> half of the space checklist<https://openhatch.org/wiki/OSCTC_space_checklist>to make sure you're set up equipment-wise.  Are you planning to have
>>>> someone take pictures and/or take notes?
>>>>
>>>> One more note - we have an exit survey that we'd love for students to
>>>> fill out.  We love to get as much feedback as we can so we can improve our
>>>> events.  If you can make sure the students see this link - I would
>>>> recommend putting it up on a chalkboard/blackboard at the start of the day,
>>>> and then mentioning it a few times to remind folks - that'd be great:
>>>> http://bit.ly/uofa-exit-survey
>>>>
>>>> best
>>>> Shauna
>>>>
>>>>
>>>>
>>>> On Wed, Feb 5, 2014 at 12:59 AM, Shauna Gordon-McKeon <
>>>> shaunagm at gmail.com> wrote:
>>>>
>>>> Looks like you've got everything covered!  That's great to hear -
>>>> thanks for going over it all with me.
>>>>
>>>> Just to clarify a few things:
>>>>
>>>> - Am I correct that you'd like to do a remote career panel, via google
>>>> hangouts?  If so, how many people would you like on the panel?  For remote
>>>> panels I recommend staying small, to minimize logistical issues. I can do
>>>> email introductions for you and some potential remote mentors tomorrow.
>>>>
>>>> - Would you like us arrange for any projects with remote mentors via
>>>> IRC?  We have plenty of contributions people can make to OpenHatch itself.
>>>>  We find that students enjoy this because it's easy to immediately connect
>>>> to a community (ours), but it's also great to work on projects with someone
>>>> physically at the event.  Whatever you prefer.  :)
>>>>
>>>> best
>>>> Shauna
>>>>
>>>>
>>>> On Wed, Feb 5, 2014 at 12:08 AM, Shane Gianelli <
>>>> shanejgianelli at gmail.com> wrote:
>>>>
>>>> Yes, I will be running the event on Saturday.
>>>>
>>>> I think the schedule model you posed is what we had settled on, with a
>>>> minor modification.  After the Career Panel, we were planning on having a
>>>> 30 minute talk-back with all the mentors who, for the most part, all have
>>>> real-world work experience so that we can help answer any other questions
>>>> the students might have.
>>>>
>>>> The Mentor-Event breakdown will be as follows:
>>>>
>>>> Laptop Setup - *Matt,* Kate - We will help get all machine variations
>>>> setup, all mentors will be on hand to help  on a one-on-one basis.
>>>>  Open Source Tools - *Chris LaRose *- With other mentors offering
>>>> one-on-one help.
>>>> Practicing Git Activity - *Chris van Horne*
>>>> Career Panel - *Shane* - I will introduce this event and facilitate it.
>>>> Mentor Talk Back - *Roey* - Roey will lead the discussion but all
>>>> mentors will be involved.
>>>> Workshop - I am asking that all Mentors bring a project or an idea with
>>>> them that they will present and responsible for engaging with the students
>>>> involved in it during the workshop period.
>>>>
>>>> I will make sure to keep everything on track and introduce each event,
>>>> yes.  I will be emailing all of the mentors tonight.
>>>>
>>>> Thanks,
>>>>
>>>> Shane
>>>>
>>>>
>>>> On Tue, Feb 4, 2014 at 10:30 AM, Shauna Gordon-McKeon <
>>>> shaunagm at gmail.com> wrote:
>>>>
>>>> Thanks for getting back to me.  The next thing we have to do, by the
>>>> end of the day, is to discuss the curriculum and make sure we have people
>>>> willing to run the various parts.
>>>>
>>>> Shane, I presume you will be the one "running" the event - that is,
>>>> making sure each activity proceeds roughly on time, reminding people when
>>>> it's their turn to present, etc?
>>>>
>>>> My suggested schedule:
>>>>
>>>> 10am-10:30am Laptop Setup<https://openhatch.org/wiki/Open_Source_Comes_to_Campus/Curriculum/Laptop_setup>,
>>>> Introductions (Need someone to lead introductions, low effort)
>>>> 10:30-11:30am Open Source Tools presentation<https://openhatch.org/wiki/OSCTC/Tools>(Need someone to lead this, high effort)
>>>> 11:30-12:30pm Practicing Git activity<https://openhatch.org/wiki/Open_Source_Comes_to_Campus/Practicing_Git> (Need
>>>> someone to introduce the activity, low effort, and at least 3-4 people
>>>> willing to lead small groups)
>>>> 12:30-1:30 Lunch
>>>> 1:30-2:00 Career Panel - It seems like all your mentors are students.
>>>>  That means we should either do a remote career panel, using google
>>>> hangouts, or turn it into more of a "talk about your experiences" panel.
>>>>  Depending on what you choose, we'll have different needs for mentors.
>>>> 2:00-5:00 Contributions Workshop - Needs someone to introduce the
>>>> activity and run checkins at 3, 4 and a wrap-up at 5.  We need to pair
>>>>
>>>>
>>>
>>> --
>>> Kate Maroney
>>> CSc 245 Section Leader
>>> Co-President, WiCS
>>> Microsoft Intern Ambassador
>>>
>>>
>>> _______________________________________________
>>> Campus-uofa-staff mailing list
>>> Campus-uofa-staff at lists.openhatch.org
>>> http://lists.openhatch.org/mailman/listinfo/campus-uofa-staff
>>>
>>>
>>
>> _______________________________________________
>> Campus-uofa-staff mailing list
>> Campus-uofa-staff at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/campus-uofa-staff
>>
>>
>
> _______________________________________________
> Campus-uofa-staff mailing list
> Campus-uofa-staff at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/campus-uofa-staff
>
>

-- 
Zuoming Shi
President, UA Video Game Developers Club
President, UA Asian Music Club
Computer Science and Mathematics, University of Arizona
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/campus-uofa-staff/attachments/20140206/76c52adc/attachment.html>