[Ssc-dev] Git/code housekeeping

[Nathan of Guardian]

As we get into the home stretch here on a public release of v1 of the
InformaCam app/system/service, I want to take the change to upgrade our
development process.

The git repo for the app is now called "InformaApp":
https://github.com/guardianproject/InformaApp

The git repo for the core/engine is now called "InformaCore":
https://github.com/guardianproject/InformaCore

The overall project tracker for bugs, feature tickets and roadmaps is
still at:
https://dev.guardianproject.info/projects/informacam

We are now working on the "Public Beta" milestone, which you can follow
and review here:
https://dev.guardianproject.info/versions/106

Please note, the old git repo paths are seamlessly redirected to the new
ones, so, developers, you do not need to update any thing on your end
for now.

At this point, the only people who can directly commit or modify these
repos are Harlo, Hans and myself. That said *EVERYONE* will need to do
Pull Requests from here on out instead of committing directly into the
repo. This means you make a clone of the repo yourself, make a branch
for the feature or bug you are working on, and then do a pull request
against the main repo master branch to request a code review and merger.

Once your pull request is submitted, ask someonee else to review it, and
ultimately I will be the one who does final approval and merging.

A few things:

- best to keep the pull requests short and to the point; focus on a
particularly bug ticket, optimization or new feature

- in commit messages, try to reference the ticket number you are working
on ("fixes #1234"). If you have no ticket number, that is a bad sign, so
go and create one at least, so you can explain what it is you are doing.

- Reviewing code, giving feedback and having good process is fun,
educational and hygenic for all!

That's all for now!

+n