19:01:58 #startmeeting storyboard 19:01:59 Meeting started Wed Feb 8 19:01:58 2017 UTC and is due to finish in 60 minutes. The chair is zara_the_lemur__. Information about MeetBot at http://wiki.debian.org/MeetBot. 19:02:00 Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 19:02:03 The meeting name has been set to 'storyboard' 19:02:15 #topic Announcements 19:02:19 None of which I'm aware 19:02:36 #topic Urgent Items 19:02:41 anyone want to flag anything? 19:03:02 okay, moving on! 19:03:06 #topic in-progress work 19:03:51 My attention span to work on the migration of of branched items has been a bit of a roadblock. 19:03:57 heh 19:03:57 But I am trying. 19:04:16 I'm afraid my week ended up busier than expected and I've also not made much meaningful progress on the migration scripts either 19:04:27 I've been having a bit of a strange week, investigating how far storyboard can be abstracted from its current db framework. so I've been generally around but not able to focus on migration things. 19:04:41 otoh I suddenly have way more knowledge of both sql and how the storyboard backend fits together 19:04:44 SotK, you one patch looked good to me. What was your concern? 19:04:45 which should come in useful 19:05:26 zara_the_lemur__, thats good news :) 19:06:22 I've been trying to figure out a bug where sometimes users get created with a fake openid url because the script fails to find their real one, after hitting a bug where the script also can try to create duplicate users for some reason 19:06:30 diablo_rojo: :) I've also been chipping away at that blogpost and hope to have something done by tonight and up by tomorrow 19:06:48 I figure if I say that it will make me finish it 19:06:57 given sb is already using an orm and oslo.db, hopefully there's not a lot to generalize to run with additional database backends? 19:07:00 zara_the_lemur__, woot woot! If you want me to look it over, let me know. 19:07:47 fungi: we have some mysql-specific things; I started with postgres because I figured that'd be the best way to find them, so it's possible some things I've looked at are actually just postgres quirks... 19:08:22 have any examples? there's a wip change for it, right? 19:08:38 pretty sure i saw one skitter through the channel earlier today 19:08:42 fungi: yeah, I'll get the link, hang on :) 19:09:12 #link https://review.openstack.org/#/c/430395/ 19:09:38 I deleted all the db migrations and made a fresh one because there was a problem with 018 that baffled me 19:10:44 recasting some fields to enum type i guess 19:10:52 SO MANY 19:10:54 yep 19:11:04 (it wasn't really *that* many, just felt like it) 19:11:10 if nothing else this should make it easier for me to get features into storyboard in the future since I'll have a better idea what's going on 19:11:49 seems like that could become a wrapper function or decorator or something. i wonder how other projects are doing that 19:11:49 my conceptual model for how the database communicated with the API was much woollier this time last week 19:12:34 yeah, there may actually be examples in historic storyboard code 19:12:38 since we used to support it 19:14:02 (I've also done a little review this week, though not very much, but it's a good week to catch me for review) 19:16:16 oh, this also might be interesting as a demonstration of what a relatively small project would need to do to simultaneously support postgres and mysql, so if people ask after that support elsewhere, it might be something useful to point people at 19:16:38 (once I have the wip in a form where both *are* supported, anyway) 19:17:17 'this is the kind of thing you would need to commit to doing if you want that support' 19:18:10 I am rededicating myself to reviews this week and next week. 19:18:36 cool 19:19:51 anyone else have anything in-progress? otherwise I'll move on to open discussion! 19:20:07 #topic Open Discussion 19:20:16 I think this is our new record :) 19:20:18 It would be really great if we could be close to getting monasca over by the PTG. 19:20:52 yeah, do you reckon we're blocked on that, SotK? 19:21:28 I know that means I gotta get it together with he branched stuff. 19:21:48 My goal is to get that done by the EOD Friday so we can get it tested and merged next week. 19:21:52 Sound reasonable? 19:22:08 * diablo_rojo says the plan out loud so maybe it will happen- just like zara_the_lemur__ 19:22:13 I think so, I should be able to commit to testing stuff next week 19:22:14 heh 19:22:41 if it turns out I can commit to more than that, then it might be worth me taking responsibility for more of the migration 19:22:54 though I don't think I'll know until tomorrow if that's possible 19:23:03 certainly seems doable 19:23:45 zara_the_lemur__, That's fine :) Finish the blog post first I think and then figure out whats next. 19:24:15 sure 19:26:39 SotK, what are you looking at this weekish? 19:27:54 I think he's travelling atm so may have a not-great connection 19:29:47 hopefully I can get the user bug fixed, and then the "some weird characters break story description rendering if they are imported" bug 19:30:05 changing priority to set a tag rather than a priority should be trivial 19:30:12 have you written a story up anywhere with current status? 19:30:24 I don't think so, I can do so after 19:30:46 yay, thanks, please do, that way I can take a look if I *do* get some time. 19:31:00 sounds great 19:31:53 (I guess the downside is that if I do, I'll just ask a ton of questions and then you'll wind up working on it anyway...) 19:32:12 but there's always /ignore! 19:32:31 That is a big stick 19:33:12 ;_; 19:33:51 zara_the_lemur__, lol I am trying not to do that very thing with the migration handling of branches 19:34:35 haha 19:35:06 though please feel free to ask about things in #storyboard! 19:35:17 noted 19:35:24 I am normally open to answering tons of questions :) 19:35:45 I basically talk to myself all day asking things and sometimes people drop in and give me a pointer 19:36:01 so there isn't pressure associated with asking a question 19:37:36 or being asked a question 19:39:11 anyone else have any discussion topics? 19:39:30 not i 19:39:55 okay, meeting ends in... 19:39:55 10 19:39:57 9 19:39:58 8 19:39:58 7 19:39:59 6 19:40:00 5 19:40:01 4 19:40:01 3 19:40:02 2 19:40:02 1 19:40:04 #endmeeting