| *** MaxV_ has joined #storyboard | 01:24 | |
| *** MaxV_ has quit IRC | 02:17 | |
| *** MaxV_ has joined #storyboard | 02:36 | |
| *** MaxV_ has quit IRC | 02:42 | |
| *** Toshi has joined #storyboard | 04:04 | |
| *** Toshi has quit IRC | 07:01 | |
| *** jcoufal has joined #storyboard | 07:05 | |
| *** jang has joined #storyboard | 08:17 | |
| *** hashar has joined #storyboard | 08:18 | |
| *** jcoufal has quit IRC | 09:10 | |
| openstackgerrit | Nikita Konovalov proposed a change to openstack-infra/storyboard: Refresh token support https://review.openstack.org/94363 | 09:36 |
|---|---|---|
| *** jcoufal has joined #storyboard | 10:15 | |
| *** jang has quit IRC | 10:16 | |
| *** jang has joined #storyboard | 10:25 | |
| *** jcoufal has quit IRC | 10:39 | |
| *** jcoufal has joined #storyboard | 10:40 | |
| *** jang has quit IRC | 11:55 | |
| *** jang has joined #storyboard | 11:58 | |
| *** mfer has joined #storyboard | 13:02 | |
| openstackgerrit | Nikita Konovalov proposed a change to openstack-infra/storyboard-webclient: Make Timeline configurable https://review.openstack.org/93433 | 13:53 |
| openstackgerrit | Nikita Konovalov proposed a change to openstack-infra/storyboard-webclient: Configure Timeline from Story details https://review.openstack.org/93563 | 13:54 |
| openstackgerrit | Nikita Konovalov proposed a change to openstack-infra/storyboard-webclient: Configure Timeline from Story details https://review.openstack.org/93563 | 14:04 |
| openstackgerrit | Nikita Konovalov proposed a change to openstack-infra/storyboard-webclient: Configure Timeline from Story details https://review.openstack.org/93563 | 14:14 |
| *** david-lyle has joined #storyboard | 14:37 | |
| *** jang has quit IRC | 15:17 | |
| *** hashar has quit IRC | 15:40 | |
| *** miqui has quit IRC | 16:47 | |
| *** miqui has joined #storyboard | 16:50 | |
| *** jcoufal has quit IRC | 18:56 | |
| *** jcoufal has joined #storyboard | 18:56 | |
| *** jang1 has joined #storyboard | 19:05 | |
| * krotscheck grumps about these UX videos. | 19:07 | |
| krotscheck | It’s like they create more questions than answers. | 19:07 |
| gothicmindfood | krotscheck: splain! | 19:12 |
| krotscheck | gothicmindfood: Right, so my big question right now is “Why do we have tasks” | 19:18 |
| gothicmindfood | a good questions indeed | 19:18 |
| gothicmindfood | my understanding in Brussels was "we have tasks because there are discrete items of work we want to track that are part of a larger story/feature/bug" | 19:18 |
| krotscheck | So what is a discrete item of work? Everyone in the videos is confused about it. Some tried to comment on a task, some wondered “Hey, what if this task requires a larger design doc, where do I put that?” | 19:20 |
| krotscheck | So they you create a new story and move the task over, how do you keep track of that task from the original story? | 19:20 |
| krotscheck | What about the discussion on a particular task? | 19:20 |
| krotscheck | It feels to me like the separation of “Story” and “Task” results in people adding their own interpretation as to what they are, and (in most cases) expect them to behave identically. | 19:24 |
| krotscheck | I’m of half a mind to redefine “Story” as “A living record of an engineering effort”, and explicitly link in design docs, git commits, jenkins runs, each as their own component of one single document. | 19:25 |
| gothicmindfood | so - functionally, I think tasks are also supposed to be unique commits to Gerrit | 19:28 |
| gothicmindfood | for purposes of tracking done work, too, right? | 19:28 |
| gothicmindfood | with the understanding that many bugs will probably only have one task | 19:29 |
| krotscheck | That’s how I think of them. | 19:29 |
| gothicmindfood | and I also observed the same confusion about the difference between a task and story | 19:29 |
| krotscheck | But calling them “Tasks” seems to be confusing. | 19:29 |
| gothicmindfood | but that might be something that, froma nomenclature perspective has to be taught rather than expected to be understood intuitively. | 19:30 |
| gothicmindfood | though UX could help that intuition somehow, I'm sure of it. | 19:30 |
| krotscheck | Why not just call it “Commit”? | 19:30 |
| krotscheck | …if it quacks like a commit, walks like a commit, looks like a commit... | 19:30 |
| *** jang1 has quit IRC | 19:37 | |
| gothicmindfood | haha | 19:44 |
| gothicmindfood | ttx: ^^ | 19:44 |
| gothicmindfood | krotscheck: because it may or may not have a commit associated with it? | 19:44 |
| gothicmindfood | krotscheck: and the purpose of having 'tasks' be generalized also might lie in having storyboard be a tool for personal use alongside project use as well | 19:45 |
| gothicmindfood | I'm obviously just trying to straw man this, and don't have any particular objections at the moment. :) | 19:45 |
| krotscheck | As soon as we let tasks be freeform, them we risk users trying to overload them to do more than they were intended to. | 19:47 |
| krotscheck | “Hey why can’t I comment on this task”? | 19:47 |
| krotscheck | “Hey this task needs a design discussion relevant only to the project it’s on" | 19:48 |
| krotscheck | Not to mention the fact that a search on stories is really a search on tasks. | 19:48 |
| krotscheck | “I want task X to be dependent on Story Y, and Story Z to be dependent on Story W | 19:49 |
| krotscheck | AND task V | 19:49 |
| *** jang1 has joined #storyboard | 19:56 | |
| gothicmindfood | and you think that'll change if we just change it's name to commit? | 19:56 |
| *** jang1 has quit IRC | 20:00 | |
| krotscheck | Well, sortof. I feel that commits/patches should be treated independently of tasks. | 20:03 |
| krotscheck | So, the idea behind tasks is that they’re all backed by a commit. | 20:04 |
| krotscheck | (As per the storyboard design session on thursday) | 20:04 |
| krotscheck | But now you’re saying they need to be freeform. | 20:04 |
| krotscheck | Well, if they’re freeform then we don’t get the Magic Status Updatey From Gerrit. | 20:04 |
| krotscheck | Because not every task will be associated with a commit. | 20:05 |
| *** jang1 has joined #storyboard | 20:05 | |
| *** jang1 has quit IRC | 20:10 | |
| gothicmindfood | krotscheck: but, if gerrit does register that a set of tasks has passed through the gate as commits, it could auto-close them. | 20:19 |
| gothicmindfood | it doesn't have to be a 1-1 relationship - there can and will be tasks that don't have commits affiliated with them, I'm assuming | 20:20 |
| krotscheck | And what I’m saying is that we shouldn’t call them tasks if they’ve got additional data attached to them that make them a special case citizen. | 20:22 |
| gothicmindfood | krotscheck: additional data that may or may not make them that, I think is the trouble, right? | 20:30 |
| krotscheck | More or less. Chances are that Gerrit is going to create brand new tasks for a story anyway. | 20:31 |
| krotscheck | Unless an engineer includes both story # and task #? | 20:31 |
| krotscheck | ttx: I’m going through the MVP 1.1 list right now. What is “Tags”? | 21:06 |
| *** mfer has quit IRC | 21:18 | |
| *** krotscheck has quit IRC | 21:19 | |
| *** krotscheck has joined #storyboard | 21:20 | |
| *** jang1 has joined #storyboard | 21:21 | |
| *** jcoufal has quit IRC | 21:21 | |
| *** jang1 has quit IRC | 21:26 | |
| krotscheck | Edge case: I’m creating a story titled “Stories should be taggable” with a task in the infra-specs repository. Unless I create a task called “implement what the spec says” this project will never show up in storyboard’s list. That feels like I’m creating a task that will eventually get either ignored or deleted. | 21:32 |
| krotscheck | Actually, I just did it 3 times in the last 20 minutes. Probably not an edge case. | 21:33 |
| *** jang1 has joined #storyboard | 21:42 | |
| *** jang1 has quit IRC | 21:56 | |
| *** phschwartz_ has joined #storyboard | 22:34 | |
| *** phschwartz has quit IRC | 22:38 | |
| *** anteaya has quit IRC | 22:38 | |
| *** krotscheck has quit IRC | 22:49 | |
| *** cody-somerville has quit IRC | 22:49 | |
| *** phschwartz_ has quit IRC | 22:54 | |
| *** phschwartz has joined #storyboard | 22:54 | |
| *** jang has joined #storyboard | 22:55 | |
| *** krotscheck has joined #storyboard | 22:56 | |
| krotscheck | We’ve got another UI iteration on the storyboard dashboard: http://invis.io/D3UN5LSU | 22:57 |
| *** anteaya has joined #storyboard | 22:57 | |
| *** cody-somerville has joined #storyboard | 23:12 | |
| *** jang has quit IRC | 23:16 | |
| *** david-lyle has quit IRC | 23:26 | |
| *** openstackgerrit has quit IRC | 23:49 | |
| *** openstackgerrit has joined #storyboard | 23:50 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!