| *** davidlenwell has quit IRC | 06:06 | |
| *** davidlenwell has joined #storyboard | 06:08 | |
| *** jtomasek has joined #storyboard | 06:16 | |
| *** coolsvap|away is now known as coolsvap | 09:15 | |
| *** coolsvap is now known as coolsvap|away | 09:48 | |
| *** coolsvap|away is now known as coolsvap | 10:11 | |
| *** coolsvap is now known as coolsvap|away | 10:25 | |
| *** coolsvap|away is now known as coolsvap | 11:22 | |
| persia | paulsherwood: I don't see any distinction between "lane" and "worklist", other than the spelling, and perhaps some logical guards to ensure that a single task does not appear on multiple "lanes" within some "board". | 13:28 |
|---|---|---|
| persia | And there are lots of values to having worklists for tasks entirely independent of whether one happens to be using a kanban-like UI. | 13:29 |
| persia | The key issue is that a scalable task tracking system cannot have dependencies like automation that means "blocked-by-customer" automatially goes into someone else's "incoming". | 13:29 |
| persia | Instead, one needs to have metadata that allows one to generate that class of functionality in complete awareness that anyone else can suddenly chose to do something in complete ignorance of what items any other person happened to put in a worklist. | 13:29 |
| persia | Most of the rest of it can be handled by pointing automation at the API | 13:29 |
| SotK | I've been thinking a bit on the idea of "semantic worklists", eg. a worklist with a rule that it should contain all tasks who have status:review | 14:12 |
| SotK | I imagine such worklists should only contain tasks | 14:13 |
| SotK | I also assume that one could set constraints on things other than just the task status, so as to not end up with ridiculously large lists | 14:14 |
| SotK | ie. jrandom user can create a semantic worklist with the constraints "status:review, project:foo-project" which will always show tasks which are in "review" and part of "foo-project" | 14:15 |
| SotK | rather than needing to create a list of every task in the database that is in review | 14:16 |
| persia | That sounds fairly useful, but I'm not convinced everyone can understand the name: I know I like the word "semantic", but I'm unconvinced everyone has the same value for the term as I :) | 14:16 |
| SotK | indeed, I'd like it if a better name sprouted in my head | 14:17 |
| persia | Maybe "smart lanes" or something like that? Mind you, some folk don't like apple-inspired lingo. | 14:18 |
| * SotK imagines "add a smart iLane in your iKanban dashboard" ;) | 14:20 | |
| persia | heh | 14:22 |
| *** MarkAtwood has joined #storyboard | 14:59 | |
| *** coolsvap is now known as coolsvap|away | 15:09 | |
| paulsherwood | persia: re worklist vs lane - agreed | 15:37 |
| paulsherwood | what's wrong with lane, and special lane? i know it's a bit basic | 15:39 |
| SotK | I worry that "special lane" just makes me wonder what makes it special | 15:41 |
| *** jcoufal has quit IRC | 15:43 | |
| * SotK ponders "filtered lane/worklist" or similar | 15:49 | |
| *** coolsvap|away is now known as coolsvap | 15:54 | |
| persia | I asked a collegue, who suggested "automatic worklist" | 16:33 |
| SotK | I think I like that | 16:34 |
| *** coolsvap is now known as coolsvap|away | 16:36 | |
| paulsherwood | +1 | 16:55 |
| *** coolsvap|away is now known as coolsvap | 17:08 | |
| *** davidlenwell has quit IRC | 18:03 | |
| *** davidlenwell has joined #storyboard | 18:05 | |
| *** jcoufal has joined #storyboard | 19:00 | |
| *** coolsvap is now known as coolsvap|away | 19:04 | |
| *** jtomasek has quit IRC | 19:21 | |
| *** jcoufal has quit IRC | 20:26 | |
| *** coolsvap|away is now known as coolsvap | 22:05 | |
| *** MarkAtwood has quit IRC | 22:40 | |
| *** coolsvap is now known as coolsvap|afk | 23:14 | |
| *** openstack has joined #storyboard | 23:41 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!