| *** diablo_rojo has quit IRC | 00:53 | |
| *** diablo_rojo has joined #storyboard | 01:50 | |
| *** diablo_rojo has quit IRC | 01:57 | |
| *** jtomasek has quit IRC | 06:55 | |
| *** openstackgerrit has quit IRC | 08:48 | |
| *** openstackgerrit has joined #storyboard | 08:48 | |
| *** fay_ has joined #storyboard | 09:03 | |
| *** jtomasek has joined #storyboard | 10:23 | |
| *** alexismonville has joined #storyboard | 11:42 | |
| *** alexismonville has quit IRC | 11:47 | |
| *** alexismonville has joined #storyboard | 12:15 | |
| Zara | reminder that the storyboard meeting is at 15:00 UTC | 14:08 |
|---|---|---|
| Zara | we have an agenda over here, but it's old! https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting | 14:09 |
| Zara | we really need to move this meeting to a later slot... | 14:09 |
| SotK | yeah | 14:19 |
| Zara | my thought is sometime between 18:00UTC and 21:00UTC would be best, not sure which day (well, would rather avoid friday) | 14:22 |
| SotK | 18:00UTC is likely too early for me | 14:23 |
| Zara | okay, between 19:00 and 21:00? | 14:24 |
| SotK | yeah, that is best for me | 14:25 |
| Zara | ironically fri at 19:00 is the first obviously free spot I've found in #meeting. there aren't many weekly meetings that clash in that timeslot, but lots of biweekly things. | 14:29 |
| Zara | oh, I think #meeting may be free weds 19:00 | 14:31 |
| Zara | anyway, this week's meeting in 2 mins | 14:58 |
| Zara | in this meeting, we can discuss moving the meeting, so it's all really meta | 14:58 |
| persia | I don't know. I don't think there was enough discussion about when to have discussion about discussing schedule changes in the meeting. | 14:59 |
| Zara | looks like we need to discuss when to discuss! :D | 15:00 |
| persia | Perhaps starting about an hour ago? | 15:00 |
| *** diablo_rojo has joined #storyboard | 15:56 | |
| Zara | yay, new meeting time went through, thanks, all! :D | 16:35 |
| *** fay_ has quit IRC | 17:02 | |
| *** pabelanger has joined #storyboard | 17:48 | |
| pabelanger | afternoon | 17:48 |
| pabelanger | looking for some help with storyboard | 17:48 |
| Zara | 'sup? | 17:48 |
| pabelanger | So, in https://storyboard.openstack.org/#!/story/2000773 I just manually created 25 new tasks | 17:49 |
| pabelanger | which I basically copy / pasted from git commit messages | 17:49 |
| pabelanger | is there any way I could have done that, without copy / paste? | 17:49 |
| pabelanger | eg: have storyboard, create a task, based on a commit message | 17:50 |
| SotK | you could probably have done some magical shell command to parse a git log and create tasks named after the commits using the API directly | 17:50 |
| pabelanger | Ya, think so | 17:51 |
| Zara | yeah, or use the python client (which is pretty similar, might be slightly easier)-- really to do that properly I think you'd want to extend the gerrit plugin | 17:51 |
| Zara | the tricky bit would be mapping tasks to projects, I think | 17:51 |
| Zara | the other thing is that arguably the task-tracker should be showing what work is planned, rather than listing stuff retrospectively (I can't talk because I do it all the time, but I can see folks discouraging it) | 17:53 |
| pabelanger | Ya, this is a retrospective issue for sure. Was asked to import my tasks, over having tasks first created then assigned | 17:54 |
| pabelanger | so, might not be an issue moving forward | 17:54 |
| Zara | yeah, I think ideally tasks are created in storyboard before there's any code, but I couldn't say how often the ideal workflow occurs | 17:56 |
| *** jtomasek has quit IRC | 17:58 | |
| zaro | pabelanger: i'm not sure there's an easy way to do that. seems like chicken/egg issue. if you auto create tasks how would you know what task number would be in your commit message? | 18:20 |
| zaro | the only way i could see it working is to maybe initiate task creation from git-review, like git-review --create-tasks | 18:23 |
| zaro | i'm pretty sure git-review would not want to add a flag specifically for storyboard though. | 18:24 |
| pabelanger | Ya, I'm not sure the use case is valid too much | 18:32 |
| pabelanger | I think moving forward, somebody would create the tasks first | 18:32 |
| pabelanger | and I would be assigned said task | 18:33 |
| *** zara_the_lemur__ has joined #storyboard | 18:46 | |
| zara_the_lemur__ | hm, for https://review.openstack.org/#/c/390671/ , for some reason I thought it depended on the api patches but now I'm wondering if I'm mixed up | 19:18 |
| openstackgerrit | Merged openstack-infra/storyboard: use processutils from oslo.concurrency https://review.openstack.org/394570 | 19:30 |
| zara_the_lemur__ | I'm vanishing for the evening; 'night! | 19:35 |
| *** zara_the_lemur__ has left #storyboard | 19:38 | |
| *** diablo_rojo has quit IRC | 20:09 | |
| SotK | nope, doesn't depend on the API patch | 20:36 |
| SotK | without the API patch you can still get the exciting "search endpoint has no parameter status" error or however it is phrased | 20:37 |
| *** diablo_rojo has joined #storyboard | 21:17 | |
| *** alexismonville has quit IRC | 22:26 | |
| *** pabelanger has left #storyboard | 22:39 | |
| persia | A potentially sensible workflow would be to use a storyboard client to generate the task, which then gives you a task number, which then goes into the commit message, which is then submitted to gerrit. | 22:55 |
| persia | Ought be relatively easy to create a python-storyboardclient based tool that takes some arguments (e.g. story number, description, project), and some config (e.g. developer identity) and outputs a the ID of a newly-created self-assigned task that can be used in the git commit message. | 22:56 |
| *** diablo_rojo has quit IRC | 23:38 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!