Monday, 2018-03-05

*** udesale has joined #storyboard04:21
*** udesale_ has joined #storyboard06:03
*** udesale__ has joined #storyboard06:05
*** udesale has quit IRC06:07
*** udesale_ has quit IRC06:09
*** jtomasek has joined #storyboard08:17
*** udesale_ has joined #storyboard11:03
*** udesale__ has quit IRC11:06
*** udesale_ has quit IRC11:09
*** udesale has joined #storyboard13:10
*** udesale has quit IRC13:11
*** udesale has joined #storyboard13:12
aspiershi all, if someone adds a task to an existing story, does that automatically subscribe them to comments on the story?14:26
aspiersdiablo_rojo_phon, SotK, persia, Zara_: actually before that I should ask if you got home OK :)14:27
SotKaspiers: it doesn't, though I think we should probably implement that at some point14:27
persiaaspiers: Yes.  I hope you as well.14:28
aspiersSotK: thanks14:28
persiaAs a Launchpad user, I often have use cases where I do not wish to be subscribed to stories where I have added tasks.14:28
aspierspersia: yep, journey wasn't too bad despite Cityjet's best efforts to ruin it14:28
SotKaspiers: I got home safely thanks, hope you did too (I assume you did, as you are here)14:28
persiaA common example use case is in dealing with stable support: as a developer I want to be able to fix a task in master, and open a task suggesting backporting, and then tell the stable team to go mark that task as invalid if they don't want to do it or otherwise deal with it.14:29
persiaBut as I have now done the part I care about, I may not want to be subscribed to the story anymore.14:29
aspierspersia: sure. What do you think about making auto-subscription the default, though, so as to discourage "dump and run" behaviour?14:29
persiaSince the default notification policy is "do not notify", I'm not sure that change will do what you wish :)14:30
aspiersand also to avoid people being accidentally out of the loop on stuff they really do want to track14:30
persiaFor folk who leave notification disabled, subscription is mostly about managing the dashboard.14:30
aspiersThere is a strong precedent in other systems for auto-subscription when you contribute to something14:30
persiaThere is a strong precedent in other systems for automatic notification on subscription.14:31
persiaSince that was already decided to be disabled, I'm not sure that we should follow the other bits of the precedent without considering what that means in the absence of notification.14:31
persiaI'm not opposed, but I do think it needs a bit of thought, as only people who expressly enabled notification would be notified of changes, whether autosubscribed on activity or subscribed by others.14:32
aspiersRight, so "notification" and "subscription" are different thingss14:32
aspiersThis damn 's' key14:32
persiaYes.14:32
aspiersI'm talking about auto-subscription, not auto-notification14:32
aspiersThey are somewhat orthogonal14:33
persiaRight.  I don't think autosubscription will reduce dump&run nor cause folk to be more involved in a conversation in the absence of notificaiton.14:33
aspiersI think it will do the latter to some extent14:34
persiaAnd I think autosubscription could be incredibly painful for people who run scripts (e.g. "add tasks for all maintained branches for these N CVEs")14:34
aspierssince some people actually look at their subscription dashboard hopefully14:34
persiaWhy do you think it will do the latter?14:34
persiaThat makes sense.14:35
aspierspeople who look at their subscription dashboard will see activity on things they are involved in14:35
persiaBut I wonder if we don't want to change "Stories created by me" to be "Stories and Tasks created by me" or similar.14:35
aspierswithout automatic subscription, it would be far too easy for them to miss that14:35
aspiersthis points to another issue I discussed with Zara_14:36
persiaOr is the point of using subscription for this to enable unsubscription for folk who are truly done with a story?14:36
aspierswhich is that I think tasks should support comments14:36
persiaThey do.  They just don't support comment threading or persistence.14:36
aspiersyou mean task *notes*, or something else?14:36
aspiersI don't mean notes, I really mean comment14:36
persiaI do mean "notes" :)14:36
aspierscomments14:36
aspiersSo, rephrasing: the existing task notes mechanism doesn't cut it for me14:37
persiaSo, what part of using Launchpad do you find annoying because Launchpad puts all comments in a single bug in a single comment stream?14:37
persiaI'm not terribly opposed, but given that it's a complaint I have yet to hear about LP (and I've heard *lots* of complaints about LP), I wonder if there is a layer mapping issue.14:38
aspiersI don't understand that question :)14:38
aspierssorry14:38
persiaSo, launchpad provides a single unified comment stream for all bugtasks in a bug.  Storyboard does the same, except "bugtask"=="task" and "bug"=="Story".14:38
persiaIn the event that a user is reporting a usability problem with LP, it is interesting to help Storyboard not have that problem.14:38
persiaIn the evcent that a user has no issues with the LP interface for this, but issues with the SB interface, I wonder if there is a difference in conceptual mapping that is better resolved through documentation.14:39
aspiers"bugtask"=="task" is the bit I somewhat disagree with, as we already discussed in Dublin14:39
aspiersIIRC we agreed that bugtasks are a poor substitute for tasks which happen to work on most/all the scenarios Launchpad needed14:40
aspiersbut they do not work for my use cases14:40
persiaI remember discussing it, I don't remember reaching consensus.  I can say that SB "task" is explicitly modelled on LP "bugtask", except with the limitation of one task per project per story removed.14:40
*** tosky has joined #storyboard14:40
aspiersthe LP scenarios are related to tasks such as backporting14:40
persiaIf each task is to have a separate comment thread, and to be truly separate, I am less certain how they fit in the same story.14:41
aspierserr, maybe not backporting14:41
aspierstrying to remember14:41
aspierssomething to do with applying the same kind of change across a bunch of projects14:41
persiaAlso backporting (in that a bugtask can be mapped to a project or a release in a project)14:41
persiaJust doesn't allow multiple tasks against the same branch of the same project.14:41
aspierse.g. look at https://storyboard.openstack.org/#!/story/200143914:41
aspierstotally different use case14:41
aspiersI will now append a comment and lament the fact that it would not be seen by mugsie except for the fact that I'm mentioning his nick here14:42
persiaDepends on how he uses Storyboard, but yes, if he isn't subscribed, doesn't have notifications, and isn't using some other tooling to find out about changes, it might be a while before he sees it.14:43
persia(or if his notifications go to a black hole, as do my LP notifications, by way of example)14:43
aspiersall three of those conditionals are very likely to be true14:44
persiaYes.  I still think it better to put it in SB than put it in an etherpad, which is how much of this sort of thing has been tracked in the past.14:44
persia(where putting it in an etherpad has all the same negative aspects)14:45
aspiersexactly14:45
aspiersStoryboard has the potential to solve these kinds of things14:45
aspiersI suggest the case where a task contributor would benefit from auto-subscription is more common than the one where it would be a nuisance14:46
aspiershaving said that, there's no reason (momentarily ignoring lack of dev resources) why it couldn't be made optional14:46
aspierse.g. "always auto-sub" / "never auto-sub" / "ask me each time I add a task"14:47
aspierslet me tweak that slightly:14:47
aspierse.g. "always auto-sub" / "never auto-sub" / "ask me each time"14:47
aspiersand those would be the choices for several options, such as "when I add a task", "when I comment on a story" etc.14:48
aspiersI think existing precedents justify defaulting to "always"14:49
aspiersbut maybe only for the web UI; this could be skipped for API calls14:49
aspierspersia: I will submit a story for that14:57
*** diablo_rojo_phon has quit IRC14:57
toskytalking about notifications: it seems that preferences for email notifications are not saved14:57
aspiersoops14:57
*** diablo_rojo_phon has joined #storyboard14:58
toskythere is a story for that: https://storyboard.openstack.org/#!/story/200122914:58
SotKthey are saved, its just a visual bug iirc15:00
SotKyou may still not receive emails, I'm not sure on the status of our request to remove storyboard.o.o's host from the relevant blacklist15:00
toskyoh15:02
toskycan you please add this detail the story?15:02
SotKI will do so later when I've checked that I'm not misremembering15:03
toskythanks!15:04
toskyI have a question about the installation: after following https://docs.openstack.org/infra/storyboard/install/development.html , I'm not sure how to login15:05
toskythere is step about making your user admin, but that's after logging in the first time15:05
toskywhich fails for me with an error about the validity of valid_oauth_client15:05
SotKtosky: can you paste the error please?15:07
toskySotK: http://paste.openstack.org/show/691849/15:08
toskyI enabled the valid_oauth_clients key, removed storyboard.openstack.org, left localhost and added the public IP of the instance that I'm using for testing15:08
persiaaspiers: I think a preference defaulting to "always" makes sense.  I'm just not sure we've separated the goals we are achieving from implementation details in other systems.15:11
toskySotK: nevermind and sorry: PEBKAC, a blatant typo in the valid_oauth_clients key15:21
SotKtosky: heh, glad you figured it out15:23
*** openstackgerrit has quit IRC15:34
aspierspersia: https://storyboard.openstack.org/#!/story/200162515:38
aspiersSotK, Zara_: is there already a story for an "Assign to me" button?16:18
aspierssearch seems completely broken so can't find it16:19
SotKaspiers: I don't think there is one16:26
aspiersSotK: there is now ;-)16:26
SotKthanks :)16:27
aspiersoh no, I didn't create that yet16:27
SotKhttps://review.openstack.org/#/c/548058/ should make search less broken16:27
aspierswill create now16:27
aspiersoh great, yeah search is currently pretty broken16:27
aspiershttps://storyboard.openstack.org/#!/story/200162916:28
SotKyep, even more so than usual xD16:28
aspiersIRC bot doesn't announce submission of new stories yet?16:28
*** udesale has quit IRC16:29
SotKnot yet, it doesn't have any storyboard integration afaik16:30
aspiersok16:42
aspiersSotK: https://storyboard.openstack.org/#!/story/200163016:44
*** jdandrea has quit IRC16:47
*** jdandrea has joined #storyboard16:47
SotKaspiers: thanks17:02
*** openstackgerrit has joined #storyboard17:22
openstackgerritMerged openstack-infra/storyboard master: Fix login when using python 3  https://review.openstack.org/54559617:22
openstackgerritMerged openstack-infra/storyboard-webclient master: Use icons.less for tasks, worklists, and boards  https://review.openstack.org/54567517:45
*** jamesmcarthur has joined #storyboard17:46
Zara_SotK: I just posted a completely useless review on 548244 but I thought you might enjoy it anyway17:47
Zara_I remember we discussed it but I didn't realise you'd actually sent a patch, haha17:48
openstackgerritMerged openstack-infra/storyboard-webclient master: Upgrade node version in tests to 6  https://review.openstack.org/54570317:49
Zara_heh, biggest pet peeve atm: back button. makes reviewing 300x slower for webclient changes. I know sam thursfield left a story about this approx 200 years ago but it's still true17:58
openstackgerritZara proposed openstack-infra/storyboard-webclient master: Make $scope.project into a promise in the detail view  https://review.openstack.org/54824318:03
Zara_the js draft build for that wasn't loading icons, so rebased that.18:04
Zara_will see if it makes a difference; looked fine on my machine18:04
Zara_well I didn't get to 548244 buuut I'm done for the day18:05
Zara_o/18:05
*** Zara_ is now known as zara_the_lemur__18:05
zara_the_lemur__(I'm on freenode twice but don't want to mess around with my channels for now)18:06
*** jamesmcarthur has quit IRC18:24
*** jamesmcarthur has joined #storyboard18:24
*** diablo_rojo has joined #storyboard18:41
*** jamesmcarthur has quit IRC18:56
*** jamesmcarthur has joined #storyboard18:57
*** jamesmcarthur has quit IRC18:57
*** jamesmcarthur has joined #storyboard18:57
*** jamesmcarthur has quit IRC19:14
*** tosky has quit IRC19:31
*** tosky has joined #storyboard19:35
*** jamesmcarthur has joined #storyboard21:02
*** jtomasek has quit IRC21:04
*** jamesmcarthur has quit IRC21:06
*** tosky has quit IRC21:38
*** jamesmcarthur has joined #storyboard21:59
*** jamesmcarthur has quit IRC22:00
*** jamesmcarthur has joined #storyboard22:00
*** tosky has joined #storyboard22:08
SotKargh the publish job is still broken :(22:18
SotKturns out we do use version_from_git after all22:24
SotKs/_/-/22:24
persia:(22:24
SotKI will attempt to find time to fix the bug in version-from-git asap, but I probably won't have time until Thursday22:26
persiaGiven that the wbapp hasn't updated in > 6 months, I don't think  < 6 days more will hurt anyone, although active bug reporters may report more known (or even resolved) issues.22:27
*** jamesmcarthur has quit IRC23:59

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