Jump to: navigation, search

Difference between revisions of "PersonaMeetingInformation"

(Meeting Summary for 23 July 2014)
(Meeting Summary for 23 July 2014)
Line 15: Line 15:
==== Attendees ====
==== Attendees ====
<br />
<br />
Jeff, Thuy, Piet,  
Jeff Calcaterra, Thuy Duong, Piet Kruithof, Michael Hinnant? Jim Haselmaier?
==== Agenda ====
==== Agenda ====
<br />
<br />

Revision as of 02:34, 24 July 2014

Personas Working Group Meeting Summaries

The following is a summary for the Personas Working Group meetings. Meetings occurrence and logistics may be found at: https://wiki.openstack.org/wiki/PersonaMeetingTimes.

Meeting Summary for 6 August 2014



Meeting Summary for 23 July 2014


Jeff Calcaterra, Thuy Duong, Piet Kruithof, Michael Hinnant? Jim Haselmaier?


Jeff went through the personas on the wiki. I went through the personas mockup (link below).

The consensus was that the wiki is a reasonable way to go even though there are some limitations. However, this was only based on comments from IBM and HP.

The wiki markup is limited and sometimes difficult to wrangle into the designs we have. Thuy did some nice code for the visualizations that doesn't work with the wiki markup, for example. On the plus side, the code can be copied and fairly easily reused for other personas now that we have it as long as everyone is careful of the markup. We also discovered that the wiki automatically does versioning and pages can be rolled back.

We came up with a primitive lifecycle for personas: 1. Provisional. Persona is based on direct interview data with a customer. (someone had suggested "hypothetical", but it seems to imply it was just made up vs. unverified). 2. Draft. Persona is based on data, but we have not verified the persona with the team (or do we want to review with a real representative of the persona)? 3. Published. We published it.

Other discussions: 1. What does it mean to publish it? We could talk to the publications group and develop a similar process. 2. Are we concerned that anyone with an OpenStack ID can change the text? We can probably just wait and see if there are any issues. 3. Do we want to have a review and commit process for changes like code in OpenStack.

Requests for the group: 1. Please review the format and contents 2. If we are OK with this format and you feel comfortable with the wiki code 3. Review the Status and Data source fields and provide your feedback.

To review the persona content or format:

1. Click the "Make a Comment" link at the bottom of each page 2. Click the Edit button near the upper left corner 3. Type any comments you have there and Save it.

Meeting Summary for 9 July 2014


Piet Kruithof, Ju Lim, Michael Hinnant (HP - UXD Director for Cloud), Chris Richardson (Consulting @ HP on Cloud Initiatives, working on some community initiatives), Jim Haselmaier (independent consultant, ex-HP, working on OpenStack Cloud, consulting on OpenStack and Product Management)


  • UX questions -- assets library to represent graphic elements in Horizon and make it widely available (Chris), visual design specs / patterns library for Horizon -- how they should be shared with the community
PatternFly: https://www.patternfly.org/ <-- open source pattern library that we might be able to leverage?
Horizon Pattern Document: https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit#slide=id.g3637a7faf_1617
  • looking for folks to review and collaborate/contribute

  • Personas formatting proposal -- any feedback yet? Jacki asked if we should do it in a Google Document so it was flexible and accessible to everyone
Proposal: http://people.redhat.com/~julim/openstack/OpenStack%20Personas%20proposal-1%2020130529.ppt.
Proposal (on Wiki): https://wiki.openstack.org/wiki/Personas-page-prototype AND https://wiki.openstack.org/w/index.php?title=Personas-page-prototype-company
Feedback should be replied to on the mailing list
How do we do version control and protect the persona content? Github?

  • Update Chuck (one of the personas) -- last 2 questions & answers need some work (AI: Ju will look into it)

  • Post additional interview data into GoogleForms -- Ju and Liz had 2 more interviews that we'll need to post the data (AI: Ju will look into it)

  • New Personas to target -- self-service user
person who rolls up a service -- PaaS developer? lower priority since Solum is still incubating
Chris: a few different levels of end user, current efforts seems users responsible for operating/administering OpenStack, another user that thinks of VMs, Cinder, or Swift and they're potentially developers needing them, and another user who wants the application service
Chris: One business wrote their own UI instead of Horizon because of limitations in Horizon
How to slice the personas?

  • Anything we'd like to present or talk about for the next Summit (Paris Nov 2014)

  • Product Management working group?
