15:04:27 #startmeeting storyboard 15:04:28 Meeting started Wed Apr 13 15:04:27 2016 UTC and is due to finish in 60 minutes. The chair is SotK. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:04:29 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:04:31 The meeting name has been set to 'storyboard' 15:05:07 #link https://wiki.openstack.org/wiki/Meetings/StoryBoard Agenda 15:05:11 that doesn't look up to date 15:05:14 haven't updated it, sorry 15:05:16 since I'm not on holiday 15:05:19 I think it was last updatd for last weds 15:05:22 so it's only a week out! 15:05:28 better than I normally manage 15:05:33 :D 15:05:40 completely forgot about the meeting; bugsquash! 15:05:55 * SotK too 15:06:07 I don't know of any announcements or urgent things 15:06:40 er, I guess... infra bugsquash is now, in #openstack-sprint 15:06:55 bugs are listed on storyboard 15:07:03 and sotk is back from holiday 15:07:08 /end of my announcements 15:07:17 \o/ 15:07:23 #topic In Progress Work 15:07:34 Worklists and boards are worklisty and boardish 15:07:41 :) 15:07:51 I'm making a more obvious way to make worklists in boards automatic atm 15:07:56 \o/ 15:08:17 should be sending patches soon-ish 15:08:38 also \o/ 15:09:52 (we're completely distracted by the bugsquash) 15:10:07 cool, any plans to do 'load more on scroll'? 15:10:12 since that just came up 15:10:19 one day, if I have the time :) 15:10:25 hahaha, fair enough 15:10:40 in fairness I don't think worklists should be used for really long lists anyway 15:10:47 cool 15:11:12 #info SotK working on automatic boards and UI fixes for boards/worklists 15:11:47 so, as for me... been looking some more at the pythonclient 15:11:51 \o/ 15:11:56 last week, I got gerrit talking to storyboard! 15:12:04 okay, it wasn't saying anything interesting (yet) 15:12:14 but I'm still pleased 15:12:32 I like the idea of hooking up an automatic board to gerrit 15:12:42 and just watching the cards move around 15:13:16 you mean, changing task status using gerrit and having the board's worklists filter by various statuses? :D 15:13:55 so precise! but yes 15:14:11 #info Zara made a horrible proof-of-concept gerrit-talking-to-storyboard thing last week https://review.openstack.org/#/c/302912/ 15:14:31 so this week, been looking at the python client some more, in an effort to get it working nicely to pipe a list of stories into an etherpad 15:14:34 for the bugsquash 15:14:45 turns out it's limited because it fetches resources by ID 15:14:53 so I'm looking at fixing that 15:15:07 that's useful for scripts interacting with storyboard more generally, too 15:15:53 #info Zara is trying to make the python client more flexible, for automating queries for resources 15:16:01 exciting :D 15:16:14 I'm procrastinating from fixing all the annoying things about emails 15:16:45 well, I made a story for subscription things, at https://storyboard.openstack.org/#!/story/2000545 15:17:09 based on things we've heard a lot of people shout about since emails went up 15:17:20 er 15:17:22 #link https://storyboard.openstack.org/#!/story/2000545 15:17:30 * SotK really wants to be able to configure what type of emails he receives too 15:17:34 yes 15:18:17 I also added some things to 15:18:21 #link https://storyboard.openstack.org/#!/story/99 15:21:18 so that's probably the place for that? I want to send round a mail for feedback on notification more generally... 15:23:30 well, I made a task for it while trying to reproduce rcarillocruz's bug, anyway 15:23:48 may make more sense to split it out. 15:27:29 erm... anything else for in-progress? 15:27:32 sorry, distracted 15:27:36 these logs will be fun 15:27:55 * SotK doesn;'t think there is anything else 15:28:08 #topic Open Discussion 15:29:07 we need to plan for texas! 15:29:08 eep 15:29:14 D: 15:29:19 there's a task-tracking fishbow 15:29:20 erm 15:29:23 fishbowl 15:29:40 * Zara abdicates, makes SotK the leader, and runs away 15:30:07 I'm seeing it mainly as requirements-gathering 15:30:10 who is going to be in texas? 15:30:18 (and updating people on where we're at) 15:30:20 SotK and I 15:30:24 yay! 15:30:57 it might also turn into a meta discussion of what task tracker is infra/openstack going to use 15:31:03 it might not, but it might 15:31:08 yeah 15:31:14 come into it prepared to give a status update 15:31:27 okay, thanks 15:31:27 be open to requirements gathering 15:31:33 but it might go any direction 15:31:37 so bring a seat belt 15:31:47 yeah, I imagine there will be a lot of people attending 15:31:50 for the drama 15:32:00 well let's be prepared 15:32:47 yeah, I have neglected preparing so far with the 'sotk is on holiday excuse' 15:32:50 it doesn't really work now 15:32:59 nope 15:33:03 so... status update, requirements gathering possibly, anything else? 15:33:12 anything we should be sure to mention in status update? 15:33:23 nope just be accurate and consise 15:33:34 offer to expand if there is interest 15:33:45 but outline the highlights as bullet points 15:34:09 talk about what is already in production 15:36:07 don't worry so much about what you plan to do 15:36:07 talk about what it already does 15:37:21 that makes sense 15:37:21 if someone asks what you plan to do, then you can share plans 15:37:21 cool, wfm 15:37:21 but just include current production features in your update 15:37:21 wonderful 15:37:37 prepare that and you should be in good shape 15:37:37 plan on your update being about 5 minutes maximum, there will be questions I'm sure 15:37:56 and other discussion, but try to keep your update to 5 minutes so we can get to discussion 15:38:08 if your update is less than 5 minutes, that is fine too 15:38:15 less is more 15:38:15 okay 15:38:38 I've been caught out by surprise requests for roadmaps before... but not at the summit