| *** jjardon has quit IRC | 03:21 | |
| *** jjardon has joined #storyboard | 03:24 | |
| *** davidlenwell has quit IRC | 06:12 | |
| *** davidlenwell has joined #storyboard | 06:14 | |
| *** jtomasek has joined #storyboard | 08:06 | |
| *** jjardon has quit IRC | 08:51 | |
| *** jjardon has joined #storyboard | 08:56 | |
| *** jjardon has quit IRC | 09:02 | |
| *** jjardon has joined #storyboard | 09:10 | |
| *** jjardon has quit IRC | 09:15 | |
| *** betherly has quit IRC | 09:19 | |
| pedroalvarez | looks like the upgrade went ok :) | 09:19 |
|---|---|---|
| pedroalvarez | I triggered a check (using recheck) to see if zuul was working | 09:20 |
| pedroalvarez | Also I kind of missed some patches in storyboard: https://review.openstack.org/#/q/status:open+project:openstack-infra/storyboard | 09:21 |
| pedroalvarez | there are only three | 09:21 |
| pedroalvarez | but I guess we merged them | 09:21 |
| persia | https://review.openstack.org/#/q/status:open+project:openstack-infra/storyboard-webclient has the others | 09:22 |
| pedroalvarez | yeah, I wasn't missing those | 09:23 |
| persia | Oh, yeah, the rest merged well, I think. https://review.openstack.org/#/q/status:merged+project:openstack-infra/storyboard seems well-populated. | 09:25 |
| *** betherly has joined #storyboard | 09:38 | |
| *** jjardon has joined #storyboard | 09:40 | |
| *** openstackgerrit has quit IRC | 09:47 | |
| *** openstackgerrit has joined #storyboard | 09:47 | |
| SotK | I wonder if we should abandon jeblair's 2 really old patches | 09:51 |
| persia | Considering that the patch series mentioned in krotscheck's review of one of them is long-since merged, I think that is a safe candidate. | 09:54 |
| persia | I suspect the other one has also become uninteresting, with the paging API, paging preferences, and paging support in the UI. | 09:54 |
| persia | But I don't know enough to be confident. | 09:55 |
| SotK | that matches my belief too | 09:55 |
| persia | Oh well. I was hoping you knew enough to be confident about the other one :) | 09:55 |
| * SotK looks at them again | 09:56 | |
| SotK | ok, they both seem to be for working around the lack of paging, which is no longer an issue | 10:00 |
| SotK | I say we abandon them :) | 10:00 |
| persia | You have the powers :) They can be unabandoned, if someone is very concerned. | 10:00 |
| * SotK abandons | 10:02 | |
| persia | Leaving only one patch outstanding. Excellent. | 10:03 |
| SotK | sadly there are a couple of outstanding webclient patches too | 10:06 |
| persia | Yeah, that side has more. | 10:07 |
| SotK | one of which is the project groups thing, I wonder if we can get a consensus of how that should look today? | 10:07 |
| persia | Do we have mockups for that? | 10:08 |
| SotK | nope, just the various revisions the patch has been through | 10:09 |
| Zara | I don't think anyone has said anything about it since my last suggestion, might be wrong? | 10:33 |
| pedroalvarez | no really :/ | 10:34 |
| SotK | does anyone have opinions on Zara's last suggestion? | 10:42 |
| Zara | I think it's a great suggestino A+++ (in seriousness would probably help to see a mock or a patch if that's easier) | 10:45 |
| persia | This is https://review.openstack.org/253049 ? | 10:45 |
| Zara | ('suggestino', hm. 'suggestion'.) | 10:45 |
| SotK | persia: yes | 10:45 |
| Zara | woo, new gerrit | 10:46 |
| persia | Is patchset 3 the one on storyboard.sotk.co.uk? | 10:47 |
| SotK | nope, I shall make it so | 10:47 |
| Zara | aw, new gerrit is making me remember baserock's gerrit | 10:51 |
| persia | Zara: Because Baserock had newer gerrit? | 10:52 |
| Zara | think so, wasn't involved in the maintenance at all myself. ahh we can finally put comments in the precise place, I've missed that for months :) | 10:52 |
| Zara | (openstack's gerrit has annoyed me for ages, but it hasn't been helpful to say that, since I haven't been able to help, so haven't really mentioned it. am very happy about the upgrade!) | 10:54 |
| persia | There was a review-dev instance running newer gerrit the past six weeks or so, I thought. | 10:57 |
| persia | For next time, it always helps when folk use these test instances and provide feedback (even if the feedback is only "looks great: I really want that. Everything works for me.") | 10:58 |
| SotK | http://storyboard.sotk.co.uk/#!/project_group/list is now using patchset 3 of the project groups update | 11:04 |
| Zara | yeah, I was dimly aware of it but I'm always dimly aware of about 6 things that I should hunt for and comment on at some point. :) I think giving feedback can easily be a full-time job in openstack | 11:07 |
| persia | Inaccessible if not logged in :( | 11:08 |
| persia | And, if I log it, it auto-redirects to Dashboard. | 11:08 |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Add UI for complex permissions on boards and worklists https://review.openstack.org/235476 | 11:08 |
| persia | So -1 from me, but it might just be about where I'm looking at it. | 11:09 |
| persia | Zara: Indeed. "3-4 reviews per day" is considered a high level of activity around here. | 11:09 |
| SotK | oh huh, good spot persia | 11:10 |
| SotK | wait, it works for me | 11:10 |
| persia | Then that is probably worth debugging. | 11:10 |
| SotK | can you reproduce the issue? | 11:11 |
| * Zara suspects access token issues because it's always the access tokens, gah | 11:12 | |
| persia | I can reproduce. | 11:13 |
| Zara | (looking at about sha patch-- it'd be nice to correlate the shas to human-readable version numbers, but we'd need to get that versioning in place again first.) | 11:25 |
| SotK | yeah, that would be good if we ever get something to correlate them to :) | 11:25 |
| persia | To me, the only value to human-readable release numbers is if someone plans to support some release as a stable branch. Do you plan such support, or plan just pure contiuous delivery? | 11:26 |
| Zara | I think we should work toward stable branch releases, so yes, but it's not something I've planned in any depth | 11:26 |
| Zara | so 'plan to' in the sense of 'want to do this in the future' rather than 'have a plan' | 11:26 |
| persia | Sorry: my complaints about the layout were mostly because of an overagressive browser cache. I retract my -1 | 11:29 |
| persia | Zara: Yes. My default preference is always for continuous delivery, so that one fixes bugs in one place, and one is careful to release features in a way that does not break things for users. | 11:30 |
| persia | The OpenStack Storyboard is entirely CD, which I think is nice. | 11:30 |
| persia | Some of the other Storyboards are not entirely CD, but I don't know if that behaviour should be encouraged. | 11:30 |
| * SotK likes the CD too | 11:30 | |
| Zara | in practice, you can be careful but things still break. I like having an option for continuous delivery, for those who want to use it, and try to be as careful as possible, but I like stable releases as a safety net. (and also as markers for 'you can expect to find these features in this version', which would be arduous to find for every sha1) | 11:36 |
| Zara | eg: if you're installing a big group of projects with multiple incompatibilities, and you're forced to use an old version of one of those projects, it's helpful to know which version of, say, storyboard was compatible with it when current master isn't | 11:37 |
| *** betherly has quit IRC | 11:39 | |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Make kanban cards be the correct width https://review.openstack.org/256457 | 11:40 |
| persia | My experience with releases is that everyone waits for the release to report bugs, and then complains when the development team works on the development branch, rather than fixing the bugs or backporting new features to the release branch. | 11:40 |
| persia | But my experience may not be everyone's experience. | 11:40 |
| persia | As for installing a big group of things: for organisations that would find storyboard useful (where there are many project groups, each with many projects, etc.), I suspect that storyboard will generally be given one or more dedicated VMs. | 11:42 |
| persia | Especially because that way one can just grab stuff from our puppet modules to automate everything. | 11:42 |
| persia | (yes, non-puppet shops may need to fiddle a bit, but ...) | 11:42 |
| *** betherly has joined #storyboard | 11:44 | |
| Zara | yeah, that's the flipside. I still prefer it, because people will complain whatever we do, but that gives me the option to see a small list of versions with features, known bugs and incompatibilities and pick one based on my needs (and upgrade if those needs change/if the list of known bugs gets too long). that can be useful when you need a tool for a clearly defined job that's not likely to change for a while. | 11:45 |
| persia | The other worry is that one ends up with poor reviews. Because one of the other public operators of a Storyboard is so far behind, many users complain about features fixed months ago. | 11:46 |
| persia | Or look for alternate tools | 11:47 |
| SotK | that would be my main worry | 11:47 |
| Zara | there's nothing to stop someone using an old tarball without versions that we define, though. | 11:47 |
| persia | Since even the CD users complain about missing features or bugs, and the majority of users are CD users, I am surprised at the desire by developers to support more branches. | 11:47 |
| persia | Yes. Folk can use old tarballs, but if the project communication is that the right way to do it is to use CD, and people using old tarballs are considered silly and told to upgrade, the impact is less. | 11:48 |
| SotK | indeed | 11:48 |
| Zara | I disagree; CD has been the default view here and it hasn't had that effect. if we have versions, it means we have more control over what old versions other people use, and can avoid anyone using anything embarrassing. | 11:48 |
| * persia used to be a big fan of releases, but as a greater understanding of typical software development developed, came to understand that a "release" isn't usually actually any more stable or bug-free than a non-release, unless the team isn't being careful anyway | 11:49 | |
| persia | Zara: How? If we publish daily tarballs, someone could choose to consume any one of them. | 11:49 |
| persia | We can *recommend* people only use certain versions, but I don't understand why we would recommend someone use a version other than "master". | 11:50 |
| Zara | willing to bet people will look for a version before they resort to the daily tarball, for the reasons I gave above-- they have a quick record of what it can do relative to other versions. | 11:50 |
| *** jjardon has quit IRC | 11:51 | |
| persia | Fair, but, again, at what point do *you* want to recommend someone run something other than "master"? | 11:52 |
| * SotK doesn't know how we'd deal with the support implications implied by releases either | 11:53 | |
| persia | I think we're in agreement on telling people not to run old versions, and I think we're in agreement about making sure we have a recommendation so that people can use something we think is good. | 11:53 |
| Zara | maybe other people choose things in a very different manner to me; I know that when newest tempest wasn't appropriate with other old openstack components, the first course was to try the versioned releases instead of manually testing each sha1 to see if tempest were compatible with other things. and that worked, and saved a lot of time. maybe storyboard isn't analogous, I'm not sure. | 11:53 |
| *** betherly has quit IRC | 11:53 | |
| Zara | so I'm not saying 'we should encourage people to use releases', I'm saying 'make life easier for devs who can't use the option they'd ideally like' | 11:54 |
| Zara | I don't trust everyone to give storyboard a dedicated VM; I'd like to but I just don't xD | 11:54 |
| Zara | should people use master? yes. can they always use master? no. but I also don't have a lot of time to sink into the support side, so it's somewhat moot. it just seems less effort for us to say 'btw, you have x features in this release' compared to someone struggling to find that out. we're not obligated to do it, either way. | 11:57 |
| Zara | I just think it'd be nice of us! :P | 11:57 |
| *** jjardon has joined #storyboard | 11:59 | |
| *** jjardon has quit IRC | 12:11 | |
| SotK | do people think that its fine to just have the "Show x projects" and "Hide x projects" buttons, or would you prefer something like "> Show x projects" and "v Hide x projects"? | 12:12 |
| Zara | the latter is more consistent with the recent events list, don't think I'd block it either way tbh | 12:13 |
| * SotK will do the latter to avoid any remote chance of someone confusing the hide button for a project | 12:14 | |
| Zara | hahaha | 12:15 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Tidy up project groups states https://review.openstack.org/253049 | 12:29 |
| *** jjardon has joined #storyboard | 12:31 | |
| pedroalvarez | hep, ping me if you need some reviewing today :) | 12:33 |
| pedroalvarez | for things you want to merge before tomorrow, if any | 12:34 |
| persia | The storyboard review would be good to land, as some of the webclient stuff is blocked on it. | 12:34 |
| persia | (but I'm not an active developer, so someone may correct me) | 12:34 |
| persia | On the webclient, the ones that I think are most exciting are the commit sha and the email preferences, although project groups got discussed a lot, and should be in a final shape. | 12:35 |
| SotK | argh, still broken a bit -.- | 12:36 |
| persia | Maybe not that one yet, then :) | 12:37 |
| pedroalvarez | yeah, I'd love to see the email-preferences one merged, but the team decided to not merge until that can work in s.o.o IIRC | 12:37 |
| pedroalvarez | wich is fair | 12:38 |
| persia | Heh: this is why my preferences are untrustworthy :) | 12:40 |
| *** betherly has joined #storyboard | 12:41 | |
| Zara | the project groups patch is a blocker for unlimited pagination; that's the main reason I care about that patch. project groups aren't a big priority for me either. | 12:42 |
| pedroalvarez | well, time to create a board for storyboard?:??? | 12:42 |
| pedroalvarez | :D | 12:42 |
| SotK | probably | 12:44 |
| pedroalvarez | it should be the board number 1 | 12:44 |
| pedroalvarez | clearly | 12:44 |
| SotK | then time to discover that the UI for adding cards is extremely sub-optimal with a large database | 12:44 |
| pedroalvarez | https://storyboard.openstack.org/#!/board/1 | 12:44 |
| SotK | Zara: I believe that board is currently yours? | 12:45 |
| Zara | yes | 12:45 |
| pedroalvarez | Backlog Doing Review Done ? | 12:46 |
| Zara | there you go, you're now owners. | 12:46 |
| pedroalvarez | \o/ | 12:46 |
| Zara | I just wanted to have the first one. ;_; | 12:46 |
| SotK | :) | 12:46 |
| Zara | also to spot any bugs that would only be noticeable in master, don't think I noticed any | 12:47 |
| pedroalvarez | this is an epic day! | 12:47 |
| persia | Is this a priority worklist for storyboard, or a kanban board for tracking storyboard activities? | 12:48 |
| persia | Being called "test board" doesn't help :) | 12:48 |
| * SotK thinks the latter | 12:48 | |
| SotK | though we should probably have the former too | 12:48 |
| pedroalvarez | but lanes in kanban board can be used for priority too | 12:48 |
| Zara | it was a test board at the time of naming. it may now be something new | 12:49 |
| persia | The former could be a lane in the latter, really. | 12:49 |
| pedroalvarez | snap | 12:49 |
| persia | Depends how you want to work: do you prefer a priority list, or a status list. | 12:49 |
| persia | Both seems annoying to maintain, to me. | 12:49 |
| pedroalvarez | It'd be good to have the backlog of the kanban as a priority list | 12:49 |
| persia | Zara: Excellent use of "resolute" :) | 12:49 |
| SotK | pedroalvarez: +1 | 12:50 |
| pedroalvarez | the name of the column could be: prioritised backlog | 12:51 |
| pedroalvarez | just ideas :) | 12:51 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Tidy up project groups states https://review.openstack.org/253049 | 12:51 |
| SotK | (now fully functional) | 12:51 |
| persia | +1 to having the backlog lane be priority-ordered | 12:52 |
| Zara | :) | 12:52 |
| SotK | http://storyboard.sotk.co.uk/#!/project_group/list is now running the most recent version of https://review.openstack.org/253049 | 12:54 |
| persia | Could I ask that board 1 be cleaned up to be useful for how Storyboard is developed? | 12:57 |
| persia | I'd like to show it off, but it needs more lanes, better titles, etc. | 12:57 |
| pedroalvarez | I tried to | 12:57 |
| SotK | how urgently? | 12:58 |
| * SotK would like to obtain food in the imminent future | 12:58 | |
| persia | Not hugely: just a preference | 12:58 |
| Zara | mind if I take the reference to cores out? think it just tracks storyboard development atm, not specific to cores | 13:01 |
| SotK | go ahead :) | 13:01 |
| persia | I think removing "core" is much friendlier | 13:02 |
| *** jjardon has quit IRC | 13:02 | |
| persia | That only Storyboard cores have write access to the board would be sensible. | 13:02 |
| *** jjardon_ has joined #storyboard | 13:02 | |
| persia | If you granted access to other active developers, I think nobody would be surprised. | 13:03 |
| Zara | then changed it from 'StoryBoard Board' because that looked a bit odd | 13:03 |
| persia | But I wouldn't expect to be able to set your priorities, given my limited contribution. | 13:03 |
| Zara | but if anyone dislikes that, please change it back :) | 13:03 |
| Zara | I've put me, adam and pedro as owners for the moment | 13:03 |
| Zara | if we get annoyed with persia we'll set it to 'private' | 13:03 |
| Zara | B) | 13:04 |
| persia | I hope I can *read* it, I just don't expect to write it. | 13:04 |
| Zara | I believe you should be able to read it (unless it's private), just not write it, so fear not | 13:05 |
| Zara | I also need to head out soonish to measure a floor for a wardrobe and things. shouldn't be gone that long | 13:08 |
| persia | I can, although there appear to be no stories. | 13:08 |
| Zara | haven't put any in it yet! :) | 13:08 |
| * SotK adds one | 13:09 | |
| Zara | we'll want a way to click and drag a task we're currently viewing onto a board | 13:10 |
| SotK | we will indeed | 13:10 |
| SotK | or at least a button to do so | 13:11 |
| Zara | yeah | 13:11 |
| SotK | and also a way to search properly in the add card UI | 13:11 |
| Zara | heh | 13:11 |
| SotK | rather than the madness I made | 13:11 |
| Zara | still, it's a good start. :) | 13:11 |
| * persia is amused to see the process of dogfooding already generating so much input | 13:11 | |
| Zara | we should probably have a separate board just for worklists and boards :P | 13:11 |
| persia | So, these should be written up, and put in the priority backlog :) | 13:12 |
| persia | (because until you have a working board, it gets tricky to determine which of the other things need doing soonest) | 13:12 |
| Zara | it's mostly stuff we were already aware of, tbh, but weird recording tasks for things which aren't implemented. | 13:12 |
| * Zara disappears for a bit | 13:17 | |
| *** jjardon_ is now known as jjardon | 13:23 | |
| *** betherly has quit IRC | 13:29 | |
| *** betherly has joined #storyboard | 13:29 | |
| *** betherly_ has joined #storyboard | 13:32 | |
| *** betherly has quit IRC | 13:33 | |
| *** betherly_ is now known as betherly | 13:33 | |
| *** betherly_ has joined #storyboard | 13:41 | |
| SotK | oh dear, moving cards is giving a 500 error | 14:31 |
| Zara | argh, there's always something | 14:31 |
| SotK | but working | 14:31 |
| Zara | also wow that took longer than expected | 14:32 |
| Zara | protip: if you're assembling a bed, put the slats on *before* the mattress | 14:32 |
| Zara | I forgot there were slats | 14:32 |
| SotK | hahaha | 14:32 |
| Zara | I spent about 20 minutes wrestling with a double mattress that was waaaaay too heavy for me, while it kept falling under the bed or sliding off one side when I put it on the other | 14:32 |
| Zara | I was like 'HOW DO PEOPLE BALANCE THESE THINGS' | 14:33 |
| Zara | then went into the other room and saw the slats and remembered them | 14:33 |
| Zara | I didn't even intend to go to assemble the bed but there was a chance to do DIY and I'm only human... | 14:33 |
| Zara | I'm stayin' laaaate tonight~ | 14:33 |
| pedroalvarez | hm,,, I can't move cards into empty lanes | 14:36 |
| SotK | argh | 14:38 |
| pedroalvarez | :) | 14:38 |
| SotK | ha, that will be caused by the "make cards the right width" patch | 14:39 |
| SotK | I bet the droppable area becomes non-existent now it has display:inline-block | 14:40 |
| SotK | oops | 14:40 |
| pedroalvarez | roar! | 14:40 |
| SotK | indeed it does | 14:40 |
| pedroalvarez | oh yes, it's only a tiny bit on the top-left corner | 14:42 |
| pedroalvarez | the droppable area | 14:42 |
| pedroalvarez | but then, lanes with cards look awful | 14:42 |
| pedroalvarez | (if you revert that change) | 14:42 |
| SotK | setting a min-width and min-height will fix it | 14:43 |
| SotK | but moving a card into a lane on master eats the card | 14:46 |
| SotK | s/master/s.o.o/ | 14:46 |
| pedroalvarez | nope | 14:47 |
| * pedroalvarez plays with the tet card story | 14:47 | |
| pedroalvarez | test* | 14:47 |
| SotK | wait, is that card really small for you? | 14:48 |
| pedroalvarez | that might be the reason of the extralong cards too? | 14:48 |
| SotK | could be | 14:49 |
| pedroalvarez | I bet because of the "task_assignee_changed" one | 14:49 |
| pedroalvarez | too long string | 14:49 |
| SotK | aha! | 14:49 |
| pedroalvarez | removing inline-block makes it bigger | 14:50 |
| *** betherly_ has quit IRC | 14:54 | |
| SotK | I don't get why it all works fine on my test instance but s.o.o is so completely broken | 14:58 |
| pedroalvarez | do you want me to put the same version on teststoryboard.b.o? | 14:59 |
| SotK | that would be helpful, thanks :) | 15:00 |
| * pedroalvarez triggers ansible | 15:00 | |
| SotK | whaaa, I've now just moved a card without a 500 error | 15:35 |
| Zara | ~why not~ | 15:36 |
| SotK | seems only to happen when a lane with a bunch of cards in is updated | 16:02 |
| SotK | (currently this is a bit silly and makes a PUT request for each card in the affected lane) | 16:03 |
| pedroalvarez | up in teststoryboard | 16:07 |
| Zara | I've forgotten my baserock openid and trying to reset it didn't work, btw | 16:07 |
| pedroalvarez | :( | 16:08 |
| SotK | ooh, I see the error in teststoryboard \o/ | 16:08 |
| pedroalvarez | do you want ssh access? | 16:08 |
| SotK | yes please :) | 16:09 |
| Zara | so I can't login to teststoryboard (and the 'reset password' for openid not working may also be something the baserock team need to fix) | 16:09 |
| pedroalvarez | SotK: /msg me your ssh public key please | 16:09 |
| SotK | everything is broken today | 16:09 |
| SotK | pedroalvarez: done | 16:10 |
| pedroalvarez | SotK: done | 16:12 |
| SotK | thank you :) | 16:12 |
| pedroalvarez | np | 16:14 |
| pedroalvarez | feel free to change to launchpad openid if you have problems with the baserock one | 16:14 |
| Zara | how do I do that? I'm trying to get into teststoryboard but the login button defaults to openid.baserock.org | 16:16 |
| pedroalvarez | it was for SotK who has root access now | 16:16 |
| pedroalvarez | (the comment) | 16:16 |
| SotK | gah now I can't see the error again | 16:17 |
| Zara | oh, right | 16:17 |
| SotK | all I did was `less /var/log/apache2/error.log`, `less /var/log/storyboard/sb.log`, and `tailf /var/log/storyboard/sb.log` | 16:18 |
| Zara | some kind of race condition? | 16:18 |
| Zara | maybe doing the less took some time I have no idea | 16:19 |
| SotK | saw it again briefly | 16:19 |
| Zara | maybe it's shy | 16:19 |
| SotK | hooray a log | 16:19 |
| SotK | this is very odd | 16:20 |
| Zara | tbf, 'very odd' happens weekly | 16:21 |
| SotK | looks like pika is exploding for some reason | 16:21 |
| * Zara googles pika, gets animal pics, eventually sees it's a python pkg | 16:22 | |
| SotK | it handles publishing notification events to rabbitmq | 16:22 |
| Zara | 'A pika is a small mammal, with short limbs, very round body, rounded ears, and no external tail'-- I'm just going to imagine that you can find one of those inside every storyboard instance | 16:23 |
| Zara | suddenly it all makes sense. | 16:24 |
| -openstackstatus- NOTICE: Zuul is moving in very slow motion since roughly 13:30 UTC; the Infra team is investigating. | 16:43 | |
| SotK | OK, I have a workaround for the 500 error :D | 17:40 |
| Zara | \o/ | 17:40 |
| SotK | I'll send a patch in a second | 17:41 |
| Zara | :) I'll test it asap | 17:41 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard: Workaround 500 error when moving items in worklists https://review.openstack.org/259128 | 17:47 |
| Zara | testing now \o/ | 17:49 |
| pedroalvarez | Rabbitmq is still something I don't know anything about | 17:51 |
| pedroalvarez | might be some differences in dev and prod | 17:51 |
| SotK | seems like pika is breaking sometimes, idk why properly | 17:52 |
| Zara | my other notifications seem fine, which I thought I should check for just in case. no weird errors. can't test everything, but doesn't seem to break anythign else for me so far | 17:52 |
| openstackgerrit | Adam Coldrick proposed openstack-infra/storyboard-webclient: Fix various style bugs with cards https://review.openstack.org/259131 | 17:53 |
| SotK | can we please merge both of those? :D | 17:55 |
| * pedroalvarez tests the latter | 17:55 | |
| Zara | first one merged | 17:57 |
| SotK | \o/ | 17:57 |
| Zara | I haven't seen the super wide cards issue | 17:57 |
| Zara | is it a chrome thing, or is there a link? | 17:57 |
| Zara | unless you mean tall cards? | 17:57 |
| SotK | nope, I mean wide | 17:58 |
| pedroalvarez | Zara: http://teststoryboard.baserock.org/#!/board/2 | 17:58 |
| Zara | huh @_@ | 17:58 |
| Zara | weird, that didn't happen on mine | 17:59 |
| Zara | or was mine created after it was patched behind the scenes? | 18:00 |
| pedroalvarez | I think the inline-block patch introduced this regression | 18:00 |
| Zara | (http://teststoryboard.baserock.org/#!/board/4 ) | 18:01 |
| pedroalvarez | yeah, the problem is with longnames | 18:02 |
| SotK | that board doesn't have something with a long enough name | 18:02 |
| pedroalvarez | but without whitespaces | 18:02 |
| pedroalvarez | somethinkuselesslikethis | 18:02 |
| pedroalvarez | s/k/g/ | 18:02 |
| Zara | oh, right, I thought we didn't care about that because it wasn't going to happen | 18:02 |
| pedroalvarez | it actually happened | 18:02 |
| pedroalvarez | and in our board | 18:03 |
| SotK | just not very badly thankfully | 18:03 |
| pedroalvarez | come on grunt! you can compile this thing faster | 18:03 |
| Zara | but we know the longnames one breaks drag and drop? | 18:04 |
| Zara | into new lanes? | 18:04 |
| SotK | what do you mean? | 18:05 |
| Zara | I thought the reason drag and drop into new lanes, unless done from the top left corner, wasn't working was because of the cards width patch | 18:05 |
| Zara | s/new lanes/empty lanes | 18:06 |
| SotK | different cards width patch :) | 18:06 |
| SotK | heh | 18:06 |
| Zara | ahaha | 18:06 |
| * SotK has made a right mess of it all | 18:06 | |
| Zara | lol, because that bit seemed to work on curent master | 18:06 |
| SotK | https://review.openstack.org/259131 fixes the drag and drop too | 18:06 |
| pedroalvarez | yay! http://teststoryboard.baserock.org/#!/board/2 | 18:06 |
| Zara | so I was thinking 'idk that solving the edge case of long names is preferable to good drag and drop, but it's because I had things mixed up. | 18:07 |
| Zara | xD | 18:07 |
| Zara | will test now, thanks for being patient | 18:07 |
| pedroalvarez | works good from phone too | 18:09 |
| pedroalvarez | anymore before I leave? | 18:10 |
| * SotK doesn't think so | 18:10 | |
| SotK | thanks for sticking around to help :) | 18:11 |
| pedroalvarez | right! enojoy your holidays!! :D | 18:11 |
| pedroalvarez | no problem | 18:11 |
| Zara | hm, the title of a long no-whitespace task goes out of the modal but that's a fix for another time | 18:11 |
| Zara | yeah, thanks pedroalvarez! | 18:11 |
| SotK | yeah I'm going to rework that modal as soon as I can anyway :) | 18:12 |
| Zara | np | 18:12 |
| SotK | adding to boards is currently pretty arduous | 18:12 |
| pedroalvarez | anytime | 18:12 |
| pedroalvarez | let's hope zuul merges this | 18:12 |
| * SotK has fingers crossed | 18:13 | |
| Zara | okay, it seems to work fine, can't find anything else it's breaking | 18:13 |
| SotK | \o/ | 18:13 |
| Zara | anything else to do, or am I okay to catch a train? | 18:27 |
| SotK | I think you're OK to catch a train :) | 18:27 |
| Zara | woop! \o/ | 18:27 |
| openstackgerrit | Merged openstack-infra/storyboard: Workaround 500 error when moving items in worklists https://review.openstack.org/259128 | 21:09 |
| openstackgerrit | Merged openstack-infra/storyboard-webclient: Fix various style bugs with cards https://review.openstack.org/259131 | 21:12 |
| SotK | \o/ | 21:41 |
| pedroalvarez | Good | 22:08 |
| SotK | now we just to wait for them to filter through to storyboard.o.o | 22:34 |
| pedroalvarez | Going sloooooow | 22:37 |
| pedroalvarez | But eventually.. | 22:37 |
| * SotK wonders why his browser is saying review.openstack.org's cert has been revoked | 22:38 | |
| SotK | I suspect its something on my end, given it works elsewhere | 22:38 |
| pedroalvarez | Yeh, my phone dke | 22:39 |
| pedroalvarez | .. didn't complaint | 22:39 |
| SotK | yeah, even using a different browser is working now, weird | 22:40 |
| SotK | seems like its updated now | 23:13 |
| SotK | after adding some things, I suspect our backlog is too long to be fully prioritised :) | 23:24 |
| persia | That is why I like worklists. Nobody ever fully prioritises all the bugs, or at least not in a project with any number of users. | 23:54 |
| persia | Instead, one picks some that are obviously priorities, and if the list gets too short, adds some more (but usually, the list does not get too short because bugs are escalated). | 23:55 |
Generated by irclog2html.py 2.14.0 by Marius Gedminas - find it at mg.pov.lt!