Read more at http://maffulli.net/2014/07/07/a-forum-for-openstack-related-product-managers/
Vote at https://review.openstack.org/#/c/105251/
Win the Enterprise effort -- see https://etherpad.openstack.org/p/Win-The-Enterprise.

Meeting Summary for 25 June 2014


Piet Kruithof, Jeff Calcaterra, Kelly Lisai, Sogra Nishath Aminah Nailor,Thuy Duong, Jacki Bauer


(1) Welcome new members!

  • Kelly Lisai, Dell?
  • Sogra Nishath, Dell?
  • Aminah Nailor, Wells Fargo

(2) The current asks are as follow:

(3) We are going to review the template and provide feedback to Jeff in two weeks. In the meantime, Jeff will keeep plugging along...

(4) Ask: Update Chuck (one of the personas)

  • Need clarfication from Ju and Liz on what should be changed.

(5) Ask: Post additional interview data into GoogleForms -- Ju and Liz had 2 more interviews that we'll need to post the data

(6) Ask: please start thinking about what we want to complete by next summit. Do we want to create personas or refine current ones? Which personas should we target if want to do new ones?

(7) Potential personas to consider:

   * Application Developers
   *     Application Operation support
   *     Infrastructure/layered product developers
   *     Network Operators
   *     Testers
   *     Infrastructure Architects
   *     Governance, process, Infrastructure Planners - for analysis, metrics, roadmapping, storage and compute planning

(8) People willing to do interviews:

   * Kelly Lisai, 
   *     Sogra Nishath 
   *     Aminah Nailor
   *     Jeff Calcaterra

Meeting Summary for 11 June 2014


Jeff, Ju, Jacki


  • Short meeting as not enough quorum
  • No one completed previous action items, so the ask is that folks follow-through on their action items for the next meeting.
  • Ask: Everyone to review and provide feedback -- see "personas formatting proposal" that Jeff sent out
  • Ask: Update Chuck (one of the personas)
  • Ask: Post additional interview data into GoogleForms -- Ju and Liz had 2 more interviews that we'll need to post the data

Meeting Summary for 28 May 2014


Jeff, Thuy, Ju, Liz


Meeting Notes

  • Ask: Update Chuck (one of the personas)
  • Ask: Post additional interview data into GoogleForms -- Ju and Liz had 2 more interviews that we'll need to post the data

Meeting Summary for 30 April 2014

Cancelled due to lack of attendance. 2 day persona development meeting occurring in Austin, TX on May 1 & 2, 2014. Read-out will be sent after the 2 days.

Meeting Summary for 2 April 2014


Ju, Liz, Piet


(1) Team Updates Follow-up on Persona Interviews: Finish 1st round of interviewing by end of 31 March 2014, debrief on April 2, final round of interviews by TBD 1st round or persona interview checkpoint feedback on persona form

Liz Form Feedback:

   1) Make Job Title longer
   2) Make primary job role field a few paragraphs big.
   3) Add box for more details after “which cloud services do you use?”
   4) How is this “Your Environment” different from the next question about their office environment?
Ju: This is the Infrastructure Environment. Questions is confusing and poorly worded. This is about what does their infrastructure environment look like, e.g. # data centers, # regions, availability zones, cells, # nodes, # instances, capacity, etc.


Liz Survey Questions Feedback:

5) I think Years of Experience should be asked right after Title. It will be clear this isn’t meant to be just in their current position since that’s asked later.
6) The responsibilities question really came out when I asked about his primary job role. It was just natural. Should this be closer to this question?
7) Questions about the user under “Your environment” were confusing to ask to a developer. Should there be a qualifying “Do you support users?” type of question before these? +1 - I had a hard time with my interview, as he was a beginning OpenStack developer and didn't understand the questions I was asking.
8) Seemed to capture Key Responsibilities pretty well when asked about role…do we need this additional question about key responsibilities under “your tasks?"

Jacki Other Feedback
-I'm OK with the questions overall, since they are flexible and easy to change the order or skip questions that aren't relevant to the person being interviewed. I'm more worried about the people we have to interview. Not many replied to the survey, so it seems like we aren't selecting people based on how good of a candidate they are, but are just taking whatever we can get.

Supporting docs:

(2) Next rounds / next steps <-- need milestones according to OpenStack Summit deadline Review and create responses Validate personas Finalize personas Publish personas

Meeting Summary for 19 March 2014


Piet, Liz, Ju, Jacki, Thuy, David Lyle </br>


