Open Source Comes to Campus/Curriculum/Git/Organizer: Difference between revisions
Content added Content deleted
imported>Shauna No edit summary |
imported>Shauna No edit summary |
||
Line 2:
===Step 1===
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: 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 2===
Step 3: 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 3===
▲
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].
| |||