Vookoo organisation

[andy-thomason]

I suggest that we create a vookoo organisation on GitHub with pointers to documentation.

Ideally, the project should have:

• CI testing with travis/appveryor
• doxygen doc generation with travis
• A vookoo.github.io website with the docs.
• Badges for CI and docs.

The copyright should now be "Vookoo contributors" and we
should name you in the README (you can do this as badges, too).

I'm doing this with extendr right now:

https://github.com/extendr/extendr

[lhog]

I think it's a very good idea.

Most alike projects are either too 3rd party heavy or abandoned/broken, vku is still the unique offering in its space, but it certainly needs improvement and more people involved in it.

CC: @FunMiles

[andy-thomason]

You guys have been doing great things here. You should get some recognition.

[andy-thomason]

I've re-assigned the copyright to "Vookoo contributors."

As a word of advice, you should try to get a waiver from any employers to carry out open
source work.

[FunMiles]

I am my own employer ;)
I am going to have a bit more free time starting later this week. I'll create a few PRs. I already have two.
I am wondering if I need to really separate the PRs? One of the PRs I have in process right now starts from the other.