(1) Horizon Usability Testing - prioritization of items to be fixed and next steps?

  • Talk proposed for OpenStack Summit to present Horizon Usability Testing findings (http://summit.openstack.org/cfp/details/32).
  • Prioritized list of findings has been emailed / shared. Soon to be posted onto wiki.
  • Group should come with concrete proposal (e.g. wireframes) on what the fix/improvement is for Summit.

(2) persona screener update - only 18 responses. We'll have around 24-30 people (from persona screener and Horizon usability test screener) to contact for persona interviews

(3) Finalize persona interview questions: https://etherpad.openstack.org/p/personawg-persona-questions Thuy to do some re-organization of the questions.

(4) Raw notes or persona interview note template / repository?

  • The notes will need to be captured (from everyone in one place) -- use GoogleForms
  • Piet will put a Form together for folks to enter the data - Done

(5) Teams: Melissa & Piet, Ju & Liz, Jeff & Thuy, Jacki & Member of RackSpace Researchers

(4) Ju to send out list of candidates to interview to the 4 teams (before end of this week), who are responsible to contact, schedule and interview the potential persona interview candidates.

  • Finish 1st round of interviewing by end of 31 March 2014, debrief on April 2, final round of interviews by TBD

(5) other topics?

Meeting Summary for 12 March 2014


Ju, Jeff, Thuy, Liz


(1) Pool from persona screener & Horizon usability testing screener

  • Only 7 people responded on the persona screener, and only 2 interested in participating in persona interview, but neither meets our 3-4 targetted users (cloud admin, cloud end user, cloud developer). Still, because they expressed interest, we'll include these 2 in our persona interviews.
  • About ~22-24 from Horizon usability testing screener. Most were cloud admins and some cloud endusers / Paas developers. No cloud developers. ASK of each team to reach out to their internal development teams to do 2-3 developer interviews.
  • AI: Need to resend the screener to try and get more responses

(2) persona interviewing next steps

  • We'll have 1-2 person teams (Melissa & Piet, Ju & Liz, Jeff & Thuy, Jacki & ?). Easier to have teams from same company as harder to coordinates schedules across three organizations vs. the team and the persona interview candidate.
  • completion time for persona interviews: 1st week of April 2014?
  • AI: Ju to send out the curated list of potential candidates for the 4 teams -- see below -- contact, schedule and interview the potential persona interview candidates.

(3) finalize questionnaire & template in March 19 2014 meeting

(4) next steps

Meeting Summary for 5 March 2014


Piet, Liz, Ju, Jenny, Fei, Jacki, Jeff, Thuy, David Lyle, Nick Chase


1. Horizon usability testing

  • Rough start but starting to improve
  • Thank to community team members who participated and took notes and contributed observations
  • Debrief early next week
  • Melissa still trying to setup a few more usability sessions
  • Some areas for improvements: create instance workflow has room for improvements
  • Audio not so great - open to new solutions / proposals for how to improve audio
  • Wiki link for the Horizon Usability Testing: https://wiki.openstack.org/wiki/HorizonUsability_Testing

2. Persona Planning Milestones

  • Propose to have 2-3 personas for Summit (Cloud Administrator, Cloud Operator, Cloud End User, Cloud Developer)+1
  • survey / screener
  • Who's interested (please write your names here): Ju, Jeff, Thuy, Liz, Jenny, Fei, Jacki, Mellisa Meingast
  • Action Item (everyone) review
  • Who's interested (please write your names here): Ju, Jeff, Thuy (note taker), Liz, Jacki, Piet, Mellisa Meingast, Marc Dysart
  • Conduct a small # of interviews and use survey after to validate and gather more datapoints
  • Next Steps
  • Send out persona screener invite tomorrow (after updates to the intro pending Jeff's feedback)
Updated intro / invite March 6 2014
Screener posted on [Personas Screener].
To embed in a blog / website:
<iframe src="https://docs.google.com/spreadsheet/embeddedform?formkey=dHl2Qi1QVzdDeVNXUEIyR2h3LUttcGc6MA" width="760" height="2460" frameborder="0" marginheight="0" marginwidth="0">Loading...</iframe>
  • Meet next week @ same time for 30 minutes and discuss teams we'll have based on the respondents and interview next steps

3. Open Topics None

Meeting Summary for 19 February 2014


Piet, Ju, Liz Blanchard, Sriram, Jeff, Thuy, Margie Callard, Jeremy Hopkins, David Lyle, Jacki Bauer


1. Updates - screener, usability testing

  • Screener setup in Survey Monkey and invite sent of week of Feb 17 2014, there were 53 respondents
  • Usability Study week of Feb 24 2014
  • Planning to conduct 10-12 tests with 2-4 sessions daily though Friday will be 1-2
  • Participants from all over (different timezones)
  • Melissa running the test using VirtualRoom, streamed via Google Hangout (limit 10 people)
  • Melissa will have VR & GH running at same time
  • Propose to pose questions and/or comments via chat
  • Let them know who will attend ahead of time
  • All observers must actively participant / contribute during and after (analysis)
  • Online document (etherpad, googledocs, multichat) for sharing
  • Schedule? TBD -- Melissa to reach out to folks tomorrow morning and schedule
  • Test is planned for 1 hour
  • Usability Test Plan?
Scenario: Spin-up a New Host
You've been asked to get a new application up and running in your Cloud. To setup the new application, you will have to create and get a virtual host up and running. Given the following Horizon credentials, how would you do so?
Guidelines on kind of OS type that would help them create the instance.
Individual Tasks:
-Create a security key pair. (Could be set up optionally before test)?
-Create a network. (Could be set up optionally before test)
need to add a section for creation of full neutron setup.
that basically means:
1. create router
2. attach router to external network
3. create network
4. attach network to router
5. create subnet
6. create sec groups as required (note: if you don't provide a default sec group as we do in PC, then you need to make sure to create a default sec group and add a rule for port 22 to allow ssh access)
-Import an image. (Could be optional)
-Launch an instance using security key pair X, network Y, and image Z. (Could add in additional requirements such as size or number of instances to launch.)
-Confirm that instance was launched successfully.
How often is this task performed?
What types of application do you typically put in your cloud?
Are these application hosts long running or short-lived?
When the host is no longer needed, what do you typically do, e.g. keep it running, retire it, archive it, etc.?
Scenario: Make a Point-in-Time Copy of the Host
Now that you have your host up and running, assume that you've made some changes on the host and now need to make a point-in-time copy of it, so that you can access it or revert to the point-in-time copy at a later time. What steps would you take to make a point-in-time copy?
Individual Tasks:
-Either Launch an instance successfully, or identify a running instance in the instance view.
-Choose to take a snapshot of that instance.
-Confirm that the snapshot was successful.
How often is this task performed?
What's your use case for performing this task?
How many PiT copies do you typically keep? What do you do with the old PiT copies?
Scenario: Launch a New Instance using a Snapshot or Image
Using the Point-In-Time Copy of the Host previously made, how would you start up another instance?
Individual Tasks:
-Choose to either create an instance and boot from a snapshot, or identify a snapshot to create an instance from.
-Confirm that the instance was started successfully.
How often is this task performed?
What's your use case for performing this task?
Scenario: Launch an instance that boots from a specific volume.
You want the Host you created to use persistent storage (instead of ephemeral storage) when it starts up and when it's running. What steps would you take to change to enable the host to start up using persistent storage?
Individual Tasks:
-Create a volume (Could be set up optionally before test)
-Launch an instance using Volume X as a boot source.
How often is this task performed?
How many people typically perform this task? Specifically, is the storage setup by someone else?
Scenario: Understand how many vCPUs are currently in use vs. how much quota is left.
You're interested in resource utilization. Where would you go to see this information?
Individual Tasks:
How often is this task performed?
What does the information tell you?
What do you typically look for?
Is there anything missing?
Qualifying questions - plans for them but don't have them yet
Focus on the Self-Service Cloud End User (HP calls this user the "Steve Persona") for the usability testing

2. Persona - screener, next steps

There are 2 screeners: usability study, persona
We have a strawman for persona (using the usability study) but need more work on it, ask location of the respondent
ASK: Smaller working group to review
Who's interested (please write your names here): Ju, Piet, Liz Blanchard, Jeff
Meet next Wed same time as this meeting timeslot

3. Persona planning (milestones)

Propose to have 2-3 personas for Summit (Cloud Administrator, Cloud Operator, Cloud End User, Cloud Developer)+1
survey / screener -- 2 weeks' time, by next meeting (March 5th); need to give survey a week to find candidates
interview -- Finish interviewing by March 26th?
interview script/questions
use survey monkey?
ASK: Smaller working group to work on this?
Who's interested (please write your names here): Ju, Jeff, Thuy, Liz, Jenny, Fei, Jacki
preliminary review
persona development
full review
persona validation
publish/share persona Summit, just before summit or after?

4. Open Topics

Vote for our persona session at the summit!

Meeting Summary for 5 February 2014


Nick Chase, Liz, Piet, Dave Lyle, Fei Guo, Jenny, Jacki, Mellisa


1. Updates from last meeting

OpenStack Personas Working Group Wiki started by Nick Chase. Thank you Nick Chase!!!+1

2. Confirmation that we will meet every other Wednesday beginning Feb 5 4:00EST (21:00 UTC)

Let Piet know if you want to be added to the calendar invite.

3. Summit proposal for Juno Release Summit.

Submitted for the Atlanta OpenStack Summit. This should be available to vote for after Feb 14th. Liz will send link when available.
Title: Development and Application of the OpenStack Personas
This session builds on Dave Neary’s previous efforts to develop a set of personas to help the development community align with their users’ needs and tasks.
The team will share updates from the newly formed OpenStack Persona Working Group, which is made up of members from over ten global companies. The session will include a review of the methodology used to develop the personas, insights from the user interviews and the personas created from the effort.
Finally, the team will provide recommendations and examples for how the community can effectively use the personas during their own planning, design, development, and testing efforts to improve user experience.
Q: Does it make sense to propose this in the main track, or in the Developer Summit? More exposure to developers in the dev section. (DN)

4. User roles to focus on initially

  • Cloud Developer: Design, implement, publish and maintain the technical aspects of a service component
  • Cloud Operator: Monitor running systems, and track and initially triage events
  • Cloud Administrator: Responsible for all cloud operational processes in their area of expertise (e.g., Network)
  • Tenant / Domain Administrator: Responsible for administering a customer’s communities and their resources.
  • Cloud Consumer / End User: Request & use resources, depending on aaS offering (IaaS, PaaS, SaaS, etc. user).

5. Next steps

Develop screener for the roles
Pilot screener with a few people, make any necessary edits
Begin developing interview questions
Ask about primary tasks, secondary tasks (which tasks are in your core role)
Discussion around how to find individuals to interview
openstack-operators mailing list? openstack-dev mailing list? G+ groups, linkedin groups, Blogs/newsletters that we run (Not just limited to OpenStack...VMWare, Azure too)

6. Open topics

Jared Spool's Persona Building Steps
a) Built a cross-functional team including User Experience Designers, Software Testers, Documentation Specialists, Product Managers, Developers. (Done)
b) Gave an overview to the team on what Personas are, how they are used, how we will construct them. (Done)
c) Broke out into small teams to break down some of the preparation tasks.
d) Prepared a screener to run by potential interview candidates.
e) Prepared a set of interview questions and reviewed with the entire team.
f) Performed a few mock interviews to practice.
g) Visited 20 interviewees and asked the same interview questions to all while taking a lot of notes.
h) Created a scale of answers for each question and mapped all 20 participants back to scale. (We used colored sticky notes to differentiate between all participants)
i) Identified clusters of interviewees responses.
j) Created persona writeups based on these clusters keeping the folks that we interviewed in mind.
k) Finalized persona designs including a short write up on the persona and included a photo, Key Attributes, and Behavioral Drivers.
l) Printed large versions to post around the office, small 5x7 cards on keyrings for the team to keep and reference.

