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

Content added Content deleted

Inline

Revision as of 21:19, 22 November 2013

There's a bit of work which needs to be done ahead of time to set up this activity.

Step 1: Customize site

Customize the site in the repository github-website-editing-demo. If you do not have admin access to it, you can submit changes as a pull request. There are different versions to play with in different branches - if you're not familiar with branching, ask in #openhatch for help. (You'll probably want to talk to Shauna and/or Asheesh before submitting a pull request anyway.)

Step 2: Create/check issues

Customize the issues in the issue tracker, as needed. Make sure the issues in the issue tracker match the current version of the site.

Step 3: Create organizations

Create organizations for each project. We typically title this hostname-#, i.e. morris-1, morris-2, morris-3, princeton-1, princeton-2, princeton-3. While doing this, you can grant administrative privileges to anyone you know will need them.

Step 4: Run setup.py

Run setup.py, found in OpenHatch's repository open-source-comes-to-campus, in the folder scripts.

Step 5: Prep instructors

Before you do the activity, you should have a list of mentors and assign them to an organization. Make sure each instructor is a) given admin privileges for their organization and b) knows which organization they'll be using for their activity. You'll need to get instructors' github usernames in order to do A.

That should be it! If you run into any problems, ask on #openhatch.

@@ Line 1: / Line 1: @@
 There's a bit of work which needs to be done ahead of time to set up this activity.
-===Step 1===
+===Step 1: Customize site===
 Customize the site in the repository [https://github.com/openhatch/github-website-editing-demo github-website-editing-demo].  If you do not have admin access to it, you can submit changes as a pull request.  There are different versions to play with in different branches - if you're not familiar with branching, ask in #openhatch for help.  (You'll probably want to talk to Shauna and/or Asheesh before submitting a pull request anyway.)
-===Step 2===
+===Step 2: Create/check issues===
 Customize the issues in the issue tracker, as needed.  Make sure the issues in the issue tracker match the current version of the site.
-===Step 3===
+===Step 3: Create organizations===
 Create organizations for each project.  We typically title this hostname-#, i.e. morris-1, morris-2, morris-3, princeton-1, princeton-2, princeton-3.  While doing this, you can grant administrative privileges to anyone you know will need them.
+===Step 4: Run setup.py===
-Step 4:  Run setup.py, found in [https://github.com/openhatch/open-source-comes-to-campus/tree/master/scripts OpenHatch's repository open-source-comes-to-campus, in the folder scripts].
+Run setup.py, found in [https://github.com/openhatch/open-source-comes-to-campus/tree/master/scripts OpenHatch's repository open-source-comes-to-campus, in the folder scripts].
-Step 5:  Prep instructors.  Before you do the activity, you should have a list of mentors and assign them to an organization.  Make sure each instructor is a) given admin privileges for their organization and b) knows which organization they'll be using for their activity.  You'll need to get instructors' github usernames in order to do A.
+===Step 5: Prep instructors===
+Before you do the activity, you should have a list of mentors and assign them to an organization.  Make sure each instructor is a) given admin privileges for their organization and b) knows which organization they'll be using for their activity.  You'll need to get instructors' github usernames in order to do A.
 That should be it!  If you run into any problems, ask on #openhatch.