Open Source Comes to Campus/Curriculum/Git/Instructors: Difference between revisions

Your goal, over the course of this 40-60 minute activity, is to help students experience what it is like to make changes to a project through GithubGitHub.

We've created a GithubGitHub organization for you to use, and given you administrative access to it. Within that organization is a repository. The repository is named $organization-name.github.io, because this is the name it needs to have for GithubGitHub to automatically generate a [http://pages.github.com/ GithubGitHub page]. You can see an unaltered example of a new organization with a new repository [https://github.com/princeton-9 here].

Within the repository, we have created a set of bitesize issues for students to work on. (See [https://github.com/princeton-9/princeton-9.github.io/issues here] for example.) You will ask students to pick an issue to work on and claim it by leaving a comment. Students can work by themselves or in groups. If they decide to work together, try to have them leave all of their githubGitHub usernames somewhere on the GithubGitHub issue that they solved as a group. That's for our record-keeping about how the event went.

* Asheesh recommends you encourage Windows and Mac users to stay away from "GithubGitHub for Windows" and "GithubGitHub for Mac" because the steps you need to follow with those are different than what we have documented. Others have disagreed on this, but that's what Asheesh thinks. (The laptop setup guide also steers clear of those, so if students are following directions, they will do things the Asheesh way.)

* Your main repository is configured, via [http://pages.github.com/ GithubGitHub Pages], to load on the web at a HTTP URL the same as the repository name. So, once you merge students' pull requests, they should be visible on the web at that address.