| *** banix has joined #openstack-meeting-3 | 00:12 | |
| *** xuhanp has joined #openstack-meeting-3 | 00:39 | |
| *** mestery has joined #openstack-meeting-3 | 00:48 | |
| *** wchrisj has joined #openstack-meeting-3 | 00:56 | |
| *** xuhanp has quit IRC | 01:00 | |
| *** banix has quit IRC | 01:01 | |
| *** wchrisj has quit IRC | 01:32 | |
| *** carl_baldwin has joined #openstack-meeting-3 | 02:19 | |
| *** carl_baldwin has left #openstack-meeting-3 | 02:20 | |
| *** jcoufal has quit IRC | 02:28 | |
| *** coolsvap|afk is now known as coolsvap | 02:38 | |
| *** amotoki has quit IRC | 02:38 | |
| *** eghobo has joined #openstack-meeting-3 | 03:49 | |
| *** lpetrut has joined #openstack-meeting-3 | 04:10 | |
| *** eghobo has quit IRC | 04:37 | |
| *** eghobo has joined #openstack-meeting-3 | 04:38 | |
| *** eguz has joined #openstack-meeting-3 | 04:40 | |
| *** rand738 has quit IRC | 04:43 | |
| *** rand738 has joined #openstack-meeting-3 | 04:43 | |
| *** eghobo has quit IRC | 04:44 | |
| *** ttrifonov is now known as ttrifonov_zZzz | 06:16 | |
| *** lpetrut has quit IRC | 06:17 | |
| *** amotoki has joined #openstack-meeting-3 | 06:24 | |
| *** jtomasek has joined #openstack-meeting-3 | 06:59 | |
| *** jtomasek_ has joined #openstack-meeting-3 | 07:01 | |
| *** jtomasek_ has quit IRC | 07:02 | |
| *** ttrifonov_zZzz is now known as ttrifonov | 07:13 | |
| *** jcoufal has joined #openstack-meeting-3 | 07:22 | |
| *** jtomasek has quit IRC | 07:23 | |
| *** jtomasek has joined #openstack-meeting-3 | 07:23 | |
| *** lpetrut has joined #openstack-meeting-3 | 07:33 | |
| *** nacim has joined #openstack-meeting-3 | 07:37 | |
| *** eguz has quit IRC | 07:50 | |
| *** MaxV has joined #openstack-meeting-3 | 08:11 | |
| *** lpetrut has quit IRC | 08:15 | |
| *** alexpilotti has joined #openstack-meeting-3 | 08:16 | |
| *** lpetrut has joined #openstack-meeting-3 | 08:33 | |
| *** lpetrut has quit IRC | 09:27 | |
| *** david-lyle has joined #openstack-meeting-3 | 10:46 | |
| *** coolsvap is now known as coolsvap|afk | 10:52 | |
| *** amotoki has quit IRC | 11:28 | |
| *** david-lyle has quit IRC | 11:41 | |
| *** enikanorov has quit IRC | 12:04 | |
| *** enikanorov has joined #openstack-meeting-3 | 12:04 | |
| *** YorikSar has left #openstack-meeting-3 | 12:18 | |
| *** xuhanp has joined #openstack-meeting-3 | 12:36 | |
| *** MaxV has quit IRC | 12:53 | |
| *** MaxV has joined #openstack-meeting-3 | 12:54 | |
| *** mfer has joined #openstack-meeting-3 | 12:55 | |
| *** banix has joined #openstack-meeting-3 | 13:19 | |
| *** HenryG has quit IRC | 13:21 | |
| *** mwagner_lap has quit IRC | 13:39 | |
| *** enikanorov_ has joined #openstack-meeting-3 | 13:57 | |
| *** mestery_ has joined #openstack-meeting-3 | 13:58 | |
| *** mestery has quit IRC | 13:58 | |
| *** wchrisj has joined #openstack-meeting-3 | 13:58 | |
| *** enikanorov has quit IRC | 13:59 | |
| *** wchrisj has quit IRC | 14:31 | |
| *** wchrisj has joined #openstack-meeting-3 | 14:32 | |
| *** mestery_ is now known as mestery | 14:32 | |
| *** jpomero has joined #openstack-meeting-3 | 14:32 | |
| *** amotoki has joined #openstack-meeting-3 | 14:47 | |
| *** HenryG has joined #openstack-meeting-3 | 14:48 | |
| *** banix has quit IRC | 14:54 | |
| *** cjellick has joined #openstack-meeting-3 | 14:54 | |
| *** cjellick has quit IRC | 14:56 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 14:58 | |
| *** corvus has joined #openstack-meeting-3 | 14:59 | |
| krotscheck | Who’s here for Storyboard? | 15:00 |
|---|---|---|
| ttx | o/ | 15:00 |
| krotscheck | #startmeeting Storyboard | 15:00 |
| openstack | Meeting started Mon Apr 14 15:00:42 2014 UTC and is due to finish in 60 minutes. The chair is krotscheck. Information about MeetBot at http://wiki.debian.org/MeetBot. | 15:00 |
| openstack | Useful Commands: #action #agreed #help #info #idea #link #topic #startvote. | 15:00 |
| NikitaKonovalov | hi everyone | 15:00 |
| corvus | hi | 15:00 |
| *** openstack changes topic to " (Meeting topic: Storyboard)" | 15:00 | |
| openstack | The meeting name has been set to 'storyboard' | 15:00 |
| krotscheck | Hey hey | 15:00 |
| krotscheck | #topic Work on Soft/Hard delete. | 15:01 |
| *** openstack changes topic to "Work on Soft/Hard delete. (Meeting topic: Storyboard)" | 15:01 | |
| * corvus is aka jeblair | 15:01 | |
| krotscheck | Quick update: We’ve got a patch in for tasks | 15:01 |
| krotscheck | thanks to NikitaKonovalov | 15:01 |
| SergeyLukjanov | o/ | 15:01 |
| krotscheck | I’ve got a broken tasks for stories. | 15:01 |
| krotscheck | Sorry | 15:01 |
| krotscheck | Broken patch | 15:01 |
| krotscheck | Anyone been working on projects? | 15:01 |
| krotscheck | Guess not. | 15:02 |
| *** cjellick has joined #openstack-meeting-3 | 15:02 | |
| krotscheck | Well, mordred went through and deleted all the not-using-storyboard tasks on thursday, so that might not come up for a while yet. | 15:02 |
| *** sdague has joined #openstack-meeting-3 | 15:02 | |
| krotscheck | #topic Last meeting agenda | 15:03 |
| *** openstack changes topic to "Last meeting agenda (Meeting topic: Storyboard)" | 15:03 | |
| krotscheck | Sorry, that’s a more appropriate topic. | 15:03 |
| *** cjellick has quit IRC | 15:03 | |
| krotscheck | Re: UX/UI resources, I’m in contact with HP’s internal resources, but they’’re just now hiring up that team, so unlikely to get much help re testing labs, etc from there. | 15:03 |
| krotscheck | Re: ElasticSearch/Sphinx. | 15:03 |
| *** cjellick has joined #openstack-meeting-3 | 15:03 | |
| krotscheck | NikitaKonovalov did a really good analysis of the advantages of ES | 15:04 |
| krotscheck | #link https://etherpad.openstack.org/p/Storyboard_ES | 15:04 |
| NikitaKonovalov | I guess we are considering only ES now, no Sphinx anymore | 15:05 |
| corvus | krotscheck: did you get input from clarkb and mordred? | 15:05 |
| krotscheck | I took the time to talk to mordred about that as well, and between NikitaKonovalov and mordred’s comments it quickly came out that everyone (in OS) is using ES, and nobody seems to be using sphinx. | 15:05 |
| corvus | krotscheck: who is 'everyone'? | 15:05 |
| krotscheck | I didn’t have the time to talk to clarkb - mostly because clarkb was in HeartBleed hell. | 15:05 |
| krotscheck | corvus: Well, ruhe did a search across the openstack codebase and couldn’t find any references to sphinx | 15:06 |
| krotscheck | So “everyone” to me means “the skill set in openstack seems to be heavily biased towards elastic search" | 15:06 |
| krotscheck | In short: We have a bunch of information on the ES side, but little on sphinx. | 15:07 |
| corvus | krotscheck: right, but we can't expect those people to just show up and start working on this; there's typically very little overlap. moreover, they're extremely unlikely to show up and run it... | 15:07 |
| krotscheck | So I’m not quite comfortable making a decision on that yet without additional ideas of what sphinx would buy us. | 15:07 |
| corvus | we should also consider things like ease of deployment, extra dependencies for people running it, resources needed, administration, etc | 15:08 |
| NikitaKonovalov | corvus: how hard is it to start a minimal ES installation? | 15:08 |
| * ruhe is here | 15:08 | |
| krotscheck | corvus: I’m less concerned with them “running it”, and more of “Who can we annoy with questions when we try to build up our own skills in that area” | 15:08 |
| ruhe | to start local ES for development you need three steps: 1. download archive 2. unpack it 3. run shell command | 15:08 |
| corvus | NikitaKonovalov: i don't know actually. the only one i've seen in practice falls over all the time and consumes about 0.5fte just to keep it running. | 15:09 |
| krotscheck | corvus: Sounds like you’re pretty invested in making sure that we make the right decision here, would you like to come up with an etherpad of pro/con arguments and make a recommendation? | 15:09 |
| krotscheck | As I said, so far we’ve only got half of the picture. | 15:09 |
| krotscheck | (or one third, or one fourth, given that there may be other solutions we’re not considering) | 15:10 |
| corvus | krotscheck: i don't have time for that in the next several weeks. i think we should consult clarkb on es... | 15:10 |
| corvus | krotscheck: what did you learn from mordred about sphinx? | 15:10 |
| krotscheck | Given that the person I was going to ask about sphinx basically said : Ehn, everyone else is using elasticsearch... | 15:10 |
| krotscheck | corvus: ^ | 15:11 |
| krotscheck | I can dig through those logs. | 15:11 |
| corvus | krotscheck: so we'll learn a lot just by asking clarkb. i expect he'll say one of "no way man i'm not running another one of those" or "sure, a small one will probably be fine". and then we'll have the ops story. :) | 15:12 |
| krotscheck | Extract more information, but the only meaningful statement about sphinx was that it was the de-facto standard back when mordred was an sql consultant. | 15:12 |
| corvus | if anyone else knows someone who has run a small-scale es, that would be great to know. | 15:12 |
| krotscheck | corvus: Well, I want to make sure that storyboard is as self-contained as possible, right? | 15:12 |
| krotscheck | Requiring a large dedicated ops team doesn’t lead to easy adoption inside of orgs, etc etc... | 15:13 |
| krotscheck | But yeah, I’ll check with clarkb | 15:13 |
| corvus | krotscheck: exactly; i think we should target being able to run this all on a single modest server | 15:13 |
| krotscheck | Ok, so ES/Sphinx investigation to continue. | 15:14 |
| corvus | (for a small set of projects; and scale up after that) | 15:14 |
| NikitaKonovalov | Anyway, we may say that ES is optional and servers for a performance | 15:14 |
| NikitaKonovalov | If some one does not use it then fall back to sql | 15:14 |
| corvus | NikitaKonovalov: oh that makes sense; would you fall back on a full table scan? | 15:14 |
| corvus | ok cool | 15:14 |
| * corvus reads etherpad quickly | 15:14 | |
| krotscheck | Ok, so that’s an appropach should we decide to go with ES | 15:14 |
| * krotscheck speak good engrish | 15:15 | |
| corvus | i wonder if we could trigger a background es update from the api? | 15:16 |
| krotscheck | Honestly, search isn’t a super pressing issue _yet_, since at best we’re a week out of actually implementing it, but let’s all keep it in mind as we continue. | 15:16 |
| krotscheck | Anything else re: es/sphinx? | 15:16 |
| corvus | so we're not blocking like the explicit flow | 15:16 |
| corvus | and we don't have to wait for esriver | 15:16 |
| NikitaKonovalov | corvus: we can use evenetlet or even another process to do that | 15:17 |
| corvus | NikitaKonovalov: cool. maybe we could start with explicit but then make that a future enhancement for performance... | 15:17 |
| corvus | oh, i just noticed the 'updated_at' part of es river | 15:18 |
| corvus | that might not be so bad then. | 15:18 |
| krotscheck | With any luck, we’ll be able to reduce the number of search queries anyway by being smart about determining what’s relevant to a particular user. | 15:19 |
| corvus | i think i still lean toward explicit or something like it because it's simpler (fewer dependencies) | 15:19 |
| corvus | heh, i can't really decide between those two; i'll keep thinking about it :) | 15:20 |
| krotscheck | Feels like y’all want to do some design discussion, let’s put search into the design discussion list and move on to the MVP 1.01 topics ttx didn’t get around to last time. | 15:20 |
| corvus | krotscheck: ++ | 15:20 |
| krotscheck | #topic Stories with all alnded tasks should not be in primary UI filter | 15:20 |
| *** openstack changes topic to "Stories with all alnded tasks should not be in primary UI filter (Meeting topic: Storyboard)" | 15:20 | |
| krotscheck | So, I’m working on that right now. | 15:21 |
| krotscheck | Because it annoys the living daylights out of me. | 15:21 |
| krotscheck | My current approach is…. | 15:21 |
| krotscheck | Well, I’d like some feedback on it. | 15:21 |
| ttx | FTR the MVP 1.01 stuff are all the things I *think* would make a better experience at our early dogfooding stage | 15:21 |
| krotscheck | ttx: before I continue too much down that road, could you look at the patch and see if it does what you want it to? | 15:21 |
| ttx | feel free to add more stuff to it | 15:21 |
| krotscheck | #link https://review.openstack.org/#/c/86452/ | 15:22 |
| ttx | krotscheck: sure | 15:22 |
| ttx | might not manage to get to it today though | 15:22 |
| ttx | this week is a bit busy | 15:22 |
| krotscheck | ttx: That’s ok, I don’t know why it’s breaking anyway :) | 15:22 |
| corvus | of the things in ttx's list, the ones i most feel the need for are: ui filter, assignments, story activity | 15:23 |
| krotscheck | kk | 15:23 |
| corvus | one that i would like to add is: some kind of priority. | 15:23 |
| krotscheck | “Tasks can’t be edited” is done. | 15:23 |
| ttx | the projectgroup thing makes a better experience for storyboard specifically, since that allows to see "all of it" | 15:23 |
| corvus | i'm not sure where the priority discussions ended up at; i wasn't keeping up with that... | 15:23 |
| ttx | but it's useless without the ui filter | 15:23 |
| NikitaKonovalov | krotscheck: it should be easy to filter completed tasks on server side, and have a fetch_all_flag to get all the rest | 15:24 |
| ttx | priority handling is still a bit up in the air | 15:24 |
| krotscheck | You have to click on the actual task to bring up the edit form, so the UI needs to change, but you can do it. | 15:24 |
| krotscheck | Ok, guys. One topic at a time please. | 15:24 |
| ttx | I mean, we know how to do it the dumb way (high/medium/low) | 15:24 |
| * ttx freezes | 15:24 | |
| krotscheck | corvus: ttx I agree that priority should probably be mvp 1.01 | 15:25 |
| ttx | krotscheck: i'll mark it done | 15:25 |
| krotscheck | Anyone else? | 15:25 |
| *** coolsvap|afk is now known as coolsvap | 15:25 | |
| ttx | krotscheck: the ideas we had for "priority" were a bit ambitious, with crazy kanbans and stuff :) | 15:26 |
| krotscheck | Sorry, edited agenda | 15:26 |
| krotscheck | Ok | 15:26 |
| krotscheck | Support for Project Groups | 15:26 |
| krotscheck | #topic Support for Project Groups | 15:26 |
| *** openstack changes topic to "Support for Project Groups (Meeting topic: Storyboard)" | 15:26 | |
| ttx | project group is a key feature as we add more projects | 15:26 |
| ttx | at this point it's only useful to see storyboard (two projects) in one shot | 15:26 |
| krotscheck | ttx: How many levels deep were you thinking on that? | 15:26 |
| ttx | krotscheck: you mean, shall we have groups of groups ? | 15:27 |
| NikitaKonovalov | ttx: shoud those groups match OS Programs | 15:27 |
| krotscheck | ttx: Yeah, for instance: We could have “Openstack-Infra” as a group, “Storyboard” as a subgroup, etc. | 15:27 |
| NikitaKonovalov | if so, let's call them programs also? | 15:27 |
| corvus | NikitaKonovalov: that's a neat idea | 15:28 |
| ttx | krotscheck: in my view we can model everything with a single level | 15:28 |
| krotscheck | Works for me | 15:28 |
| ttx | i/e/ storyboard-webclient would be part of several groups ("storyboard", infra, official openstack stuff, etc) | 15:28 |
| krotscheck | Gotit | 15:28 |
| ttx | that said, groups of groups would make specifying those groups easier | 15:28 |
| ttx | i.e. if you add a project to "infra" it could automatically appear in "official stuff" | 15:29 |
| ttx | so I can see the benefit of that | 15:29 |
| krotscheck | Yeah, but if one project can be a part of many groups, then we could have a parent group composed of subgroups and individual projects, and quite frankly that’s a set of edge cases that may be a little too complex for how young the project is. | 15:29 |
| ttx | the only "needed" part is the ability for one project to belong to multiple groups | 15:29 |
| * krotscheck is just trying to keep our features and commits digestible :) | 15:30 | |
| ttx | because some of them just won't be a subgroup of another | 15:30 |
| ttx | for example you could have a "UI project group" that goes Horizon, Storyboard-webclient etc | 15:30 |
| krotscheck | Oh man, that would make me so happy | 15:30 |
| krotscheck | I could create a “Javascript only” project group and ignore all the silly python stuff. | 15:31 |
| krotscheck | :D | 15:31 |
| corvus | i agree, groups of groups would be nice; we can probably start with just direct membership and expand it later | 15:31 |
| ttx | krotscheck: ideally we would also support "personal project groups" which would be like your personal list | 15:31 |
| corvus | should just need an extra mapping table | 15:31 |
| krotscheck | Alright, so any disagreements with keeping project groups in MVP 1.01? | 15:31 |
| ttx | that can be baked into the same system, or be done more like a subscription thing | 15:31 |
| corvus | (gerrit lets you compose group membership, and we use it quite often) | 15:31 |
| krotscheck | corvus: You suggested that it might be less important than UI filter, activity, and assignments? | 15:32 |
| corvus | ttx: ++; i lean toward subscription there for ease of end-user use | 15:32 |
| corvus | krotscheck: only because we only have 4 projects now, but yes | 15:32 |
| krotscheck | Subscription is definitely a better metaphor. | 15:32 |
| ttx | krotscheck: I think projectgroup is not very useful until we have ui filter | 15:32 |
| krotscheck | kk | 15:32 |
| krotscheck | But still MVP 1.01? | 15:33 |
| krotscheck | Or not? | 15:33 |
| ttx | the idea being to get to the relevant information | 15:33 |
| ttx | for me yes | 15:33 |
| krotscheck | corvus? | 15:33 |
| krotscheck | NikitaKonovalov? | 15:33 |
| krotscheck | SergeyLukjanov? ^ | 15:33 |
| NikitaKonovalov | agree | 15:33 |
| corvus | krotscheck: yes, we'll be able to use it in mvp1.01 when it exists | 15:33 |
| ttx | juggling between storyboard and storyboard-webclient is my #1 pain with SB at the moment | 15:33 |
| krotscheck | ok | 15:33 |
| ttx | so projectgroup would fix that for me | 15:33 |
| krotscheck | ttx: Quick side question: Is that for creating tasks, or for listing things? | 15:33 |
| ttx | for listing things. Tasks should always point to a specific project | 15:34 |
| krotscheck | kk | 15:34 |
| krotscheck | Good to know. | 15:34 |
| krotscheck | Ok, Project groups stays in MVP 1.01 | 15:34 |
| krotscheck | #topic Story Activity | 15:34 |
| *** openstack changes topic to "Story Activity (Meeting topic: Storyboard)" | 15:34 | |
| SergeyLukjanov | probably we should start from simple filtering on ui | 15:34 |
| krotscheck | SergeyLukjanov: I agree. | 15:34 |
| ttx | I added this one because it's still difficult to follow what happens on a story | 15:35 |
| * SergeyLukjanov batch processing meeting logs like Hadoop | 15:35 | |
| ttx | status changes, who did what is as valuable as the discussion | 15:35 |
| ttx | we can emulate it by leaving comments, but the time info is still missing | 15:35 |
| NikitaKonovalov | ttx: yes, but should it be mixed with comments in one flow? | 15:36 |
| krotscheck | ttx: Part of me thinks that this is a part we really should give a lot of design attention to, because it’s going to be the primary way in which we engage our users. | 15:36 |
| ttx | NikitaKonovalov: that would be my preference, I think. Could be convinced otherwise I guess | 15:36 |
| krotscheck | Deltas on tasks and stories are going to drive things like emails, notifications, etc. | 15:36 |
| ttx | usually a comment can only be parsed as part of the story history | 15:37 |
| ttx | reading comments out of context of what happened to that story would imho be difficult | 15:37 |
| ttx | but maybe I'm spoiled with Launchpad habits here | 15:38 |
| NikitaKonovalov | so we are replicating LP behavior as is | 15:38 |
| ttx | so I'm willing to hear alternate suggestions | 15:38 |
| NikitaKonovalov | I didn't say it's bad | 15:38 |
| krotscheck | I haven’t thought enough about the problem to have alternate suggestions. | 15:38 |
| krotscheck | But I really want to have them. | 15:38 |
| corvus | ttx: i like the updates in comments flow; if we put enough metadata in the db, we can change it later | 15:39 |
| *** banix has joined #openstack-meeting-3 | 15:39 | |
| ttx | I think they should appear in the same timeline -- we could have timeline filters if people really don't want to see certain things in that | 15:39 |
| corvus | but maybe planning for that basic functionality now is a reasonable approach | 15:39 |
| SergeyLukjanov | personally, I like the LP-way with status change == comment but with ability to filter only service comments | 15:39 |
| NikitaKonovalov | ttx: +1 for filtering comments | 15:39 |
| ttx | but I never heard the complaint that LP discussion contained extraneaous info | 15:39 |
| ttx | krotscheck: would you keep both comments and activity in the same table, or try to mix two tables ? | 15:40 |
| krotscheck | ttx: Honestly, I agree with you on UI completely, I just have strong opinions about the implementation. | 15:40 |
| corvus | krotscheck: in what way? | 15:41 |
| krotscheck | I feel that it should be modeled as a stream of events of different types, which then carry with them references to the appropriate records. | 15:41 |
| krotscheck | I don’t feel overloading the comments table is the right way to go about it. | 15:41 |
| krotscheck | And that a story event could be, say “status changed”, or “comment, status changed”, etc etc. | 15:41 |
| ttx | krotscheck: fair enough. i just fear we would duplicate the comment in the activity table saying "dude left a comment" | 15:41 |
| corvus | krotscheck: so a timeline with ids and timestamps, and then 'comment' and 'event' tables link to that? | 15:41 |
| ruhe | jira has a nice way to separate different type of events/comments. it has a tab for full-history changes, tab for user comments, tab for status changes | 15:42 |
| krotscheck | corvus: ….maaaybe. | 15:42 |
| krotscheck | corvus: As I said, haven’t had much time to think it through. | 15:42 |
| NikitaKonovalov | krotscheck: possibly a TimelineEvent table for status changes, and comment_id field to link a comment to it | 15:42 |
| krotscheck | corvus: Immediate concerns are holy crap big table of ID’s is that going to be performant | 15:42 |
| ttx | krotscheck: don't have strong opinions on how to do it under the hood. I think by default it should show up in the same timeline, but that's about it | 15:43 |
| krotscheck | NikitaKonovalov: Yeah, something like that. | 15:43 |
| ttx | krotscheck: oh, one thing | 15:43 |
| krotscheck | Yes | 15:43 |
| krotscheck | ? | 15:43 |
| ttx | krotscheck: in LP there was the ability to leave a comment when you changed status, like to justify your change | 15:43 |
| corvus | krotscheck: ok. i don't have terribly strong feelings about the implementation at this point; i do think we all agree that what's stored in the db should be expressive enough to support the kind of filtering,etc we might want to do later | 15:44 |
| ttx | and then it would appear on the same event in the timeline | 15:44 |
| krotscheck | ttx: Yeah, already flagged that as a consideration. | 15:44 |
| ttx | It was a good thing because it forced people to explain why they had changed something | 15:44 |
| ttx | I fear if we sperarate them too much we would encourage the wrong behavior | 15:44 |
| krotscheck | ttx: That’ll be interesting to figure out since status happens on tasks and comments happen on stories :) | 15:44 |
| krotscheck | ttx: And it’s not very RESTful to modifiy two resources in one call :) | 15:45 |
| *** enikanorov_ has quit IRC | 15:45 | |
| ttx | yes, that'w why I bring it up. I hope we can preserve it, but it may not fit that well | 15:45 |
| krotscheck | ttx: I feel we SHOULD preserve that, even if it doesn’t fit well. | 15:45 |
| krotscheck | But given those constraints I think we can figure something out. | 15:45 |
| ttx | for example, someone removing a task should almost always explain why | 15:45 |
| ttx | because otherwise you just don't understand what happened | 15:46 |
| ttx | he could leave a comment after the fact... but good UI would let him do it in one go. Might be a REST nightmare with two calls :) | 15:46 |
| krotscheck | Ok, so summary sounds like: “Yes we all want this, possibly in one filterable timeline, but design needs some offline gray metter.” Sound about right? | 15:46 |
| corvus | ayup | 15:46 |
| ttx | ayup | 15:46 |
| krotscheck | Alright. | 15:46 |
| NikitaKonovalov | lgtm | 15:46 |
| SergeyLukjanov | +1 | 15:47 |
| krotscheck | Honestly, I don’t think we have enough people right now to assign someone to it. | 15:47 |
| krotscheck | At least not before next monday | 15:47 |
| krotscheck | #agreed We all want a story timeline/activity history, possibly in one filterable timeline, but design and implementation needs oflfine gray matter | 15:47 |
| ttx | arguably less urgent than the ui filter | 15:48 |
| krotscheck | ttx: Yeah, taht’s why I’m focused on that :) | 15:48 |
| krotscheck | Actually, NikitaKonovalov, what are you working on right now? | 15:48 |
| krotscheck | Want to take this on? | 15:48 |
| NikitaKonovalov | I'll take it | 15:48 |
| krotscheck | Awesome. | 15:48 |
| krotscheck | #action NikitaKonovalov Implement story actions/timelines | 15:48 |
| krotscheck | Ok, next topic | 15:49 |
| krotscheck | #topic Story priority | 15:49 |
| *** openstack changes topic to "Story priority (Meeting topic: Storyboard)" | 15:49 | |
| * krotscheck unfreezes ttx | 15:49 | |
| ttx | story priority? | 15:49 |
| ttx | ok... | 15:49 |
| ttx | that's one of the areas where we actually want to get smarter than Launchpad | 15:50 |
| *** ttrifonov is now known as ttrifonov_zZzz | 15:50 | |
| ttx | and let different groups of stakeholders have different priorities for stuff | 15:50 |
| ttx | trick is it's easily said, not so easy to design | 15:50 |
| ttx | My last try at it was at https://wiki.openstack.org/wiki/StoryBoard/Task_Lists | 15:51 |
| krotscheck | #link https://wiki.openstack.org/wiki/StoryBoard/Task_Lists | 15:51 |
| ttx | i.e. use several ordered task lists instead of a "priority" | 15:51 |
| ttx | so let's take a practical example | 15:51 |
| krotscheck | ok | 15:51 |
| ttx | for that MVP 1.01 | 15:51 |
| krotscheck | (quick aside: I can probably knock out Task Assignments pretty quickly, I think it’s already supported by the API) | 15:52 |
| ttx | we could have had a task list where we would have listed all the things we want there, and then play with their ordering | 15:52 |
| krotscheck | (since we’re running low on time) | 15:52 |
| ttx | (relative priotity by ranking) | 15:52 |
| ttx | It's a bit ambitious and we are not exactly following on clear footsteps here | 15:53 |
| NikitaKonovalov | krotscheck: the assignee_id is pretty availbel to use | 15:53 |
| ttx | so it might just be a bit crazy / unusable | 15:53 |
| ttx | It's also quite a bit of work to do the crazy trello-like UI | 15:53 |
| krotscheck | ttx: So, to me this sounds like priority is an integer rather than a specific status. | 15:54 |
| krotscheck | And that the basic UI decision is “This is more important/less important” than it currently is. | 15:54 |
| krotscheck | The question is whether we care about explicit priority, or relative priority. | 15:55 |
| ttx | krotscheck: right, but also priority is only relevant in the context of a specific task list | 15:55 |
| krotscheck | i.e. “This task is more important than that one” vs. “This is in the same group as these” | 15:55 |
| ttx | i.e. the priority for release management may not be the priority for the core devs etc. | 15:55 |
| corvus | (fwiw, i'm very open to experimentation here; i don't mind at all of we go through several completely different iterations. i'd rather have something sooner, even if we throw it out and have to reprioritize everything) | 15:56 |
| ttx | hence the idea of having multiple task lists, and infdicate priority by ordering that subset of tasks | 15:56 |
| krotscheck | ttx: How many different task lists do you think there will be? | 15:56 |
| ttx | krotscheck: i expect people to have their own task list, then at least one project-level one for milestone planning | 15:57 |
| *** xuhanp has quit IRC | 15:57 | |
| ttx | but i also expect people to run with them and start listing their little group priority | 15:57 |
| SergeyLukjanov | sorry for offtopic: any thoughts when we could add subscriptions? | 15:57 |
| ttx | (see types of task lists in the wiki doc) | 15:57 |
| krotscheck | We have two minutes | 15:58 |
| krotscheck | SergeyLukjanov: As soon as someone builds it :). Which, given our current backlog, looks about… 3 weeks? | 15:58 |
| ttx | krotscheck: to simplify first I would keep task lists at the project level | 15:58 |
| krotscheck | ttx: Ok, priority by project first. | 15:58 |
| krotscheck | Check | 15:58 |
| ttx | i.e. a project could have multiple task lists in a table | 15:59 |
| krotscheck | FTR: I love having personal vs. project priority | 15:59 |
| ttx | krotscheck: might be worth baking in a personal task list (same as the personal project group) | 15:59 |
| krotscheck | Yeah, but not MVP 1.01 :) | 16:00 |
| NikitaKonovalov | krotscheck: do you mean the tasks that you have created have a bigger priority than other in the same project? | 16:00 |
| ttx | Oh sure, I'm not sure we can do something with priority in 1.01 :) | 16:00 |
| krotscheck | Honestly, this is one place where not having FK’s is going to be magical, because we can do fun overloady thingies in the ORM. | 16:00 |
| ttx | task lists could also live at projectgroup level, fwiw | 16:00 |
| ttx | i.e. "storyboard priorities" rather than "storyboard-webclient priorities"' | 16:01 |
| krotscheck | Anyway, we’re out of time. Any last comments before we get kicked out? | 16:01 |
| *** jcoufal has quit IRC | 16:01 | |
| corvus | ttx: :( we need some kind of priority soon | 16:01 |
| ttx | nope thx! | 16:01 |
| ttx | corvus: 1.02? | 16:01 |
| krotscheck | corvus: We can do a really stupid task-level priority to start with if you need something RTFN | 16:02 |
| corvus | i find it _very_ hard to work without some kind of sorting | 16:02 |
| ttx | corvus: maybe it can be done incrementally, starting with a unique per-project list | 16:02 |
| corvus | krotscheck: yeah, anything would help :) | 16:02 |
| *** coolsvap1 has joined #openstack-meeting-3 | 16:02 | |
| krotscheck | Ok, so let’s start with that for 1.01 and then give it some love next release | 16:02 |
| krotscheck | #endmeeting | 16:02 |
| *** openstack changes topic to "OpenStack Meetings || https://wiki.openstack.org/wiki/Meetings" | 16:02 | |
| openstack | Meeting ended Mon Apr 14 16:02:50 2014 UTC. Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4) | 16:02 |
| openstack | Minutes: http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-04-14-15.00.html | 16:02 |
| openstack | Minutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-04-14-15.00.txt | 16:02 |
| openstack | Log: http://eavesdrop.openstack.org/meetings/storyboard/2014/storyboard.2014-04-14-15.00.log.html | 16:02 |
| ttx | krotscheck: also we should hit all the weird stuff -- like the fact it's tasks you actually add to task lists, not stories :) | 16:03 |
| *** eghobo has joined #openstack-meeting-3 | 16:03 | |
| ttx | (see unsolved issues in the wiki page) | 16:03 |
| krotscheck | Got it | 16:03 |
| *** coolsvap1 has quit IRC | 16:03 | |
| *** coolsvap1 has joined #openstack-meeting-3 | 16:04 | |
| *** coolsvap1 has quit IRC | 16:08 | |
| *** nacim has quit IRC | 16:33 | |
| *** MaxV has quit IRC | 16:44 | |
| *** SumitNaiksatam has quit IRC | 16:56 | |
| *** corvus is now known as jeblair | 17:11 | |
| *** SumitNaiksatam has joined #openstack-meeting-3 | 17:12 | |
| *** eghobo has quit IRC | 17:12 | |
| *** eguz has joined #openstack-meeting-3 | 17:12 | |
| *** eguz has quit IRC | 17:12 | |
| *** eghobo has joined #openstack-meeting-3 | 17:13 | |
| *** MaxV has joined #openstack-meeting-3 | 17:15 | |
| *** MaxV has quit IRC | 17:23 | |
| *** SumitNaiksatam_ has joined #openstack-meeting-3 | 17:39 | |
| *** SumitNaiksatam has quit IRC | 17:39 | |
| *** SumitNaiksatam_ is now known as SumitNaiksatam | 17:39 | |
| *** enikanorov_ has joined #openstack-meeting-3 | 17:52 | |
| *** coolsvap is now known as coolsvap|afk | 17:54 | |
| *** ruhe has left #openstack-meeting-3 | 18:00 | |
| *** rand738 has quit IRC | 18:16 | |
| *** rand738 has joined #openstack-meeting-3 | 18:16 | |
| *** rand738 has quit IRC | 18:17 | |
| *** rand738 has joined #openstack-meeting-3 | 18:19 | |
| *** lpetrut has joined #openstack-meeting-3 | 18:21 | |
| *** jtomasek has quit IRC | 18:29 | |
| *** jtomasek has joined #openstack-meeting-3 | 18:38 | |
| *** eguz has joined #openstack-meeting-3 | 18:51 | |
| *** eghobo has quit IRC | 18:55 | |
| *** jcoufal has joined #openstack-meeting-3 | 18:57 | |
| *** baojg has joined #openstack-meeting-3 | 19:15 | |
| *** baojg has quit IRC | 19:15 | |
| *** baojg has joined #openstack-meeting-3 | 19:17 | |
| *** baojg has quit IRC | 19:18 | |
| *** enikanorov_ has quit IRC | 19:26 | |
| *** enikanorov_ has joined #openstack-meeting-3 | 19:27 | |
| *** MaxV has joined #openstack-meeting-3 | 19:37 | |
| *** MaxV has quit IRC | 19:43 | |
| *** MaxV has joined #openstack-meeting-3 | 19:44 | |
| *** MaxV has quit IRC | 19:45 | |
| *** jcoufal has quit IRC | 19:46 | |
| *** sarob has joined #openstack-meeting-3 | 19:53 | |
| *** jtomasek has quit IRC | 19:56 | |
| *** mwagner_lap has quit IRC | 20:22 | |
| *** sarob has quit IRC | 20:40 | |
| *** yamahata has joined #openstack-meeting-3 | 20:47 | |
| *** sarob has joined #openstack-meeting-3 | 20:49 | |
| *** Sukhdev has joined #openstack-meeting-3 | 20:57 | |
| *** markmcclain has joined #openstack-meeting-3 | 21:00 | |
| *** mfer has quit IRC | 21:01 | |
| *** MaxV_ has joined #openstack-meeting-3 | 21:09 | |
| *** ruhe has joined #openstack-meeting-3 | 21:10 | |
| *** lpetrut has quit IRC | 21:12 | |
| *** MaxV_ has quit IRC | 21:18 | |
| *** sarob has quit IRC | 21:28 | |
| *** MaxV_ has joined #openstack-meeting-3 | 21:49 | |
| *** Sukhdev_ has joined #openstack-meeting-3 | 21:55 | |
| *** Sukhdev__ has joined #openstack-meeting-3 | 21:57 | |
| *** Sukhdev_ has quit IRC | 21:57 | |
| *** Sukhdev has quit IRC | 21:58 | |
| *** markmcclain has quit IRC | 22:01 | |
| *** sarob has joined #openstack-meeting-3 | 22:02 | |
| *** sarob has quit IRC | 22:07 | |
| *** Sukhdev__ has quit IRC | 22:14 | |
| *** banix has quit IRC | 22:16 | |
| *** sarob has joined #openstack-meeting-3 | 22:21 | |
| *** sarob has quit IRC | 22:26 | |
| *** sarob has joined #openstack-meeting-3 | 22:37 | |
| *** sarob has quit IRC | 22:57 | |
| *** sarob has joined #openstack-meeting-3 | 22:57 | |
| *** MaxV_ has quit IRC | 23:00 | |
| *** yamahata has quit IRC | 23:01 | |
| *** sarob has quit IRC | 23:01 | |
| *** mwagner_lap has joined #openstack-meeting-3 | 23:11 | |
| *** MaxV_ has joined #openstack-meeting-3 | 23:31 | |
| *** MaxV_ has quit IRC | 23:37 | |
| *** yamahata has joined #openstack-meeting-3 | 23:47 | |
| *** yamahata has quit IRC | 23:56 | |
| *** wchrisj has quit IRC | 23:59 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!