Open Stack

Hi John:

It was great to meet you too, and we're glad you were able to hear about what we're trying to do with the Personas in OpenStack and are interested in championing and embracing the use of personas within the Nova efforts.

Thanks for sharing the template links makes reference that the types of users who may get affected or use the feature listed in the template, as well as the impact on the user roles themselves.  I like the direction you're taking as this is indeed what we're hoping the Community will start to do, i.e. start framing the problem / user stories / use case in terms of the user / persona who would be performing it, as not every capability within OpenStack will be done by only a superuser.

So far, we're still fairly early in the persona development efforts and have developed personas for the Cloud Administrator / Operator, or superuser.  We don't yet have personas created for the Self-Service End User (aka "End User"), "Deployer" user roles, and many other user roles that are much needed.

We'd definitely love to have you participate in our Persona Working Group efforts, and to see what's going on in the group, please refer to the following:

OpenStack Persona Working Group Links:
Wiki: https://wiki.openstack.org/wiki/Personas
Working Group Etherpad: https://etherpad.openstack.org/p/persona-working-group
Meeting Summary and Archives: https://wiki.openstack.org/wiki/PersonaMeetingInformation#Personas_Working_Group_Meeting_Summaries
Mailing List: http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas
Persona Blueprint: https://blueprints.launchpad.net/openstack-ux/+spec/horizon-personas
Meeting Information Conference Telephone # 
Meeting Summaries: https://wiki.openstack.org/wiki/PersonaMeetingInformation
USA Toll #: 1-702-696-4520 
USA Toll Free #: 1-866-409-2889 
Conference Code: 4351602479
International #s -- see https://wiki.openstack.org/wiki/PersonaMeetingTimes
IRC: #openstack-ux
Next Meeting:
Date: Wednesday May 28, 2014
Time: 4:00pm - 5:00pm US/EST (2100 UTC)
OpenStack UX Wiki (in case you're interested): https://wiki.openstack.org/wiki/UX#OpenStack_User_Experience
There's a biweekly meeting starting soon on IRC.  When we refer to IRC meetings, it's only done in chat (no voice, no video… only text)
There's a Doodle currently underway to figure out the best time to meet for folks interested: http://doodle.com/3m29dkn3ef2em5in
The group is using the [openstack-dev] mailing list with the [UX] tag in the subject line

I'd probably suggest joining our OpenStack Persona Working Group meeting (meets every 2 weeks) and/or checking the Meeting notes/summaries and Etherpad on what we're working on, and how you can contribute, and/or promote adoption of personas within the Development lifecycle.  If it's helpful, we're also more than happy to come speak with the Nova team about it as well.

Thanks again for your interest, and we look forward to working with you.

Kind regards,
Ju Lim
Member of the Technical Staff
Red Hat
Email: julim at redhat.com
IRC: julim on #openstack-ux (Freenode)

On May 20, 2014, at 7:29 AM, John Garbutt <john at johngarbutt.com> wrote:

> Hi all,
> 
> It was great to meet with some of you in one of the summit sessions.
> 
> I am keen to get developers thinking more about users when writing up
> nova-specs.
> 
> Right now we indirectly define two users in the template:
> "end user" and "deployer"
> http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/template.rst#n49
> 
> Also see:
> http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/template.rst#n175
> http://git.openstack.org/cgit/openstack/nova-specs/tree/specs/template.rst#n209
> 
> This is obviously massively coarse, but its better than what we had
> before (i.e. nothing). Before we had issues with people thinking about
> a private cloud as used by the people who deployed that cloud. While
> we shouldn't make it hard for them, clearly the split deployer / end
> user case is also important. A list of deployment scenarios, with a
> collection of personas related to each, might be where I am currently
> thinking we could go.
> 
> API design is probably where I am most concerned. We are working hard
> on the next generation of our API during Juno, and it would be good to
> do that with a clearer view of our users. Technically the compute
> programme still owns python-novaclient as well, but for now I am more
> concerned about getting an API that maps well to users' metal models
> of the system, and as we add new features, that we don't break that.
> 
> I am currently battling (in my head) with the idea of nova really just
> being a component, rather than the complete system. For example GUI vs
> CLI vs API is less of a big deal to us, as in some sense, its someone
> else's issue. Having said that, creating an API that means the GUI is
> unable to deliver a good experience is clearly a bad thing. In a way,
> horizon could be one of our "end users", but thats a bit odd really.
> 
> 
> Anyway, lets take baby steps:
> 
> I would love to help review the current personas / persona generation
> process, and see how we can improve the nova-spec template to
> reference that effort. I got some buy in for trying this out during
> the Nova un-session design summit session.
> 
> I am happy to become a sort of Nova UX champion, as part of the
> Blueprint Czar role. No real idea what that means yet, but thats the
> fun part, right?
> 
> 
> Many thanks,
> John
> 
> 
> IRC: johnthetubaguy
> Nova Blueprint Czar
> Software Developer IV at Rackspace
> Working from home, in Cambridge, UK
> 
> _______________________________________________
> openstack-personas mailing list
> openstack-personas at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-personas

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-personas/attachments/20140520/3c3e0d4a/attachment.html>