*** davidlenwell_ is now known as davidlenwell | 04:35 | |
*** coolsvap|away is now known as coolsvap | 04:41 | |
*** jtomasek_ has joined #storyboard | 07:10 | |
*** jtomasek_ is now known as jtomasek | 07:11 | |
*** openstackgerrit has quit IRC | 08:32 | |
*** openstackgerrit has joined #storyboard | 08:33 | |
SotK | morning storyboard! | 10:14 |
---|---|---|
Zara | morning! | 10:14 |
*** mrmartin has joined #storyboard | 10:43 | |
*** mrmartin has quit IRC | 11:03 | |
Zara | btw, what does 'sensible updating of cards in boards/items in worklists' mean? | 11:14 |
SotK | at the moment when you move a card there are a load of PUTs sent to update the position of every card affected by the move | 11:15 |
Zara | ah, right | 11:16 |
SotK | but really there should be one PUT and then the backend should figure out which other positions need to change | 11:16 |
Zara | yeah | 11:16 |
Zara | I was thinking, it'd be cool for a board to have an option where its lanes share titles with the task statuses, and cards automatically move to the lane with same title as their task status | 11:17 |
Zara | may well be a story for that already | 11:17 |
*** coolsvap is now known as coolsvap|away | 11:17 | |
SotK | that sounds like a board whose lanes are "automatic worklists" | 11:18 |
SotK | which is something I started but didn't finish before Christmas because I got sidetracked with emails and other stuff | 11:19 |
Zara | ah, okay, sorry, I thought automatic worklists were different (maybe hadn't made the connection) | 11:19 |
Zara | to me automatic worklists in that context sounds like it would mean that 'all cards in review in a storyboard instance are in the review lane', etc | 11:21 |
Zara | *tasks, not cards | 11:22 |
pedroalvarez | lot of things can be automated | 11:22 |
Zara | whereas I was thinking 'all tasks in review on a board are put in the review lane' (the lane title being an implementation detail). idk if that's different to what you were thinking or not. | 11:23 |
pedroalvarez | let's call what SotK is implementing "Automatic population of worklists" | 11:23 |
SotK | I was planning to allow filtering such that you could get a more useful set of things than "all tasks in review in a storyboard instance are in the review lane" | 11:26 |
Zara | ah, okay, gotcha. so automatic worklists are a way of implementing automatic boards | 11:27 |
SotK | that was the plan, yeah :) | 11:27 |
Zara | :P I didn't realise that bit but makes sense! | 11:27 |
SotK | So I've realised it doesn't actually say anywhere that descriptions are in markdown | 11:31 |
Zara | ah, yeah, would be good to mention that | 11:32 |
*** mrmartin has joined #storyboard | 12:43 | |
Zara | how is it already 12:56 when I still haven't had time to review today | 12:56 |
Zara | there are a couple of things waiting in review, btw. https://review.openstack.org/#/c/257505/ is a step on the way to displaying a user's subscribed resources on one page | 13:00 |
Zara | https://review.openstack.org/#/c/263717/ makes it much nicer to add a board | 13:00 |
Zara | https://review.openstack.org/#/c/263235/ fixes paging controls for small screens. someone with a mobile should test this! | 13:01 |
Zara | as for me, I have POST templates for stories waiting https://review.openstack.org/#/c/264286/ | 13:01 |
Zara | pedroalvarez: is your storyboard ansible role (https://github.com/palvarez89/ansible-role-storyboard) up anywhere in the openstack world? I saw there was a story about openstack infra ansible roles (https://storyboard.openstack.org/#!/project/828), but it doesn't seem to be populated... | 13:41 |
pedroalvarez | nope, it's not anywhere in the openstack world | 13:43 |
Zara | shall I ask in infra about the best place for it? or did you have a reason to want it kept separate? | 13:59 |
* Zara asks anyway :P | 14:40 | |
pedroalvarez | tbh, I never asked because I didn't find more ansible roles for infra things | 14:55 |
Zara | yeah, that's strange. I've seen ansible crop up in a lot of infra conversation. maybe they're still researching it? | 14:59 |
krotscheck | Oh, there we are | 15:23 |
Zara | heh | 15:23 |
krotscheck | Infra's using ansible | 15:23 |
krotscheck | They've switched invoking puppet via agent cron, to invoking puppet via remote ansible | 15:23 |
krotscheck | And are slowly migrating things | 15:24 |
Zara | pedroalvarez^ | 15:24 |
pedroalvarez | nice | 15:25 |
Zara | so we were talking about storyboard search, and the plan to just use the one on the right, and Krotscheck raised some issues | 15:25 |
Zara | specifically: what happens when there are lots of criteria? | 15:26 |
krotscheck | Issue 1: The search bar is able to contain quite a number of different criteria. | 15:26 |
krotscheck | Issue 2: There are two distinct use cases taht may conflict. case 1- I want to quicknav to something given only a number and/or a name. case 2- I want to filter on that thing. | 15:26 |
pedroalvarez | I would be happy to continue moving StoryBoard to Ansible | 15:27 |
SotK | hmm, I think the one on the right should remain the same as it currently is tbh (that is, not use criteria), and we should provide an advanced search option somewhere for the filtering approach | 15:28 |
Zara | maybe something like an expanded search would work? (a button for 'more search options...', near the header searchbar) | 15:29 |
Zara | snap | 15:29 |
Zara | I think other buttons may perform the advanced search function currently but it's not obvious from the interface that that's what they do, compared to the header search | 15:29 |
krotscheck | How about changing the suggestion text in the header from "search" to "navigate" | 15:30 |
krotscheck | And then updating the renderers in the dropdown to include more descriptive text. | 15:30 |
krotscheck | Like "goto: <storyname>" | 15:30 |
* SotK would be in favour of that | 15:30 | |
Zara | also, pressing enter after typing in serach text results in a search rather than a navigate; do we want to change that behaviour? | 15:34 |
krotscheck | The behavior of that was supposed to be indicated by the little search icon next to the text that was typed in in the dropdown, which is also the default highlight | 15:35 |
Zara | ah, to me that makes it look like the whole thing is a searchbar, but it'd be good to know if I'm unusual or if that's confused other people. | 15:37 |
krotscheck | It's definitely a nuanced control. | 15:37 |
Zara | I can imagine someone typing in a whole story name and expecting to go to the story when pressing 'enter', but I can also imagine someone being thoroughly confused by that. | 15:38 |
Zara | I'm trying to think how to make it clearer since I like now neat it is! now I get it, it seems obvious, but I've gone several months without understanding why it sometimes did one thing and sometimes did the other. | 15:44 |
krotscheck | I think it's a questino of conflicting visual messages. | 15:47 |
Zara | yeah, I just looked at the search on the left and there the dropdown lists search results | 15:47 |
Zara | so that might be why | 15:47 |
krotscheck | All the 'what does this do' is in the left icon column, and it's actually trying to tell yo u two different things. | 15:47 |
krotscheck | If it's a magnifying glass, it's trying to tell you: "hey, you're going to search for this" | 15:48 |
krotscheck | If it's a resource icon, it's trying to tell you "This is a thing" | 15:48 |
krotscheck | But not "You're going to navigate to this.=" | 15:48 |
krotscheck | Perhaps the appropriate way to address this is to take the renderer and split it into <type Icon> <Name || label> <action icon> | 15:49 |
Zara | whereas the search icon accessed from the sidebar gives pictures of resources in the dropdown, but when they're clicked on, they lead to a page of search results | 15:49 |
krotscheck | Well, they add that resource to the constraint criteria and refresh the content, but yes ;) | 15:50 |
Zara | heh | 15:50 |
krotscheck | (It's hard for me to nt think of an app as "Pages" too) | 15:50 |
Zara | it's good to correct me! thinking in AngularJS terms is still hard for me. | 15:51 |
*** mrmartin has quit IRC | 15:56 | |
krotscheck | It's promises all the way down. | 16:03 |
Zara | eep :) | 16:31 |
openstackgerrit | Merged openstack-infra/storyboard-webclient: Improve usability of the "New Board" modal https://review.openstack.org/263717 | 16:51 |
SotK | \o/ | 16:51 |
openstackgerrit | Merged openstack-infra/storyboard: Add a subscriber_id parameter to various GET API endpoints https://review.openstack.org/257505 | 16:58 |
openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: Fix Project Group Edit https://review.openstack.org/265935 | 17:12 |
openstackgerrit | Merged openstack-infra/storyboard-webclient: Don't hide paging controls for xs window sizes https://review.openstack.org/263235 | 17:29 |
Zara | hm, cards probably need to display assignees | 17:38 |
SotK | yeah, they do need to | 17:39 |
SotK | I'll add a task for it | 17:40 |
SotK | I don't really know the best way of doing it, as shoving a name on the card too might look messy | 17:41 |
Zara | I guess that's where tiny profile pictures are useful. failing that, maybe small names in the bottom right of the cards? | 17:42 |
Zara | I think someone would want to be able to see them all instantly to get an overview, but maybe a 'show assignees' button that reveals the names on all the cards could work | 17:43 |
Zara | so they can hide them the rest of the time | 17:43 |
*** mrmartin has joined #storyboard | 17:43 | |
* SotK thinks we should use gravatar or libravatar or something :D | 17:43 | |
Zara | :D it could work as a first step for trialling approaches to pictures in storyboard, though you'll murder me for saying that. | 17:44 |
Zara | still, that'd be a plugin which is the approach I'm more comfortable with. | 17:45 |
Zara | oh, it's cross-site, ignore me! | 17:46 |
SotK | yeah, the gravatar (and libravatar) API works by hashing an email address, its neat and easy | 17:46 |
Zara | I just looked them up since I've seen them used but knew nothing about the internals | 17:46 |
Zara | cool | 17:46 |
SotK | (I was having a play with gravatar-in-storyboard around Christmastime, but forgot why I wanted it other than "it's cool", now I remember I wanted to show card assignees) | 17:47 |
Zara | haha | 17:47 |
Zara | yeah, avatars which show the name on a hover sound good to me | 17:48 |
Zara | could use them next to names for creators of stories etc, too | 17:48 |
SotK | I wonder if there is a preference as to which of gravatar or libravatar should be used? | 17:48 |
Zara | any difference in licenses? | 17:49 |
SotK | libravatar is open source so you can host your own, gravatar is just a closed-source web service (and I suspect has more users) so it isn't possible to host your own afaik | 17:51 |
SotK | that is my understanding anyway | 17:51 |
Zara | okay, libravatar is AGPL | 17:52 |
Zara | so I think we shouldn't use it | 17:52 |
SotK | we wouldn't be running or redistributing any of their code, just making use of their web api, so I don't *think* it would cause a problem (though I could be very wrong) | 17:53 |
Zara | ah, if we're just making use of the api then it sounds like we'd be better off using the one with more users anyway? | 17:54 |
Zara | (at first libravatar appealed because I thought it'd give storyboarders the freedom to host their own if they wanted to, but the AGPL makes that harder for businesses.) | 17:54 |
Zara | so sounds like gravatar might work better for our needs for now, though I'm not sure how using a web service like that as part of a project works with openstack rules? | 17:55 |
SotK | I'm not sure either | 17:57 |
* SotK thinks it would be better to use gravatar too, but is open to other's opinions | 17:58 | |
*** mrmartin has quit IRC | 18:23 | |
paulsherwood | libravatar fallsback to gravatar | 18:47 |
*** mrmartin has joined #storyboard | 18:51 | |
paulsherwood | SotK: https://github.com/CodethinkLabs/Hobokan/search?utf8=✓&q=libravatar was all it took to add libravatar/gravatar to our home-grown kanban | 19:23 |
paulsherwood | (so that line calls to libravatar... and libravatar calls to gravatar for us if there is no libravatar for the user's email) | 19:30 |
paulsherwood | (and you don't need to use any of libravatar's code) | 19:30 |
*** mrmartin has quit IRC | 20:20 | |
*** persia has quit IRC | 21:53 | |
*** persia has joined #storyboard | 21:53 | |
*** jtomasek has quit IRC | 21:59 | |
*** davidlenwell has quit IRC | 22:05 | |
-openstackstatus- NOTICE: Gerrit is restarting to resolve java memory issues | 22:06 | |
*** davidlenwell has joined #storyboard | 22:29 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!