| *** jtomasek has joined #storyboard | 06:37 | |
| *** matthewbodkin has joined #storyboard | 07:46 | |
| *** dmsimard has quit IRC | 08:05 | |
| *** jtomasek has quit IRC | 08:13 | |
| *** jtomasek has joined #storyboard | 08:13 | |
| *** dmsimard has joined #storyboard | 08:54 | |
| * SotK wonders how he missed that empty config causes defaults to be ignored, given all the talk about how config works on Thursday... | 09:01 | |
| Zara | heh | 09:33 |
|---|---|---|
| *** faybrocklebank has quit IRC | 09:35 | |
| *** faybrocklebank has joined #storyboard | 09:35 | |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Always fall back to default config values https://review.openstack.org/343536 | 09:41 |
| Zara | :) | 09:41 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Always fall back to default config values https://review.openstack.org/343536 | 09:47 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Allow comments to be edited by their owner https://review.openstack.org/343539 | 09:47 |
| *** markus_z has joined #storyboard | 09:50 | |
| Zara | oh, hi again markus_z! :) | 10:10 |
| Zara | I liked your test stories :) | 10:10 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Allow comments to be edited by their owner https://review.openstack.org/343539 | 10:23 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Always fall back to default config values https://review.openstack.org/343536 | 10:23 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Allow timeline events to be related to worklists and boards https://review.openstack.org/342263 | 10:30 |
| Zara | argh so many patches | 10:34 |
| markus_z | Zara: Unfiltered brain dump stories :) | 10:44 |
| markus_z | anteaya: My notes about storyboard are at the bottom of https://etherpad.openstack.org/p/nova-bugs-team | 10:45 |
| markus_z | Long story short, SB is not yet fully there but very very close. | 10:46 |
| markus_z | Everything I said there is from my personal perspective of working with Nova bugs | 10:47 |
| Zara | Okay, taking a look now. :) Assuming tag-completion is a thing, would tags work for e003 and e004 | 10:49 |
| markus_z | I haven't excessively used the API, but the docs look like everything's in place | 10:49 |
| Zara | ? | 10:49 |
| markus_z | As a workaround, yes. | 10:49 |
| Zara | okay, yeah I'm thinking of stuff that would work in the short term since if we wait 'til it's perfect, I worry we'll end up lingering forever-- but it needs to be usable! | 10:51 |
| markus_z | True. The limiting factor in Nova is the amount of people who do the triage and want to keep an overview. If SB does the job slightly harder, the amount of bug reports per day will squash us | 10:52 |
| Zara | yeah, understood. fwiw, I'm happy to help with triaging things in storyboard, since I do that a bit anyway... though I might not know what I'm getting into... :) | 10:54 |
| Zara | but yeah, I can probably help with 'expired' or 'not enough info' things, at least. | 10:55 |
| Zara | ( btw I'm marking things as 'tags should work' for my own reference, since the other things are more immediate blockers) I'm not sure what e009 is saying | 10:58 |
| Zara | so I'll mention that it's possible to generate a worklist automatically from a tag, so that anything tagged 'RFE' would end up on that list. I'm not sure if that's helpful for that point. | 11:00 |
| Zara | what functionality does launchpad have that ensures e010? | 11:01 |
| markus_z | E009 = we (Nova) have separate teams for RFEs and bug reports. Nowadays, when people open a ticket in LP, they don't mark it specifically as bug or RFE. The very few people who do the bug triage need to decide if its a bug report or RFE. | 11:02 |
| markus_z | E010 = "mark as duplicate" :) It's on the right hand side, for example https://bugs.launchpad.net/nova/+bug/1460630 | 11:02 |
| openstack | Launchpad bug 1175464 in OpenStack Compute (nova) "duplicate for #1460630 should not add default security group to quantum unless api-request had it" [High,In progress] - Assigned to sahid (sahid-ferdjaoui) | 11:02 |
| markus_z | E009) I'm not sure if I could explain that good enough. I want the story creator to make a decision if the story is a bug or a RFE to keep the list for the bug triage folks smaller. | 11:04 |
| markus_z | Otherwise is will be too big to handle | 11:04 |
| markus_z | "it" == the list of actual bug reports | 11:04 |
| Zara | (ahh, right, so it automatically searches for another bug and requires its ID as the input, I see.) | 11:05 |
| markus_z | yes | 11:05 |
| markus_z | E010) LP: If the user cannot provide an ID to the other bug, it is not possible to mark it as duplicate. | 11:06 |
| *** AJaeger has joined #storyboard | 11:07 | |
| AJaeger | storyboard team, could you review and merge https://review.openstack.org/#/c/335826/ and https://review.openstack.org/#/c/335824/ to update the list of binary package requirements that storyboard has, please? Adam gave already a +2, so needs another +2A, please | 11:07 |
| Zara | Oh, sorry! for some reason I thought that had gone through... | 11:09 |
| Zara | AJaeger: thanks for chasing that up | 11:09 |
| AJaeger | thanks, Zara ! | 11:12 |
| Zara | markus_z: how far can fixes on the social side help with these things? ie: establishing that if someone doesn't label a bug correctly, nova will not look until it's labelled? I worry we could end up trying to fix things that are human problems, but I also don't have data to know if templates, etc help (or if people just fill them with nonsense). | 11:14 |
| * SotK leaves a couple of comments in the nitpicks section | 11:14 | |
| SotK | are templates per-project, or a global thing? | 11:15 |
| Zara | (I guess I'm wondering how far the tool can help if the community doesn't want to make an effort to make things easier for the triage team) | 11:15 |
| Zara | at any rate, it'd be easy to include that template in the project description for 'nova', as a first step. | 11:16 |
| openstackgerrit | Merged openstack-infra/storyboard: Update other-requirements.txt https://review.openstack.org/335826 | 11:17 |
| markus_z | Zara: I think you're asking where to spent your resources? My observation is, if the tool can be used in a "wrong" way, it will happen. I cannot fix people. | 11:19 |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Update other-requirements.txt https://review.openstack.org/335824 | 11:21 |
| Zara | markus_z: yeah, I guess I'm wondering if you should spend effort chasing it up when people misuse it, or say 'if you don't pay attention to our needs, we won't pay attention to your rfe', and then they can choose whether or not to take the steps to get the team to read it. but I don't know whether that's actually feasible on a project the size of Nova. | 11:22 |
| markus_z | the short answer is, we don't have the resources/people to chase it up. Too much new bug reports per day. | 11:23 |
| markus_z | Some bug reports will already be ignored, not because we're bad people but because we don't have the bandwidth. | 11:24 |
| markus_z | I closed ~180 reports some weeks ago. That's something I want to avoid in the future. | 11:25 |
| markus_z | http://lists.openstack.org/pipermail/openstack-dev/2016-July/098792.html | 11:26 |
| Zara | yeah, I bet that was great fun... :) but I'm sure people appreciate it! what happens if you move to storyboard and have to ignore more bug reports? (maybe that's a silly question; I'm trying to get items on the list into an order of priority from 'my job is absolutely impossible' to 'this is worse than it was, but I can live with it for a month') | 11:28 |
| Zara | since I'm expecting a list of comparable length from several projects. | 11:28 |
| *** AJaeger has left #storyboard | 11:30 | |
| * Zara wonders about feasibility of a python script 'if story in nova and story has no tags and story older than a week, post comment 'the nova team has not looked at this as it is missing vital info; please tag with the following...', then run weekly. | 11:32 | |
| Zara | SotK: could you take a look at anteaya's Users API Docs? https://review.openstack.org/#/c/338570/ I think it's okay to merge like that | 11:34 |
| markus_z | The tagging needs expertise and it is a weekly rotating job to look for untagged bug reports. | 11:34 |
| Zara | ah, I mean in places where the team might use tags in order to classify a story when first submitting it. I'm thinking for e009. | 11:36 |
| Zara | s/team/person writing the story | 11:36 |
| * Zara has not woken up properly yet, evidently... | 11:36 | |
| Zara | eg: instead of using a backlog spec, encouraging the user to tag the story 'rfe' | 11:37 |
| Zara | then if there's a story in the nova project without a 'bug' tag or 'rfe' tag, having a script pick up on that? | 11:37 |
| Zara | I'm trying to think of things that won't affect the structure of storyboard too much if other projects have different needs | 11:38 |
| markus_z | I see where you're coming from. I would wait for their feedback. I doubt that it will be hugely different. | 11:39 |
| markus_z | The API doc shows field "is_bug" and "story_type_id", that gave me hope that E009 doesn't change a lot. | 11:40 |
| Zara | ah yeah, it's in there, we've just never used it (I personally use tags). there's also support for branches and milestones in the api | 11:41 |
| markus_z | I mean this: http://docs.openstack.org/infra/storyboard/webapi/v1.html#Story | 11:41 |
| Zara | I'm just not sure quite what it looks like in practice so I've left off making a lot of noise about that | 11:41 |
| markus_z | Does it make sense to talk with the other projects too and then have a meeting to decide about *real* blockers? | 11:42 |
| * SotK thinks that seems like a sensible plan | 11:43 | |
| markus_z | Personally, I like SB more than LP. But discussing other people's workflows is a mine field :) https://xkcd.com/1172/ | 11:44 |
| Zara | yyup :) | 11:44 |
| Zara | I'd like to focus on the absolutely critical blockers so we can get things moving; my trouble is knowing who decides what those are | 11:46 |
| persia | The is_bug field is an artefact of a historical disagreement about whether anyone could define the difference between a bug and a feature. | 11:46 |
| persia | Some people thought it could be done, and started the work, and other people argued it couldn't be done, so the work was dropped. | 11:47 |
| * persia doesn't know of any plans to do anything with that, but may be mistaken | 11:47 | |
| Zara | markus_z: and then my other trouble is trying to get people to avoid giving us wishlists, so I very much appreciate you separating out the essential things from the rest. :) | 11:47 |
| markus_z | persia: Yeah, sometimes it's a case-by-case decision if it's a bug or not. But more often than not it is clear. | 11:49 |
| persia | heh, yeah, well. I am actively not taking a position on that debate today :) | 11:50 |
| markus_z | Zara: Especially E001 + E002 + E011 worry me. The rest can be mitigated for a short time. | 11:50 |
| markus_z | persia: funny thing is, Nova has different deadlines for bugs and for features. Sometimes (very seldom) people try to sneak in a feature disguised as bug... | 11:51 |
| markus_z | E004 is essential too. 1/3 of new bug reports fall into that category | 11:52 |
| markus_z | It's very unlikely that other projects don't want that | 11:53 |
| persia | Oh, my. That model means that there has to be a definition, which complicates things. I wonder how many of those "sneaky" folk are doing so intentionally vs. accidentally. | 11:53 |
| Zara | markus_z: Okay, fantastic. could you make a note of those 'absolutely must d before migrations' on the etherpad so I have it for reference? | 11:53 |
| markus_z | Zara: yep, will do | 11:53 |
| Zara | thank you! :D | 11:54 |
| markus_z | persia: I doesn't happen *that* often. | 11:57 |
| persia | :) | 11:57 |
| markus_z | Zara: I added a "summary" below the "essential missings" | 11:57 |
| Zara | markus_z: thank you! :) now I'm having fun reading the 'awesome' section; thanks for including that! :D | 11:58 |
| markus_z | Question Q003 is a thing were I hoped there is a clear transition path. I won't be the only one asking this. | 11:58 |
| Zara | I don't have the answer to that just yet. the spec for migration has 'get blockers' as a first step, then 'assign someone to the *actual* migration' after that | 11:59 |
| Zara | so I assume things will be discussed at that point | 11:59 |
| Zara | for gerrit, we're using story: <number> and task: <number> so it shouldn't conflict with lp | 12:00 |
| markus_z | It's not trivial to solve, I guess. If that's well explained in a ML post or wiki, that will mitigate a lot of acceptance issues (I guess). | 12:01 |
| * markus_z guesses a lot | 12:02 | |
| Zara | hehe, so do I! :) I'm trying to find the place where it was discussed, but not having luck immediately, so my guess is it's in the infra meeting logs someplace... | 12:04 |
| markus_z | I have to focus on Nova now, just ping me in #openstack-nova when questions arise. | 12:05 |
| Zara | that's fine, and thanks again! :) | 12:07 |
| *** markus_z has left #storyboard | 12:07 | |
| *** alexismonville has joined #storyboard | 12:15 | |
| * Zara goes back to looking at the typeahead | 12:32 | |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: WIP search for boards and worklists https://review.openstack.org/341562 | 12:42 |
| Zara | I've pushed the wip in case anyone can see what's missing | 12:43 |
| Zara | hopefully there are no weird test changes leftover | 12:43 |
| Zara | if anyone feels like taking a look to help out | 12:44 |
| openstackgerrit | Merged openstack-infra/storyboard: Add example commands for the Users api https://review.openstack.org/338570 | 13:07 |
| Zara | \o/ | 13:07 |
| *** faybrocklebank has quit IRC | 13:15 | |
| Zara | does anyone have a moment to take a look at https://review.openstack.org/#/c/342164/ ? it's a fix for a little annoying niggle that will burn you if you use storyboard a lot | 13:15 |
| Zara | you can test it by typing numbers into the header search | 13:16 |
| *** dmsimard has quit IRC | 13:16 | |
| *** fay has joined #storyboard | 13:17 | |
| * pedroalvarez takes a look | 13:18 | |
| *** fay is now known as Guest52301 | 13:18 | |
| pedroalvarez | seems to work fine | 13:20 |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Always fall back to default config values https://review.openstack.org/343536 | 13:21 |
| Zara | yay | 13:22 |
| *** Guest52301 is now known as faybrocklebank | 13:22 | |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Make the notifications block fixed on large and medium screens https://review.openstack.org/342164 | 13:30 |
| *** faybrocklebank has left #storyboard | 13:31 | |
| *** alexismonville has quit IRC | 13:53 | |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Filter non-public fields when getting a list of users in a Team https://review.openstack.org/343647 | 14:03 |
| * Zara pores over it for next time... | 14:04 | |
| *** faybrocklebank has joined #storyboard | 14:18 | |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Filter non-public fields when returning users in a Team https://review.openstack.org/343647 | 14:35 |
| pedroalvarez | reviewed :) | 14:44 |
| SotK | thanks! | 14:44 |
| Zara | hm, my config keeps being set to 'enableEditableComments:true' when I remove it. | 14:46 |
| SotK | hmm, very weird | 14:50 |
| SotK | definitely removing the one in `dist/`? | 14:50 |
| Zara | yeah | 14:53 |
| * Zara tries again | 14:53 | |
| Zara | aaand it's back | 14:58 |
| Zara | it seems like it just remembers whatever I set it to last | 14:58 |
| SotK | o.O | 14:58 |
| *** alexismonville has joined #storyboard | 14:58 | |
| SotK | what do you see in the network inspector as the result of the GET for config.json? | 14:59 |
| Zara | Attempting to load parameters from ./config.json libs.js:11607:18 | 15:00 |
| Zara | Configuration: enableEditableComments -> true | 15:00 |
| * Zara deletes it again, since I restarted the webclient between changing it that time | 15:00 | |
| Zara | okay, removing it gives: GET | 15:01 |
| Zara | XHR | 15:01 |
| Zara | http://172.16.20.111:9000/config.json [HTTP/1.1 404 Not Found 3ms] | 15:01 |
| Zara | GET | 15:01 |
| Zara | http://172.16.20.111:35729/livereload [HTTP/1.1 101 Switching Protocols 2ms] | 15:01 |
| Zara | Cannot load ./config.json, using defaults. libs.js:11607:18 | 15:01 |
| Zara | Configuration: enableEditableComments -> false | 15:01 |
| Zara | which seems sensible. | 15:01 |
| Zara | but then if I start the webclient again, it'll default to true | 15:01 |
| SotK | whaaaaaaat | 15:03 |
| Zara | the draft build doesn't seem to do that | 15:03 |
| Zara | https://www.youtube.com/watch?v=YQpLNCRIxWA | 15:04 |
| Zara | yeah, it seems to think 'true' is the default | 15:09 |
| SotK | but it set it to false when there was no config file, it makes no sense | 15:10 |
| Zara | yup. when I delete the config, the webclient says 'false'. when I autogenerate new config by restarting the webclient, it sets that to 'true'. | 15:12 |
| *** alexismonville has quit IRC | 15:12 | |
| SotK | why does your webclient generate new config? o.O | 15:15 |
| Zara | when I delete config.json and run the webclient, it makes a config.json | 15:15 |
| Zara | so I was deleting it before while keeping the webclient running | 15:16 |
| SotK | hmm, it shouldn't do | 15:16 |
| Zara | hahaha | 15:16 |
| persia | When you write "run the webclient", do you mean "load the javascript into the browser", or something with grunt? | 15:17 |
| Zara | ah, the latter; would it help if I pasted my command and output? | 15:22 |
| Zara | http://paste.openstack.org/show/536134/ is what I do, anyway | 15:23 |
| SotK | do you still have a config.json in src/ by any chance? | 15:24 |
| Zara | aha | 15:25 |
| * Zara tries renaming it and deleting the dist/ one again | 15:26 | |
| Zara | there we go, it's not making it now | 15:26 |
| persia | So, when running the grunt command, that actually rebuilds the webclient (as well as launching a browser), which has lots of effects. | 15:26 |
| SotK | the weirdest thing about that is that wasn't that not working when you wanted it to last week? xD | 15:27 |
| Zara | yup, it totally wasn't working! | 15:27 |
| SotK | \o/ | 15:27 |
| Zara | that is how I *wanted* it to work | 15:27 |
| Zara | maybe it needed a config.json put into dist/ once before it could find it in src/ in the future | 15:27 |
| Zara | that's annoying, it's meant that's taken far longer to test than it needed to. | 15:29 |
| Zara | but yeah, now double-checked and moving the config.json back into src makes it build again in dist/ | 15:30 |
| * SotK wonders why on earth that wasn't working last week | 15:30 | |
| Zara | :< | 15:31 |
| Zara | well, I've tested as much as I can. it's probably ready for merge. I'm nervous. | 15:31 |
| Zara | the js-draft seems fine | 15:32 |
| Zara | ARE WE READY? | 15:33 |
| * pedroalvarez nods | 15:33 | |
| Zara | okay, have +A'd | 15:34 |
| Zara | I can be around again this evening if necessary | 15:35 |
| * SotK too | 15:35 | |
| Zara | \o/ | 15:35 |
| Zara | testing teams patch now | 15:43 |
| Zara | well, after I get water | 15:43 |
| Zara | btw, I think we're safe as far as the httpproxy danger just mentioned in #infra goes, but would appreciate it if anyone who better knows how to check can check (I just learned about it from that page and did a `grep -r CGIHandler` which didn't bring anything up) | 15:47 |
| Zara | hm, would help if I spelled it right | 15:48 |
| Zara | https://httpoxy.org/ | 15:48 |
| Zara | so not httpproxy, I just imagined that. | 15:48 |
| SotK | I believe we are safe from it, we use wsgi rather than cgi | 15:50 |
| Zara | cool, that matches my understanding, I just didn't want to only trust my understanding xD | 15:51 |
| *** matthewbodkin has quit IRC | 16:00 | |
| Zara | teams patch seems fine to me, thanks! :D | 16:02 |
| Zara | sorry it took me a while | 16:02 |
| *** alexismonville has joined #storyboard | 16:25 | |
| pedroalvarez | oh, I see that the edit-comments patch has been merged | 16:47 |
| pedroalvarez | I want to put that in my production :) | 16:47 |
| Zara | \o/ | 16:47 |
| Zara | I'm watching it nervously xD | 16:47 |
| pedroalvarez | i will do that this evening, no time now | 16:48 |
| pedroalvarez | see ya! | 16:48 |
| Zara | np, 'night! | 16:48 |
| *** wendar_ has joined #storyboard | 17:05 | |
| *** zigo has quit IRC | 17:06 | |
| *** jmccrory has quit IRC | 17:06 | |
| *** wendar has quit IRC | 17:06 | |
| *** zigo has joined #storyboard | 17:06 | |
| *** jmccrory has joined #storyboard | 17:10 | |
| *** alexismonville has quit IRC | 17:19 | |
| *** wendar_ is now known as wendar | 18:14 | |
| Zara | 3 most recent patches haven't merged yet. I'll check back periodically in case anything weird happens | 18:38 |
| Zara | s/merged/built. anyway, have built, and all seems fine. This was your pointless announcement of the evening! | 20:14 |
| Zara | I hope you found it very informative and enjoyable. | 20:15 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!