[openstack-dev] [all][tc] TC Candidates: what does an OpenStack user look like?

Andrea Frittoli andrea.frittoli at gmail.com
Fri Oct 13 17:26:44 UTC 2017

On Thu, Oct 12, 2017 at 5:51 PM Zane Bitter <zbitter at redhat.com> wrote:

> (Reminder: we are in the TC election campaigning period, and we all have
> the opportunity to question the candidates. The campaigning period ends
> on Saturday, so make with the questions.)
> In my head, I have a mental picture of who I'm building OpenStack for.
> When I'm making design decisions I try to think about how it will affect
> these hypothetical near-future users. By 'users' here I mean end-users,
> the actual consumers of OpenStack APIs. What will it enable them to do?
> What will they have to work around? I think we probably all do this, at
> least subconsciously. (Free tip: try doing it consciously.)
> So my question to the TC candidates (and incumbent TC members, or anyone
> else, if they want to answer) is: what does the hypothetical OpenStack
> user that is top-of-mind in your head look like? Who are _you_ building
> OpenStack for?

Unlike a few years ago we don't walk so much in the dark anymore.
We now know a lot of our users because:
- some are contributors to OpenStack. OpenStack developers but not only.
  contributors to OpenStack I don't mean only code, but any kind of
  like presenting and discussing use cases at the PTG, at the forum or on
  mailing list, providing feedback, ideas, resources and even motivation.
- some are adjacent communities that depend on or collaborate with
- some answer our user survey.

So who am _I_ building OpenStack for?

- For OpenStack developers, since I work mostly on QA and CI
- For the users that are closer to the OpenStack community. I don't want to
  on hypothetical users that don't care to talk to the OpenStack community.
  Consistency across projects in they way they different projects are
built, tested,
  deployed, operated, documented and consumed is important for this type of
- I build it to be a good software for everyone to use. I care about
usability, good
  documentation, stable APIs, proper logging features that
  make it a good software for anyone to invest their time on.


Andrea Frittoli (andreaf)

> There's a description of mine in this email, as an example:
> http://lists.openstack.org/pipermail/openstack-dev/2017-October/123312.html
> To be clear, for me at least there's only one wrong answer ("person who
> needs somewhere to run their IRC bouncer"). What's important in my
> opinion is that we have a bunch of people with *different* answers on
> the TC, because I think that will lead to better discussion and
> hopefully better decisions.
> Discuss.
> cheers,
> Zane.
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20171013/703cac66/attachment.html>

More information about the OpenStack-dev mailing list