7. Worked on screener (survey)

Meeting Summary for 17 January 2014


Piet Kruithof, Ju Lim, David Lyle, Nick Chase, Liz Blanchard, Jacki Bauer, Dave Neary, Jenny Mahmoudi, Fei Guo, Birgit Schmidt-Wesche, Jeff Calcaterra

Meeting Summary

Here's a short summary of the last meeting and what was decided:

  • The goal of the Persona Working Group project is to make clear the needs of the people who are consuming OpenStack, so the cummunity understands what the product they're building needs to provide.
  • Initially the focus will be on technically-focused personas in order to ease development and also get community buy-in.
  • Methodology will be based on creating personas using the following video as guidance: http://aycl.uie.com/virtual_seminars/building_personas_in_30_days_or_less; rather than be site-visit focused, it will be more questionnaire focused.
  • Initial "buckets" (categories) that we will focus on are: Operator, User, Developer. These are intentionally broad.
  • Within those buckets will go the roles defined below (lines 68 to 165 in the Etherpad), as agreed by the working group.
  • Once we have roles, we will develop questions and recruit participants.
  • Roles are designed to make sure we haven't missed sub-groups within the buckets, and to facilitate question creation.
  • Decisions will be discussed in meetings but "ratified" on the mailing list, in case people miss the meeting.
  • For meetings, we still are determining when to meet. Current thinking is to meet every 2 weeks and perhaps host the meetings at at alternates times every other meeting so team members that are not in the US will have an easier time to join the meetings. Here's yet another Doodle to figure out the 2 different meeting times on which to meet:
