15:02:48 <krotscheck> #startmeeting storyboard 15:02:49 <openstack> Meeting started Mon Apr 28 15:02:48 2014 UTC and is due to finish in 60 minutes. The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot. 15:02:50 <openstack> Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. 15:02:53 <openstack> The meeting name has been set to 'storyboard' 15:02:54 <krotscheck> WHo’s here? 15:03:37 <NikitaKonovalov> o/ 15:03:47 <krotscheck> Huhn. Ok 15:04:00 <krotscheck> Well, hopefully other people will join later. Want to do this informally and just give a status update? 15:04:07 <krotscheck> Agenda-ish: https://wiki.openstack.org/wiki/StoryBoard 15:04:33 <NikitaKonovalov> my update is not very long 15:04:51 <NikitaKonovalov> I've updated my change with timeline to carefully migrate comments 15:05:14 <krotscheck> Noticed that, looks good. 15:05:38 <NikitaKonovalov> there is also a change to add a special test that should not allow migrations with the same id 15:05:56 <NikitaKonovalov> here it is https://review.openstack.org/#/c/90047/ 15:06:21 <NikitaKonovalov> And now I'm working on Project Groups API 15:06:36 <krotscheck> Oooh, good one 15:06:44 <NikitaKonovalov> waiting for reviews on this one https://review.openstack.org/#/c/90736/ 15:07:36 <krotscheck> I was thinking: doesn’t alembic yell at you when you don’t have the same migration? 15:08:14 <NikitaKonovalov> It prints a warning to stdout and goes on as if nothing happened 15:08:27 <krotscheck> Oh. 15:08:33 <krotscheck> That’s all sorts of fail 15:09:14 <krotscheck> Anything else, or shall I do mine? 15:09:21 <NikitaKonovalov> here is the proof https://github.com/zzzeek/alembic/blob/master/alembic/script.py#L217 15:09:29 <NikitaKonovalov> but that's all from my side 15:13:59 <krotscheck> Ugh, sorry, got disconnected 15:13:59 <krotscheck> Anyway. 15:14:00 <krotscheck> What was the last update I sent? 15:14:34 <krotscheck> I started using a tool for UI reviews. I have to add participants to the project manually (it’s not just open), so if you want to see what I’m working on UI/UX wise ping me. 15:14:58 <NikitaKonovalov> I 15:15:00 <krotscheck> The tool itself is here: https://projects.invisionapp.com/d/main#/projects 15:15:12 <NikitaKonovalov> yea, I've got your invitation 15:17:16 <krotscheck> This week I’m planning on landing those patches and adding stupid task priorities. 15:17:42 <krotscheck> Also, likely, adding the typeahead dropdown for project selection in the new story modal. 15:17:47 <krotscheck> ‘cause, really, we need it there. 15:18:34 <NikitaKonovalov> Ok I'll take care of priorities on server-side 15:18:45 <krotscheck> NikitaKonovalov: I can do that. 15:18:49 <krotscheck> Unless you REALLY want to 15:19:16 <NikitaKonovalov> Well, I was actually thinking on what to do next 15:20:24 <NikitaKonovalov> I've also seen your story about splitting alembic migrations for auth and non-auth stuff 15:20:36 <NikitaKonovalov> that looks interesting 15:20:41 <krotscheck> NikitaKonovalov: Yeah, that was something I’m currently pondering whether it’s a good idea or not. 15:21:06 <NikitaKonovalov> (unless alembic has another 'just_a_warning' fotr us) 15:21:28 <krotscheck> I mean, if slqalchemy/alembic and pecan/wsme are the OpenStack Way (tm), then making some of the common code across services easily pluggable would really help other projects. 15:23:12 <NikitaKonovalov> It will, but afaik openstack projects tend to use keystone for auth and communicate thorugh clients with it 15:23:46 <krotscheck> So it’d require that our pluggable auth is pluggable. 15:23:47 <krotscheck> Hrm 15:23:56 <krotscheck> Sounds like that’s one too many plugs. 15:24:11 <krotscheck> But hey, we’re not the only service out there using this stack, so... 15:24:35 <krotscheck> Anyway, if there’s nothing else I’m ok just calling this meeting and letting everyone get back to work. 15:25:14 <NikitaKonovalov> krotscheck: agree 15:25:19 <krotscheck> Alright 15:25:24 <krotscheck> #endmeeting