Spring Social community opportunities
I'm starting to update the documentation about contributing to Spring Social on Spring Social's GitHub Wiki. The first piece of that effort can be found here: https://github.com/SpringSource/spri.../Api-Providers
What you'll find there is a long list of API providers that either are or could be considered for Spring Social extensions. In many cases, there are already projects underway to offer Spring Social connection support and an API binding. In others, you'll find the 3rd column empty, indicating that (as far as I know) nobody is working on a Spring Social extension. Both of these represent opportunities for the community to be involved.
Obviously, if nobody is working on an extension for one of the providers, it's an opportunity for you to start one. If you do, please let me know so that I can tell everyone about it.
But even if someone is already working on a Spring Social extension for the provider you're interested, that doesn't mean that the opportunity is lost. I'm sure that the project leads for those projects would be happy to accept pull requests to help move their project along.
Finally, I'm certain that there are likely some pieces missing in Spring Social's core to be able to fully support some of the providers. Maybe a provider requires some custom parameter sent in the OAuth flow or in many cases, Spring Social doesn't even support the authorization scheme employed by the API. In that case, there's an opportunity to improve Spring Social itself. At very least you can open an issue at https://jira.springsource.org/browse/SOCIAL and let me know what's needed. Or, better yet, I encourage you to follow the instructions at https://github.com/SpringSource/spri...i/Contributing to contribute the needed change yourself.
It's awesome that we have such an active Spring Social community and I look forward to working with you to make Spring Social even better.