ubuntu-phone team mailing list archive

[Łukasz 'sil2100' Zemczak <lukasz.zemczak@xxxxxxxxxxxxx>]

Hey Robert,

Looking nice so far, thanks for the enhancements!

Some ideas for improvement that might also help out with one of the
issues that Michael mentioned below:

The generall idea is to de-clutter the bileto interface. The hover
overlay menu is a step in the right direction, but I was actually
thinking of doing something different. What if each bileto landing could
be click-to-expand? This would mean that the main interface could
generally only show the most important information, but in the expanded
view it could show all the details that are generally interesting only
for certain people - like landers of the given feature and trainguards.

This could be done by either introducing an accessible button 'See
Details' or just by a onclick of the table row, after clicking which the
landing would expand and show all details + the actual silo controls.
The hover bar is nice, but when you think about it, silo actions aren't
performed as frequently and aren't as time-critical to be visible
everywhere. And besides, landers are generally only interested in the
controls of a selected landing they're working on. This way we could
have an even more clean and visible interface, but with all the info and
controls we need. Just a click away.

The good ol' Issue Tracker I once made has something similar, but
not-too-fancy as it has no animations of the expanding:
 http://people.canonical.com/~lzemczak/issues/

This was also basically the main idea of the CI Airline UI we were
preparing.

On the spreadsheet there was no other choice but include ALL the
required data in the main row - with our custom tools we should only
show the most important, and leave the rest visible to only those that
want to see it. Then things like 'what merges are actually configured'
or all the comments for a silo etc. could be in the details. Then we
could only show the top-most comment on the main view.

What do you think?

Cheers,

W dniu 27.08.2015 o 12:15, Michael Zanetti pisze:
> Hi Robert,
> 
> it's nice to have only one site for all the stuff. Some little feedback:
> 
> * when adding a new branch to an existing silo and then reconfiguring
> it, before one could easily see if the reconfigure step was successful
> or not, depending if the new MR would show up on the dashboard or not.
> Now, adding it will always make it appear there and in order to see if
> it really ended up in the silo config, I think one needs to either check
> the configure job's history to find out.
> 
> * I find it a little harder to find my silos in bileto, I think that's
> partially because the list has less spacing than the entries in the
> dashboard had, but also because bileto still shows my old, already
> landed silos.
> 
> Would be nice to get some improvements for those over time.
> 
> Thanks a lot,
> Michael
> 
> On 27.08.2015 02:17, Robert Park wrote:
>> Hi everybody!
>>
>> A quick heads up about some improvements I've made to the Bileto
>> Requests page, here:
>>
>> https://requests.ci-train.ubuntu.com/
>>
>>
>> Most notably, for requests that have silos assigned, I've added links
>> to the Build/Publish/Clean jobs, which for most people should
>> alleviate the need to ever visit the dashboard[0] ever again. If you
>> find there's something missing from the requests page and you're going
>> to the dashboard for any reason, please let me know ASAP! My goal is
>> to remove the dashboard soon, as it's existence is blocking my ability
>> to get some other exciting work done.
>>
>> This update also comes with a slew of smaller niceties:
>>
>> * The cluttered Assign/Edit/Comment/etc actions are now swept into a
>> hidden pop-up that only appears when you hover on each request. This
>> cuts down on visual clutter significantly, hopefully without being too
>> unintuitive (let me know if you have any problems using the new
>> actions menu).
>>
>> * when logging in, SSO now redirects you back to the page you were on,
>> rather than the front page.
>>
>> * if you ever tried to manually fiddle with the URL before, you might
>> have noticed that you had to reload the page to make bileto notice
>> your URL changes. This is now fixed and bileto will now respond to
>> manual URL manipulations in a live and responsive way.
>>
>> * I've changed the way the URLs are interpreted, which has changed all
>> the URLs (sorry if you had bookmarks!) but this allowed me to
>> eliminate several dozen lines of weird corner cases in the code, and
>> better future-proof against expansions of backend API features.
>>
>> * There's a new "trainguards" page[1] which highlights only requests
>> that are ready to be published, so us trainguards don't have to hunt
>> around for such things.
>>
>> * and probably other things I can't remember.
>>
>>
>> Anyway, take it for a spin, please let me know what you think!
>> Hopefully this is helpful ;-)
>>
>>
>> [0] https://requests.ci-train.ubuntu.com/static/dashboard.html
>>
>> [1] https://requests.ci-train.ubuntu.com/#/trainguards
>>
> 
> 
> 


-- 
Łukasz 'sil2100' Zemczak
 Foundations Team
 lukasz.zemczak@xxxxxxxxxxxxx
 www.canonical.com