You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Aug 1, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Aug 1, 2023. It is now read-only.
We've discussed this - but I figure a public issue tracking it / timelines / et al would be good. As gophercloud has first class openstack support, we want to move it out of the /rackspace namespace and break out the vendor bits to allow for a more open community and guidelines on how to plug in vendor support/extensions (those could live under the org too). I set up https://github.com/organizations/gophercloud/
I want to propose to move this project into the OpenStack organization (https://github.com/openstack) and to use the common development workflows of OpenStack. This way we can consume the existing OpenStack infrastructure (e.g. the Gerrit for code reviews or there Jenkins to run test jobs). What do you think about it?
@berendt we've discussed this at length, with inside and outside contributors and agreed that non python, open source SDKs should use the tools and contribution model most appropriate for them. In the case of gophercloud and other go utilities that is the default git/github workflow and packaging within the ecosystem.
@annegentle (TC), @everett-toews and other sdk and ecosystem authors and openstack contributors agree. Jclouds, fog, and many other SDKs that build up the openstack ecosystem use the tooling and processes native to their communities.
Thanks @berendt for discussing here too. I'm personally advocating for a huge happy festival field outside of the OpenStack big tent where all these ecosystem tools dance happily. 👯 Go and Gophercloud are ecosystem as are the others - Java/jclouds, Ruby/fog. Thanks for asking.
Activity
berendt commentedon Oct 29, 2015
I want to propose to move this project into the OpenStack organization (https://github.com/openstack) and to use the common development workflows of OpenStack. This way we can consume the existing OpenStack infrastructure (e.g. the Gerrit for code reviews or there Jenkins to run test jobs). What do you think about it?
jnoller commentedon Oct 30, 2015
@berendt we've discussed this at length, with inside and outside contributors and agreed that non python, open source SDKs should use the tools and contribution model most appropriate for them. In the case of gophercloud and other go utilities that is the default git/github workflow and packaging within the ecosystem.
@annegentle (TC), @everett-toews and other sdk and ecosystem authors and openstack contributors agree. Jclouds, fog, and many other SDKs that build up the openstack ecosystem use the tooling and processes native to their communities.
berendt commentedon Oct 30, 2015
@jnoller Thanks for the explanation.
annegentle commentedon Oct 30, 2015
Thanks @berendt for discussing here too. I'm personally advocating for a huge happy festival field outside of the OpenStack big tent where all these ecosystem tools dance happily. 👯 Go and Gophercloud are ecosystem as are the others - Java/jclouds, Ruby/fog. Thanks for asking.
jrperritt commentedon Apr 13, 2016
gophercloud/gophercloud
The library is currently unstable pending feedback, but is up-to-date with this library.