<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body bgcolor="#FFFFFF" text="#333333">
Hello Everybody!<br>
<br>
my name is Jarda (shortening from Jaromir) and I'm working on
Horizon in a way of improvement the UX. Couple of weeks ago, there
was set up community on Google+ to group UX related people to
discuss designing issues. I think it was really great idea to start
this effort and I love to see all people interested in helping
Horizon being a better place. However, Google+ posts and discussions
don't work very well for broader discussions about design issues,
and I'd like to state here few examples of why I think so:<br>
- Comments are very narrow (worse readability, long comments are
really bad supported).<br>
- Comments don't include images support.<br>
- There is no way where to store supportive materials.<br>
- Nobody knows what issues are resolved, what are still active.<br>
- No possibility to search for related topic (was this already
discussed? Am I the first one to ask this?).<br>
- Notifications are also not from the best ones (activity of members
just slipped down); not big awareness.<br>
<br>
... and I have little bit more troubles with using it for design
discussions.<br>
But long story short - I'd like to propose using GitHub for storing
documentation and starting discussions related to UX of OpenStack
(Horizon).<br>
<br>
In my opinion the best way to deal with UX in Horizon is to create a
GitHub repository "user_experience" within OpenStack account, store
related documentation in there and use GitHub Issues for
discussions. Here are some benefits:<br>
* You can get subscribed to the repositoryor even just issue you are
interested in, so you get notifications on your mail or just online
(whatever works for you).<br>
* Issues are grouping topics very well together so the discussion
for the topic stays at one place and everything is connected.<br>
* Once the issue is solved we can close it (and it is archived).<br>
* Issues have quite good options for text formatting.<br>
* You can past image directly to the post.<br>
* You can upload bigger temporary supportive materials to your
forked repository.<br>
* The upstream repository itself can work as a good place to store
UX documentations for Horizon (wireframes, documents, guides, etc).<br>
* What goes to the repository itself goes through pull-request
process so we can make sure that there are ideas which were publicly
discussed and accepted.<br>
<br>
Also, it provides better accessible way for any contributor, who is
having some UX related issue. Since "user_experience" repository
would be placed among other projects, it will be very easy to notice
it and find this place if I need such a help. So, it is more likely,
that we will increase activity and get more ideas together, also we
enhance connecting developers and design people together, if both
are contributing. I see UX as another project under OpenStack,
though - sure - little bit different type of project, but still a
project. And if we manage to get this project active we will
definitely enhance resulting UX of Horizon, which is a goal.<br>
<br>
What do you think about this idea? Any thoughts? I'd be very happy
to help with setting this up so it works smoothly.<br>
<br>
Best<br>
-- Jarda<br>
jcoufal at #openstack-horizon<br>
</body>
</html>