[openstack-dev] [all] Question for the TC candidates

Michael Krotscheck krotscheck at gmail.com
Thu Apr 23 18:09:41 UTC 2015

Hey there Chris!

On Thu, Apr 23, 2015 at 9:17 AM Chris Dent <chdent at redhat.com> wrote:

> What can and should the TC at large, and you specifically, do to
> ensure quality improves for the developers, end-users and operators
> of OpenStack as a full system, both as a project being developed and
> a product being used?

OpenStack needs to become as boring as possible.

Clouds, to me, are plumbing. They're not themselves interesting, rather
they are the platforms upon which interesting things are built. And they
shouldn't be, either! Use hardware as an analogy: The RJ-45 connector is
ubiquitous for physical network connections. If each manufacturer used
something different, you'd soon be spending all your time soldering
adapters, and the last thing I want our operators, developers, or customers
to do is waste their time doing the cloud-equivalent.

Example: Pep8 is boring. Benefit: We don't waste time arguing about tabs
vs. spaces anymore.

The TC can set policies that encourage being boring. It's the closest we
have to an ISO standards board, and while the TC has no real power to
mobilize resources to build things, it can advise and encourage adoption of
policies and standards. Some examples include: Test Coverage standards,
common middleware, consistent API standards... you get the idea. The more
boring OpenStack becomes, the easier it will be to work on, operate, and
talk about.

As for myself: I'm going to focus on making UI projects as boring as
possible. This includes lots of things, so let me get into specifics:
- Creating, and encouraging the use of, common middleware that encapsulates
existing RFC's and standards which support UI development (CORS, Common
Auth, etc.)
- Researching, Drafting, Proposing, and Shepherding policies for UI
development that involve all stakeholders, including upstream and
downstream engineers, Package Maintainers, and operators.
- Creating the tools that will allow us to publish UI libraries to the
global community (mostly JS, we've got the Python part handled).
- Getting involved in UI tooling projects (Node, Sass, etc) and advocating
a more enterprise-supportive approach to topics like security, package
signing, package structures, audit trails, and distribution.

That about sums it up. Have a nice day!

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20150423/56fa5896/attachment.html>

More information about the OpenStack-dev mailing list