Chris Dent wrote:
It's the Campaigning slot of the TC election process, where members of the community (including the candidates) are encouraged to ask the candidates questions and witness some debate. I have some questions.
Thanks Chris ! I'll try to make short answers, as the campaigning period unfortunately ended up overlapping with long-planned vacation :)
* How do you account for the low number of candidates? Do you consider this a problem? Why or why not?
The TC activity traditionally took some significant time, so it was better suited to people who had the chance to spend 100% of their work time on OpenStack. As we mature, we have less and less people who can spend 100% of their time on OpenStack. Sometimes they have to share their time with other projects, or with their organization other priorities. It is therefore more difficult to find candidates with the available time. I don't think it is a problem in itself -- it is more a reflection of how our community changed and how much our systems remained the same.
* Compare and contrast the role of the TC now to 4 years ago. If you weren't around 4 years ago, comment on the changes you've seen over the time you have been around. In either case: What do you think the TC role should be now?
Having recently worked on the "role of the TC" document, for me it captures the role of the TC as it is. 4 years ago, we just finished evolving our systems to cope with massive growth. I think today we need to start evolving them again, with an eye toward long-term sustainability.
[...] * What can the TC do to make sure that the community (in its many dimensions) is informed of and engaged in the discussions and decisions of the TC?
Maybe we need to differentiate "communicating what we are doing as the TC" and communicating the global direction". OpenStack developers can ignore the former but should not ignore the latter. In the past we did converge both and hope everyone would read everything, and that was not very successful.
* How do you counter people who assert the TC is not relevant? (Presumably you think it is, otherwise you would not have run. If you don't, why did you run?)
The TC is responsible for the whole of OpenStack, rather than the pieces (which are separately handled by project teams). We are in a good position to take a step back and make sure "OpenStack" looks good, beyond individual pieces. I personally think it is important, and it is why we are relevant. -- Thierry Carrez (ttx)