-
Notifications
You must be signed in to change notification settings - Fork 62
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
future of dopy (fork?) #49
Comments
@kontrafiktion - I will add you as a contributor to dopy - no problem. Tearing it appart and removing V1 was already in the pipe, just never had the time to complete / review. (see https://github.com/Wiredcraft/dopy/tree/refactor) Lots of work needed indeed:
I simply do not have time at the moment. We'll be merging a few PR today and so on and push a new release out there. Let's see how the collaboration could go on, and I can also consider giving you access to pypi. |
thanks for the trust I started to adapt the Ansible digitalocean module to use tags as well.
|
I will merge at least the tags pull request and bump the version number to 0.3.8 until end of week |
i was pretty close to creating a fork myself and/or rewriting the ansible modules to use one of the other maintained digital ocean python libraries. i'm happy to help to keep this one alive. i'm not much of a python person either, but I can learn. |
@ kontrafiktion I see that you may have already started on adding tags support to the core module. Don't want to duplicate effort. Anyway I can help? |
Dopy seems to be sleeping again (#22).
I contacted @zbal in Feb. 2015 and he offered to add more committers. I declined then,
because my immediate concern was resolved. But now I would really like to see tag support
(#48) added because I am eagerly waiting to add this to Ansible.
I would gladly help out reviewing PRs and committing. I am not quite sure how easy it is to share the responsibility for uploading new versions to PyPi.
If this does not work, I propose to create a "dopy2".
And I would completely rip out the DigitalOcean V1 API.
What do you think?
Pinging @regentgal and @zyegfryed
The text was updated successfully, but these errors were encountered: