Now that the provider has a repository in the OpenStack project namespace, we need to move over the existing set of issues and pull requests and create an initial work list for migrating patches and fixing existing issues. I've started up an etherpad where we can track that work[1]. In the longer run we should migrate over to Launchpad or Storyboard. One question, to help preserve continuity with the K8S community workflow: do we want to investigate ways to allow for issue creation in the OpenStack namespace on GitHub? -Chris [1] https://etherpad.openstack.org/p/k8s-provider-issue-migration On Friday, March 24, 2017 at 7:27:09 AM UTC-7, Davanum Srinivas wrote: > > Folks, > > As discussed in the etherpad: > https://etherpad.openstack.org/p/go-and-containers > > Here's a request for a repo in OpenStack: > https://review.openstack.org/#/c/449641/ > > This request pulls in the existing code from kubernetes/kubernetes > repo and preserves the git history too > https://github.com/dims/k8s-cloud-provider > > Anyone interested? please ping me on Slack or IRC and we can continue this > work. > > Thanks, > Dims > > -- > Davanum Srinivas :: https://twitter.com/dims > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20170402/8ce78958/attachment.html>