Giving Lager its Own Github Organization

[jrwest]

The same initial thoughts and concerns as #58 probably apply so please see the link for more details.

I would propose that this move happen simultaneously with the move in #58 so that the annoying dependency management work only has to be done once.

[jrwest]

One additional note: @Vagabond should be involved with discussions here as he is most familiar with the lager codebase and its status

[sdebnath]

Lager has become such a widely used tool in the Erlang community, that it makes sense for it to be in its own organization if Basho is up for doing so (read more active PR cycles). There are plenty of well known and active Erlang community members who are more than willing to help with this project.