Code policies

For this class, we will all be contributing to the existing e-mission repos hosted on github. e-mission is open source under a BSD license. In order to ensure consistency, all code submissions from the class will be using a fork-pull model. There are detailed instructions on this model available, and I also found this summary useful. A very brief summary is:

Fork the repo into your own github repo
Clone the fork
Work on the clone
Check your changes to your fork
Submit a pull request
Ensure that the commit messages are descriptive enough to be useful to somebody who is looking at the code a year or two years later. You will be asked to add comments or a more descriptive message if warranted.

Mini-project policies

Each week has a list of suggested mini-projects that we have come up with for your convenience. The projects have been entered as issues into the repo and tagged with an estimate of their size.
You can also propose your own mini-project by browsing the code and figuring out something that needs improvement. This is not hard to do :) Please discuss any mini-project that you propose with the TA to ensure that it is sized correctly.

In order to pick a project, simply have one person in your team assign the related issue from the repo to himself/herself.

Mini-project assignments are first come, first served.
If you really, really want to work on a mini-project that somebody else has already grabbed, talk to them offline and work it out.
If you are proposing a new mini-project, add an issue for it to the issue list in the repo after discussion with the TA.
Every submitted pull request must refer to an issue that it is fixing. This makes it easier to track why code changes were submitted and pulled, and will close the issue automatically.

Key files

We use several keys for cross-client and API authentication. The public instructions for the repo ask users to register for their own keys. Since you are EECS students, if you choose not to register for your own keys, you can get them from our internal repo.
https://repo.eecs.berkeley.edu/git/users/shankari/cs-194-s2015.git

The repo does not have anonymous access.
You cannot browse the code, you MUST clone it to access it.
If you have been selected for the class, you have read access to this repo.
Please don’t share the keys with people outside the class.
Please don’t publish the keys to any unencrypted location outside eecs (dropbox, google docs)
Please don’t email the keys to others (even in the same class)