Skip to content

A number of useful commits from the-kenny, plus compatibility with Google's OAuth and support for refresh tokens - #9

Open
stuarth wants to merge 9 commits into
DerGuteMoritz:masterfrom
stuarth:master
Open

A number of useful commits from the-kenny, plus compatibility with Google's OAuth and support for refresh tokens#9
stuarth wants to merge 9 commits into
DerGuteMoritz:masterfrom
stuarth:master

Conversation

@stuarth

@stuarth stuarth commented Aug 12, 2012

Copy link
Copy Markdown

No description provided.

@dkropfuntucht

Copy link
Copy Markdown

We just opened a recent fork for clj-oauth2. Any chance we can collaborate to merge some of these open pull requests on to our (or another) fork and update clojars?

@stuarth

stuarth commented Sep 24, 2015

Copy link
Copy Markdown
Author

@dkropfuntucht sure, happy to help. Looks like you forked from the-kenny's repository, so you're interested in the last 3 commits I added?

@dkropfuntucht

Copy link
Copy Markdown

Excellent! From a practical standpoint, and getting the features I need, I only need the commit that I added to my own fork. I'm not 100% happy with my change, but it solves our problem.

Still: I think I have a general interest in all of the pull requests that have been sitting on this fork. Each of the pull requests here had to be created for a reason, so it might be nice to roll them into a new version of the library. Assuming we can find time to test the result.

To clarify: we're also willing to take up testing of the resulting library against Google, Facebook, and Github's API.

@DerGuteMoritz

Copy link
Copy Markdown
Owner

Hi everyone, sorry for the negligence about this library. I haven't been using it anymore pretty much after its initial release and was too busy with other projects to keep an eye on its maintenance unfortunately. I don't see this changing anytime soon either, so I'd be happy to turn it over to somebody with an active interest in it. I'm not sure how to proceed on this exactly, though. Any suggestions? :-) Also, there seem to be viable alternatives like https://github.com/ddellacosta/oauth2-client by now, so we could also opt to retire clj-oauth2 and point to one of those. What do you think?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants