17:11:07 #startmeeting UX 17:11:08 Meeting started Mon Oct 27 17:11:07 2014 UTC and is due to finish in 60 minutes. The chair is david-lyle. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:11:09 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:11:12 The meeting name has been set to 'ux' 17:11:26 Seems like there's enough people 17:12:31 I don't see an agenda, so... 17:12:38 #topic Open Discussion 17:12:40 So, it looks as though Jaromir isn't able to attend. Are there any complaints if I go ahead and drive the meeting? Or would someone else like to? 17:12:42 enough people, but they are quite short-spoken ) 17:12:51 haha 17:12:56 go for it Piet 17:13:01 I just started the meeting 17:13:06 so the log is running 17:13:12 #chair Piet 17:13:13 Current chairs: Piet david-lyle 17:13:25 Piet you are now a chair as well 17:13:32 you can set topics etc 17:13:55 So, we are working on a Visual Design Specification to help UI devs, designers, etc adhere to Horizon pattersn. The URL is https://docs.google.com/presentation/d/1OKy_oXZQSg8Feo0p6Es7giR6a-w_CK8H03D2R2yAUjs/edit#slide=id.g3637a7faf_084 17:14:21 Please review and provide feedback. 17:14:42 Piet, that's exactly what I've been searching for couple of hours ago at #openstack-ux :)! 17:15:07 Excellent! 17:15:51 We also have an assets library with png images of common Horizon controls and patterns. Let me know if you would like a copy. 17:16:39 I will be posting a link to the Visual Design Spec and Assets Library to the UX wiki by tis afternoon 17:16:41 Piet, aren't they contained in Horizon repo? Or you mean specific assets for designers creating some mock-ups? 17:17:01 Specifically, for designers creating mocks 17:17:09 We should add that as a linked folder in google docs, link it from the pattern document 17:17:25 For example, we have one that can be used with Balsamiq 17:18:34 Sounds good - I can take care of that 17:19:47 Also, Invision has agreed to allow the community to post mocks to their tool for review. Pls reach-out to me if you would like an account. 17:20:32 We already have some cool stuff for the Details Page, Launch Instance, etc that could use reviews from the community 17:20:36 Piet, david-lyle: speaking of openstack.invisionapp.com (btw, thanks, I've received an invite) is it now an official way of sharing mock-ups? 17:21:07 Newp - its the "unofficial" way to share mocks 17:21:33 I wouldn't say it's official. But it may be an effective way, since we are missing an official way 17:21:50 I've been thinking about sharing mock-ups for Merlin UI for Mistral (as soon as mock-ups are ready) on it... 17:22:07 Exactly- I'm looking to build momentum - we really need a good platform for reviews 17:22:26 The search for a common open tool has not produced a clear answer 17:23:18 guess, it would be better to start with something finally :) 17:23:39 Agreed - felt like we were floundering a bit 17:25:33 david-lyle, is there some time at summit scheduled for live discussion of mock-ups? 17:25:47 I mean, at the Horizon section... 17:25:51 I agree, this seems like a good approach. We will look into sharing things this way as well. 17:26:20 http://kilodesignsummit.sched.org/overview/type/horizon 17:26:21 Feel free to reach-out if you would like to join Invision 17:26:28 there is a UX session 17:26:41 Ju should be coordinating with others 17:26:50 julim: that is 17:27:05 ack david-lyle 17:27:11 okay 17:27:12 will reach out to folks 17:27:24 if there is not enough time in the UX/Horizon session, we can share them in the open Horizon session of Friday 17:27:36 great, I think it'll be great to have a good conversation about the current design mocks and direction 17:29:58 Jeff, can you talk about the personas? 17:30:38 just a thought, but someone else acting as co-chair for this meeting on the wiki while lblanchard is out would help 17:31:12 I don't mind if everyone else agress 17:31:58 works for me 17:32:18 About Personas 17:32:21 k _ I'll reach out to you later about is required 17:32:23 +1 17:32:43 go jacalcat 17:32:53 We have a framework on the wiki 17:33:26 The key ideas are that they are organized around types of ecosystems, which are either applications or types of companies working together 17:34:06 We have a lot of placeholders for personas we think exist, that need some content 17:34:10 david-lyle… sdoyle will be co-chair for this mtg too 17:34:24 Should we move them off the wiki and back to google docs? 17:34:41 Google docs for personas? 17:34:53 I've got to step out for a bit and will be back in a couple hours (doctor's appointment...apologies) 17:35:24 I think they are OK there. I think what I hacked together in the wiki is workable. It mainly needs contributions. 17:35:41 Yeah - the thing about the wiki is that you have such little control over the design and layout of the Persona documents 17:36:48 True, Google docs forces everything into an awkward linear format 17:37:24 Jeff, what kind of feedback are you looking for? 17:37:25 I think it makes sense to come up with the content first, then we can turn it into a website. 17:38:56 1. Do the ecosystems and personas we have ring true with your org? 17:38:56 2. Fill in the placeholders with whatever info you have (and make sure that you reflect that in the status and data sources fields 17:39:18 That would be the two main things 17:39:33 One point of feedback is that we don't have enough information for the specific personas. I remember that we had a lot of really good dimensions that were created during the Austin meeting 17:40:58 For example, orgnizational change culture, need for customization in Horizon, size fo cloud, etc. 17:42:12 Right. Those are mainly reflections of the company or the ecosystem, and I was hoping we could reflect those in the companies. 17:43:28 Are we going completely away from using individuals and just using companies? 17:43:41 I think that is OK. We can put whatever we know and reflect that in the state. 17:44:04 k 17:44:11 I think its both. 17:44:26 Should we have an offsite to work on them? 17:44:52 I think that would be good, but probably not until 2015 at this point. 17:45:36 This is the wiki page I started: https://wiki.openstack.org/wiki/OpenStack_Personas 17:45:43 k 17:46:16 Would anyone else on the team be interested in attending a persona offsite? 17:46:17 CNBB securities is the best reflection of one fleshed out: https://wiki.openstack.org/wiki/CNBB_Securities_Comany_Overview 17:47:00 TBD Medium-Sized IT service provider providing Cloud Services is a good reflection of the number of personas that might be involved: https://wiki.openstack.org/wiki/TBD_Medium-Sized_IT_service_provider_providing_Cloud_Services 17:47:08 jacalcat: will the personas in CNBB potentially the same persona in another company? 17:48:03 Everyone, please review Jeff's work and provide feedback. 17:49:01 That's one of the questions that comes up with this approach. They might be very similar and we might share content between them, but I would keep them separate. 17:49:26 I would hope there would be some consistency in the personas. It would be interesting to show how the same role might change based on the environment. 17:49:49 I think the end users will likely be the same for some of them, but would change going from a test and development environment to a production environment. 17:50:34 We could take the IBM approach and combine or separate roles based on the company 17:50:39 So, they would change their needs and activitiy, but be the same persona - right? 17:51:33 #hinnant - yes 17:52:00 It might be easier to think of them as roles rather than personas 17:52:47 Eight minutes left...anything else that needs to be discussed? 17:52:48 I would say, give them different names, but they might be essentially the same persona. 17:53:00 Because they might diverge based on validation. 17:53:54 Another question on a different topic. Is there a way to join in the design discussions at the summit remotely? 17:54:30 How are we going to validate? 17:54:58 David, is it possible to attend remotely? 17:57:17 Any other topics? 17:58:21 remote presents some difficulty, if someone wants to open a google chat or hangout that can work 17:58:34 if it gets to large, can be problematic 17:58:49 *too 17:58:55 I can't go but would appreciate if someone could do that. 17:59:47 I don't think I'll have the bandwidth personally to set that up, but I can ask those present 18:00:02 but it would be nice to have that arranged beforehand 18:00:11 time's up 18:00:16 #endmeeting