Friday, 2016-01-29

*** yarkot has quit IRC01:32
*** coolsvap|away is now known as coolsvap02:36
*** yarkot has joined #storyboard02:48
*** coolsvap is now known as coolsvap|away03:30
*** coolsvap|away is now known as coolsvap03:49
*** coolsvap is now known as coolsvap|away05:15
*** coolsvap|away is now known as coolsvap06:31
* SotK notices not much of the merged stuff has made it into s.o.o yet :(09:04
pedroalvareznoticed that too09:05
pedroalvarezif you want a sneak peek storyboard.baserock.org :)09:06
persiaHeh.  Not continuous, but sometimes faster :)09:07
*** coolsvap is now known as coolsvap|away09:15
pedroalvarezthere might be a way to find out what happened09:24
pedroalvarezit has happened before IIRC09:24
paulsherwoodwhat am i looking out for at s.b.o, precisely?09:55
paulsherwoodooh, latest at the top :)09:56
Zarahah, me three10:09
Zarasaw it last night, last thing on s.o.o was merged on the 22nd :(10:09
Zaraand yeah, I also think it happened before, a tarball wasn't generated then.10:10
SotKeven the API patches aren't running on there this time afaict10:11
Zaraoh :S10:11
Zarawe need to get the api version up there too...10:12
SotKindeed we do10:13
SotKso many things to do10:13
ZaraSotK: what makes you think the API patches aren't running either?10:14
Zara(also, morning!)10:16
Zara(the subscriptions page is also up now in s.b.o, and the kanban should load faster)10:16
SotKthe lanes aren't "resolved" when I do look at https://storyboard.openstack.org/api/v1/boards/110:17
Zara:(10:18
Zaratimezones mean it'll probably be a few hours before infra can help with this10:19
ZaraI've left a message in the channel10:19
paulsherwoodWould others be interested in the ability to click on the various states of Stories (eg in https://storyboard.baserock.org/#!/dashboard/stories) and get a filtered view of, eg, just 'todo' items (appearing on the same page)? currently clicking there does nothing10:19
Zarapaulsherwood: I can see why it would be useful; so far you're the first person to ask after it, whereas multiple people have asked after other features (eg: due dates on cards), so for now I think we should make those the priority, but put that suggestion on the 'watch for if other people request this' list10:25
SotKcreate a story for it :)10:25
SotKit does indeed sound like a useful feature10:26
Zara(getting storyboard to have some way of representing the 'how much do people desire this feature?' list is something I'm personally keen on, because atm I have to make that list by hand)10:29
pedroalvareztrello has this feature to vote cards10:38
pedroalvarezfor things like this might be cool10:39
* SotK wants a "Me too" button on stories for it or similar10:39
pedroalvarezthat would be actually the same concept :)10:39
persiaI have never understood why this sort of feature is interesting to anyone, so would be curious to hear an explanation of what someone might do as a result of someone else pressing such a button.10:45
pedroalvarezso you find a bug when using a project, find the bug report, and instead of saying "hey, same here", you press that +1 button10:46
paulsherwood+110:46
SotK"I have some free time, I'll look at the bug list and see which are affecting lots of people"10:46
Zarayup, you can see how many people that bug actually affects, it's useful for prioritizing.10:47
persiaWhy do either.  What is anyone going to do as a result of you doing that?10:47
SotKI might use my free time to fix one of the bugs affecting a lot of people10:47
Zaraand I would shift the issue up the todo list if I were managing that project.10:48
persiaZara: most affected users will not use the buttons, so that is not actually useful prioritisation input for developers, even if most developers were not being paid to follow the priorities of their management.10:48
Zarapersia: they will often use them if they're directed to them when they complain in irc.10:49
ZaraI agree they won't use them in the wild10:49
Zaraunless there's a culture of using the buttons, which takes a while to create10:49
persiaOnly a very small subset of users use bugtrackers, and many of those are support folk, such that their ability to replicate is multiplied to get user counts.10:50
persiaZara that culture does not help, because most users never interact with upstream.10:50
persiaSotK: while I agree with the "I have some time..." reason to look for a new bug, my concern is that I do not believe the data can be even representative, let alone accurate, and suspect it is better to have a collaborative worklists maintained by a support team if one wants a list of bugs that impact users.10:53
Zarastoryboard is currently based around the needs of software teams, who tend to use bugtrackers more. and I find some input better than none for these things.10:54
ZaraI don't think this feature contradicts having a worklist10:55
Zarait's one of many inputs used to create that worklist10:55
ZaraI *want* to make worklists for storyboard development, and atm I'm finding it annoying having to collate information about impact in places other than storyboard. I can manually add comments to each story saying who wanted what when, which cannot be used as a filter in the future, or I can direct people to a button and filter results by it later.10:58
pedroalvarez<nibalizer> Mem:          4003       3859        143          0          6         7411:13
pedroalvarez<nibalizer> certainly looks out of memory11:13
pedroalvarezdid you see that?11:13
Zaraah, no, thanks11:13
openstackgerritAdam Coldrick proposed openstack-infra/storyboard-webclient: Fix broken link on task cards in boards  https://review.openstack.org/27401811:22
*** mrmartin has joined #storyboard11:29
Zara^ is pretty crucial for boards. :/11:39
pedroalvarezif we merge that.. and webclient gets updated, it will break because api changes for worklists won't be present..11:40
pedroalvarezjust saying .. :)11:40
pedroalvarezhmm.. I can't reproduce it11:43
Zarawe've found they're pointing to the wrong thing11:44
Zaraso I didn't notice on my test instance because my test stories are often named things like 'fdsfdkjl', which look similar to each other11:44
Zarabut it's noticeable on s.b.o because there are fewer stories than the tasks listed in the kanban11:45
pedroalvarezyeah, patch looks good, but I can't reproduce the expected failure in storyboard.baserock.org11:45
Zaraso you get a 404 instead11:45
Zara?11:45
Zarahm, I get a 404 when clicking on task titles.11:45
Zarahttps://storyboard.baserock.org/#!/board/111:46
pedroalvarezZara: yeah, do you see the tasks in Done?11:46
pedroalvarez3 of them are pointing to story 2711:46
Zarawhah? on my screen it's 96,97.98 and 7111:47
pedroalvarezok... cache..11:47
Zarahahaha11:47
ZaraRESTART THE WORKER11:47
pedroalvarezhahah11:47
pedroalvarezno no, chrome this time..11:47
Zara:P11:47
pedroalvarezthere should be a way to force the cache...11:47
pedroalvarezforce the cache to clean up..11:47
pedroalvarezor something..11:48
Zarayeah, I don't think that patch should introduce any problems11:48
Zarasince afaik your api is up to date11:48
pedroalvarezyeah, I'm just worried about OpenStack's instance11:53
Zarait might be okay, both the UI and API patches have been merged, in the right order...11:55
Zaraif it does cause a problem, then I think the mess will be further back than that patch11:55
Zarait's been about a week since it last updated, afaict. :(11:56
openstackgerritMerged openstack-infra/storyboard-webclient: Fix broken link on task cards in boards  https://review.openstack.org/27401811:57
persiaI do not suggest "me too" conflicts with worklists: I just believe "me too" fails to offer value for any of the uses for which I have ever heard it suggested, with the single exception of the purpose of reducing the number of files issues, although most non-developers easily confuse problems with similar symptoms, such that developers seeking to resolve issues often benefit from the additional entries.12:42
persiaThere is an http header to say "do not cache", but this tends to make things slow and/or annoy people when pressing " Back" requires more round-trips.  Be careful if using Pragma: no-cache12:47
pedroalvarezyes, found that, and I don't want to slow things down12:49
*** mrmartin has quit IRC13:12
*** jtomasek_ has joined #storyboard13:34
*** jtomasek has quit IRC13:34
*** jtomasek_ has quit IRC14:21
*** krotscheck has quit IRC15:10
*** krotscheck has joined #storyboard15:21
*** alexismonville has joined #storyboard16:09
*** alexismonville has quit IRC16:32
* SotK creates https://storyboard.openstack.org/#!/story/2000476 with his current thoughts on deadlines/targets for cards in kanbans17:19
* persia gets to the second bullet point before having semantic disagreement, and decides to re-read and draft a comment tomorrow.17:24
SotK:) thanks!17:26
persiaThe short version being that "hard" delivery is an expression of desire by a single person (although others may agtmree).17:26
persiaNo, thanks for writing up the thoughts in detail before implementing: I find it easier to think a this level than attempting to generalise from several reviews in the same topic.17:27
* SotK decides it will be easier to reply to a storyboard comment than try to explain the reasoning in IRC and will wait for the long version17:31
persiaGood idea :)17:34
pedroalvarezhttps://review.openstack.org/27417717:47
Zara'night, storyboard. worker mystery to be untangled on Monday, I'm off to eat tea and pretend to be an adult whose tea != haribo.18:10
* SotK reads about the worker mystery19:00
*** krotscheck has quit IRC19:17
*** mrmartin has joined #storyboard20:12
*** mrmartin has quit IRC21:50
*** mrmartin has joined #storyboard21:53
*** mrmartin has quit IRC21:58

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!