15:00:48 #startmeeting storyboard 15:00:49 Meeting started Wed Mar 16 15:00:48 2016 UTC and is due to finish in 60 minutes. The chair is Zara. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:00:50 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:00:52 The meeting name has been set to 'storyboard' 15:01:08 #topic announcements 15:01:12 There are none 15:01:22 well, SotK is ill, and betherly is on holiday, if that counts 15:01:29 expect merges to be a bit slower than usual 15:01:40 #topic Urgent Items 15:01:47 I have one thing listed! 15:01:53 The last of the email config patches! 15:02:02 #link https://review.openstack.org/#/c/293367/ 15:02:14 I realise this is like an ongoing comedy skit at this point 15:02:19 but that should be the last one 15:02:46 it awaits reviews, please review if you want email notifications to come to a storyboard.openstack.org near you 15:03:00 #topic In Progress Work 15:03:14 SotK had been working on worklists and boards before illness 15:03:42 his eta on Thurs was Fri, then he couldn't concentrate, and thought he might be ill; now he's ill 15:04:16 so.... probably in review soon, ceteris paribus 15:05:13 #info Automatic Worklists and Boards seems to be going well, progress frozen while SotK is ill 15:05:31 I've been looking at task comments, this week 15:05:53 or task notes, to use the term I *should* be using, in the name of consistency 15:06:08 you can now comment directly on a task in storyboard 15:06:12 it is the best 15:06:15 I use it all the time 15:06:37 #info you can now put notes on a task in storyboard from the story view 15:06:46 I have some further patches for this in review 15:06:53 To be clear, this isn't a discussion on a task, but rather a single editable markdown field that people can populate with things? 15:06:59 yes 15:07:12 * persia was worried for a moment by the use of "comment" 15:07:16 yeah, that's why I should avoid calling it 'comments' 15:07:19 it confuses things 15:07:27 it's effectively a task-description 15:08:12 (in terms of the implementation, anyway) 15:09:00 there are some examples here, currently only viewable for someone logged-in 15:09:07 #link https://storyboard.openstack.org/#!/story/2000511 15:09:17 you can see I went overboard :P 15:09:29 so, other patches for that are in review: 15:09:41 #link https://review.openstack.org/#/c/291755/ 15:09:45 that is the most important one 15:10:00 it lets someone add/view notes to a task from the board view 15:10:18 I predict it'll be very annoying to only be able to do it from the story view 15:10:47 #link https://review.openstack.org/#/c/292957/ 15:11:00 ^ lets logged-out people read, but not edit task notes 15:11:14 and 15:11:15 My concern is that people may use these notes from other views in lieu of discussion in the story, which may cause either discussion to be lost or captured forever in the task description. 15:11:18 #link https://review.openstack.org/#/c/292462/ 15:11:34 That said, we'll have to see how people actually use it :) 15:11:36 mentions task notes in the list of task details in the 'task details changed' email 15:11:44 agreed, I noticed it because I wanted to do it 15:12:07 we might eventually want different things visible from boards vs stories... but it's a long way off! 15:13:19 oh, just read backscroll, sorry, should've looked at window 15:13:50 I think eventually we'll want history for task notes and things like that; theoretically it should go in the events timeline, but I'm not sure about the space around that 15:13:59 when you add/change a note, it does a PUT 15:14:07 Maybe sometthing to discuss in Austin. 15:14:31 and that triggers the 'task details changed' event, at least. so it shoudl be possible to have a 'task notes changed' event, and log the details of the task description change in the timeline 15:14:45 we currently don't do that for story descriptions, either, and we should 15:14:58 so I can see that being part of a bigger effort involving events timelines/history etc 15:15:08 (along with history for boards/worklists) 15:17:41 the task note changes will be recorded in emails (even without the task note email patch), so there will be a history, but not in the best place. 15:18:44 Other in progress work... I have lots of misc stuff in review 15:18:53 and most of it is waiting on SotK's +2 at this point 15:19:01 or any other storyboard core, if anyone's around, I just default to his 15:19:23 (he will be on holiday soon, so I will have to bang on some doors for a couple of weeks) 15:19:51 if anyone's bothered by having multiple search icons, this is still in review: 15:19:56 #link https://review.openstack.org/#/c/279204/ 15:20:49 if anyone wants a very basic page that just lists all boards and worklists, we need the above + this: 15:21:01 #link https://review.openstack.org/#/c/279753/ 15:21:31 I'm used to storyboard so I'm happy to work around those until we have time to make the list of all boards + worklists nicer 15:21:45 at this point, it's only of relevance to people who want to demo features 15:23:11 the multiple search thing is confusing, but only for new users, and I think most of our users are used to it and don't care. 15:23:19 so *shrug* 15:23:32 moving on! 15:23:43 #topic Discussion 15:23:58 so we mentioned getting a public dev instance, last week 15:24:15 I've written up motivations for that 15:24:20 #link https://storyboard.openstack.org/#!/story/2000028 15:24:31 on an older story about it 15:24:35 some tasks may be outdated 15:24:55 #link http://storyboard.sotk.co.uk/#!/dashboard/stories 15:25:03 ^ is the closest thing we have to a public playground instance atm 15:25:19 I think SotK runs it at home or something 15:25:25 I don't even know. 15:26:29 oh, actually, no, I think it's on our infra. anyway, it's slower than production, and we dig it up when we want to demo something, so we don't maintain it well 15:26:41 *our -> our employer's, not infra's 15:27:19 actually I'll just stop speculating because sotk has like 30 instances and I can never remember which is which 15:28:16 it'd be good to have something more official, that ran from master (or a dev branch) 15:28:56 ran from -> was CD from 15:29:06 I can't write words today 15:29:35 anyway, hopefully that story makes it a bit clearer, please add details as appropraite 15:29:40 *appropriate 15:29:55 other things... 15:30:11 I've put a task-tracking session on the infra etherpad, because why not 15:30:24 #link https://etherpad.openstack.org/p/infra-newton-summit-planning 15:31:34 in seriousness I'm not clear on task-tracker requirements and I'd like to get that clearer 15:31:35 On dev instance: isn't production CD from master? Wouldn't we want some pre-CD collection of patches? 15:32:44 persia: so, there are a few motivations. if we just want a playground, we can use master CD. if we want a place to demonstrate wip, I was thinking we could have a dev branch that would CD to a dev instance 15:33:19 Ah. I see. 15:33:45 or we have some combination, or something a bit different; I've just tried to collect some thoughts on it together 15:35:16 for demoing wip, I think we may actually need multiple instances, but after a while it gets ridiculous 15:35:54 (I'm thinking of situations where we're making DB changes that conflict with each other, so we can't just pull changes into one instance) 15:36:59 anyway, returning to infra-task tracking-- if it's better as a cross-project session, I'd be fine with doing that instead 15:38:34 I think we're already fairly clear on what storyboard will focus on in Newton, so it's more to check that it makes sense. 15:39:10 if I get there and everyone's saying that a task-tracker needs VR, useful to know. 15:39:31 moving on... 15:39:37 #topic Open Discussion 15:39:54 Openly discuss things! 15:40:23 anyone have anything to discuss? 15:42:04 * Zara considers changing her nick to 'SotK' and having a discussion 15:42:33 oh well, hope he feels better soon! 15:42:51 In that case, I'll give it another coupla minutes, then end this meeting 16:00:43 Zara: I think you forgot to actually end your meeting. 16:00:51 sorry! 16:00:54 #endmeeting