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

From OpenHatch wiki
Content added Content deleted
imported>Paulproteus
imported>Paulproteus
Line 8: Line 8:


== Concept behind the weekend ==
== Concept behind the weekend ==

The [http://campus.openhatch.org/ website about these events in general] explains:


<blockquote>
<blockquote>
Line 13: Line 15:
</blockquote>
</blockquote>


* Sat, Feb 25 is the ''workshop'' day.
More info: http://campus.openhatch.org/
* Sun, Feb 26 is the ''project'' day.


== NOTE ==
== NOTE ==

Revision as of 22:50, 22 February 2012

About this page

Hi, staff! This wiki page is intended mostly as a reference for staff so that you can see, before-hand, what will happen at the Open Source Comes to Campus event at UMD.

Venue logistics

See the main page for this.

Concept behind the weekend

The website about these events in general explains:

A typical Open Source Comes to Campus event has two parts: a workshop where we teach you how to use the tools and lingo associated with open source software development, and a project day where you and your fellow students choose an open source software project to work on, find a bug to tackle, and (hopefully) write your first patch, make your first documentation fix, or otherwise make a contribution to open source software.

  • Sat, Feb 25 is the workshop day.
  • Sun, Feb 26 is the project day.

NOTE

This page is a working draft of what might happen on Saturday, Feb 25, at UMD College Park.

Schedule

Detailed Saturday schedule

  • 10:00 AM: Laptop setup begins (if you are done early, you can Q&A with instructors)
  • 10:30: Brief opening ceremonies -- explain structure + goals
    • Led by Asheesh
  • 10:45 - 11: More laptop setup (if you are done early, you can Q&A with instructors)
  • 11 - 11:30 AM: Communicating as a user: finding the community and getting help
    • Led by Jessica McKellar
  • 11:30 - 12 PM: History and ethics of free, open source software
    • Led by Asheesh
  • 12 PM: Break + lunch.
  • 1 PM: Split into groups of max size 10, with 2 staff in each group. Students stay put; staff rotate between rooms.
  • 1 PM - 2 PM: Module 1 (1h)
  • 2:05 - 2:55 PM: Module 2 (50min)
  • 3:00 - 3:45 PM: Module 3 (45min)
  • 3:45 PM: Come back into the full group
  • 3:55 PM: Wrap-up: feedback, and next steps

Students rotate between the following three modules:

  • More about the command line
  • Getting, modifying, and verifying open source software
  • Project organization (bug trackers; git format-patch; github; people's roles in a project)

List of TAs

  • Venkatesh Srinivas