[ Don't Merge ] Question

Sorry for the PR, but you appear to have the issues functionality for this repository disabled
---
( or github moved the button again and I couldn't find it )


Please don't think I'm being cruel or aggressive, but I'm curious as to why you didn't simply pull request the Laravel adapters to the main repository Please let me explain, since it's something we see quite often. Both the service provider and facade can be easily added without effecting the internal code of the bundle.

This would mean that you wouldn't have to maintain another fork, or to pull changes from upstream for fixes. It also means that users of other frameworks would be able to contribute their own adapters, and boost the popularity of the project.

If all of the adapters were on packagist, it would look like this.

```
zack/tiny (stars:50)
golonka/tiny-laravel (stars:20)
smurf/tiny-symfony (stars:3)
monkey/tiny-cakephp no stars
zombie/tiny-codeigniter (stars:20322)
```

It would be much simpler to have the project package, and then to find adapters for all the frameworks that are used. It gives the confidence that they are all being kept up to date. I realize that you can reference the other project in the composer package to avoid losing changes, but then you still have to manage, or be reactive to version changes.

Again, sorry if this appears as criticism, as a Laravel team member I appreciate all that is done to support the framework. I'm just trying to raise awareness of something that others and I have noticed occurring on package, don't worry, you aren't alone!

Thanks for the code, and for using Laravel!