Open Source Comes to Campus/Website editing via git: Difference between revisions

no edit summary
imported>Paulproteus
imported>Paulproteus
No edit summary
 
(2 intermediate revisions by the same user not shown)
Line 22:
 
* If students work together, try to have them leave all of their github usernames somewhere on the Github issue that they solved as a group. That's for our record-keeping about how the event went.
 
* Sometimes a student will submit a pull request that needs fixing. For example:
** They might make unrelated changes in the file.
** They might fail to fix the issue correctly.
** They might submit two commits that need to be in separate pull requests, since we haven't taught them about branches yet.
* When this happens, you should usually '''ask all students to watch you as you provide feedback (in person) to the person who submitted'''. Rationale:
** Usually there is something to learn about git, or about being careful, that all the students will benefit from.
** If you spend more than a few minutes working one on one with a student, the other students won't have anything to do, and then you'll have a long review queue and struggle to get on top of it.
 
* The laptop setup guide can be found at: http://bit.ly/laptop-setup
Line 30 ⟶ 38:
 
* Your main repository is configured, via [http://pages.github.com/ Github 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.
** Note that it takes about 2 minutes for the site to update with new changes. So don't expect it all to happen immediately.
 
* If you finish early, or if you have questions, tell Asheesh and Shauna on the #openhatch IRC channel.
 
* If students finish early, congratulate them, and tell them to work on the "Finding an open source project that suits a partner's interests" activity.
Anonymous user