Promote new Maintainers

[michaeldfallen]

Firstly an apology: I have recently switched jobs (leaving my job at Kainos to go contracting on my own). That has led to a lot of paperwork and admin that's taken up much of my time. So I haven't been able to devote the time git-radar needs to keep up with the excellent contributions we've had, fix the issues that are annoying some and clean it up to a good standard.

At the same time I've recently switched to Ubuntu and any time I do try to do any work the tests not passing on Linux (mentioned way back in #38) have hampered my coding.

---

Basically I need some help and I'd be interested in offering one or two people commit access so they can become Maintainers and help me support this tool.

Things needed to be fixed to make this work are:

Community

To do this we would need to start a bit of a community around Git Radar, perhaps a Gitter.im chat room or a public slack, so we can discuss plans in more realtime than github issues. Nothing heavy handed or anything.

Automation

Currently releases are done manually on my laptop. Since that laptop is no longer a Macbook testing brew releases is now quite difficult. On the other hand there are no packages being built for any Linux. Would be nice to set up CircleCI or Travis to automate this. Tools like FPM have made building multitarget packages much easier.

Testing

Tests currently require a Macbook and access to the file system. Docker instances could be spun up instead to run tests against, reducing the need for a macbook and enabling CircleCI/Travis to build tests on every pull request / on master.

[srstevenson]

@michaeldfallen You can get an OS X environment on Travis by setting language: objective-c, so could test the Homebrew formula that way.

[michaeldfallen]

@srstevenson that's a great little hack. I'll have to look in to that, thanks.

[mriehl]

FTR as a user I'd like to clarify that my stance is that you owe me nothing. I am grateful for any personal time you pour into the software I use, and if you're having a rough time then you don't owe anyone an apology.

Opening up to more contributors or maintainers is always a good move though, kudos for that 👍

I can certainly help with setting up automation (would also suggest to release after every change to master as part of the CI process) but I am unsure how helpful that would be. I don't expect you to trust me right off the bat and most things (activating travis hook, setting up automatic releases) require pretty crazy privileges.

[hallzy]

@michaeldfallen I realize that this is now quite a long time ago, but I still regularly use this tool and I'd be happy to give some time to this. I definitely don't want to be the sole maintainer of the project but anything I can do to help keep this project going and get some issues closed I would be happy to do.