When you vote, please keep in mind, we're trying to come up with 2 different meeting times -- one that accommodates US (most of the team currently) and one that accommodates folks overseas (Europe, Asia, Australia, etc.).
  • we need more folks to reviews the persona roles (lines 68 to 165 in the Etherpad) and comment on which ones you've come across, the titles most commonly associated with the role, and vote on which roles we should work on. Please do so before our next meeting.
  • OpenStack Personas Working Group Useful Links:
Mailing List archives: http://lists.openstack.org/pipermail/openstack-personas/
Mailing List: openstack-personas at lists.openstack.og
IRC: #openstack-ux
Etherpad: https://etherpad.openstack.org/p/persona-working-group

Meeting Summary for 18 December 2013

The initial meeting was kicked off on 18 December 2013.


Piet Kruithof (HP), Ju Lim (Red Hat), Liz Blanchard (Red Hat) , Andreas Jaeger (SUSE), Nermina Miller (Mirantis), Jeff Calcaterra (IBM), David Avila (IBM), David Lyle (HP), Jenny Mahmoudi (Puppet Labs), Terry Bleizeffer (IBM) Unable to attend but would have liked to: Tom Fifield (OpenStack Foundation), John Pruitt (Dell), Dave Neary (Red Hat), Birgit Schmidt-Wesche (IBM), Nick Chase (Mirantis), Fei Guo (Puppet Labs), Thuy Duong (IBM), Jacki Bauer (RackSpace)


