-
Notifications
You must be signed in to change notification settings - Fork 29
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
[Question] still maintaining and ssh_keys #40
Comments
Hi @ruiztulio! Yes, it is still under maintenance. Right now I am just working on it when a new issue appears or reviewing a pull request. A harder work will come with the new Travis API (yes, they are already working on it). About |
@menegazzo I'd be pleased to test it if you do it and post the results here, in the other hand I can write it too, but it will take me a little more time to analyse your code and do a proper PR. Either way I'd be glad to help. |
@ruiztulio I am going on vacation tomorrow so I have a proposal for you: do a fork and submit a PR right away. This way I can participate more actively with you on this issue (even coding). Also feel free to reach me on Hangouts or through e-mail. Either way, if you prefer waiting I can work on this in a couple of weeks. |
Hi. Unfortunately I don't have the time to keep the support on this library. If you have the interest in taking the ownership of this, let me know. |
Hi @menegazzo , this is not an issue is a question Do you still maintain this package? My question is because I'm planning to use it for a new development that is about to begin, but as you can imagine we don't want to use an abandoned library.
Another question, I checked the code a little, but I cannot find the ssh_keys management implementation, it is done? or not yet?
Thanks in advance
The text was updated successfully, but these errors were encountered: