| *** anteaya has quit IRC | 01:54 | |
| -openstackstatus- NOTICE: pip 8.1.2 broke our local python mirror, some jobs will fail with "No matching distribution found". We're investigating. Do not "recheck" until the issue is solved | 07:08 | |
| *** ChanServ changes topic to "pip 8.1.2 broke our local python mirror, some jobs will fail with "No matching distribution found". We're investigating. Do not "recheck" until the issue is solved" | 07:08 | |
| *** fay_ has joined #storyboard | 07:12 | |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Complex priorities UI in stories https://review.openstack.org/312666 | 09:52 |
|---|---|---|
| Zara | zzzzz, morning, storyboard, zzzzzzz | 09:55 |
| Zara | SotK: btw, could you record work on complex priorities in storyboard.openstack.org ? I can't find it at a glance | 10:09 |
| SotK | yeah, sorry | 10:12 |
| Zara | thanks :) | 10:25 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Allow lists of boards and worklists to be paged https://review.openstack.org/309481 | 10:28 |
| Zara | ohh, I thought I'd merged that, ooops | 10:29 |
| SotK | merge conflict :) | 10:29 |
| Zara | ugh search error | 10:29 |
| Zara | whyyyy I tested search | 10:29 |
| SotK | ? | 10:30 |
| Zara | ah, it doesn't like searches containing spaces (header search) | 10:30 |
| Zara | oh no, any searches | 10:30 |
| Zara | ¬_¬ | 10:30 |
| Zara | grrrrrrrrrRRRrrr | 10:30 |
| Zara | 500: GET /api/v1/tasks/search: (InternalError) (1052, u"Column 'title' in where clause is ambiguous") | 10:31 |
| Zara | http://paste.openstack.org/show/496679/ | 10:31 |
| SotK | aha! | 10:31 |
| Zara | I test search *every time*, gahhhh | 10:32 |
| Zara | oh yeah, I'm going to try harder to make task titles match commit message titles where relevant, be good if others could do the same (helps with search when the thing in review hasn't been linked in task notes) | 10:37 |
| Zara | (or story linked in commit) | 10:37 |
| * Zara makes story for search error: https://storyboard.openstack.org/#!/story/2000579 | 10:40 | |
| Zara | complete with shameless theorizing | 10:40 |
| SotK | Zara: https://storyboard.openstack.org/#!/story/329 | 10:44 |
| Zara | ohh, that one, ace. probably lost it because I marked it merged earlier, then didn't update after discussion oops | 10:46 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Improve the worklist filtering functionality https://review.openstack.org/310287 | 10:52 |
| Zara | (I was going to test priorities stuff, though would rather merge fix for search weirdness first so that it's easier to know which patchset might've caused problems if we find further weirdness) | 10:56 |
| Zara | now to find out why weirdness... | 10:56 |
| Zara | so far can't find anything in those patches that'd make 'title' ambiguous where it wasn't before (I'm assuming the error means it's not sure whether it should match against story_title or task_title) | 11:15 |
| Zara | ugh, so I know why I didn't find it in my test instance-- I didn't update my db properly a while ago and it gives an error on search. but it was only giving that error so it didn't let me know there was something else wrong. | 11:26 |
| * Zara fixes test instance... | 11:26 | |
| Zara | orrr not... | 11:39 |
| Zara | I'm not sure what I need to change. getting http://paste.openstack.org/show/496699/ when I try to search | 11:40 |
| Zara | based on old notes, I tried `alter table users add fulltext search(`full_name`);`, but didn't help | 11:41 |
| SotK | I think you need the email column in the fulltext index too | 11:47 |
| SotK | `alter table users add fulltext search(`full_name`, `email`);` | 11:47 |
| Zara | darn, tried that (but after, alone) and it said something about a key being duplicated | 11:48 |
| Zara | will try two together... | 11:48 |
| Zara | (as in, I tried to do: alter table users add fulltext search(`email`); | 11:48 |
| Zara | still doing it | 11:49 |
| Zara | (ERROR 1061 (42000): Duplicate key name 'search') | 11:49 |
| Zara | would imagine I have to remove it then add them together? | 11:49 |
| SotK | yeah, or give the second one a different name | 11:50 |
| SotK | `alter table users add fulltext search(`full_name`);` creates a new fulltext index for the table, called "search" which indexes the full_name column | 11:50 |
| Zara | how do I remove it? I'm guessing giving it a different name will probably trip me up in the future if I need to look for it. | 11:51 |
| Zara | or manipulate it somehow more generally | 11:51 |
| * SotK would expect `alter table users drop index search;` | 11:52 | |
| Zara | okay, will try that, thanks | 11:53 |
| Zara | hm, said nothing was affected but it's letting me add it now | 11:54 |
| Zara | and search works fine now, thanks | 11:55 |
| Zara | though... it works in my instance. | 11:55 |
| Zara | it doesn't on master | 11:55 |
| Zara | so what's going on with that...? | 11:56 |
| SotK | works in my instance too, idk | 11:56 |
| Zara | \ o / | 11:56 |
| Zara | so that little detour had nothing to do with the issue on master | 11:56 |
| Zara | ace | 11:56 |
| SotK | I'm very confused as to why it isn't broken on my test instance, the error on master is very sensible | 11:58 |
| Zara | ah, so you know what code is causing the ambiguity? I couldn't find it | 11:58 |
| SotK | well, the sql that is being emitted is bad | 11:59 |
| SotK | (`title` is a column in two of the tables used in the query) | 11:59 |
| Zara | yeah, I couldn't find where the query had changed (recently) to cause that to happen, but might've been because I was lookign for 'title' when I should've looked at something more abstract | 12:00 |
| *** ChanServ changes topic to "StoryBoard - A task tracker for OpenStack development needs :: http://storyboard.openstack.org/ :: https://wiki.openstack.org/wiki/StoryBoard" | 12:00 | |
| -openstackstatus- NOTICE: We have a workaround for our mirrors to attempt to translate package names if a match isn't immediately obvious. A more complete fix is yet to come. It is now safe to 'recheck' any jobs that failed due to "No matching distribution found". Please join #openstack-infra if you discover more problems. | 12:00 | |
| Zara | maybe master has newer mysql which is complaining instead of guessing? | 12:00 |
| Zara | s/master/s.o.o | 12:00 |
| SotK | this is a "why did this ever work" kind of bug | 12:04 |
| Zara | =D | 12:04 |
| SotK | hmm, actually... | 12:05 |
| Zara | that sounded promising | 12:07 |
| * Zara decides sotk got eaten by a bear, aw. | 12:13 | |
| Zara | oh yeah, storyboard meeting at 15:00 utc | 12:13 |
| Zara | I keep forgetting it's wednesday today | 12:13 |
| SotK | this is very weird | 12:15 |
| persia | Is the description of story #99 still correct? | 12:18 |
| persia | I thought s.o.o had working email. | 12:18 |
| SotK | no, it is not correct | 12:18 |
| * SotK fixes | 12:19 | |
| *** anteaya has joined #storyboard | 12:30 | |
| *** openstackgerrit has quit IRC | 12:33 | |
| *** openstackgerrit has joined #storyboard | 12:33 | |
| *** jseutter has joined #storyboard | 12:47 | |
| Zara | guessing this is very out of date and should be taken out of the review list: https://storyboard.openstack.org/#!/story/153 | 13:04 |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Removed explicit references to node_modules/.bin https://review.openstack.org/304557 | 13:05 |
| persia | Zara: "review" seems an odd status after this much time, but maybe it is languishing in infra-specs or something. Maybe check with rcarrillocruz? | 13:07 |
| SotK | I've seen the spec that is talked about somewhere I think | 13:11 |
| * Zara asks him in #infra | 13:41 | |
| SotK | ok, so the search bug is because s.o.o is using version 0.2 of SQLAlchemy_FullText_Search, which doesn't construct the SQL entirely sensibly | 14:04 |
| Zara | =D | 14:08 |
| Zara | I should wander off to get chocolate more often, seems to help | 14:09 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Fix error in search due to multiple `title` columns in query https://review.openstack.org/315071 | 14:11 |
| Zara | \o/ will look at that now | 14:14 |
| *** anteaya has quit IRC | 14:30 | |
| * Zara is nitpicky about commit msg | 14:36 | |
| SotK | I'm confused as to what you think it should be reworded to | 14:37 |
| Zara | I think I'd rather it said that version 0.2 was used before and that the minimal version required is now bumped to 0.2.3 | 14:38 |
| Zara | otherwise it sounds like the requirement might be something like '@latest', since some packaging systems have support for things specified that way | 14:39 |
| persia | Oh, good point. | 14:39 |
| persia | Perhaps even better to mention that the necessary feature was introduced in 0.2.3 (or whenever it was introduced: no reason not to use 0.2.3 even if it was introduced in 0.2.1) | 14:39 |
| * SotK grumbles about having to go figure out when it was fixed | 14:41 | |
| SotK | well, that was painless | 14:42 |
| Zara | xD | 14:43 |
| Zara | ooh, just noticed you're using the nice story link in the commit message, \o/ | 14:44 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Fix error in search due to multiple `title` columns in query https://review.openstack.org/315071 | 14:45 |
| Zara | oh wait it didn't have a +1 on the rework, I was too quick to +A that | 14:46 |
| SotK | the rework was only the commit message, I don't think it matters | 14:46 |
| Zara | I removed it pending persia jic | 14:46 |
| Zara | persia: I'll +A again if you're fine with it, just letting you know I'm waiting on your +1 or nod on irc or somesuch | 14:48 |
| persia | Right, I'm waiting for UbutnuOne to let me press the button :) | 14:48 |
| Zara | :D | 14:48 |
| persia | Done | 14:48 |
| Zara | \o/ | 14:49 |
| Zara | oh yeah, meeting in 10 mins | 14:50 |
| * Zara wonders how out of date the agenda is this week | 14:50 | |
| persia | 10 minutes to fix :) | 14:50 |
| Zara | (answer is 'very'; it thinks the summit is next week) | 14:51 |
| Zara | Announcements | 14:52 |
| Zara | No meeting next week, summmmmittttttt. Task tracking session 9am, Austin, Texas, go there instead | 14:52 |
| Zara | im so polite | 14:52 |
| persia | Three weeks then. Good luck :) | 14:52 |
| Zara | agenda up here: https://wiki.openstack.org/wiki/Meetings/StoryBoard#Agenda_for_next_meeting not sure whether our announcements count as annoucements, really | 14:56 |
| Zara | meeting in 1 minute | 15:00 |
| persia | So, about priorities UX :) | 16:00 |
| SotK | I think just adding a button which shows a modal is just as bad as removing priorities and replacing it with nothing tbh | 16:04 |
| SotK | if I'm looking at the story detail page, I want to know its priority at a glance | 16:04 |
| SotK | I agree that without being able to subscribe to worklists its a little "ALL THE INFORMATION", but that is something that can be improved upon later | 16:05 |
| SotK | (I also agree we need to paginate, I realised that soon after sending the patch) | 16:05 |
| Zara | yeah, I think a problem I have with that implmentation is that I don't think a long list of the worklist-positions of that story or tasks in it does reveal anything at a glance, because of the 'all the information' problem. even if you have one, there's still quite a lot for the reader to think about and parse (what's this list for? whose is it? what's the position relative to the other items?) | 16:07 |
| Zara | so if we could find a way to make a button more informative, that could be clicked to reveal more, that'd be my ideal (I think) | 16:07 |
| SotK | it reveals that a lot of people care about sorting/tracking that story somehow, and therefore probably care about the story | 16:09 |
| Zara | then maybe a button should just have the number of worklists a story is present in | 16:09 |
| SotK | I can only think of a button which says "in 28 worklists, click to see which", which to me seems more annoying than just showing the worklists | 16:09 |
| Zara | plus the similarity to the due_dates layout bothers me, because it's totally different information. | 16:09 |
| persia | I wonder if there is a way to calculate a score of some sort. | 16:10 |
| Zara | so I think it requires a user to read quite a lot to work out what's going on on the page. | 16:11 |
| Zara | I'm not especially in love with the idea of a modal, if we can have a list that's collapsed | 16:11 |
| persia | So that one shows the priority as that score, and can expand to see details. | 16:11 |
| * persia was thinking of something like the reciprocal of the means of the rankings, or some such, so that high positions on long lusts rank better. | 16:12 | |
| persia | Note this would only be a placeholder until there is a better way to discover the priority to one's own principals. | 16:13 |
| SotK | are we talking per-task score here or per-story? | 16:13 |
| persia | The score could be the button label | 16:13 |
| SotK | (note: I suspect that "Priority: 6" is pretty meaningless unless there is information on the calculation easily available) | 16:14 |
| persia | I think most cards in worklists will tend to be at the task level. Plus, for many stories, the priorities vary be task. | 16:14 |
| persia | Yes, the algorithm would need to be public, and would be games, etc. | 16:15 |
| SotK | what would you suggest happens after there is a better way to discover priority that interests oneself? | 16:16 |
| SotK | also, I think that even with a public algorithm we'll get a lot of "how can I set the priority number?" | 16:18 |
| openstackgerrit | Merged openstack-infra/storyboard: Fix error in search due to multiple `title` columns in query https://review.openstack.org/315071 | 16:22 |
| Zara | I think giving it an overall number is the wrong approach. we want to show 'who cares' and 'how much do these people care, relative to everything else they're doing', and that's something that one can't digest at a glance anyway. So I think I'd rather start from a 'whose worklists is this in?' point than 'how many worklists'... though easy to say, harder to do | 16:23 |
| persia | Hmm. Good points. I retract my suggestion. | 16:24 |
| persia | In my dream world, there is a little box that lists priorities set by my principals or not. | 16:24 |
| SotK | I don't think there is a way to express "whose worklists is this in" that is simple, clear, and not a lot of reading | 16:25 |
| persia | But I am not quite sure how to deal with the massive list issue Zara raises. | 16:25 |
| persia | SotK: do you think that continues to be true if there is a way to express "I only care about these opinions."? | 16:26 |
| SotK | it depends how we implement "I only care about these opinions" | 16:27 |
| persia | Hmmm... | 16:27 |
| Zara | I think a little box of avatars'd work, with 'more info>' for details of list positions | 16:27 |
| SotK | Zara: but we don't have avatars :) | 16:27 |
| persia | I think "more info" is more text than "100/102" | 16:28 |
| Zara | once per box | 16:28 |
| Zara | aiui the idea behind this is that a priority only matters relative to the influence of someone setting it. | 16:28 |
| SotK | that box quickly gets very big when your story is related to 30 worklists each with multiple stakeholders | 16:28 |
| persia | Plus avatars tend not to be unique over a large audience. | 16:28 |
| Zara | roughly, if we're going to give a complex breakdown of priorities, I don't think we can give people very relevant info on them at a glance *because* it's complex, so if people want details, they're going to have to ask for more. | 16:30 |
| persia | On the other hand, I do not expect most folk to have 30 principals | 16:30 |
| SotK | we could allow subscription to users, and then display the set of users who own a worklist containing the task/story that one is subscribed to | 16:30 |
| SotK | that may be more useful than subscribing to individual lists | 16:31 |
| persia | Why? | 16:31 |
| SotK | each worklist can be owned by multiple people, so I'm not sure how valuable displaying the owners of lists is | 16:32 |
| persia | I can think of several cases where I care about some list for someone, but not their other lists (e.g. the priority list set by a PTL for a cycle, but not other lists by the human that is that PTL) | 16:32 |
| SotK | hm, this problem exists both ways then | 16:32 |
| persia | How about lust titles, rather than people. | 16:33 |
| persia | So I can express "what priority does the PWG assign?". | 16:33 |
| SotK | that stops working very well when all of your principals call their list "My priorities" | 16:33 |
| Zara | :D | 16:33 |
| persia | Can we fix that with social conditioning? | 16:34 |
| persia | I think users would be more inclined to follow "Persia's wish list" or "Storyboard team Newton priorities" than "My priorities", regardless of creator. | 16:35 |
| * SotK would certainly hope that is the case | 16:36 | |
| SotK | but how many folk have principals that can be conditioned by saying "I'm not using it until you give it a better name" | 16:37 |
| persia | Lower cognitive burden. Badly named worklists may cause developers to disregard them. | 16:37 |
| persia | I think most of the community-oriented lists (PTL priorities, RT priorities, PWG priorities, etc.) Will get good names, and that most developers haze zero to one principals with whom the do not feel able to argue. | 16:39 |
| SotK | ok, so the desire is for a box containing worklist titles? | 16:39 |
| persia | I would like that, but Zara raises good points why this is bad, so I am not convinced we have to eached consensus. | 16:40 |
| * persia is not a very reliable indicator of "typical user" behaviour or feature desires. | 16:41 | |
| SotK | I think that the long-list part is only an issue between now and being able to express the set of lists you care about | 16:41 |
| SotK | (I doubt people will care about more than a few lists) | 16:41 |
| persia | How long do we expect that to be? How many worklists might get created in the meantime? Will this scare off folk who have little experience with multidimensional priorities? | 16:42 |
| persia | To put another way, does that mean we agree on UX, but need to wait for the filter feature before landing the change? | 16:43 |
| Zara | yup, I still think it's not usable yet, just to be annoying. I think we'll get a lot of complaints to the effect of 'how do I get rid of this big list of things I don't care about? I have to scroll to see the tasks. also how do I set a story's priority?' some people will want the full list at a glance, but I really believe they'll be in a minority. | 16:43 |
| Zara | SotK and I did differ on whether the list should be visible at-a-glance, I'm in favour of hiding it unless someone specifically asks | 16:44 |
| Zara | ideally they'd be able to say 'always expand this list by default' but idk that we'll ever get around to implementing that sort of preference | 16:44 |
| SotK | where we talk about an expanding list here, are we talking about something like the recent events list? | 16:45 |
| Zara | yeah | 16:45 |
| Zara | not the exact same layout but that kind of thing | 16:45 |
| persia | For me, hidden is not useful, so I would rather see the existing paradigm than something we think is ugly enough to hide. | 16:45 |
| SotK | (I also think that we can just use pagination to stop "I've got loads of stuff to scroll past") | 16:45 |
| SotK | persia: +1 | 16:45 |
| Zara | + I think you get a gerrit effect where there's so much stuff on the screen it will panic new users | 16:47 |
| SotK | I still think that some always-there indication of "priority" is better than a hidden indication of it | 16:48 |
| Zara | yeah, I'm not sure there is a useful indication that can be parsed at a glance with this approach, but if you can think of one, that'd be best. | 16:48 |
| Zara | a list of even five items with 'x out of y items' can't be parsed fast imo | 16:49 |
| persia | So, do we feel we have consensus on UX, and that this requires being able to identify lists of interest (so, discoverable worklists, worklist subscriptions, etc.) before being suitable for production? | 16:49 |
| * SotK doesn't know what Zara thinks of the list box even if it is filtered by interest | 16:50 | |
| SotK | Zara: I agree, but one can quickly see "oh 5 people care about this" | 16:50 |
| persia | Zara: I think it varies human-to-hunan, in the range 3-7 items, but yes, 5 is hard for about 50% of users. | 16:50 |
| SotK | just because the extra information is there, doesn't mean it has to be read to see there are 5 things in the list | 16:50 |
| persia | ++ | 16:51 |
| SotK | and a big list with "1 to 10 of 29" is more at-a-glance parsable than a button with a number on to me | 16:51 |
| Zara | is it valuable to know it's in 5 lists? I thought originally the point of this was to find out *who* cared, otherwise we might as well just have an 'I care about this' button :P | 16:51 |
| SotK | "oh look, so many people care I have to page through" | 16:51 |
| Zara | which people have railed against in the past | 16:52 |
| SotK | the point is to find out if people you care about care | 16:52 |
| SotK | but we have no way to define "people you care about" at the moment | 16:52 |
| persia | (for reference, the 3-7 number comes from experiments with random object collections being displayed for short periods of time, with subjects tested for identification and recall immediately thereafter) | 16:52 |
| SotK | and the current situation is the first pass | 16:52 |
| SotK | (show every list that cares) | 16:52 |
| SotK | since that at least gives some indication of the amount of interest | 16:53 |
| * SotK thinks there should be an "I care about this" button, it should be the button to add it to a worklist you own | 16:53 | |
| persia | I think the current code us good as a way to argue about display implementation, but we should assume very short lists (<10), and wait until we can expect that before landing. | 16:53 |
| Zara | yeah, I'm fine with that first pass as a demo for helping us work out how to represent it, but not to merge, since I think giving that indication is less beneficial than the harm we get from making storyboard look very complicated. | 16:54 |
| Zara | snappish | 16:54 |
| SotK | so what do we show logged out users when we can define what we care about? | 16:55 |
| persia | SotK: I would like a more general add-to-worklist implementation, so that I can more easily set things when I wear different hats. | 16:55 |
| persia | SotK: no priority. | 16:55 |
| SotK | persia: I was expressing a general add-to-worklist desire in a bad way | 16:55 |
| persia | I think that if we do not know who is looking, we have no way of suggesting whether any expression of importance is meaningful to them. | 16:56 |
| Zara | (I'm not yet sure about the lists titles in a box implementation for just users I care about; since it's opt-in, it's better, though I still don't know if those would get very long.) | 16:56 |
| SotK | if they get very long, they can be paged, and if the paging is annoying, people should care about less things | 16:56 |
| persia | That said, having a navigation element to get to the massive list of any worklist with the item (on a separate page) might be interesting and safe to show anonymous users. | 16:57 |
| Zara | SotK: then you need the 'I care about worklists made by this user under conditions xyz' thing | 16:57 |
| persia | +1 on telling people to care about less things if the list is too hard to read | 16:57 |
| * persia still doesn't understand why the user us important | 16:58 | |
| SotK | Zara: nah, we just need "I care about this list" | 16:58 |
| persia | ++ | 16:58 |
| SotK | if the person is creating loads of lists (to the point you want to automate caring), then that person shouldn't be cared about | 16:59 |
| Zara | so you want to subscribe to worklists and have only those you subscribe to show up when you browse to a story (/that contains a task) in one of them? | 16:59 |
| SotK | yes | 16:59 |
| persia | Yes | 17:00 |
| Zara | right, I missed that agreement, sorry | 17:00 |
| SotK | that is what is intended to go in the list that currently is all the worklists, since there is currently no way to subscribe to a worklist | 17:01 |
| persia | And use social controls for well-named worklists, single priority worklist for given stakeholder wearing a given hat, etc. | 17:01 |
| SotK | +1 | 17:01 |
| persia | Zara: do you share our agreement, or are there other reservations? | 17:03 |
| Zara | fine with that, I think. personally wouldn't bother with pagination for it beyond eg: show 3 by default, or click for all, since I doubt a user will want results on different pages--- but that's a small difference | 17:03 |
| SotK | it needs to be paginated in case someone subscribes to 2000 lists because they are foolish | 17:04 |
| Zara | heh | 17:05 |
| SotK | (and we need to not crash when they click "show all") | 17:05 |
| persia | Also, because there are some 5-signa folk around, I think 10 by default is safer. | 17:06 |
| * SotK has learnt from zaro's notifications nightmare | 17:06 | |
| SotK | +1 | 17:06 |
| persia | (Not that 3 by default is bad, but it is limiting to people with large set appreciation, and people with smaller set apprec iation can just subscribe to less) | 17:07 |
| Zara | yeah, my motivation for that was that the current placement moves the task list down the page, which I think will be interesting to people more often-- but that might just be a matter of shuffling things around, not sure | 17:08 |
| persia | For fair disclosure: I scored 5.8 when I did the test at uni, and probably have a narrower set size now) | 17:08 |
| SotK | Zara: it only does that if the description is short :) | 17:08 |
| Zara | yeah, there have been active stories with short descriptions, so I think we should assume it can happen: https://storyboard.openstack.org/#!/story/2000175 | 17:09 |
| * SotK agrees, but also doesn't think that it moves it down far enough to be of consequence | 17:10 | |
| persia | I suspect most active stories with short descriptions are unlikely to be priorities for most folk that actually do stuff. | 17:11 |
| Zara | hm, well that's made me consider something else-- will we get a situation where someone subscribes to a worklist because they care about changes in it, but don't care about displaying it in related stories or tasks? | 17:12 |
| persia | If it is important, it us probably either easy or would benefit from more precise description. | 17:12 |
| persia | Zara: can you describe an example case where that would be interesting? | 17:12 |
| *** fay_ has quit IRC | 17:14 | |
| Zara | not sure yet. will give it some thought. I don't know that I'd ever want to subscribe to a worklist | 17:14 |
| Zara | (my thinking originally was that I don't care about priority field, but then if I don't subscribe to a worklist anyway, that's moot) | 17:15 |
| SotK | I think having two ways to express interest in a worklist will be horrendously confusing | 17:15 |
| persia | Zara: not to put you on the spot in logs (feel free to decline to answer), but why would you not want to be subscribed to your manager's worklist, assuming they could put it in Storyboard? | 17:17 |
| Zara | because I'd already know what I was meant to be doing through other channels, such things get out of date quickly, and it's not likely to have total overlap with mine, so I'd get notified about things that weren't relevant to me. | 17:19 |
| * SotK is imagining not having notifications for worklists at first | 17:21 | |
| SotK | and having them able to be turned off even when they do exist | 17:21 |
| * persia has generally been fortunate enough to have principals whom, given good tools, will use them and not other channels to express tasking. | 17:29 | |
| *** openstackgerrit has quit IRC | 17:33 | |
| *** openstackgerrit has joined #storyboard | 17:33 | |
| persia | So, anyway, I think it is important to also support the use case of "I don't care what anyone thinks" and show no priority. | 17:38 |
| SotK | and have a "show all" button available in all cases | 17:40 |
| SotK | ? | 17:40 |
| persia | I think so, especially the unauthenticated case, but I no longer consider score or unhiding important there: it is more about discovering who else cares, rather than appreciating priority, for me. | 17:51 |
| *** krotscheck_ has joined #storyboard | 18:30 | |
| *** krotscheck has quit IRC | 18:31 | |
| *** krotscheck_ is now known as krotscheck | 18:33 | |
| *** jseutter has quit IRC | 19:04 | |
| *** jseutter has joined #storyboard | 20:02 | |
| *** jseutter has quit IRC | 21:09 | |
| *** jseutter has joined #storyboard | 22:01 | |
| *** jseutter_ has joined #storyboard | 22:45 | |
| *** jseutter has quit IRC | 22:46 | |
| *** zigo has quit IRC | 23:14 | |
| *** zigo has joined #storyboard | 23:15 | |
| *** jseutter__ has joined #storyboard | 23:52 | |
| *** jseutter_ has quit IRC | 23:52 | |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!