| *** cody-somerville has quit IRC | 02:06 | |
| *** notnownikki has joined #storyboard | 09:10 | |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Add 'Remove this story' button to detail page https://review.openstack.org/204587 | 09:28 |
|---|---|---|
| * Zara sees changes in storyboard.openstack.org and smiles | 09:40 | |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Render descriptions and comments as Markdown https://review.openstack.org/222709 | 10:26 |
| *** mrmartin has joined #storyboard | 10:36 | |
| Zara | preliminary investigations suggest that the potentially unnecessary stuff in my patch is indeed unnecessary. so yay, less code! | 11:10 |
| Zara | how's everyone in the wonderful world of storyboard today? | 11:16 |
| Zara | sounds about right. | 11:21 |
| Zara | (nah, it's lunchtime :)) | 11:22 |
| SotK | I can walk properly again, so thats a plus | 11:26 |
| SotK | and I'm nearly ready to send patches adding a web ui for boards and worklists! | 11:26 |
| Zara | :) and :0 respectively! | 11:28 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: Subscriptions WIP https://review.openstack.org/223562 | 12:12 |
| Zara | have removed some variables that were doing nothing... ^^' The if/else is now gone, too, though that means that there are errors along the lines of '$scope.subscriptions is not defined'. they don't make any difference to the UX, but I don't like it. | 12:16 |
| Zara | just looked at: https://storyboard.openstack.org/#!/story/2000075 | 12:45 |
| Zara | I'm not sure if it's an issue or not; I'm guessing it was done that way round in case someone wanted to add a bunch of stories to a project and then sort out the details afterwards. | 12:46 |
| * SotK isn't really sure of the point of the "add story" button on the project page, given its in the top bar anyway | 12:48 | |
| persia | I think it is an issue. | 12:48 |
| persia | Adding a lot of stories with little detail seems like a sensible use case when starting out, or when testing a barebones system. | 12:48 |
| persia | When using a larger system with much populated date, the metadata becomes the important part, and the story title almost unimportant, except as a placeholder. | 12:49 |
| Zara | SotK: the only difference (other than the navigation) is that it autoselects that specific project. | 12:49 |
| persia | Plus, unless one has magic search features, one does need to capture the number/link to be able to find it later (if nothing else, to be able to add it to worklists, etc.) | 12:49 |
| persia | SotK: +1 on avoiding duplicate "Add Story" buttons | 12:51 |
| Zara | I was thinking of the situation where someone says 'there's a project, it involves these steps' and the details get fleshed out at each stage via the edit button. I'm not sure that many people would want to assign in the same step as creating. | 12:52 |
| Zara | I'm wondering if there's some way of tweaking the 'new story' button at the top so it autoselects the current project if you're on the current project screen, because it's irritating to select a project each time | 12:52 |
| Zara | and I can imagine someone wanting to add a batch of stories to a project in one go | 12:52 |
| persia | Depends on one's workflow. Perhaps for a young project. Even so, generally I would expect to brainstorm using another tool, so I already had some tasks, tags, subscriptions, or other metadata I wanted to adjust immediately. | 12:53 |
| Zara | fair enough; I think we want to support multiple workflows so that's definitely relevant. | 12:55 |
| * SotK could feasible imagine some user storing up issues with a project in some tool or method of their own, then throwing them all on the upstream task tracker in one go | 12:55 | |
| SotK | s/feasible/feasibly/ | 12:55 |
| persia | Oh, certainly, but I think the more advanced user would end up using the API directly for that, so we can ignore UI considerations for that sort of thing. | 12:57 |
| Zara | It might be nice to have a button to create multiple placeholders (ie: stories with only a title) in one go, for the situation I described. Have to be careful not to crowd the UI, though, and not worth doing if nobody actually wants it... will probably just keep an eye out for comments related to it, for now. | 13:00 |
| persia | Makes sense. It's the current default, so changes could be unexpected. | 13:02 |
| persia | Although one still has the trick of finding them post-creation: that ought have some sense to it, just to cover the corner cleanly. | 13:04 |
| Zara | ah, I meant something a bit different from the current default, ie: a form where you put in, say, ten titles at once, then submit, instead of clicking 'add story' once per story. (sorry if I misinterpreted that) | 13:05 |
| SotK | perhaps being able to add stories to the list on a project detail page the same way you add tasks to a story on the story detail page? | 13:07 |
| Zara | yes, something like that would be great | 13:08 |
| persia | That would be much more sensible than the current: maybe switch the default, and add a story to add that later, as an extension once the other stuff works? | 13:15 |
| Zara | yeah, I'll add a comment to the story that sparked the discussion in the first place, in case the original writer is interested. :) | 13:16 |
| Zara | https://storyboard.openstack.org/#!/story/2000075 <- if anyone disagrees with that summary, please correct me. :) | 13:25 |
| Zara | hahaha, I have 27 storyboard webclient branches in git. | 13:34 |
| Zara | while looking at other patches, noticed that the paging arrows appear even if the total number of pages is so low that there's not an option to page through. wondering if we could hide them in those circumstances? | 13:57 |
| Zara | atm it's a bit confusing, and it some places it looks bit messy (eg: on the detail page for a project group that doesn't contain many projects/stories | 13:59 |
| Zara | eg: https://storyboard.openstack.org/#!/project_group/56 | 13:59 |
| Zara | so not just the arrows but possibly the option of how many to display, if the total number is under 10 | 14:00 |
| Zara | the 'active merged invalid' thing over on the left is also looking a bit peculiar these days... | 14:03 |
| Zara | and I only just realised that that's a way of choosing which stories to display, so I'm not convinced it works UI-wise. | 14:04 |
| Zara | (I'd thought it was a way of changing the status of stories, and only now when thinking about it has it occured to me that there's only one option for the whole list, so it's just a way of choosing what to display on the screen) | 14:05 |
| SotK | maybe tabs would work better for that (like on the project detail page)? | 14:06 |
| Zara | I guess the main advantage is that it lets you display as many categories as you want simultaneously | 14:15 |
| Zara | otoh it currently looks bad and it's inconsistent. | 14:15 |
| SotK | I'm not 100% sure it even works properly if you select more than one category | 14:16 |
| Zara | it seemed to at a glance, but I didn't check closely | 14:16 |
| SotK | + it doesn't render properly in Firefox | 14:16 |
| Zara | looked a little closer; it does at least seem to work (unless it's lying and saying things are merged etc when they're not) | 14:17 |
| * SotK was probably mistaken then xD | 14:18 | |
| Zara | the rendering might have confused matters since the 'merged' box is next to active and the 'invalid' box is next to merged | 14:18 |
| Zara | but if you assume they go left to right and then top to bottom in the same order as written, they seem to work, haha. | 14:19 |
| openstackgerrit | Monty Taylor proposed openstack-infra/python-storyboardclient: Change ignore-errors to ignore_errors https://review.openstack.org/225716 | 14:23 |
| openstackgerrit | Monty Taylor proposed openstack-infra/storyboard: Change ignore-errors to ignore_errors https://review.openstack.org/225719 | 14:24 |
| Zara | about to look at markdown patch but can come back to it in a bit. also, just remembered-- pdar was going to patch some documentation; did I just forget about those patches or are we still waiting for those? | 14:25 |
| SotK | thanks! | 14:26 |
| SotK | I haven't seen those patches that pdar was working on | 14:26 |
| Zara | :( | 14:28 |
| *** notnownikki has left #storyboard | 14:30 | |
| Zara | also are we okay to just +1 workflow those coverage patches? | 14:31 |
| SotK | They won't break anything, we should probably just merge them | 14:33 |
| Zara | yeah, I was thinking we'd have more broken things if we waited around for reviews on those. | 14:33 |
| Zara | heh, we might end up being responsible for python-storyboardclient... which seems fair enough but I currently know nothing about it. | 14:38 |
| SotK | me neither, I wonder if anyone actually uses it | 14:39 |
| Zara | yeah. I'd like to do minimal maintenance, eg: where there are patches to stop everything breaking, so that someone else can potentially use or maintain it down the line without it being too far behind. | 14:39 |
| Zara | I like the idea of the whole thing being written in python but not sure how practical that actually is for the use-case. | 14:40 |
| Zara | seems like it's squashing a language into a place it's not suited to.... but I could be wrong. | 14:40 |
| * SotK assumes that its a CLI client for the API like the other similarly named projects in OpenStack | 14:41 | |
| Zara | Ahhhh | 14:41 |
| Zara | that would make a lot more sense, haha | 14:41 |
| Zara | in which case that might be something that would have more users if storyboard were more popular. | 14:42 |
| SotK | indeed | 14:42 |
| Zara | gonna +1 workflow ignore_errors, then | 14:44 |
| *** MarkAtwood has joined #storyboard | 14:44 | |
| *** mrmartin has quit IRC | 14:46 | |
| Zara | hm, the python-storyboardclient patch failed to merge | 14:49 |
| Zara | wondering if it's because storyboard updated, or if it's unrelated. | 14:49 |
| Zara | I suppose there could be a backlog of unmerged patches if it's been lost in the wilderness for a while. | 14:49 |
| Zara | ah, good, it hasn't been lost | 14:51 |
| openstackgerrit | Merged openstack-infra/storyboard: Change ignore-errors to ignore_errors https://review.openstack.org/225719 | 14:51 |
| Zara | we just didn't know about it. last updated in March. | 14:51 |
| SotK | logs suggest its due to the oslo rename | 14:52 |
| SotK | (so the tests are failing) | 14:52 |
| Zara | ahh | 14:52 |
| Zara | makes sense. | 14:53 |
| Zara | so we'll need to apply the oslo rename patch and then the ignore_errors one | 14:54 |
| Zara | I'll put a story up before I forget about it. | 14:54 |
| *** cody-somerville has joined #storyboard | 14:54 | |
| SotK | thanks :) | 14:56 |
| Zara | of course, I'll still need to remember that python-storyboardclient exists | 14:57 |
| Zara | https://storyboard.openstack.org/#!/story/2000360 | 14:57 |
| Zara | (in https://storyboard.openstack.org/#!/project/755 ) | 14:58 |
| Zara | hm, had a weird crash when looking at markdown patch (trying to put a table in comments) but it works fine now | 15:26 |
| Zara | not sure what was up | 15:26 |
| Zara | I got a little black 'no entry' sign in the comments box and it was unresponsive. opened same page in a different tab and everything was fine | 15:27 |
| SotK | hmm, weird | 15:28 |
| SotK | can you paste the markdown you were using somewhere? | 15:28 |
| Zara | I tried again with the same thing and it worked so I don't think it was that-- and I couldn't copy paste from the box after it went weird. I think it was this but I can't be sure: | 15:30 |
| Zara | barbarbar | 15:30 |
| Zara | <table> | 15:30 |
| Zara | <tr> | 15:30 |
| Zara | <td> | 15:30 |
| Zara | Foo | 15:30 |
| Zara | Bar | 15:30 |
| Zara | Baz | 15:30 |
| Zara | </td> | 15:30 |
| Zara | </tr> | 15:30 |
| Zara | </table> | 15:30 |
| Zara | moop | 15:30 |
| Zara | was trying out inline html in comments to see if it did anything weird. | 15:30 |
| Zara | and it did, but could be totally unrelated | 15:31 |
| SotK | weird, it works for me too | 15:32 |
| Zara | hm, line wrap also seems to be broken in the comments for long comments on stories, but not sure if that's to with me messing around with tables in previous comments in markdown | 15:34 |
| Zara | ohh, or actually, it might be that linewrap doesn't happen with no spaces | 15:34 |
| Zara | that probably doesn't matter :) | 15:35 |
| Zara | yeah, it's just the spaces | 15:35 |
| Zara | might make sense to display most recent comment first | 15:37 |
| SotK | I think it'd be good to allow the user to choose how to order the comments (ie. oldest-first or newest-first) | 15:38 |
| Zara | yeah | 15:39 |
| SotK | I tend to find oldest first better if there is a discussion, but newest first better if I just want to look at updates or something | 15:39 |
| Zara | yeah, I tend to want newest-first as the default, but if that's unusual then we can leave oldest-first as the default | 15:40 |
| persia | I think oldest-first is the common model for issue trackers. | 15:42 |
| Zara | yeah, github (for example) do it that way round-- but they display far more comments per page by default. So +1 to a higher default number of comments if we keep it as oldest-first. | 15:50 |
| *** mrmartin has joined #storyboard | 15:58 | |
| Zara | hm, (very) small niggle with markdown patch-- I notice old comments were indented slightly and story descriptions include author and date immediately below the title | 16:14 |
| Zara | *included | 16:14 |
| Zara | I think this was because of the carriage return | 16:14 |
| Zara | (though maybe because it was originally a paragraph?) | 16:15 |
| Zara | and I prefer the old look, if it's possible to retain it | 16:15 |
| Zara | I'm not super super fussed, but I think the new way looks a bit more crowded. | 16:16 |
| Zara | oh, it must be the carriage return; it's still a paragraph | 16:17 |
| SotK | You mean as opposed to being in the top right? I moved it up there as I thought it looked weird where it used to be if there was something like a quote or heading at the start of the story | 16:18 |
| Zara | yeah, I think it looks better under the title. I won't lose sleep over it either way, though if it's just aesthetic, might be better to leave it for another patch. | 16:22 |
| Zara | I don't think it would look weird with a quote but if someone can show me it looking weird with a quote, I'll change my mind, haha. | 16:23 |
| Zara | have left some comments, anyway, much the same as here. | 16:42 |
| Zara | 'night, storyboard! until tomorrow! | 17:00 |
| *** cody-somerville has quit IRC | 19:16 | |
| *** mrmartin has quit IRC | 19:20 | |
| *** mrmartin has joined #storyboard | 19:43 | |
| *** cody-somerville has joined #storyboard | 19:58 | |
| *** mrmartin has quit IRC | 20:02 | |
| *** cody-somerville has quit IRC | 20:11 | |
| *** notnownikki has joined #storyboard | 20:24 | |
| *** notnownikki has quit IRC | 20:51 | |
| openstackgerrit | Adam Coldrick proposed openstack-infra/python-storyboardclient: Fix oslo imports https://review.openstack.org/226064 | 21:41 |
| *** MarkAtwood has quit IRC | 22:57 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!