Open Source Comes to Campus/UMD/Staff: Difference between revisions

← Older edit

Open Source Comes to Campus/UMD/Staff (view source)

Revision as of 01:53, 25 February 2012

991 bytes added , 12 years ago

→‎Venue logistics

Anonymous user

imported>Paulproteus

Revision as of 05:52, 23 February 2012 (view source) imported>Paulproteus No edit summary ← Older edit		Latest revision as of 01:53, 25 February 2012 (view source) imported>Paulproteus (→‎Venue logistics)
(11 intermediate revisions by the same user not shown)
Line 9: How to get there, '''by car, or for more details''': See the [http://www.admissions.umd.edu/visit/directions/index.cfm official UMD Visitor's Guide] Once on campus, you'll have to find the Computer Sciences building <http://classrooms.umd.edu/buildings/csi.html>. Note that we have reserved the entire third floor of this building, for both days. (On[http://g.co/maps/9nhe9 ~~Friday, Feb 24, Asheesh will add a note~~Close to this ~~page with more details about the building's location on campus.~~intersection]) == Concept behind the weekend == Line 29: * Deonna is our local contact with UMD AWC. * Maco Morgan is leading the command-line module. ** Kaitlin Lee will be TAing the command-line module. * Venkatesh Srinivas is TA-ing. (Haven't yet decided which module he will TA for.) * John Stumpo will be leading the Getting modifying and verifying module. ** Venkatesh Srinivas is TA-ing.▼ * Asheesh Laroia will lead the Project organization module ** Tentatively: Luke Faraone will TA. Otherwise, Jessica McKellar will. == What it means to be a module lead instructor == ~~== If you're a TA... ==~~ You prepare whatever teaching aids are necessary -- slides, exercises -- and help students understand the part of the curriculum that you are assigned. You also should discuss your teaching plan with your TA so that the TA can help answer students' questions. We aim for about half of the module time to be lecture/discussion, and half to be hands-on exercises. If you need help designing lecture, discussion, exercises, let Asheesh know and he will help. == What it means to be a TA == The purpose of TAs is to help make sure students get the most out of a module. Specifically, you help the primary instructor by answering student questions about the material and help them past problems with their laptops, either by showing them how to solve a problem or escalating the issue to the instructor if you can't fix it. On Friday or Saturday, before the module's first run, you should spend some time (5 to 20 minutes) discussing the module with ~~the~~its lead instructor. You're welcome to participate in other ways, as they make sense to you -- for example, ~~ask~~help ~~annoying~~elucidate ~~questions~~under-addressed topics during the Ethics and Economics section. ~~(-:~~by asking questions. == Other essential links == Line 44 ⟶ 56: * [[Open_Source_Comes_to_Campus/UMD/Laptop_setup\|Laptop setup]] info == ~~Schedule~~Saturday schedule == Detailed Saturday schedule. We're fairly confident it will stick to this. Line 70 ⟶ 82: * Project organization (bug trackers; git format-patch; github; people's roles in a project) == ~~List of TAs~~Sunday == Goal: Get students to pick a FLOSS project that seems interesting, and make a direct contribution of effort of some kind. Schedule: * 10:00 AM: Coffee is here; doors open. * 12:30 PM: Lunch arrives. * 5 PM: Wrap-up. To do: ▲* Venkatesh Srinivas * We should come up with a hand-selected list of good bite-sized bugs across projects.