Thursday, 2013-12-12

*** SergeyLukjanov has joined #storyboard05:17
*** SergeyLukjanov is now known as _SergeyLukjanov05:33
*** _SergeyLukjanov has quit IRC05:33
*** SergeyLukjanov has joined #storyboard05:51
*** SergeyLukjanov has quit IRC06:17
*** lifeless has quit IRC06:48
*** lifeless has joined #storyboard07:15
*** NikitaKonovalov has joined #storyboard07:27
*** SergeyLukjanov has joined #storyboard10:17
*** NikitaKonovalov has quit IRC10:42
*** drdee has quit IRC12:04
*** SergeyLukjanov is now known as _SergeyLukjanov12:54
*** _SergeyLukjanov has quit IRC12:54
*** NikitaKonovalov has joined #storyboard13:06
*** SergeyLukjanov has joined #storyboard13:23
*** gothicmindfood has joined #storyboard13:58
gothicmindfoodttx: hi there/ping!14:01
gothicmindfood(this is colette)14:01
ttxgothicmindfood: I figured as much14:01
ttxgothicmindfood: welcome14:01
gothicmindfoodthanks!14:01
ttxno cody?14:02
gothicmindfoodI don't know - mordred and cody are both in Barcelona this week14:02
ttxHah14:02
gothicmindfoodso they may or may not make it14:02
gothicmindfoodyou know, they have tapas to eat and stuff.14:02
ttxhmm14:02
ttxnomnom14:02
gothicmindfood:-)14:02
ttxit's like the only reason one would ever go to "HP discover"14:03
ttxanyone else for the storyboard meeting ?14:03
NikitaKonovalovhi14:03
SergeyLukjanovhey guys14:03
SergeyLukjanovwas AFK14:03
ttx3 makes a meeting14:04
ttx#startmeeting storyboard14:04
openstackMeeting started Thu Dec 12 14:04:00 2013 UTC and is due to finish in 60 minutes.  The chair is ttx. Information about MeetBot at http://wiki.debian.org/MeetBot.14:04
openstackUseful Commands: #action #agreed #help #info #idea #link #topic #startvote.14:04
openstackThe meeting name has been set to 'storyboard'14:04
ttxyay, a meeting bot14:04
ttxSince i didn't expect I would chair this, we don't have a meeting agenda14:04
ttxso it should be quick14:04
SergeyLukjanovcool, we have an own meeting channel :)14:04
ttx#topic gothicmindfood introductions14:04
ttxgothicmindfood: care to introduce yourself to our Russian friends ?14:05
gothicmindfoodha. Ok. Hi to everyone!14:05
gothicmindfoodI'm Colette and I'm a new hire at HP on mordred's team.14:05
gothicmindfoodhe brought me on (and we've got a couple others joining in the next week or so) to work on Storyboard.14:06
gothicmindfoodI'm not really a coder - I'm more of a process person, though I have a big interest in learning python and getting up to speed.14:06
ttxSergeyLukjanov, NikitaKonovalov: quick reverse intro ?14:06
mordredhey14:07
mordredsorry I'm late14:07
SergeyLukjanovttx, sure14:07
SergeyLukjanovmordred o/14:07
ttxmordred: howdy14:07
NikitaKonovalovhi14:07
ttxmordred: you don't have cody around, do you ?14:07
mordrednope. we may have gone drinking last night. he might be dead in a ditch in barcelona14:08
SergeyLukjanovI'm Sergey, PTL of Savanna, working in Mirantis and very interested in Storyboard14:08
SergeyLukjanov:)14:08
gothicmindfoodOh cool. Nice to meet you Sergey - were you in Hong Kong?14:08
SergeyLukjanovgothicmindfood, yep14:08
NikitaKonovalovI'm Nikita, I also work in Mirantis and contributed to Savanna project14:09
mordredI'm Monty, former PTL of Infra, I hire people to work on things - and I'm going to get storyboard stood up and working if it kills all of you :)14:09
NikitaKonovalovmostly to it's UI part14:09
gothicmindfoodI was too! Came to a couple of the Savanna sessions. Loved what I saw.14:09
ttxok, moving on14:09
ttx#topic Winter Storyboard sprint/meetup14:09
SergeyLukjanovgothicmindfood, glad to here that ;)14:09
ttxI have absolutely no news about that.14:09
ttxexcept that I proposed limited options14:10
mordredoh - you did? to dev list?14:10
mordredI may have missed that14:10
ttxone being to organize something around FOSDEM (Brussels, Feb 1-2)14:10
ttxmordred: private email to cody as requested14:10
mordredah. ok14:10
ttxthe other is to do something mid-February (week of 10 or 17)14:10
SergeyLukjanovttx, I really like the meetup in Europe :)14:11
ttxMy January filled up14:11
mordredI believe gothicmindfood is on tour in february14:11
gothicmindfoodMy February post February 3rd is no good14:11
gothicmindfoodbut if I got back to NYC on the 3rd, I could be okay14:11
mordredgothicmindfood: how about Feb 1/2 in brussels? perhaps meet the day before?14:11
mordredlike, Jan 31 ish14:12
ttxyes, we could do a 2-day before the weekend, then you can leave on Sunday (2nd)14:12
gothicmindfoodThat would  be good. I'd have to figure out how to get my cello to NYC without me, or just do a fly back to SFO to pick it up before going back to NYC.14:12
gothicmindfoodthe 29th/30th could be better just to give me cello-pick-up time.14:12
ttxalso, beers++ and FOSDEM++14:12
gothicmindfoodand I go home on the 2nd early, go to NYC on the 3rd14:12
gothicmindfoodbeers++ and mussels++++14:13
ttxlater options are scarce, as I enter what's known as the reelase-summit spiral of doom14:13
ttxonly to be out of it in... late May14:13
gothicmindfoodttx: can we get you some medication to help alleviate the symptoms of that? ;-)14:14
mordredhehe14:14
mordredwe call that wine14:14
ttxit would probably interact with all the drugs I already have to take to duplicate myself in two places14:14
mordredI need to check on budgets at HP to see if we can all commit to being there14:14
ttxwine is part of it14:14
gothicmindfoodmordred and I should go splitsies on a case of burgundy for you.14:14
mordredbut I think functionally it seems doable14:14
ttxgothicmindfood: one interesting thing with Brussels is I travel by train, which makes bringing wine a much more realistic option14:15
ttxalthough wine in brussels is like having beer in spain. Wrong.14:15
ttxmordred: I expect cody has details on everyone's availability by now14:16
gothicmindfoodttx: I will trade you any weird american thing I can get on a plane for some decent Morgon. Always, fwiw.14:16
SergeyLukjanovmordred, I need to check budget too14:16
ttxok, moving on then14:16
ttx#topic Early objectives14:17
ttxSo, the trick at this point is to make progress that will still be useful once we make drastic changes14:17
ttxI wouldn't invest too much in UI polish (like those error messages you proposed, NikitaKonovalov)14:18
ttxbecause they might just get completely removed if/when we switch to SemanticUI14:18
ttxsearch is still very useful because it's so much missing from the prototype it's not even funny14:18
mordred++14:18
mordredsearch  - thank you14:19
SergeyLukjanovthe very simple improvements could be useful for using storyboard to track storyboard work14:19
ttxbut I think the decoupling of the backend / RESTification is what we should be focusing on right now14:19
mordredthat's a good point14:19
SergeyLukjanovttx, agreed, that's what I'd like to see :)14:19
mordredCD is my number one goal - I want to get one up and running soon14:19
mordredbut14:19
mordredI did this: https://github.com/emonty/stories14:19
mordredwhich is a split out of the DB into sqlalchemy/alembic14:20
mordredso it's set up for migrations, whcih means CD is possible14:20
mordredI think actually what I should do is take that and make it a patch to storyboard14:20
ttxmordred: could you explain how it works a bit more ?14:20
ttxit's just the DB being split ?14:20
mordredit's just the db models14:20
mordredyes14:20
SergeyLukjanovis it possible to use sqla in django?14:21
ttxmordred: does it need to stand alone ?14:21
NikitaKonovalovit is14:21
* SergeyLukjanov not really aware about how django works14:21
NikitaKonovalovbut do we really need to stick sqlalchemy?14:21
mordredit does not need to stand alone - I think it should just go back into our main tree14:21
mordredand be used as model library14:21
gothicmindfoodDo we have a free-standing non-code version of the data-model floating around anywhere?14:22
ttxmordred: so that means we don't use django model anymore -- do we also lose the automagic admin/ stuff ?14:22
mordredI do not want to marry ourselves too much to django way of thinking, because we don't have good openstack integration that way14:22
mordredhoirizon is an outlier14:22
ttxor does django just falls back onto its 4 feets ?14:22
mordredI'd rather we have sqlalchemy and alembic and pecan/wsme like the other projects14:22
mordredttx: we do lose admin that way - but I don't care, because I don't want to use that14:23
mordredwe want to get projects into storyboard with manage-projects/projects.yaml anyway14:23
mordredso before we ahve a rest api for that14:23
ttxmordred: so.. if we build the UI on top of a REST client, we'll need two components anyway14:23
NikitaKonovalovstill I have seen a kind of Django-sqlalchemy binding library which may be helpful before moving to wsme14:23
mordredjust having an import thing that can read projects.yaml and insert it into the db is all we need14:23
mordredttx: sure - but we can do that piece meal14:24
mordredif we have the model in the repo using sqlalchemy, but the rest of the app is consuming it via python classes14:24
mordredwe can ADD a pecan rest api14:24
ttxshould we make that split (Db+REST server / REST client / UI) earlier rather than later ?14:24
mordredand then start replacing the python db calls with rest calls14:24
mordredI think we can do it gradually.14:24
mordredI don't tihnk it's essential for us to make a big switch14:24
ttxshould it live all in same repo ?14:24
ttxs/should/can14:24
mordredfor now, yes14:24
mordredbecaus SANITY14:25
mordredwe'll go crazy if we try to do a 3 repo split at this point14:25
mordredNikitaKonovalov: neat! that might be a good middle step!14:25
ttxso we would start the backend/pecan server on one side and start the django app on the other, but they could just live in same repo. OK14:25
mordredyup. and the django app might not even talk to the wsme server at first :)14:26
NikitaKonovalovthere is no client now, so it may start from scratch in a separate repo14:26
mordredthat is a great point14:26
ttxso one thing we could start working on is a API14:26
ttxbecause so far this has been mostly model-driven14:27
ttxand then UI-driven14:27
ttxwhereas the important piece in the final architecture is actually the API14:27
mordredyah. agree14:27
NikitaKonovalov+114:27
mordredI have an 8 hour plane flight tomorrow - I may take a first stab at one14:27
mordredand see what you guys thinmk14:27
mordred":)14:27
ttxand that's probably where process people like gothicmindfood can bring value without being too caught in technical implementation details14:28
ttxgothicmindfood: fwiw see work areas @ https://wiki.openstack.org/wiki/StoryBoard14:28
ttxApi would belong in "main concepts"14:28
ttxmordred's pilot work would rather be "Technical Architecture"14:29
gothicmindfoodthanks for that, ttx.14:29
ttxmordred: would be good to see what API we need for the current state14:30
ttxmordred: so yes, if you like to work in planes. Or are in a business seat14:30
mordredttx: I was thnking that would make for a great v1 api - purely functional, no 'good' design14:30
ttxI'll think about it too in my spare time14:31
mordredttx: then we can add a v2 api that is well designed, and then start rewriting the UI to consume it14:31
mordredyou have spare time?14:31
ttxthe danger, I think, is to start so high-level we can never make fast progress in evolving the current version14:31
ttxthis is, in essence, a Launchpad replacement. Not something that will revolutionize task/bug tracking14:32
ttxI mean, it may revolutionize, but that's for version 3.014:32
ttxWe need this thing now14:32
ttxand even if we do it "simple" it will be so much better than what we use now it's not even funny14:33
ttxthat doesn't mean we can't be smart while doing it. just means the smartness shouldn't delay us too much.14:34
gothicmindfoodout of curiosity, ttx: what's your timetable on having something useful to use with OS looking like?14:34
ttxI think we need to have openstack-ci and a few other guinea pigs up and running by the icehouse release14:35
ttxthen a significant subset of integrated/incubated projects by J release14:35
mordredI'd lie to be more aggressive14:36
mordredI'd like to do a forklift migratoin of everyone who isn't migrated already as the very first thing afer the J summit14:36
ttxby "need" I mean so that everyone retains its sanity. I expect LP usability to not go any better now that HP recruited one of the 2 last LP devs14:36
ttxthe last one is probably already looking for a job14:36
mordredI think that, other than infra and guinea pig projects, if we have parallel trackers per project, people will go insane14:37
ttxmordred: i want us to have a good story to sell to ALL projects by I so that we can get them moved over the J cycle14:37
mordredyes14:37
ttxnobody tells me "I like Launchpad and would like to keep it"14:38
gothicmindfoodttx: but some people do say it's the best bug tracker that they've used (despite its faults)14:38
ttxso if we do something not too bad, they will gladly switch14:38
gothicmindfoodno one likes their bug trackers14:38
gothicmindfoodever.14:38
mordredgothicmindfood: I've met that guy ... thierry I think is his name14:38
gothicmindfoodHA14:39
ttxgothicmindfood: it's the best, but mostly due to its model, I think. Not its UI14:39
ttxthe part of the model that made people like it, we already copied14:39
SergeyLukjanov:)14:39
mordred++14:39
mordredttx: btw - good work on the model14:39
ttxand extended where they failed to apply it (features)14:39
mordredI did not feel the need to make large changes when I was doing the sqla work14:40
ttxand then completed it (project groups just make sense)14:40
mordredand questions I had were answered by the model itself14:40
ttxmordred: the POC was just a Db model originally14:40
ttxthen without UI people would not have loved it14:40
mordredthe one thing it was missing was user/groups14:40
gothicmindfoodttx: understood, II just still think least-hated means it's valued. ;-)14:40
gothicmindfoodttx: dyou have a non-code data model map somewhere?14:41
mordredbut I believe that was just because you were using django auth stuff14:41
ttxgothicmindfood: certainly. people will realize it wasn't that bad once presented with an laternative14:41
mordredgothicmindfood: heh.14:41
gothicmindfoodttx: (2nd question: or can I make one??) ;-)14:41
ttxOur work is to make it "not suck" enough14:41
mordredgothicmindfood: make one all you want! I'll even look at it and tell you waht I think14:41
mordredttx: ++14:41
ttxgothicmindfood: I think NikitaKonovalov posted one14:42
NikitaKonovalovI made a wiki page a bit earlier https://wiki.openstack.org/wiki/StoryBoard/ObjectModel about the object14:42
ttxAlso there was one (now outdated) at https://wiki.openstack.org/wiki/Task_Tracker_Requirements14:42
mordredoh - neat. I hadn't seen that14:43
ttxgothicmindfood: that said we already have UX questions. Like "do we need to be able to mark tasks invalid/wontfix/opinion"14:43
mordredI should go and make sure that the new db code still maps to that14:43
ttxvs. just delete the invalid tasks14:44
ttxgothicmindfood: or Should priority be set for the whole story or per-task ?14:44
ttxthose are not critical, but still affect the model14:44
* mordred votes for task at the data model layer14:44
mordredbut - it's possible that we have a more somple ui that only shows it on the story for now, and that code sets the priority on every task on the story14:45
ttxsometimes they are simplicity vs. customizability decisions, and I don't care that much about them14:45
mordredyes14:45
mordredI think also - invalid vs. delete could also be a UI thing14:45
mordredwe could have an invalid status in the db14:45
mordredand have the UI 'delete' operation set that status and then never show invalid things14:46
mordredthat way we have complete data in the db for historical reasons should we want to analyze it - but don't have to do complex user workflows14:46
ttxbasically, there are a few things i'm very attached to (like obviously the task/story layer), but a lot of others I'm very open about (UI framework, RESt decoupling, priority per task or per-story, etc.)14:46
gothicmindfoodttx: any reason we can't have story priorities *and* task priorities as different types of priorities?14:46
gothicmindfoodmordred: maybe admin module can see invalid, but not basic user?14:47
ttxgothicmindfood: no, I think mordred is right. Store prio at task table, and by default assign the first task prio to every task. Then allow people to change them14:47
mordredgothicmindfood: maybe so14:47
ttxprobably the right tradeoff between usability and finesse14:47
mordredalso - I think there wants to be a concept at some point of user priorities14:48
mordredlike, there is the global priority of a task for the project14:48
ttxmordred: that's an interesting concept to explore yes14:48
mordredbut on my personal todo list14:48
gothicmindfoodttx: certainly more in line with how a SCRUM team views stories - each story has a priority in the list that's unique and ordered.14:48
mordredyou know - pbr bugs are WAY more important for me to look at than jim14:48
ttxmordred: Ithink there are two difefrent concepts there. Importance (impact) and Priority (for me)14:49
gothicmindfoodttx: ++14:49
mordredttx: yah.14:49
gothicmindfoodexactly14:49
mordredalso - there is an interesting thought from gothicmindfood there14:49
ttxbut then bugtrackers who have both are generally confusing14:49
gothicmindfoodmordred: not that we don't love your priorities, but they are, in fact, yours14:49
gothicmindfood;-)14:49
mordredwhich is unique ordered priorities - rather than arbitrary categories14:50
NikitaKonovalovmay be just add a "favorites" for each user14:50
ttxmordred: so haveing story/task importance on one side and PERSONAL priority on the other would work14:50
mordredNikitaKonovalov: ++14:50
gothicmindfoodmordred: I don't see why we shouldn't be able to have both.14:50
* SergeyLukjanov likes favorites too14:50
ttxOh. and that personal priority could also be used in two dimensions. Kanban style14:50
mordredttx: right - I mean, a task-priority-user mapping table shoudl allow any user to set private priorities on tasks for themselves14:50
ttxuser or groups.14:51
mordredttx: can you explain that last thought?14:51
mordredah14:51
ttxthis is getting better by the minute14:51
gothicmindfoodmordred: I'm thinking about an ordered list vs labeled priorities and not thinking they're mutually exclusive.14:51
mordredyup14:51
mordredI'm grokking now14:51
mordreda user can have a prior list - a group can have a prior list - and the task can have an importance14:51
gothicmindfoodalso, projects probably have their story priorities set by their tech lead, right?14:52
ttxmordred: trello-style kanbans have things in different columns, but you can still order them. So that lets you express complex priorities14:52
gothicmindfood(just checking)14:52
ttxgothicmindfood: that would be a group priority yes14:53
mordredgothicmindfood: yeah. I expect jeblair to say which things are the most important for infra to care about14:53
ttxyou could combine priority AND subscription to build a "things I care about" view14:53
ttxanyway, that doesn't affect the base model14:53
ttxthat's interestig tricks we can play on top of it14:53
ttxto make the result more suable in dev work planning14:54
ttxusable*14:54
gothicmindfoodttx: it's also a little bit about modeling users, but it  may impact workflow decisions *with* the model14:54
ttxand not just a relmgt tracking tool14:54
gothicmindfoodso - admin, tech lead, heavy user, light user14:54
gothicmindfoodare things I'm thinking about14:54
ttx#topic open discussion14:54
ttx5 minutes left14:55
ttxanything else, or should we continue to brainstorm out loud ?14:55
mordredttx: so - stories are global and not owned by a project, yeah? and tasks have projects14:55
ttxyes14:55
mordredwho owns importance on a story if it doesn't have a project associated14:55
gothicmindfoodor stories can be owned by more than one project?14:55
gothicmindfoodI feel like a story should have at least one project, right?14:56
mordredlike, who reviews/accepts?14:56
gothicmindfoodno orphan stories?14:56
ttxmordred: we need a corner case for stories with no tasks14:56
mordredI mean, there are qualities that teh story owns14:56
ttxeither automatically craete a "orphan" task, or some other smart workflow14:56
NikitaKonovalovcan we say that the story belongs to project if all of it's task are in the same project?14:56
mordredlike the description14:56
mordredI want to know which users get to change those - or do we just go with a wiki-like "anyone can"?14:57
gothicmindfoodbut what if the story is in development - like a feature on a waitlist?14:57
mordredI'm fine with wiki-like 'anyone can' btw14:57
ttxmordred: cody said he has an idea araound that14:57
mordredawesome14:57
ttx(how to treat stories with no tasks)14:57
mordredquestion is still valid for stories with tasks14:57
ttxI suggested a hack that would make them fall into a "no-project-associated" view for further triaging14:58
mordredwhat about a story that has a task for nova and a task for cinder14:58
mordredwho owns the top-level story data14:58
mordredI'm just going to assert 'nobody'14:58
gothicmindfoodboth should, right?14:58
gothicmindfoodwith the ability to see that others know it as well?14:58
ttxmordred: I'd say it's undefined prio until a task is added14:58
mordredwhat about the story description14:58
ttxundefined meaning "to triage"14:58
ttxmordred: free-for-all14:59
mordredgreat14:59
mordredI love it14:59
gothicmindfoodwhoever gets it first ;-)14:59
ttxI don't think restricting bugtracker access has done anything good anywhere14:59
gothicmindfoodcan we have project teams be able to 'poke' each other to do stuff? ;-) (half-joking)14:59
ttxwe just need to tighten milestone planning stuff, targeting etc14:59
ttxbut who can change status / edit desc / titles ? Probably not15:00
ttx(as long as they are authenticated)15:00
ttxok time is up15:00
ttxfamous last words ?15:00
ttxgothicmindfood: that would be "add a task for another project"15:01
ttxgothicmindfood: (we already do that a lot in LP)15:01
ttxgothicmindfood: so yes, it's something we need to preserve15:02
ttx#endmeeting15:02
openstackMeeting ended Thu Dec 12 15:02:31 2013 UTC.  Information about MeetBot at http://wiki.debian.org/MeetBot . (v 0.1.4)15:02
gothicmindfoodttx: sounds good15:02
openstackMinutes:        http://eavesdrop.openstack.org/meetings/storyboard/2013/storyboard.2013-12-12-14.04.html15:02
openstackMinutes (text): http://eavesdrop.openstack.org/meetings/storyboard/2013/storyboard.2013-12-12-14.04.txt15:02
openstackLog:            http://eavesdrop.openstack.org/meetings/storyboard/2013/storyboard.2013-12-12-14.04.log.html15:02
ttxwe can continue discussion off-meeting, but I may or may not answer15:02
gothicmindfoodnp15:03
mordredgothicmindfood: omg re: poke15:03
gothicmindfoodmordred and I have things to discuss on le gchat15:04
gothicmindfood;-)15:04
mordredttx: dependencies15:13
*** drdee has joined #storyboard15:23
*** drdee has quit IRC15:46
*** gothicmindfood has quit IRC15:56
*** drdee has joined #storyboard16:09
*** drdee has quit IRC16:10
*** NikitaKonovalov has quit IRC16:21
*** SergeyLukjanov has quit IRC16:21
*** AaronGr_Zzz has joined #storyboard16:33
*** AaronGr_Zzz is now known as AaronGr16:33
*** AaronGr has left #storyboard16:33
*** SergeyLukjanov has joined #storyboard17:14
*** NikitaKonovalov has joined #storyboard17:18
*** NikitaKonovalov has quit IRC17:41
*** NikitaKonovalov has joined #storyboard17:43
*** gothicmindfood has joined #storyboard17:43
*** gothicmindfood has left #storyboard17:44
*** NikitaKonovalov has quit IRC18:03
*** NikitaKonovalov has joined #storyboard18:05
*** NikitaKonovalov has quit IRC19:12
*** NikitaKonovalov has joined #storyboard19:14
*** NikitaKonovalov has quit IRC19:15
*** SergeyLukjanov has quit IRC19:46
*** SergeyLukjanov_ has joined #storyboard19:47
*** SergeyLukjanov_ has quit IRC19:48
*** SergeyLukjanov has joined #storyboard19:48
*** SergeyLukjanov is now known as _SergeyLukjanov21:31
*** SergeyLukjanov has joined #storyboard21:45
*** SergeyLukjanov has quit IRC23:57

Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!