| *** coolsvap|away is now known as coolsvap | 03:20 | |
| *** SotK has quit IRC | 03:52 | |
| *** SotK has joined #storyboard | 03:52 | |
| *** mrmartin has joined #storyboard | 06:04 | |
| *** jtomasek has joined #storyboard | 06:14 | |
| *** cody-somerville has left #storyboard | 06:15 | |
| *** mrmartin has quit IRC | 06:50 | |
| *** mrmartin has joined #storyboard | 07:11 | |
| *** mrmartin has quit IRC | 07:57 | |
| *** coolsvap is now known as coolsvap|away | 08:43 | |
| Zara | morning, storyboard! | 10:14 |
|---|---|---|
| SotK | morning! | 10:17 |
| SotK | hm, so as far as I can tell, the only remaining difference in setup between production and my puppet deployment is that master uses a remote database server (I assume) | 10:49 |
| Zara | so what have you changed so far? | 10:51 |
| SotK | nothing, I just ran puppet with the database pointing to a server running locally and emails worked fine | 10:52 |
| Zara | gah | 10:53 |
| Zara | should we ask about it in #infra? | 10:54 |
| Zara | maybe someone's seen something similar before or can give some pointers | 10:54 |
| * Zara asks | 10:59 | |
| Zara | we have, what, 4 different instances with emails running at this point? xD | 11:01 |
| SotK | yep xD | 11:02 |
| Zara | 'IF YOU WANT TO TEST EMAILS, GO TO STORYBOARD.BASEROCK.ORG' | 11:04 |
| pedroalvarez | ha! | 11:04 |
| Zara | you win | 11:04 |
| pedroalvarez | main difference: we have access to the box | 11:04 |
| Zara | yeah, I was thinking you'd also be in a better place to find out the state of the gerrit plugin. | 11:04 |
| pedroalvarez | that helps, so the win isn't fair | 11:04 |
| pedroalvarez | hm.. yea | 11:05 |
| pedroalvarez | h | 11:05 |
| pedroalvarez | I'm interested on that | 11:05 |
| Zara | https://gerrit.googlesource.com/plugins/its-storyboard/+/318525276660db5fe909fd6bd45d5fe0b2ca47f9/src/main/resources/Documentation/quick-install-guide.md is the install guide | 11:05 |
| Zara | it may work for comments, though it was never updated to change story status | 11:06 |
| pedroalvarez | this could be one of the best points of gerrit + storyboard | 11:07 |
| Zara | repo: https://gerrit.googlesource.com/plugins/its-storyboard/ | 11:07 |
| Zara | yep | 11:07 |
| Zara | I think it'd be good to test it in baserock because we have access to the box and it'll be faster. in terms of upgrading the plugin, we'd really need to find someone who knew gerrit's inner-workings | 11:08 |
| Zara | afaik it'd take the storyboard team a while to learn and that means time taken away from boards and worklists, which need to be our main focus. | 11:09 |
| pedroalvarez | I'll try to help on this, at least to check the current status of it | 11:10 |
| Zara | thank you. :) it'd be so cool to get it working! | 11:11 |
| *** openstackgerrit has quit IRC | 11:43 | |
| *** openstackgerrit has joined #storyboard | 11:44 | |
| -openstackstatus- NOTICE: review.openstack.org is being restarted to apply patches | 11:44 | |
| *** ChanServ changes topic to "review.openstack.org is being restarted to apply patches" | 11:45 | |
| Zara | note to self: spend some time separating out bug-tracker requirements and task-tracker requirements. there's always some tension there. probably also need to separate out task-tracker reqs (devs) from task-tracker reqs (mgmt). | 11:45 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: Add Create Story Button in Worklists https://review.openstack.org/269656 | 11:51 |
| *** ChanServ changes topic to "StoryBoard - A task tracker for OpenStack development needs :: http://storyboard.openstack.org/ :: https://wiki.openstack.org/wiki/StoryBoard" | 11:56 | |
| -openstackstatus- NOTICE: Restart done, review.openstack.org is available | 11:56 | |
| Zara | I need to vanish briefly between 12:30 and 1 | 12:03 |
| Zara | just a general fyi | 12:03 |
| pedroalvarez | the plugin looks easy to configure | 12:15 |
| Zara | \o/ | 12:15 |
| pedroalvarez | but it will only send comments as far I can see | 12:16 |
| Zara | yeah | 12:16 |
| Zara | "" | 12:16 |
| Zara | This implements the ability to add comments to storybaord task tracking | 12:16 |
| Zara | system[1][2]. Updating of story status will be implemented in a follow | 12:16 |
| Zara | on change." | 12:16 |
| Zara | ;_; | 12:16 |
| Zara | he may have some of the work done, just not upstreamed, so could be worth asking him about it directly again | 12:17 |
| pedroalvarez | well, the codebase is tiny | 12:19 |
| pedroalvarez | It would be really easy to improve it, but there are some implementation details we might want to discuss | 12:22 |
| Zara | okay, that sounds good =D | 12:23 |
| pedroalvarez | so, I take that what we would like to see is something like tasks moving to Review, or Merged, whenever they gerrit patch changes | 12:24 |
| pedroalvarez | s/they/their/ | 12:24 |
| pedroalvarez | *tasks*, not *stories*] | 12:24 |
| pedroalvarez | -] | 12:24 |
| SotK | indeed | 12:24 |
| pedroalvarez | then we need a way to identify tasks | 12:25 |
| pedroalvarez | (my guess) | 12:25 |
| Zara | we have that afaik? and task status? | 12:25 |
| SotK | yeah, tasks have IDs, just not very visibly | 12:25 |
| Zara | yeah, tasks can only be created by creating a story, but the task ID is separate from the story id | 12:26 |
| pedroalvarez | nice then.. | 12:34 |
| pedroalvarez | then is just a matter of making the plugin read tasks IDs from somewhere in the gerrit change, and using the API to change task status | 12:34 |
| Zara | yup. :) I think it's because storyboard was designed for developers, so there were always vague plans for this | 12:36 |
| Zara | tasks have: id, created_at, updated_at, title, story_id, project_id, assignee_id, status, creator_id and priority (which we want to deprecate in favour of personal priorities) | 12:37 |
| pedroalvarez | Zara: where have you found the text that you have quoted before? | 12:37 |
| Zara | pedroalvarez: commit message https://gerrit.googlesource.com/plugins/its-storyboard/+/318525276660db5fe909fd6bd45d5fe0b2ca47f9 | 12:38 |
| Zara | that's the last change he made, though; other changes to repo have just been to stop it getting out of date afaict | 12:38 |
| pedroalvarez | thanks | 12:39 |
| Zara | yw :) | 12:40 |
| * Zara vanishes briefly | 12:40 | |
| SotK | hm, using a remote database server and deploying with puppet, I still have working emails | 12:46 |
| pedroalvarez | :( | 12:46 |
| pedroalvarez | we definitely need more help from infra | 12:46 |
| SotK | yep | 12:46 |
| SotK | this would probably be easier to debug if we had useful logging for the workers... | 12:55 |
| Zara | storyboard meeting in an hour and 15 minutes! | 13:44 |
| pedroalvarez | no help so far from infra :/ | 13:48 |
| *** lifeless_ has joined #storyboard | 13:51 | |
| *** gothicmi1dfood has joined #storyboard | 13:51 | |
| *** krotscheck_ has joined #storyboard | 13:55 | |
| *** gothicmindfood has quit IRC | 13:56 | |
| *** lifeless has quit IRC | 13:56 | |
| *** krotscheck has quit IRC | 13:56 | |
| *** Zara has quit IRC | 13:56 | |
| *** krotscheck_ is now known as krotscheck | 13:56 | |
| *** Zara has joined #storyboard | 13:56 | |
| Zara | yay | 13:57 |
| betherly | hi all! setting up storyboard locally and looking at the documentation for it http://docs.openstack.org/infra/storyboard/install/development.html | 14:18 |
| betherly | do you all use virtual box for the install? i run virtual box on a mac but sadly mac does not support fullscreen so just wondering what options are re running a UI outside the vm | 14:19 |
| SotK | I use a VM in an internal openstack cloud, and interact with the UI from my laptop | 14:21 |
| pedroalvarez | I normally use a setup which is almost like a production environment | 14:26 |
| betherly | ok cool :) so i could set up storyboard on the vm and then ping the vm from my mac and work on the ui from there? | 14:28 |
| SotK | yeah, you should be able to | 14:28 |
| betherly | awesome thanks :) | 14:29 |
| Zara | meeting time! | 15:01 |
| Zara | that snuck up on me | 15:01 |
| betherly | ugh sorry me too! | 15:11 |
| Zara | no problem, we tend to run about 30 minutes under the allotted time so I'm quite slow with it... | 15:24 |
| pedroalvarez | <Zara> I suspect we'll get complaints related to the lack of threading... but we'll see! | 15:56 |
| pedroalvarez | heh, I already did :P | 15:56 |
| Zara | hahaha | 15:56 |
| Zara | I hope they were polite! | 15:57 |
| Zara | if they were rude, I'll put it at the bottom of my priorities list. :) | 15:58 |
| Zara | betherly: how are the adventures with the storyboard vm going? | 16:01 |
| betherly | Zara: my vm being a pain in the ass with space issues that arent an issue - miscommunication between vm and reality | 16:03 |
| Zara | sounds weird =D | 16:03 |
| Zara | anything specifically storyboard-related or just general virtualisation headaches? | 16:04 |
| Zara | (it sounds like it's a more general VM problem so far) | 16:05 |
| betherly | general virtualisation and meetings making it difficult to drill down | 16:12 |
| betherly | aarghhh | 16:12 |
| Zara | :< | 16:14 |
| * Zara is now extra glad she doesn't have a lot of disruptive meetings | 16:14 | |
| Zara | my beloved: https://wiki.openstack.org/w/images/0/0a/Storyboard_schema.png is now on the wiki btw | 16:15 |
| Zara | betherly: we're around to help with anything if you need it, though guessing much of it depends on the infra where you work | 16:15 |
| * SotK discovers his boards permissions code is slow... | 16:16 | |
| pedroalvarez | oh! | 16:17 |
| * pedroalvarez remembers a possible bug | 16:17 | |
| Zara | the schema I linked doesn't have a section for boards and worklists; I believe it was autogenerated with some magical mysql tool | 16:18 |
| SotK | pedroalvarez: go on... | 16:18 |
| Zara | (oh, actually, no, that's a different diagram, that the one I've linked was based on) | 16:19 |
| pedroalvarez | SotK: can't reproduce, so notabug | 16:24 |
| Zara | I should look at libravatar again... | 16:44 |
| Zara | not sure where the python should go. I imagine we'd want the html in the user-typeahead class, in place of the silhoutte | 16:45 |
| SotK | you probably won't need to use user-typeahead if you're using the avatar instead of the name too | 16:46 |
| Zara | ah, I started using that because it was the quickest way to get name to display instead of assignee id, and it came with a little silhoutte for free, but yeah | 16:48 |
| Zara | I'd just need ot look at user-typeahead to see how it was done | 16:48 |
| Zara | oh, okay, formatUserName | 16:51 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: Always go to Story Detail Page after adding Story https://review.openstack.org/270337 | 17:41 |
| Zara | it was bugging me when gardening. | 17:42 |
| openstackgerrit | Zara proposed openstack-infra/storyboard-webclient: Always go to Story Detail Page after adding Story https://review.openstack.org/270337 | 17:43 |
| Zara | noted story in commit.... | 17:43 |
| pedroalvarez | It would be awesome that the task itself now would be updated automatically to say "Zara" and "Progress" | 17:46 |
| Zara | yup... | 17:46 |
| Zara | iiin the meantime, I'll do it manually | 17:47 |
| Zara | also excited at the thought of task metadata meaning the task will have a field that links to the commit in review (automatically or otherwise) | 17:49 |
| pedroalvarez | any idea about how this would be represented on the UI? | 17:50 |
| Zara | well, the task status button will be deprecated, so there will be room there for something to replace that | 17:51 |
| pedroalvarez | hm... not sure about it being deprecated | 17:51 |
| Zara | i think we'll need some kind of 'more...' with a modal somewhere, but there'd be room for the most important thing in place of that | 17:51 |
| Zara | oh sorry not status | 17:51 |
| Zara | priority | 17:52 |
| * Zara facepalms | 17:52 | |
| pedroalvarez | ah | 17:52 |
| Zara | yeah, we don't think global priorities make much sense, since priorities are more of a per-user/per-team thing | 17:52 |
| Zara | so yeah, I picture link to commit where that button is, and then a 'more...' with other things at the end- but there's probably a more elegant way of doing it | 17:53 |
| Zara | I want the link to the commit because it really annoys me when gardening, putting things in the comments... | 17:53 |
| Zara | I haven't really noticed the absence of other data, though I think due-date is important for cards | 17:54 |
| pedroalvarez | so: Developer creates a patch to fix task #123, so (s)he puts "Task 123" or similar in the commit msg. Then, Storyboard itself will create a link to the commit in the task, and update the status to "Review" | 17:56 |
| Zara | yup. possibly making the assignee the same as the person who committed... but I think that could be fiddly, and might not really be that useful. (I think assignees are generally more useful before work is in review, to track who should be doing it.) | 17:59 |
| Zara | more a nice-to-have than a crucial feature | 18:00 |
| Zara | but yeah, that'd be awesome | 18:00 |
| *** lifeless_ is now known as lifeless | 18:12 | |
| Zara | heading home for the night | 18:12 |
| Zara | see y'all tomorrow! :) | 18:12 |
| *** NikitaKonovalov2 has joined #storyboard | 18:14 | |
| *** jtomasek has quit IRC | 18:15 | |
| *** cody-somerville- has quit IRC | 18:22 | |
| *** NikitaKonovalov has quit IRC | 18:22 | |
| *** NikitaKonovalov2 is now known as NikitaKonovalov | 18:22 | |
| *** cody-somerville- has joined #storyboard | 18:23 | |
| openstackgerrit | Andreas Jaeger proposed openstack-infra/storyboard: Remove argparse from requirements https://review.openstack.org/270406 | 18:31 |
| *** gothicmi1dfood has quit IRC | 18:53 | |
| *** gothicmindfood has joined #storyboard | 18:56 | |
| *** davidlenwell has quit IRC | 20:18 | |
| *** davidlenwell has joined #storyboard | 20:20 | |
| *** davidlenwell has quit IRC | 21:52 | |
| *** davidlenwell has joined #storyboard | 21:54 | |
| *** davidlenwell has quit IRC | 22:00 | |
| *** davidlenwell has joined #storyboard | 22:02 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!
