17:00:16 #startmeeting UX 17:00:17 Meeting started Mon Jun 2 17:00:16 2014 UTC and is due to finish in 60 minutes. The chair is jcoufal. Information about MeetBot at http://wiki.debian.org/MeetBot. 17:00:18 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 17:00:20 The meeting name has been set to 'ux' 17:00:27 Hi all! 17:00:38 hello! 17:01:01 o/ 17:01:09 o/ 17:01:13 Hi! 17:01:22 Hi! 17:01:39 o/ 17:01:49 o/ 17:02:06 #topic Welcome 17:02:26 I would love to welcome you all to the historically first OpenStack UX meeting. 17:03:20 It's great to see all of you here and I hope it will help us to organize our efforts better and to move things forward 17:03:50 hi all!! 17:04:08 o/ 17:04:16 As long as this is our first meeting, let me just mention few facts how this is supposed to look like: 17:04:40 1) Meetings are going to happen twice a month. At this moment it is scheduled for 1st and 3rd Monday in a month at 1700 UTC at this channel. 17:04:58 hi all 17:04:59 There is a possibility for a change (alternating) which we will discuss later today 17:05:22 2) Agenda for each meeting is always available at this link: https://wiki.openstack.org/wiki/Meetings/UX 17:05:49 Feel free to add any topic which you are interested in and which you want to discuss at the following meeting 17:06:32 3) At the end of each meeting there will be space for open discussion where we can discuss any topics which were not scheduled 17:07:06 4) Log for our meetings will be stored at following address: http://eavesdrop.openstack.org/meetings/ux/ 17:08:04 That's all from the introduction. Does anybody have any question regarding meeting organization? 17:08:35 all sounds good to me! 17:09:00 Great, let's move on 17:09:11 #topic Meeting Time 17:09:41 So based on the poll (http://doodle.com/3m29dkn3ef2em5in) I selected this time as the candidate for our meetings 17:09:54 though there are still people who can't make it this time 17:10:14 I also asked people to fill themselves into timezone overview, so we can make the time the most convenient to all 17:10:30 here is the etherpad: https://etherpad.openstack.org/p/ux-meetings 17:10:48 We have very wide range of timezones 17:11:01 for example for adi, it is pretty late night at this very moment 17:11:13 so the suggestion is to alternate the times 17:11:33 22:41, still not bad ;) 17:11:55 adi: ooo that's pretty late :) 17:12:11 1st monday in a month at 1700 UTC, 3rd wednesday in a month at 1500 UTC 17:12:40 with alternating mondays and wednesday we should cover all interested participants and still majority of us should be able to attend 17:12:46 thoughts? 17:12:50 those work for me 17:12:52 works for me! 17:12:57 Works for me! 17:13:05 +1 17:13:15 works 17:13:32 +1 17:13:43 +1 17:13:57 +1 17:14:05 although I might miss a few just due to pure confusion on my part ;) 17:14:23 +1 but may miss some based on timing 17:14:36 Looks like one voice agreement :) 17:15:01 lblanchard, julim: I will try to remind the meetings at least from the beginning 17:15:09 also mention next meeting time at the end of each meeting 17:15:23 jcoufal: sounds great…we can all try to do the same in the UX channel maybe 17:15:23 that would be good jcoufal 17:15:27 OK for me. 17:15:45 perfect 17:15:50 jcoufal: plus the wiki will show next meeting 17:16:09 Would it be possible to send out meeting invitations as well? 17:16:17 #action jcoufal to reflect meeting times in wiki, ical, etc. 17:16:38 jacalcat: if you add to the etherpad your e-mail addresses, I can add you as participants 17:16:46 jacalcat: you can sync with the openstack meetings calendar as well 17:16:47 jacalcat: I haven't seen meeting invites within OpenStack much at all…I've normally just created personal ones for my calendar 17:16:48 https://etherpad.openstack.org/p/ux-meetings 17:16:58 david-lyle: ah right openstack calendar! 17:17:17 david-lyle: yeah, though it is pretty full :) 17:17:19 david-lyle: I did that once and got flooded with them all…but maybe there is a way to only choose uX 17:17:21 https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics 17:17:29 just decline the ones you don't want 17:18:08 small reminder - currently we have just mondays, I need to arrange the change for mon&wed 17:18:17 advantage is all invite times are in UTC and work correctly even over DST switches 17:18:33 david-lyle: yeah, that is much safer option 17:18:41 those time shifts are sometimes confusing 17:19:30 #link https://www.google.com/calendar/ical/bj05mroquq28jhud58esggqmh4@group.calendar.google.com/public/basic.ics - meetings calendar if you want to sync up on meeting times 17:19:44 great, all agreed let's move on 17:20:05 I will jump a little bit in the agenda and get back to the second topic later 17:20:15 #topic StoryBoard and UX 17:20:19 HI 17:20:29 Hey krotscheck 17:20:42 Sorry, I’m interrupting. Go ahead. 17:21:20 Np. We already discussed using StoryBoard at the Summit and we agreed that we can jump to using it right away 17:21:39 The advantage for storyboard is that we can provide usability feedback 17:21:57 And we have nothing to loose if we switch from current launchpad to storyboard now 17:21:58 +1 to that, unless anyone has been poking around and has found that there are major blockers that we have in Launchpad that don't exist in Storyboard today 17:22:09 but I didn't find anything…current Storyboard looks great to me! 17:22:27 Apart from some small suffering as Thierry mentioned :) 17:22:34 So we have also blessing from infra team 17:22:49 jcoufal: what's the small suffering? Getting items into Storyboard? 17:22:52 It is just matter of allowing UX project in StoryBoard which got a bit complicated 17:23:03 lblanchard: I guess he meant usability :) 17:23:09 jcoufal: haha 17:23:13 The biggest hurdle seems to be that the existing project configuration automatically creates a git repository. https://review.openstack.org/#/c/96549/ 17:23:43 krotscheck: hmm yes, we probably don't need that…is this an issue? Or can is just remain empty? 17:23:52 I think a git repo actually would be useful 17:24:05 for storing finalized designs 17:24:10 david-lyle: that gets into the discussion of where we store our files :) 17:24:28 david-lyle: it was objected, that git might be problematic for larger binary files 17:24:30 lblanchard: Depends on who you ask. I’m ambivalent, I just want to see you guys squared away and happy. 17:25:11 jcoufal, lblanchard, david-lyle: I can see a case being made for a docs-style repo (similar to *-specs) where persona work can go, but I’m not certain the toolchain is UX friendly. 17:25:31 lblanchard: I know that Jim was against setting a git repo if it is not needed 17:25:34 Aside: Current story for UX team features is here: https://storyboard.openstack.org/#!/story/85 17:25:52 jcoufal, because of versioning?? 17:26:23 jcoufal, david-lyle, krotscheck: Perhaps we could use it for our design templates? It would be a small number of files, wouldn't get huge. 17:26:36 david-lyle: I believe it was mostly because of user experience when storing and requesting changes 17:26:51 krotscheck: is there a problem in setting a project without git repo and if we decide to store files there to add one later? 17:26:57 krotscheck: my concern is the finalized design documents now live on an askbot server not maintained by openstack, this is problematic 17:27:36 jcoufal: The problem is that the toolchain doesn’t know how to do that yet, and I don’t know enough about jeepyb yet to make that happen. 17:27:42 david-lyle: +1 we have decided to stop askbot for final designs…but have come back to using personal storage and links in ML for now…which isn't a great final solution either 17:27:55 I don't know that the iteration takes place using git, but the result could be stored, but it could get large 17:27:58 krotscheck: and the problem with having an empty repo? 17:28:30 jcoufal: I don’t know. 17:28:42 jcoufal: Ask on infra? 17:28:49 will do 17:29:31 #action jcoufal discuss git repo issues so we can move UX project under StoryBoard 17:29:52 after that we should be able to migrate things from launchpad and smoothly move to StoryBoard 17:30:14 everybody is in favor of storyboard? :) 17:30:22 (I guess I should have asked earlier) :) 17:31:46 Sure! 17:31:56 +1 17:32:16 alright, moving on 17:32:38 #topic Wireframes Review Tool 17:33:03 There is suggestion that we can start using InVision for reviewing our wreframes 17:33:13 Couple of people already used it in the past 17:33:23 okay 17:33:34 has anyone else worked with this tool? 17:33:46 it isn't opensource…so I didn't know if that would be a blocker 17:33:53 yep, I have 17:33:57 do we all need to use the same tool, or would it make sense for any tool to be used but to publish to a common format, e.g. JPG, PDF, etc. 17:34:02 or if anyone has used any opensource tool similar for reviewing designs and having comments, history 17:34:14 julim: no, this is just uploaded images 17:34:20 ah lblanchard 17:34:25 Can we use it free of charge? 17:34:26 there is a chance we could get a free version donated to the community 17:34:34 this tool is just for the review piece 17:34:35 Auto-Awesome (works on several browsers) would be fairly easy (free) too 17:34:39 and allows annotation 17:34:51 julim: keeps history of versions? 17:35:03 lblanchard - I don't believe so 17:35:04 julim: I don't think we *have to* use the same tool, but it would be easier for people - they will be used to the same workflow 17:35:55 as far as review goes, its okay. I thought InVision was pretty complex to design 17:36:18 ok jcoufal. makes sense if folks are collaborating on the same design to use the same tool. 17:36:37 adi: have you found anything that would work better? 17:36:46 this is the tool btw: http://www.invisionapp.com/ 17:37:00 I'm definitely open to any tool…this seemed to be the front-runner…then I noticed krotscheck was using it for storyboard too 17:37:10 there have been some rumblings about people not wanting to use non-open-source tooling at all 17:37:12 krotscheck: did you all try any other tools? 17:37:13 for an open-source project 17:37:26 gothicmindfood: I'm happy to use an open-source tool for this 17:37:31 gothicmindfood: just haven't found one :( 17:37:41 lblanchard: yeah, when I've heard the rumblings, I've pointed that out :) 17:37:41 lblanchard: Nope, I got an invite from piet, and said “Good enough, back to work" 17:37:46 I used it some time ago, didn't check how far away actually it evolved 17:37:53 krotscheck: ah okay 17:38:14 We could look at what ubuntu does. I think they use some combo of balsamic and wiki 17:38:15 well maybe folks can keep an eye out and do some research on open-source tools in this space? 17:38:35 so all designs and I think older versions along with critique is in one place 17:38:39 jackib: +1 Although I think balsamic is $$ 17:38:45 i've used balsamiq and pencil 17:38:47 yep it is 17:38:56 but great idea to try and understand what other opensource designers are doing 17:39:09 FYI - https://wiki.ubuntu.com/Touch/CoreApps/Design 17:39:12 adi: I tried pencil out…but it's more for wireframing 17:39:17 rather than sharing/reviewing 17:39:33 the same for balsamiq I would say 17:39:36 correct. like i said, invision is fine for reviewing 17:39:49 Regarding open-source: One of the things is, that if they decide to shut down the service, we are going to lose all history 17:40:00 It is always better if we can host the tool on openstack servers 17:40:26 though as lblanchard we havn't found any suitable open-source tool yet 17:40:33 that is a big downside 17:41:19 krotscheck: perhaps a feature of storyboard :) :) 17:41:37 comments on images, revision history of images? 17:41:38 in my industry, we like to call that scope-creep lblanchard ;) 17:41:45 gothicmindfood: haha 17:41:54 gothicmindfood: yes, and wishful thinking on my part 17:42:13 lblanchard: https://storyboard.openstack.org/#!/story/85 17:42:28 krotscheck did allow for asset upload in that story ^^ 17:42:30 but we need something. maybe a few people can do a bit of research on alternatives/pros/cons? 17:42:41 I tend to say - keep searching, we can use whatever works for everybody until we find something 17:42:54 is there anybody willing to do the research? 17:43:06 i can 17:43:21 * gothicmindfood would but I'm a ux n00b 17:43:25 I have little time right now. But I can contribute what I already use/know about 17:43:28 adi: would love to help out to help me learn more! 17:43:46 gothic: alright 17:44:02 great! we have volunteers 17:44:03 if someone identifies some tools, I'm happy to review a few of them to help out 17:44:20 Basic question, what is the requirement for that tools compared to pdf wireframe review? 17:44:23 will you guys cooperate (probably in some etherpad) and put something together? 17:44:38 jcoufal - yes 17:44:40 Toshi: great point, we should start with listing the requirements down 17:44:57 https://etherpad.openstack.org/p/uxtools 17:44:59 yes, requirements / parameters against which we do the research 17:45:07 let's do it there ^^ 17:45:10 awesome! 17:45:21 Great! 17:45:25 #link https://etherpad.openstack.org/p/uxtools - UX tools research 17:46:25 #action adi, gothicmindfood to keep the ball rolling on wireframing review tool research 17:46:38 everybody else is ofcourse welcome to contribute 17:46:47 we need feedback from everybody 17:47:02 moving on 17:47:14 #topic UX in CLI and API 17:47:30 UX is broad area 17:47:41 we are contributing the most in GUI 17:48:11 but there is need for UX also in CLI, API, DX (dev exp), etc 17:48:31 interesting 17:48:35 we are so short handed already though 17:48:49 it was mentioned multiple times on both previous summit as well 17:48:54 people are asking for help there 17:49:08 jcoufal: which projects in particular? 17:49:22 nova is definitely interested 17:49:26 but as jackib mentioned, we don't have enough people 17:49:35 Question: What do you mean by UX for CLI - Does it mean translating CLI requests (inputs) via UX? 17:49:45 there's a big need and I think it's cross project. like getting consistency 17:49:55 gothicmindfood: well if we talk about API's experience, I would say definitely all should be interested because of consistency 17:50:06 that makes sense 17:50:11 but lblanchard mentioned, nova is an example 17:50:27 adi: mostly consistency 17:50:30 yes, another example would be helping the OpenStackClient project… 17:50:34 at least that's the start 17:50:36 they already have HCI guidelines: https://wiki.openstack.org/wiki/OpenStackClient/HumanInterfaceGuidelines 17:50:45 but we could help here…as well 17:51:02 because at the moment, if you look at listing function, nova, glance and heat have different commands for it 17:51:06 if I remember correctly 17:51:10 so it's a matter of…does anyone have time? Should we try to evangelize UX in these groups somehow where we wouldn't have to focus 100% on it… 17:51:23 lblanchard: good question 17:51:41 Is there anybody interested and willing to work on APIs and/or CLIs? 17:52:02 we have a developer advocacy group at rackspace interested in this. maybe they can help out 17:52:25 I'm also wondering if there is a way to ask folks on each team if anyone has interest in UX 17:52:30 Or at least start with evangelization, talking about it, gathering people together with same interest 17:52:38 jcoufal: +1 17:53:00 +1 17:53:15 I can start the ball rolling by sending some mails to the mailing list and we can see if there is somebody willing to help, join 17:53:34 +1 17:53:36 +1 17:53:41 any other suggestions about what we can do more? 17:53:54 it would be a huge step for the component teams to know that we don't just focus on GUI/Horizon and would be happy to at least give small feedback in other areas (since we don't have enough people to have someone focus 100% on it) 17:53:56 jackib: would be great - can you talk to them if they are willing to help? 17:54:05 lblanchard: +1 17:54:17 sure thing 17:55:19 perfect 17:55:25 #topic Open Discussion 17:55:41 any other topics to discuss in remaining 4 minutes? 17:56:17 jcoufal - thanks for setting this up 17:56:19 wow, great job everyone on getting through those 4 major topics in an hour! 17:56:21 jcoufal : im good for nwo 17:56:29 jcoufal++ 17:57:34 thanks everybody for attending and your participation 17:57:56 Next meeting: Wednesday, June 18th, 1430 UTC (half an hour earlier because of conflicts), #openstack-meeting-3 17:58:10 thanks people. talk to you soon! 17:58:14 catch you all 2 weeks from Wednesday! 17:58:28 #endmeeting