Open Stack

Not sure my answer if fit one or some questions. But from my personal
PoV, there is BIG gap between the expectation from contributors and the
power of TC. As a cloud platform, though there are many
components/services, their API should be highly consistent. The
contracts between each other should be very stable. However, I don't
think we did a great job around this. And also, we do have some cross
project features are still weak, e.g. quota management, role management,
etc.

And for the single most important thing I would like to do, is getting a
most restrict API design cross project to make OpenStack like a whole
building, but not building blocks, from user perspective.


On 21/02/19 3:46 AM, 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.
>
> First off, I'd like to thank all the candidates for running and
> being willing to commit some of their time. I'd also like to that
> group as a whole for being large enough to force an election. A
> representative body that is not the result of an election would not
> be very representing nor have much of a mandate.
>
> The questions follow. Don't feel obliged to answer all of these. The
> point here is to inspire some conversation that flows to many
> places. I hope other people will ask in the areas I've chosen to
> skip. If you have a lot to say, it might make sense to create a
> different message for each response. Beware, you might be judged on
> your email etiquette and attention to good email technique!
>
> * How do you account for the low number of candidates? Do you
>   consider this a problem? Why or why not?
>
> * 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?
>
> * What, to you, is the single most important thing the OpenStack
>   community needs to do to ensure that packagers, deployers, and
>   hobbyist users of OpenStack are willing to consistently upstream
>   their fixes and have a positive experience when they do? What is
>   the TC's role in helping make that "important thing" happen?
>
> * If you had a magic wand and could inspire and make a single
>   sweeping architectural or software change across the services,
>   what would it be? For now, ignore legacy or upgrade concerns.
>   What role should the TC have in inspiring and driving such
>   changes?
>
> * 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?
>
> * 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?)
>
> That's probably more than enough. Thanks for your attention.
>
-- 
Cheers & Best regards,
Feilong Wang (王飞龙)
--------------------------------------------------------------------------
Senior Cloud Software Engineer
Tel: +64-48032246
Email: flwang at catalyst.net.nz
Catalyst IT Limited
Level 6, Catalyst House, 150 Willis Street, Wellington
--------------------------------------------------------------------------