Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Update composer.json #7
Well, if you really do want a type, you could use "silex-service-provider". But since nothing has been defined yet, I'm not sure if we should use one.
As for homepage, basically you already have the repository URL on packagist, adding the homepage will make the URL show up twice.
added a commit
this pull request
Apr 23, 2012
After some research I've added the MPL 2.0 license now.
Hope this format doesn't break anything in Packagist? I tried searching but it doesn't seem to index licenses. Either way I found some "Apache 1.1" licensed projects, so I'm hoping "Mozilla Public License 2.0" is good enough.
It doesn't really matter, but the preferred format would be "Apache2", "Apache1.1" and I guess "MPL2".
Seems like it is quite similar to LGPL, so I guess it is possible to use it. Not many people use the MPL. If you want to make things easier for users, maybe take another look at LGPL. It seems to me that it does what you want. Doctrine is using the LGPL, for example.
I did look into LGPL as well but what eventually drove me away was that it requires you to:
... which I don't want to force upon anyone wanting to use this service provider. So I'll stick with MPL but change the license code in composer.json.
Thanks for your feedback!