Hi All, Let me reflect to the question in the subject first where I would like to stick to the word ‘user’ and keep my answer simple. I think an OpenStack user is/looks like as an average person.
To give a longer explanation, in my view when we are designing our user-facing API’s we need to keep in mind that we don’t know who is going to use them BUT let that be an application developer, a researcher or even a person who seeks for a place for their IRC-bouncer, so anyone who interacts with them, should be equally able to do so without a PhD degree, the history of the development process of a particular functionality, without the need to read the code first and so forth. The above statement is applicable in any given period of time, meaning to provide a consistent and consistently pleasant and functional environment from release to release. To answer the follow up question on 'Who are _you_ building OpenStack for?’ I would mention operators as well, who need to deal with deploying, configuring, troubleshooting and managing the daily operational tasks regardless of the location, nature and size of an OpenStack deployment. I think as in many cases when this topic comes up it’s more of a social than a technical challenge. To continue on that aspect, when I’m involved in a feature design and development activity I like to imagine that I will be the one, who will operate the service and use the newly introduced functionality. It helps much to avoid decisions that sacrifices the operator and user experience in favor of faster and easier design and implementation. I also like to encourage the fellow community members to do the same and also to play with what we are producing to get the first hand experience. If the intention is there and we have the right mindset the technology will help us in the technical implications like automation, maintainability, complexity, documentation and so forth. Thanks and Best Regards, Ildikó (IRC: ildikov) > On 2017. Oct 12., at 18:51, Zane Bitter <zbit...@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? > > 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-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