| *** openstack has joined #storyboard | 00:03 | |
| *** jamesmcarthur has quit IRC | 00:09 | |
| *** jamesmcarthur has joined #storyboard | 00:20 | |
| *** openstackstatus has quit IRC | 00:46 | |
| *** openstack has joined #storyboard | 00:55 | |
| *** sparkycollier has quit IRC | 00:56 | |
| *** sparkycollier has joined #storyboard | 00:57 | |
| *** anteaya has quit IRC | 00:59 | |
| *** openstackgerrit has quit IRC | 01:49 | |
| *** jamesmcarthur has quit IRC | 01:50 | |
| *** openstackgerrit has joined #storyboard | 01:57 | |
| *** jamesmcarthur has joined #storyboard | 02:02 | |
| *** openstack has joined #storyboard | 02:39 | |
| *** openstackstatus has joined #storyboard | 02:40 | |
| *** ChanServ sets mode: +v openstackstatus | 02:40 | |
| *** jamesmcarthur has quit IRC | 03:28 | |
| *** jamesmcarthur has joined #storyboard | 03:32 | |
| *** persia_ has quit IRC | 03:44 | |
| *** thrace has quit IRC | 03:44 | |
| *** thrace has joined #storyboard | 03:47 | |
| *** jamesmcarthur has quit IRC | 03:54 | |
| *** jamesmcarthur has joined #storyboard | 03:58 | |
| *** persia_ has joined #storyboard | 04:01 | |
| *** jamesmcarthur has quit IRC | 04:03 | |
| *** jamesmcarthur has joined #storyboard | 04:13 | |
| *** jamesmcarthur has quit IRC | 04:23 | |
| *** jamesmcarthur has joined #storyboard | 04:26 | |
| *** jamesmcarthur has quit IRC | 04:33 | |
| *** jamesmcarthur has joined #storyboard | 04:39 | |
| *** jamesmcarthur has quit IRC | 04:48 | |
| *** jamesmcarthur has joined #storyboard | 04:52 | |
| *** jamesmcarthur has quit IRC | 05:03 | |
| *** jamesmcarthur has joined #storyboard | 05:06 | |
| *** jamesmcarthur has quit IRC | 05:13 | |
| *** jamesmcarthur has joined #storyboard | 05:21 | |
| *** jamesmcarthur has quit IRC | 05:22 | |
| *** jamesmcarthur has joined #storyboard | 06:22 | |
| *** jamesmcarthur has quit IRC | 06:27 | |
| *** openstack has joined #storyboard | 06:55 | |
| *** fay_ has joined #storyboard | 07:35 | |
| *** bethwhite has joined #storyboard | 08:40 | |
| *** jtomasek_ has joined #storyboard | 09:00 | |
| *** jtomasek_ has quit IRC | 09:02 | |
| *** jtomasek_ has joined #storyboard | 09:02 | |
| *** jtomasek_ has quit IRC | 09:08 | |
| Zara | morning, storyboard! | 10:16 |
|---|---|---|
| SotK | morning! | 10:16 |
| *** jamesmcarthur has joined #storyboard | 11:28 | |
| *** wendar has quit IRC | 11:31 | |
| *** wendar has joined #storyboard | 11:31 | |
| *** jamesmcarthur has quit IRC | 11:32 | |
| *** anteaya has joined #storyboard | 12:09 | |
| anteaya | morning storyboard | 12:10 |
| openstackgerrit | Merged openstack-infra/storyboard: Avoid false positives when filtering projects by subscriber https://review.openstack.org/307756 | 12:11 |
| anteaya | I added a task to https://storyboard.openstack.org/#!/story/2000610 | 12:11 |
| anteaya | which came out of a discussion I was having with dhellmann which started here: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-05-25.log.html#t2016-05-25T19:23:21 | 12:12 |
| anteaya | now he had two points yet I've only put down one story | 12:12 |
| anteaya | I was hoping to talk to you about the second item, how to display, I was hoping automated lists might do the trick here | 12:13 |
| anteaya | however the -dev instance has no stories on it | 12:13 |
| anteaya | so as a side thing, how to populate the -dev instance with some db entries | 12:13 |
| anteaya | we have all the projects and project groups which is great | 12:13 |
| anteaya | and I'm fine to just create some dummy data through the gui | 12:14 |
| anteaya | however I would feel frustrated if I had to do so many times | 12:14 |
| anteaya | so wanted to get your thoughts on how to populate the -dev instance with stories and tasks | 12:14 |
| persia | I thought the plan was to copy non-private stuff from production once a week or so, deleting anything only in -dev, but I do not remember backscroll of anyone starting on that. | 12:17 |
| anteaya | okay well I think that much work wouldn't be necessary | 12:22 |
| anteaya | one round of population per new db would be enough to suit me | 12:23 |
| Zara | yeah, the logs for that discussion are here: http://eavesdrop.openstack.org/irclogs/%23storyboard/%23storyboard.2016-05-19.log.html#t2016-05-19T14:08:26 | 12:25 |
| anteaya | I'm not interested in the db changing on a weekly basis | 12:27 |
| anteaya | it might take me one day in one week to set up a demo and 3 weeks to track down the person I want to demo it to | 12:27 |
| persia | The thought was that real production data was more likely to expose issues that would discourage merge, making it more interesting in the doc-draft use case. | 12:28 |
| anteaya | I don't understand the doc-draft use case | 12:28 |
| anteaya | I would like the db on -dev to be stable | 12:28 |
| anteaya | I don't care if it is real stories or a'dkljd;kl ;lkadjlakdfj as long as it is there when I need it to be in the form I need it to be | 12:29 |
| persia | Every candidate posted to gerrit generates a JS client that points at -dev, so folk can try new features before they land. | 12:29 |
| anteaya | Zara: so it appears the next step is for you and SotK to get db access? | 12:29 |
| anteaya | Zara: have you tried to see if you have db access now? | 12:30 |
| persia | This helps review because one does not need to merge into a local instance to see the effect of a change. | 12:30 |
| anteaya | persia: okay that is fine | 12:30 |
| anteaya | persia: the db doesn't have to change in that scenario the way I see it | 12:30 |
| persia | Delaying the weekly thing to support pre-migration demos seems sane to be tactically, but I still like the idea of automated wipe and populate for the long term. | 12:31 |
| persia | Err. Sane to me. | 12:31 |
| anteaya | that is fine, but as I stated before having a demo set up on the -dev server that disappears on me does not suit my needs for the dev server | 12:33 |
| anteaya | anyway if we can move on to how to populate the -dev db with anything | 12:34 |
| persia | One of the scenarios that happened in the past was awkward production data causing issues, for which troubleshooting was possible in gerrit because docs-draft pointed at production. With the migration to -dev (necessary for security reasons), this cannot be done currently. Fixing that operational issue us the main reason I want uodates, but not having them now does not worry me. | 12:34 |
| anteaya | great, sounds like we have a place of overlap we can label as agreement | 12:35 |
| anteaya | and a starting point | 12:35 |
| persia | Yep. | 12:38 |
| anteaya | great thank you | 12:38 |
| anteaya | I appreciate the history | 12:38 |
| Zara | (I'm coding for a change so not very responsive rn) | 12:39 |
| anteaya | Zara: I understand | 12:40 |
| anteaya | I haven't had breakfast yet but thought I would share my backlog of thoughts from yesterday before you left for the day | 12:41 |
| *** jamesmcarthur has joined #storyboard | 13:02 | |
| *** jamesmcarthur has quit IRC | 13:18 | |
| *** jamesmcarthur has joined #storyboard | 13:24 | |
| *** jamesmcarthur has quit IRC | 13:33 | |
| *** jamesmcarthur has joined #storyboard | 13:39 | |
| Zara | huh, weird, storyboard.tasks.update(id=42) will work, but storyboard.tasks.update(id=function_returning_42()) won't. is it a python syntax thing I'm not aware of? am I missing something obvious? | 13:39 |
| anteaya | Zara: I don't know | 13:40 |
| anteaya | Zara: dhellmann is a fabulous python person | 13:40 |
| anteaya | I recommend you introduce yourself | 13:40 |
| dmsimard | Zara: types could be relevant, maybe you're expecting an integer, or a string, it's important that the function returns a literal 42, not "42", for example | 13:43 |
| Zara | ah, I realised what it was, it was actually that I wasn't returning what I thought I was returning (I had the 'return' statement at the wrong level of indentation.. so yeahh... :/) | 13:43 |
| anteaya | ah glad you found it | 13:46 |
| anteaya | dmsimard: oh good, you know python! | 13:46 |
| dmsimard | yeah, I write a lot of python stuff and working with openstack requires some level of python as well :) | 13:47 |
| dmsimard | I'm not a professional python developer by any stretch, though | 13:47 |
| dmsimard | I couldn't write proper unit tests from scratch to save my life | 13:47 |
| anteaya | that it does | 13:50 |
| anteaya | me either | 13:50 |
| anteaya | but I can follow the pattern of what exists | 13:50 |
| anteaya | glad to have your help here | 13:50 |
| Zara | yay, the regexp code I shamelessly poached from jeepyb works | 13:53 |
| anteaya | yay | 13:53 |
| anteaya | shameless poaching is the road to success | 13:53 |
| dmsimard | except when you're Google poking at Java code :) | 13:54 |
| anteaya | you have experience with google and java? | 13:54 |
| Zara | phew, I may have also shamelessly poached a bunch of mtreinish's control flow. | 13:56 |
| anteaya | oh good call | 13:59 |
| anteaya | shamelessly poaching mtreinish's things is a good idea | 14:00 |
| dmsimard | anteaya: no, but there's lawsuits about Google taking bits of code from Java and Oracle stuff | 14:04 |
| *** jamesmcarthur has quit IRC | 14:04 | |
| anteaya | dmsimard: ah I see, I often fail to follow the news | 14:05 |
| dmsimard | It's for Android, there's been an ongoing case for years :) | 14:05 |
| Zara | okay, so my script shooooould now update a task requested with the status and commit message as a task note (haven't tested status properly yet, going to check now) | 14:10 |
| Zara | yup, that works | 14:12 |
| *** jamesmcarthur has joined #storyboard | 14:12 | |
| Zara | it currently just replaces the task notes rather than appending anything to them | 14:13 |
| Zara | have not looked at owner at all, think that's a bigger task | 14:13 |
| Zara | I should push what I have so far, anyhoo | 14:14 |
| anteaya | dmsimard: well shows you how much I know | 14:18 |
| anteaya | Zara: yay progress | 14:18 |
| Zara | there. so atm I don't yet know how to handle the various errors, so as a goofy workaround it just updates task 42 by default whenever the commit message doesn't match the regexp. | 14:27 |
| Zara | so that's one to change :D | 14:27 |
| pedroalvarez | that's easy to fix, but I guess now that workaround is helping you given that commit msgs won't have task ids :) | 14:33 |
| Zara | yeah. I think it's just me not knowing stuff rather than it being hard; the workaround was the first thing I thought of xD. so, it needs error-handling, appends rather than replacements-- and then getting the auth token is the thing remaining (I think we should leave updating the owner of a task to later, since it's more complex, and in the meantime this would be better than nothing). the rest is mainly t | 14:33 |
| Zara | idying it at this stage. | 14:34 |
| * pedroalvarez nods | 14:35 | |
| Zara | I seem do that quite a bit... (things like 'if x doesn't have the expected value, give it some other expected value' rather than 'if x doesn't have the expected value, don't do what you were planning to do', since there's a gap in my knowledge there) | 14:35 |
| Zara | but I'd rather learn how to do it right | 14:35 |
| pedroalvarez | you can return 'None' as well :) | 14:35 |
| pedroalvarez | (without quotes) | 14:36 |
| Zara | well, I'm passing the task id and figured it'd get confused if it was told to update a nonexistent task | 14:36 |
| pedroalvarez | you can then do: `if identity: \n storyboard.tasks.update(...)` | 14:38 |
| Zara | (haha I failed to concatenate my strings properly when tidying it) | 14:41 |
| Zara | heh, that has also reminded me to update that dorky variable name | 14:43 |
| * Zara changes 'identity' to 'taskID' | 14:44 | |
| krotscheck | Hrm. StoryBoard is still eating comments? | 14:44 |
| Zara | it may be putting them on the next page? | 14:44 |
| krotscheck | Wait, no. It's hidden behind paging | 14:44 |
| Zara | I think this is storyboard's new chief bug | 14:45 |
| Zara | I think at this point it has burned everyone who has ever used storyboard. | 14:45 |
| * persia set comment display preferences to "100" to avoid that, and hopes that "unlimited" becomes available before "100" is too small | 14:45 | |
| krotscheck | King/queen of the... south? | 14:45 |
| persia | witch of the east? | 14:46 |
| pedroalvarez | I remember an idea of auto loading comments dynamically | 14:47 |
| pedroalvarez | when scrolling down | 14:47 |
| * SotK had such ideas | 14:47 | |
| persia | That could work, although there needs to be some feedback that this is happening: that behaviour is exceedingly annoying without feedback on high-latency networks. | 14:47 |
| pedroalvarez | but... I think this will only be useful if the newest event is the first one | 14:48 |
| *** jamesmcarthur has quit IRC | 14:48 | |
| krotscheck | pedroalvarez: continuous-load has a really bad rep in the UX community. | 14:49 |
| * krotscheck doesn't really know why, so it could just be someone being opinionated | 14:49 | |
| pedroalvarez | that's why I'm not part of it :) | 14:50 |
| krotscheck | :-P | 14:50 |
| pedroalvarez | tbh, I think I hate that behavior too | 14:50 |
| persia | krotscheck: It's hard to implement in non-annoying ways and breaks browser controls (or at least these are the arguments I usually hear) | 14:50 |
| pedroalvarez | hm.. what about only showing latest events, and then a button at the top saying "show previous 10 events" | 14:51 |
| pedroalvarez | (is something I've seen somewhere else) | 14:52 |
| SotK | I find that comments ordered in that way make following conversation difficult | 14:52 |
| SotK | unless we do comment threading in the UI I guess | 14:52 |
| anteaya | has anyone had a chance to take a look at the expand the documentation task I added to https://storyboard.openstack.org/#!/story/2000610 | 14:55 |
| persia | newest-first with threading is something I find especially confusing to read | 14:55 |
| anteaya | would be really great if I could share a patch with dhellmann soon | 14:55 |
| anteaya | even just a draft of one | 14:56 |
| Zara | I'd like users to be able to toggle newest-first to oldest-first | 14:56 |
| *** jamesmcarthur has joined #storyboard | 14:57 | |
| Zara | anteaya: krotscheck commented on it, which is how we got onto this discussion about comments being hidden. I haven't looked into it at all today (beyond reading the story) | 14:57 |
| anteaya | Zara: thanks for reading the story | 14:57 |
| anteaya | krotscheck: I don't understand what you comment means | 14:58 |
| anteaya | dhellmann would like to use the q parameter | 14:58 |
| anteaya | and would like an example to follow | 14:59 |
| anteaya | as he has been unsuccessful in figuring it out on his own | 14:59 |
| krotscheck | anteaya: Show him the comment, he'll understand why basing anything automated off of q= is a bad idea. | 14:59 |
| anteaya | can an example of using the q parameter in an api query be added to the documentation? | 14:59 |
| anteaya | krotscheck: you can go ahead and show him the comment | 15:00 |
| anteaya | he asked for some expanded documentation | 15:00 |
| krotscheck | anteaya: I'm not the coordinator, that's what you volunteered for. | 15:00 |
| anteaya | and that is what I agreed to provide | 15:00 |
| anteaya | no, I agreed to get doug expanded documentation | 15:00 |
| anteaya | could you provide some | 15:00 |
| anteaya | if that is your response could you put it in the documenation please? | 15:01 |
| krotscheck | anteaya: I'm merely here to offer my expertise. I do not have the bandwidth to contribute at this time. | 15:01 |
| anteaya | great thanks for your expertise | 15:01 |
| anteaya | when someone has some time, if they could expand the documenation about the use of the q parameter, that is what has been requested | 15:02 |
| anteaya | adding an example of its usage would be ideal | 15:02 |
| *** jamesmcarthur has quit IRC | 15:03 | |
| *** jamesmcarthur has joined #storyboard | 15:04 | |
| anteaya | krotscheck: you may interpret what I agreed to in various ways, but I am clear what I agreed to and what I did not | 15:06 |
| *** jamesmcarthur has quit IRC | 15:18 | |
| *** jamesmcarthur has joined #storyboard | 15:27 | |
| fungi | anteaya: krotscheck: i have a feeling there are other existing api methods which will work better for dhellmann's needs. is the focus on using the /search method a tunnel-vision issue? | 15:38 |
| anteaya | fungi: good question | 15:39 |
| fungi | a bunch of the get methods for various resources provide very fine-grained parameterization | 15:39 |
| anteaya | here is the entire conversation I had with doug last night: http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-05-25.log.html#t2016-05-25T19:23:21 | 15:39 |
| anteaya | I think mostly Doug picked a very small actionable thing that would not be a large burden on the storyboard devs | 15:40 |
| anteaya | so he could experience an initial interaction | 15:40 |
| anteaya | I don't think that expanding documentation on an existing feature to be unreasonable | 15:41 |
| SotK | fungi: I suspect so, I'd certainly recommend using the aforementioned get methods for automation | 15:41 |
| SotK | but yeah, we should document the search stuff better | 15:41 |
| anteaya | SotK: thank you | 15:41 |
| anteaya | mostly I think Doug would like to see the loop in action | 15:41 |
| anteaya | make a small request, see what kind of response comes back | 15:41 |
| anteaya | he is a tc member so will share his experience with other tc members when the discussion comes up | 15:42 |
| *** jamesmcarthur has quit IRC | 15:48 | |
| *** jamesmcarthur has joined #storyboard | 15:51 | |
| *** bethwhite has quit IRC | 16:05 | |
| *** jamesmcarthur has quit IRC | 16:13 | |
| *** jamesmcarthur has joined #storyboard | 16:21 | |
| anteaya | when I create an automatic worklist and filter on something like status: todo, review, progress does the worklist refresh itself if the status of a task changes? | 16:22 |
| Zara | I think you'd have to refresh the page | 16:23 |
| anteaya | like if I am filtering on review if the status changes to merged does it get removed from my automatic worklist | 16:23 |
| anteaya | Zara: if I refresh the page it will run the worklist filter again | 16:23 |
| Zara | yeah. (iirc we have some sneaky stuff with boards which means that various clicks trigger a page refresh to keep them updated. but a worklist requires a manual refresh) | 16:23 |
| anteaya | did we ever get an answer on how we want to populate the -dev instance with some stories? | 16:23 |
| anteaya | Zara: cool thanks | 16:24 |
| anteaya | I'm fine creating some stories manually if that is the best way to go at this stage | 16:24 |
| anteaya | I'm going with no we have no answer for that | 16:31 |
| anteaya | which is fine, I'll create some stories and tasks | 16:31 |
| SotK | yeah, we want to import the production db at some point, but if you want something now-ish you should create some stories/tasks | 16:34 |
| fungi | i'm assuming there's been no issues spotted with the replacement storyboard.openstack.org today? | 16:39 |
| fungi | hoping i can take a snapshot of the old one and then delete it | 16:39 |
| Zara | nope, none spotted! | 16:40 |
| *** jamesmcarthur has quit IRC | 16:43 | |
| Zara | oh ha, my gerrit-storyboard script was on in the background, I didn't notice | 16:43 |
| Zara | so it has quietly been updating task 42 all day | 16:43 |
| Zara | so... I guess this version is more robust! \o/ | 16:43 |
| Zara | I am very glad my email notifications are set off | 16:44 |
| Zara | ;) | 16:44 |
| Zara | I don't really know why I keep redacting my access token in that patch, since nobody outside my network would be able to use it anyway | 16:49 |
| fungi | it's good security hygiene | 16:50 |
| *** jamesmcarthur has joined #storyboard | 16:50 | |
| anteaya | Zara: ha ha ha | 16:51 |
| anteaya | SotK: thank you | 16:51 |
| Zara | heh, I think at first I figured 'this way I'll form the habit', then started to get annoyed by it and wondered if it was a good enough reason. | 16:52 |
| anteaya | security starts with good habits | 16:55 |
| persia | Friction like that also helps inspire less intrusive secrets management, which can be useful. | 17:01 |
| Zara | true, the place I'm using the auth token needs to be replaced by something better anyway | 17:01 |
| Zara | I have no clue how to do that yet, so that's blocked. | 17:02 |
| *** jamesmcarthur has quit IRC | 17:03 | |
| anteaya | do we have a favourite work of fiction for me to draw from for my dummy stories on -dev? | 17:07 |
| Zara | what do you want to use it for? | 17:08 |
| *** jamesmcarthur has joined #storyboard | 17:09 | |
| anteaya | just for quotes, I could go with mary had a little lamb many times over | 17:09 |
| anteaya | mary had a little lamb 06 | 17:09 |
| anteaya | just wondering if you had a preference | 17:09 |
| Zara | I'm missing context... what's the goal? | 17:10 |
| persia | Characters and plotlines for filler stories. | 17:11 |
| persia | Many folk tend to be familiar with Holmes. | 17:11 |
| anteaya | comme ca: https://storyboard-dev.openstack.org/#!/story/3 | 17:11 |
| anteaya | https://storyboard-dev.openstack.org/#!/story/list | 17:12 |
| Zara | ohhh, are you load-testing by making lots of stories? | 17:14 |
| anteaya | well at least positioning myself to test automatic worklists | 17:15 |
| Zara | ahh, right. my test instance is a mix of song lyrics and things like 'fkdjslfdsjad;fasfkd;asfkj;as' | 17:15 |
| anteaya | which was what I was trying to do when I discovered the -dev db didnt' have any stories last night | 17:15 |
| Zara | gotcha | 17:15 |
| anteaya | hence my questions this morning about -dev stories | 17:16 |
| anteaya | song lyrics are available by searching | 17:16 |
| fungi | i like using lines from carroll's "jabberwocky" personally, but really anything will do | 17:16 |
| anteaya | good idea | 17:16 |
| Zara | yeah, I was confused because I make them as I need to test things, rather than all at once to test later, so I thought you were doing that tested mass-creation | 17:16 |
| Zara | *something that tested | 17:16 |
| anteaya | fungi: oh I like that too | 17:16 |
| anteaya | persia: I can't find any of the Holmes stories on line and I haven't read them myself | 17:16 |
| Zara | (because I often put things in my test instance to test rather than to try things out) | 17:17 |
| anteaya | so I can't draw from memory | 17:17 |
| persia | Then my assumption of commonality is wrong :) | 17:17 |
| SotK | tolkien? :) | 17:17 |
| Zara | the irc logs of the storyboard channel? | 17:17 |
| anteaya | Zara: right that makes sense, but testing auto worklists really is only effective if a have a few stories | 17:17 |
| anteaya | all good ideas, thank you | 17:17 |
| anteaya | that and some good old asd;lfkjasd;lkfjasd;lkj should get me where I need to go | 17:18 |
| anteaya | my thanks | 17:18 |
| Zara | yeah, understand | 17:18 |
| persia | Also https://en.m.wikisource.org/wiki/A_Study_in_Scarlet | 17:18 |
| anteaya | persia: thank you, that was what I was looking for | 17:18 |
| * anteaya copy/pastes | 17:18 | |
| Zara | you could probably hack the storyboard-gerrit script thing I made to POST to the dev instance for each change in gerrit, but that might be more trouble than it's worth | 17:19 |
| Zara | (and then just run it for 5 secs or something) | 17:19 |
| anteaya | ohhh, where might I find your storyboard-gerrit script thing | 17:20 |
| anteaya | in the wip gerrit patch? | 17:20 |
| Zara | yeah | 17:20 |
| anteaya | thanks | 17:20 |
| Zara | tbh it's probably better not to complicate it, but it could probably be used to create a lot of stories with some tweaking | 17:21 |
| anteaya | I'll look | 17:21 |
| Zara | (not that that script even needs to be used as a base, just perhaps slightly easier for someone coming new to it. but I really like to take an example then adjust it, whereas some people prefer to code stuff from scratch so ymmv) | 17:22 |
| anteaya | I do love your internal dialogue you share in your comments | 17:22 |
| anteaya | and whoops whitespace | 17:22 |
| Zara | :) yeah, still not ready to merge in that form | 17:22 |
| anteaya | oh I'm a shameless copier myself | 17:22 |
| Zara | so it rambles and is full of spaces \o/ | 17:23 |
| anteaya | keep the rambling | 17:23 |
| anteaya | it is pure gold | 17:23 |
| anteaya | I may just copy/paste your code comments for my stories | 17:23 |
| anteaya | :) | 17:23 |
| anteaya | ah ha ha ha | 17:24 |
| anteaya | I found a keeper | 17:25 |
| Zara | (maybe for load-testing I should make a script that posts storyboard stories as it loops through a library of strings... and get the library from the saved outputs of sotk's town-generator. end up with thousands of inexplicable stories.) | 17:26 |
| Zara | anteaya: what was it? | 17:26 |
| Zara | I'm heading home now, 'night! | 17:28 |
| SotK | night! | 17:28 |
| *** jamesmcarthur has quit IRC | 17:28 | |
| anteaya | night | 17:29 |
| anteaya | return 42 #this is just here so it doesn't error when the regexp isn't matched, | 17:29 |
| anteaya | # because I missed the course on error handling and wound up studying | 17:29 |
| anteaya | # Descartes instead. | 17:29 |
| anteaya | Love that | 17:29 |
| fungi | btw, i've snapshotted the old precise-based storyboard.o.o and deleted the virtual machine for it now | 17:30 |
| Zara | \o/ | 17:30 |
| Zara | (:) the two areas of study are clear and distinct. ;_;) | 17:30 |
| Zara | right I am actually off now, goodnight for real! | 17:31 |
| anteaya | Zara: they are so | 17:31 |
| anteaya | fungi: thank you | 17:31 |
| *** jamesmcarthur has joined #storyboard | 17:36 | |
| *** jamesmcarthur has quit IRC | 17:54 | |
| *** bethwhite has joined #storyboard | 17:58 | |
| *** jamesmcarthur has joined #storyboard | 17:59 | |
| anteaya | there we go, that gives me something to work with: https://storyboard-dev.openstack.org/#!/story/list | 18:01 |
| *** bethwhite has quit IRC | 18:13 | |
| *** jamesmcarthur has quit IRC | 18:23 | |
| anteaya | okay so I can create an auto worklist filtering on repo: https://storyboard-dev.openstack.org/#!/worklist/4 | 18:25 |
| anteaya | what do I have to do to get it to filer on priority? high medium low? | 18:26 |
| anteaya | right now if I try to filter on high, search suggests a tag called high, if I select that tag I get zero results even though I know I have set high priority on at least one item | 18:27 |
| *** jamesmcarthur has joined #storyboard | 18:32 | |
| * persia recommends using worklists for prioritisation, rather than tags. | 18:48 | |
| SotK | if you go to the search page (https://storyboard-dev.openstack.org/#!/search) and type "high" then there will be a "Task priority" option offered, which will show all tasks with that set | 18:50 |
| SotK | but I agree with persia, and want the global priority to disappear | 18:50 |
| anteaya | I want to be able to filter on priority | 18:53 |
| anteaya | so I can create a worklist with items from this repo with this priority | 18:54 |
| anteaya | or with this milestone | 18:54 |
| anteaya | so the items have been prioritized and I can make a worklist as a summary of all the items that have this priority | 18:55 |
| anteaya | and I don't care about tags, that was just the only option I was given in filtering the worklist | 18:55 |
| SotK | hm, maybe the automatic worklists thing doesn't know about priority | 18:56 |
| anteaya | it doesn't seem to | 18:56 |
| anteaya | it knows about repo names | 18:56 |
| SotK | I may have done that since we were/are planning to remove global priorities | 18:56 |
| anteaya | it knows about user | 18:56 |
| anteaya | 's names | 18:56 |
| anteaya | it doesn't seem to know about asignee names | 18:56 |
| anteaya | SotK: what do you mean remove global priorities? | 18:57 |
| anteaya | what is the plan | 18:57 |
| anteaya | sorry it does seem to know about assignee though the filter calls it user, not assignee: https://storyboard-dev.openstack.org/#!/worklist/5 | 18:59 |
| persia | The plan, last I knew, was to implement the spec on multidimensional priorities, where anyone who wanted to express priority could put some items in an ordered list, and other people could care, or not, and all priority would be "priority to me", avoiding arguments. | 19:00 |
| anteaya | https://storyboard-dev.openstack.org/#!/worklist/6 okay so user means assignee when creating an auto worklist | 19:01 |
| anteaya | have you a link to the spec? | 19:01 |
| anteaya | I don't recall arguments about priorties in the past | 19:01 |
| anteaya | my sense is that the release team would want to set them | 19:02 |
| anteaya | but I can go back and clarify that point | 19:02 |
| persia | ttx wrote it up on a wiki page a couple years ago. I will dig up the link later, unless someone else knows the story number. | 19:08 |
| persia | The release team worklist would obviously be one many people would choose to care about. | 19:09 |
| anteaya | right | 19:11 |
| *** jamesmcarthur has quit IRC | 19:12 | |
| anteaya | yeah if ttx cared enough about it I hope there is an artifact more recent than a wikipage from a few years ago | 19:12 |
| anteaya | I'm trying to reply to doug hellmann's needs as he expressed them yesterday | 19:12 |
| anteaya | the release team needs have changed since storyboard began as ttx outlined at both the summit design session and in the spec for the task tracker | 19:16 |
| SotK | so I don't think multidimensional priorities are very related to the release team's needs | 19:29 |
| anteaya | SotK: please expand | 19:29 |
| SotK | The idea is that when projects involve multiple stakeholders with no clear hierarchy (multiple companies working on one product, each with their own agendas for example), global priority is at best a source of friction and argument as the stakeholders' opinions on the priority of a given task differ. At worst it is meaningless as they each change it at will to something which matches their (and only their | 19:32 |
| SotK | ) opinion of the task priority. | 19:32 |
| SotK | Also, the people who answer to one stakeholder may not need to care about the priority of a task according to some other stakeholder. | 19:33 |
| anteaya | okay I understand that point | 19:35 |
| anteaya | thank you for clearly communicating it :) | 19:35 |
| anteaya | what does this mean for the release team | 19:35 |
| anteaya | and being able to create filtered worklists | 19:36 |
| anteaya | or some other sort of summary page | 19:38 |
| anteaya | I have moved to the mindset of filtered worklists as the work for them was mostly in place | 19:38 |
| SotK | The release team are a "stakeholder" in OpenStack, who probably have priorities that people care about. In this model, they create a manually ordered worklist which represents their priorities (higher in the list == higher priority for example). Other folk can then express interest in that worklist somehow (simplest way: "look at it") to find out what the release team cares about. | 19:39 |
| SotK | (they could also make three lists each expressing some priority level, the way they prioritise is up to them I guess) | 19:39 |
| SotK | ideally, a filtered worklist would be able to filter based on "task is in the worklist named 'release-team priorities'" or something | 19:40 |
| anteaya | so here is one thing they need to do | 19:40 |
| anteaya | http://eavesdrop.openstack.org/irclogs/%23openstack-infra/%23openstack-infra.2016-05-25.log.html#t2016-05-25T19:31:47 | 19:40 |
| anteaya | they need to create a per repo summary sheet of all tasks for a milestone | 19:40 |
| anteaya | for each project's liason to the release team | 19:40 |
| anteaya | currently we have about 50 projects/programs | 19:41 |
| * SotK will look in a moment, in the process of making food | 19:41 | |
| anteaya | yup, thank you | 19:41 |
| anteaya | food is important | 19:41 |
| SotK | alright, the best way for them to do that would be to use the api directly and generate some kind of document I expect | 19:46 |
| SotK | we don't really have a good way to display that kind of range of things in the UI at the moment | 19:46 |
| anteaya | great | 19:47 |
| anteaya | hence doug's request about the q parameter | 19:47 |
| SotK | I guess we're going to need some way to create/express milestones for stuff in the UI too | 19:47 |
| anteaya | he was thinking along the same lines as you | 19:47 |
| anteaya | I noticed it wasn't there | 19:47 |
| anteaya | so let's hold off on that | 19:48 |
| persia | There is a proof of concept up, waiting on the ability to subscribe to worklists: https://review.openstack.org/#/c/312666 | 19:48 |
| anteaya | if release is the only group that wants acces to them and they use the api let's see how far we can get with that | 19:48 |
| SotK | he probably wants to use the browse endpoint (http://docs.openstack.org/infra/storyboard/webapi/v1.html#get--v1-tasks) rather than the search endpoint in order to create such a list | 19:49 |
| anteaya | persia: thank you | 19:49 |
| SotK | the q parameter is just for text search, rather than having some syntax like gerrit's | 19:49 |
| anteaya | so far he is using this: https://docs.google.com/spreadsheets/d/1BLUDgediqgOzLZMMe8a3EAPOtyINAg2rpMtSyWjhC4o/edit?pref=2&pli=1#gid=0 | 19:50 |
| anteaya | but wants to get away from a spreadsheet | 19:50 |
| anteaya | SotK: ah okay that would be helpful for the documentation to share | 19:50 |
| anteaya | SotK: any chance you feel like interacting with dhellmann in -infra? | 19:50 |
| anteaya | might speed things along for both of you, if you have time | 19:51 |
| SotK | when I've eaten food, yes :) | 19:51 |
| anteaya | awesome thank you | 19:52 |
| anteaya | yes food first | 19:52 |
| anteaya | SotK: so the backscroll is interesting | 20:12 |
| anteaya | but Doug now realizes that getting this functionality will take some time | 20:12 |
| anteaya | mostly because it is hard to articulate the work flow to anyone who isn't a release manager | 20:13 |
| anteaya | I am going to go for a short walk back in a bit | 20:15 |
| *** zaro has joined #storyboard | 20:56 | |
| * SotK finally returns from eating and rent-application-sending | 21:49 | |
| * SotK goes to read infra backscroll | 21:50 | |
| zaro | Zara: are you really going to do this? https://review.openstack.org/#/c/302912 | 21:51 |
| anteaya | I'm not online tomorrow so will talk again on Monday, thank you | 23:08 |
| persia | Monday is a holiday in the US and UK, which may affect things. It also may not :) | 23:52 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!