> -----Original Message----- > From: gordon chung [mailto:g...@live.ca] > Sent: Monday, October 03, 2016 11:31 AM > To: openstack-dev@lists.openstack.org > Subject: [openstack-dev] [tc] open question to the candidates > > hi, > > as there are many candidates this TC election, i figured i'd ask a > question to better understand the candidates from the usual sales pitch > in self-nominations. hopefully, this will give some insights into the > candidates for those who haven't voted yet. obviously, the following is > completely optional. :) > > i initially asked this to John Dickinson[1] in his self-nomination. i'd > like to open this up to everyone. the (re-worded) question is: > > the TC has historically been a reactive council that lets others ask for > change and acts as the final approver. do you believe the TC should be a > proactive committee that initiates change and if yes, to what scope? > more generally, what are some specific issues you'd like the TC address > in the coming year?
[amrith] Gordon, great question. Short answer is that I believe that the TC should be proactive. All the members in the TC are themselves active contributors to different parts of OpenStack and there is a reasonable expectation that they are remaining informed about the things that are going on in all projects, are aware of what deployers and users are trying to do with OpenStack and the problems they are facing. I believe that this gives them the ideal position to not only react to issues that come up, but also in cases take proactive steps to improve things. But, in keeping with the openness of OpenStack, I believe that any 'proactive' action should be discussed in the open and decided only after this open participatory process. In the future it may be a good idea to have an IRC meeting where all candidates attend and members of the community get to participate in a moderated discussion. This may mean that the timeline (closing deadline, polling) may need to be altered but I think an opportunity for all candidates to discuss these kinds of things would be valuable. Thanks! > > [1] > http://lists.openstack.org/pipermail/openstack-dev/2016- > September/104821.html > > thanks, > -- > gord > __________________________________________________________________________ > 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
