-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
new api version #3
Comments
Hey, thanks for your offer. If you submit your PR, we can review it and give you push access if it looks good. |
#4 submitted |
also, if you guys are no longer planning to support this gem, i'd be happy to accept a transfer to my github org. |
just wanted to follow up on the status of this PR. thanks! |
Sorry for the late reply. I discussed the matter with my colleagues, and we decided that it's better if you maintain your own fork since we no longer use the gem ourselves and don't want to spend time reviewing PRs. If you would like to be the new maintainer of the project, we could put up a link telling people to use your fork. What do you think? |
sure, no problem. do you prefer i maintain a new fork and new gem instead of transferring ownership of this repo and the existing gem to me? |
Yes, that would be perfect. That means that if one day you turn evil and put dangerous code in the repo (not that I think that will happen :) ), it's not associated to our organization. We could give you push rights for the gem. Do you want to use the e-mail address on your profile? |
|
do you plan to continue supporting this gem? if so i'll submit a PR in the next week or so to support the new version (v2) of the duo api.
thanks.
The text was updated successfully, but these errors were encountered: