[Campus-neiu-staff] building access details

[Shauna Gordon-McKeon]

This checklist may be more relevant, since it's tailored to our events:
https://openhatch.org/wiki/OSCTC_space_checklist

Thanks for linking your list, Carl - will definitely take a look through
and see if we should add anything to ours.


On Mon, Apr 21, 2014 at 12:59 PM, Jeremy L. Grajales <
jeremygrajales at gmail.com> wrote:

> I can fill in some of these details. But what are they for Meg?
>
>
> On Mon, Apr 21, 2014 at 11:53 AM, meg ford <meg387 at gmail.com> wrote:
>
>> The doc needs to be filled out by the people who made the reservations of
>> course :)
>>
>>
>> On Mon, Apr 21, 2014 at 11:52 AM, meg ford <meg387 at gmail.com> wrote:
>>
>>> Here is a link to a document based on Carl's checklist:
>>>
>>> https://docs.google.com/document/d/1yH_X_QuLfnKZQ6fgaYdhTmGmezKbXVzL29OUu9bJTvo/edit?usp=sharing
>>>
>>> I'm not sure if we need all the AV info. If there are any items specific
>>> to recording talks can you remove them, Carl?
>>>
>>> Also, are attendees bringing their own laptops? There isn't any way to
>>> install software on the school's computers so they need their own.
>>>
>>> Thanks,
>>> Meg
>>>
>>>
>>> On Mon, Apr 21, 2014 at 11:33 AM, Carl Karsten <carl at nextdayvideo.com>wrote:
>>>
>>>> Here is a check list I use for ChiPy meetings:
>>>>
>>>> http://chipyvenue.pythonanywhere.com/questionnaire/information/2
>>>>
>>>> I would cut/paste the items into the google doc and fill them in as
>>>> people provide the answers.  remove the inapplicable items so that you can
>>>> see what still needs an answer.
>>>>
>>>> On Mon, Apr 21, 2014 at 10:54 AM, Jeremy L. Grajales <
>>>> jeremygrajales at gmail.com> wrote:
>>>>
>>>>> Meg, not sure about when we'll have access to the room. Professor
>>>>> Iacobelli made those reservations I believe.
>>>>>  On Apr 21, 2014 10:24 AM, "Shauna Gordon-McKeon" <shaunagm at gmail.com>
>>>>> wrote:
>>>>>
>>>>>>
>>>>>>>>
>>>>>>> Jim mentioned that he might be willing to present the activity. Jim,
>>>>>>> are you willing to do it? I can help students with this also. I agree that
>>>>>>> it would be helpful to have someone on #openhatch to walk us through things
>>>>>>> in case there is something no one is familiar with.
>>>>>>>
>>>>>>
>>>>>> Asheesh will be available all day on #openhatch.  I will also be
>>>>>> around, but less available, as I'll be physically at an event at MIT.
>>>>>>  There may be additional people in the channel who can help as well.
>>>>>>
>>>>>>
>>>>>>> Shauna, is this the page we should use for the first contributions
>>>>>>> section of the workshop: https://openhatch.org/wiki/First_Tasks
>>>>>>>
>>>>>>
>>>>>> Yes, that's the page.  Although that being said, I think it makes
>>>>>> sense for us to switch to using event-specific pages, so I've made one here:
>>>>>> https://openhatch.org/wiki/Open_Source_Comes_to_Campus/NEIU/tasks
>>>>>>
>>>>>> Projects that won't have a person available at the event (either in
>>>>>> person or remotely) can go under "recommended projects".  Projects that
>>>>>> people will be available to help with can go under "curated tasks".  Other
>>>>>> resources can go under additional resources.
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> Also, is it OK to point students towards the MediaGoblin section on
>>>>>>> this page: https://openhatch.org/wiki/Additional_tasks
>>>>>>> if they need help choosing a first task?
>>>>>>>
>>>>>>> Meg
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>> Absolutely.  You can copy the MediaGoblin section to "recommended
>>>>>> projects" or, if someone familiar with the project (you?) will be around to
>>>>>> help, to the "curated tasks" section.
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>>  This page gives details on what's involved in
>>>>>>>>> mentoring/presenting for each part:
>>>>>>>>>
>>>>>>>>> http://openhatch.github.io/open-source-comes-to-campus/mentorguide.html
>>>>>>>>>
>>>>>>>>> If everyone could take a look through and see what they feel
>>>>>>>>> comfortable presenting/leading/floating/etc.
>>>>>>>>>
>>>>>>>>> best
>>>>>>>>> Shauna
>>>>>>>>>
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> _______________________________________________
>>>>>>>>> Campus-neiu-staff mailing list
>>>>>>>>> Campus-neiu-staff at lists.openhatch.org
>>>>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>>>>>>>>
>>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> --
>>>>>>>> shekay at pobox.com
>>>>>>>>
>>>>>>>> _______________________________________________
>>>>>>>> Campus-neiu-staff mailing list
>>>>>>>> Campus-neiu-staff at lists.openhatch.org
>>>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>>>>>>>
>>>>>>>>
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Campus-neiu-staff mailing list
>>>>>>> Campus-neiu-staff at lists.openhatch.org
>>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>>>>>>
>>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> Campus-neiu-staff mailing list
>>>>>> Campus-neiu-staff at lists.openhatch.org
>>>>>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>>>>>
>>>>>>
>>>>> _______________________________________________
>>>>> Campus-neiu-staff mailing list
>>>>> Campus-neiu-staff at lists.openhatch.org
>>>>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>>>>
>>>>>
>>>>
>>>> _______________________________________________
>>>> Campus-neiu-staff mailing list
>>>> Campus-neiu-staff at lists.openhatch.org
>>>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>>>
>>>>
>>>
>>
>> _______________________________________________
>> Campus-neiu-staff mailing list
>> Campus-neiu-staff at lists.openhatch.org
>> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>>
>>
>
> _______________________________________________
> Campus-neiu-staff mailing list
> Campus-neiu-staff at lists.openhatch.org
> http://lists.openhatch.org/mailman/listinfo/campus-neiu-staff
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openhatch.org/pipermail/campus-neiu-staff/attachments/20140421/235b967a/attachment-0001.html>