Intro - meet and greet, expectations Group Organization - follow OpenStack community

  • To be officially recognized as an official program in OpenStack, there is a high hurdle so we'll have to run this as an informal program for now (especially since there is no official UX program). David Lyle (Horizon PTL) happy to lend a hand to help champion it within the Horizon community, e.g. give up a session at Summit. Horizon would be a consumer of these personas. OpenStack community still does not quite understand UX community and what it means to have UX and still very much code driven. user-committee exists already and how does UX fit in, as well as personas fit in with that effort. There is a process to get folks recognized as ATC (Active technical contributor) for folks who don't code (e.g. benefits: voting, free admission to Summit) and David willing to support folks working on this effort as ATCs. Will need to educate the other groups as to personas since it's still a new concept. Socializing and adoption will be important.
  • Level of Engagement

Attendees & Interests

  • Nermina Miller (Mirantis) -- wants to do a blog on this effort and try to promote it and observe, understand Russian
  • Liz Blanchard (Red Hat) -- interviews, validation, visual design, could maybe get Julie Pichon to help with interviewing in French, Jarda in Czech, Alvaro in Spanish?
  • Melissa (HP) -- interviews, analysis
  • Piet Kruithof (HP) -- interviews, analysis, project management
  • Ju Lim (Red Hat) -- all, Ju speaks Malay/Indonesian
  • IBM -- wants to be involved in entire process and contribute to each deliverables; still need to figure out who from IBM would be responsible for various deliverables. Thuy (interviews), tasks assignment TBD
  • Fei and Jenny (Puppet Labs) -- 20 hours a month? creating interview plan or plan for creating interviews-, post session analysis, Fei speaks Chinese
  • David Lyle (HP) -- advisory, help initial creation process understanding defacto current personas, review
  • Andreas (SUSE) -- mainly validate and review; speaks German
  • Tom Fifield (OpenStack Foundation) - keeping tabs & documentation team interface
  • Communications -- meeting logistics, when and how
  • Less often would be better

Action Items

  • For Everyone: Doodle for voting and finding an ideal meeting time: http://www.doodle.com/yiz4xytwmkkn6uh6. Please enter your name and vote for times that work for you for the monthly meeting.
  • Monthly meeting proposed for larger group
  • Subgroups may meet more frequently and have a different rhythm

More Kick-off Meeting Notes

  • User Committee Presentations:
Portland Summit (Havana planning) - http://www.openstack.org/summit/portland-2013/session-videos/presentation/openstack-user-committee-update-and-survey-results
Hong Kong Summit (Icehouse planning) - http://www.slideshare.net/openstack/openstack-user-survey-october-2013
Q. User survey data -- can we get access to the raw anonymized data? How soon?

Return to Personas Wiki