Migrate existing repositories to GitHub organisation

[Tyler-Ward]

We should review our git repos and move ones from srobo.org/git and elsewhere to our github org and ensure repos have a readme and licence.

[RealOrangeOne]

Related to #46

[PeterJCLaw]

I am (slowly) doing this.

The process I'm following is:

• review repos by rough area (e.g: kit hardware designs is an area), identifying those which are current
• look for existing networks of them on GitHub (e.g: in the org, in related orgs or in volunteers' own accounts)
• contact the owners of the "root" repo in those networks to see if they'd be interested in "transferring" the root repo to the org, thus preserving the existing network but clarifying which repo is the "primary"; this also serves as an opportunity to invite these people to contribute to furthering the development of those repos
• contact the contributors to the repo to see what license they'd be happy to use
• if no network exists then create a new repo
• tag the repo with useful tags
• set a useful description on the repo
• add the agreed license
• add a suitable README

While doing this I'm also trying to group repos under suitable teams within the org (see discussion on #46 for the approximate approach to this).

I've generally been trying to avoid creating repos within the org without knowing what the licensing situation is going to be. This has slowed progress, but aims to ensure that we have clarity on what we can easily use and extend.

Something I've not yet been doing, but plan to do at some point, is to push a change into the cgit forks of the repos noting that the canonical repo is now on GitHub.

[kierdavis]

boards/firmware should be moved, since it is a submodule of https://github.com/srobo/kit-maintenance-docs

[PeterJCLaw]

@RealOrangeOne as you've been doing this (importing from the https://github.com/srobo-legacy org), would you like to take this task?

[RealOrangeOne]

Due to the impromptu shutdown of saffron, repos were moved to the srobo-legacy org on GitHub.

Slowly, i'm moving them over, either by renaming and importing, or updating existing repos if they're already here. I'm attempting to deduplicate where possible, but my primary intention is to get everything over to this org so people can contribute, then deal with merging repos. Repos which already exist aren't being migrated.

By the end of this, the srobo-legacy org can be deleted.