> On Apr 2, 2017, at 4:16 PM, Monty Taylor <mord...@inaugust.com> wrote: > > On 04/02/2017 02:53 PM, Chris Hoge wrote: >> 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? > > I do not think this is a thing we want to do. While I understand the > urge, a project needs to live somewhere (in this case we've chosen > OpenStack) and should behave as projects do in that location. When I > work on Ansible, I do issues on github. When I deal with tox, I file > issues on bitbucket. Back when I dealt with Jenkins I filed issues in > their Jira. I do not think that filing an issue in the issue tracker for > a project is too onerous of a request to make of someone.
Sounds reasonable. I still want to think about how to communicate efficiently across projects. This thread, for example, was cross posted across communities, and has now forked as a result. I’m personally not thrilled with cross posting. My proposal would be to consider the openstack-dev mailing list to be the source for development related discussions, and I can feed highlights of discussions to the sig-k8s-openstack, and relay and relevant discussions from there back to this list. > We have issues turned off in all of our github mirrors, so it's highly > unlikely someone will accidentally attempt to file an issue like the. > (it's too bad we can't similarly turn off pull requests, but oh well) > > >> [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 >> <https://etherpad.openstack.org/p/go-and-containers> >> >> Here's a request for a repo in OpenStack: >> https://review.openstack.org/#/c/449641/ >> <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 >> <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 >> >> >> >> __________________________________________________________________________ >> OpenStack Development Mailing List (not for usage questions) >> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe >> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev >> > > > __________________________________________________________________________ > OpenStack Development Mailing List (not for usage questions) > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev __________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
