Re: [openstack-dev] [Horizon] Specs repo
Pros: * This process makes sure implementation design for a feature happens _before_ the actual implementation. This is very important as it potentially saves developers from wasting a lot of time implementing a feature in a suboptimal way. * By making reviewers explicitly focus on the more essential aspects of a feature design, we make sure that the feature gets a better/more efficient implementation. * We will have a feature design recorded for posterity. I don't think I need to explain how useful this can be. Two more pros: * Since Horizon often has UI assets (mockups, prototypes, visual designs) that go along with a feature, the spec repo could also be used to document or link to the locations of these assets. * It’s also a way for designers who don’t code to contribute to the project, because they can create, review and edit spec docs. ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [Storyboard] [UX] Atlanta Storyboard UX Summary
On May 22, 2014, at 4:28 AM, Thierry Carrez thie...@openstack.orgmailto:thie...@openstack.org wrote: Now I understand it can be confusing, especially for people without a Launchpad Bugs background. Maybe we can find a better term for tasks (work items ? steps ? commits ?), maybe we need to educate/document more, maybe the UI should make it easier to grasp as a concept. But given that our primary audience is OpenStack developers, I suspect that once they understand the concept it's not that much of an issue. And since most of them have to use Launchpad Bugs now (which has a similar concept), the learning curve is not too steep... Is there a mockup/prototype or anything that shows what the longer term vision of storyboard is - how the information architecture and workflow will be? As an easy example, is there a plan for a story to ever have a type - like ‘bug’, ‘suggestion’, etc? The reason I ask is it can be hard to select good labels for things without knowing what the full data schema is going to look like. and vice versa, once more of that is visible in the UI, users might become less confused! I’m also curious about the terms selected - ‘story’ has a specific meaning in agile but looks to be different in storyboard, and it seems like ‘blueprint’ isn’t being used anymore. If we understand the overall thinking behind the concepts, it will be easier for people to help come up with terms that better reflect those underlying concepts. -Jacki ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [horizon] Unofficial Sunday Summit Meetup
Liz Blanchard and I will be there at 8. On May 11, 2014, at 2:53 PM, Aditya Thatte aditya.that...@gmail.commailto:aditya.that...@gmail.com wrote: Okay. Guys, please let us know if the plan is still on. On 11-May-2014 10:37 AM, Jason Rist jr...@redhat.commailto:jr...@redhat.com wrote: On Sun 11 May 2014 03:32:52 AM MDT, Aditya Thatte wrote: Is this meeting confirmed? I've reached Atlanta, and staying at the Hilton Garden Inn. On Tue, May 6, 2014 at 10:10 PM, Jason Rist jr...@redhat.commailto:jr...@redhat.com wrote: On Tue 06 May 2014 10:29:43 AM MDT, Jaromir Coufal wrote: Hi folks, during Horizon's IRC meeting, we got to the idea that it would be great to hang out on Sunday evening and meet unofficially before the Summit. We are gathering all suggestions in following etherpad: https://etherpad.openstack.org/p/juno-summit-horizon-sunday-evening (you can find the latest info here). So everybody interested - join us - we are looking forward to all of you! :) -- Jarda ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev At the moment, looks like we're planning on meeting at the Westin Sundial restaurant bar at 8PM! See the etherpad for more info. -Jason -- Jason E. Rist Senior Software Engineer OpenStack Management UI Red Hat, Inc. openuc: +1.972.707.6408tel:%2B1.972.707.6408 mobile: +1.720.256.3933tel:%2B1.720.256.3933 Freenode: jrist github/identi.cahttp://identi.ca/: knowncitizen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev I think so. I'm going to be late, due to my flight being delayed out of Denver. Might miss it! -- Jason E. Rist Senior Software Engineer OpenStack Management UI Red Hat, Inc. openuc: +1.972.707.6408tel:%2B1.972.707.6408 mobile: +1.720.256.3933tel:%2B1.720.256.3933 Freenode: jrist github/identi.cahttp://identi.ca/: knowncitizen ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
[openstack-dev] [Horizon] [UX] Better Dashboard Pages Summit Session
Hi all, Some Horizon people will be talking about improving overview/dashboard pages at the summit. We¹ll be showing some design concepts during the Dashboard Accessibility session on Friday at 9:50 am (this is a combined session). We’d like to find out if we are on the right track with some design concepts. Here¹s a preview of the mockups - Admin and User Concepts option 1 (PDF): http://bit.ly/1nmgVrC Admin Concept option 2: http://people.redhat.com/~lsurette/OpenStack/Horizon%20Admin%20Overview%20Pages_2.0.pdf User Concept option 2: http://people.redhat.com/~lsurette/OpenStack/Horizon%20Overview%20Pages_v1.0.pdf And a link to the etherpad - https://etherpad.openstack.org/p/juno-summit-overview-page-horizon Best, Jacki . Jacki Bauer User Experience Designer Rackspace Private Cloud 512.874.1226 ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
Re: [openstack-dev] [UX] Proposed tools and workflows for OpenStack User Experience contributors
Thanks for starting this conversation. It’s really important and there’s a ton of work to be done! On Apr 23, 2014, at 9:46 AM, Liz Blanchard lsure...@redhat.com wrote: On Apr 23, 2014, at 8:13 AM, Jaromir Coufal jcou...@redhat.com wrote: Dear OpenStack UX community and everybody else who is interested in OpenStack's user experience, Thanks very much for taking the time to write this up, Jarda. I think this would be an awesome list of topics to cover in the User Experience cross-project sessions scheduled for the Summit on Tuesday afternoon. What do others think? I’ll also add some thoughts below to start to drive the conversation further on this list. When there is more contributors appearing in time, I would like us to establish a formal process of how the UX work should be organized. Therefore I am suggesting a few tools below for us to be more effective, transparent and to provide a single way to all contributors so that it is easy for everybody to start, to contribute and to get oriented in our world. Wiki = introduction to OpenStack User Experience = how to contribute guide = documentation of processes = redirecting people to the right places of their interest (IRC, Launchpad, etc) +1. It would be awesome to include some basics about using the mailing list for communication along with IRC and how to balance the two. +1 Mailing list - [UX] --- = discussions about various issues = openstack-dev mailing list, using [UX] tag in the subject + brings more attention to the UX issues + not separated from other OpenStack's projects + threading is already there (e-mail clients) + no need for setting up and maintaining additional server to run our own forum - requires to store attachments somewhere else (some other server) ... similar case with current askbot anyway - requires contributors to register to the openstack-dev mailing list ... each contributor should do that anyway A big +1 to this. Currently there is a mailing list called openstack-personas that has been meant just for the persona effort, but I’ve been trying to get folks who have been involved in that effort to be sure to subscribe to this list and start generating any conversations that are pure UX here on the dev list instead of that personas mailing list. The personas mailing list was really just meant to kick off all of the work that would be done and then we’d bring high level details to this list anyways. Having more or less all UX conversations in one place makes way more sense to me. There are a lot of discussions on the persona list that I don’t think belong on dev - things like the logistics of planning user research, methodologies and so on. There will also be discussions that require feedback from designers, but would really confuse devs (designs in early stages). One negative impact of using the dev list is that the content we want devs to respond to - research results, designs in later stages,etc - might be ignored or missed because of the other ’noise'. Could we use the dev list for anything we want wider community feedback on, and use another tool (ux mailing list, invision, something else) for the rest of the conversations? Discussion forum - (terminate) -- + more interactive + easier for newcomers - separating UX outside the OpenStack world - we haven't found any other suitable tool for discussions yet (current AskBot is not doing very well) - in order not to fragment discussions into multiple places, I am suggesting termination of current AskBot and keeping discussions in mailing list Another idea would be to use the general OpenStack Askbot, but I agree it is yet another place to go to review things and the current way of using Askbot has been difficult to keep up with and follow active discussions. +1 to finding a way to use the mailing list efficiently for design reviews. I’ve found that having a way to leave comments right inline on a design has been very helpful. Jacki and I have been using a tool called “Invision” to share our designs back and forth to get each others feedback and it has been great. I think there is also a tool called Review Board that is open source. Could be worth checking that out as a discussion tool? No matter what, we should work this into the Mailing List too so that folks know when feedback has been given. Agree the discussion forum isn’t working but not sure what to do about it. I don’t think the mailing list is a solution because designers need the ability to read through the history of an issue or project, and to link many related topics together into something easily digested. And some of our work starts and stops over many months, so the mailing list would be really hard to use for this purpose. People joining the UX community would have a real challenge in getting the information they need on
Re: [openstack-dev] Operators Design Summit ideas for Atlanta
Tom, This is a great idea! Feel free to reach out to the user experience folks, as they’ll be interested both in attending and helping coordinate. http://ask-openstackux.rhcloud.com/questions/ openstack-perso...@lists.openstack.orgmailto:openstack-perso...@lists.openstack.org Best, Jacki On Mar 28, 2014, at 2:01 AM, Tom Fifield t...@openstack.orgmailto:t...@openstack.org wrote: Thanks to those projects that responded. I've proposed sessions in swift, ceilometer, tripleO and horizon. On 17/03/14 07:54, Tom Fifield wrote: All, Many times we've heard a desire for more feedback and interaction from users. However, their attendance at design summit sessions is met with varied success. However, last summit, by happy accident, a swift session turned into a something a lot more user driven. A competent user was able to describe their use case, and the developers were able to stage a number of question to them. In this way, some of the assumptions about the way certain things were implemented, and the various priorities of future plans became clearer. It worked really well ... perhaps this is something we'd like to have happen for all the projects? *Idea*: Add an ops session for each project in the design summit https://etherpad.openstack.org/p/ATL-ops-dedicated-design-summit-sessions Most operators running OpenStack tend to treat it more holistically than those coding it. They are aware of, but don't necessarily think or work in terms of project breakdowns. To this end, I'd imagine the such sessions would: * have a primary purpose for developers to ask the operators to answer questions, and request information * allow operators to tell the developers things (give feedback) as a secondary purpose that could potentially be covered better in a cross-project session * need good moderation, for example to push operator-to-operator discussion into forums with more time available (eg https://etherpad.openstack.org/p/ATL-ops-unconference-RFC ) * be reinforced by having volunteer good users in potentially every design summit session (https://etherpad.openstack.org/p/ATL-ops-in-design-sessions ) Anyway, just a strawman - please jump on the etherpad (https://etherpad.openstack.org/p/ATL-ops-dedicated-design-summit-sessions) or leave your replies here! Regards, Tom ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.orgmailto:OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev ___ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
