13:02:36 #startmeeting meeting 13:02:37 Meeting started Mon Oct 17 13:02:36 2016 UTC. The chair is mvollmer. Information about MeetBot at http://wiki.debian.org/MeetBot. 13:02:37 Useful Commands: #action #agreed #halp #info #idea #link #topic. 13:02:37 The meeting name has been set to 'meeting' 13:02:45 .hello andreasn 13:02:47 .hello mvo 13:02:48 andreasn: andreasn 'Andreas Nilsson' 13:02:51 mvollmer: mvo 'Marius Vollmer' 13:02:55 #topic Agenda 13:03:31 .hello larsu 13:03:32 larsu: larsu 'Lars Karlitski' 13:03:37 .hello dperpeet 13:03:38 dperpeet: dperpeet 'None' 13:03:41 * atomic images 13:03:44 * outreachy 13:04:06 * small storage list pattern update 13:04:58 * docker redesign 13:05:14 let's start 13:05:20 #topic atomic images 13:05:46 we are nearing getting more current atomic images again 13:05:49 via pull request https://github.com/cockpit-project/cockpit/pull/5152 13:06:01 it's a rebase of stef's work with some patches 13:06:15 that includes the fedora-atomic image 13:06:29 I've been looking at rhel-atomic, but that isn't done yet (tests failing) 13:06:41 and continuous atomic currently doesn't work at all 13:07:23 that's because kubernetes has been removed from continuous atomic builds https://github.com/cockpit-project/cockpit/pull/4942 13:07:42 is this going to happen on the other atomic systems as well? 13:08:02 do we need to update them all together? 13:08:12 no 13:08:19 the first pr I listed updates fedora-atomic 13:08:32 rhel-atomic is another pr and blocked 13:08:42 right 13:08:47 continuous-atomic is closed, since we need to install things differently 13:10:13 well, let's get fedora-atomic fixed pretty soon at least 13:10:25 the image isn't all that current, but better than what we have now 13:10:49 and it moves us from f23 to f24, right? 13:11:07 right 13:11:23 and makes sure to download the correct base image 13:11:27 should we mark this "priority" maybe? 13:12:08 good idea, done 13:13:31 cool 13:13:52 i think stuff that blocks image updates should be automatically priority 13:14:20 we didn't run the storage tests on f25 for some time 13:14:24 makes sense 13:14:29 and now that we finally can, we find the bugs 13:15:30 alright, next? 13:16:13 #topic outreachy 13:16:28 mclasen was asking here about outreachy on the weekend 13:16:37 application deadline is today 13:16:50 but I didn't know specifics. did he read you dperpeet or stefw? 13:17:40 mclasen did not contact me about outreachy yet 13:18:20 he wanted to know if you have candidates ready 13:18:55 I thought they have already started .... :-) 13:19:21 we have three potential candidates who already did contributions on issues 13:19:26 i think dperpeet is working on this ... there was third possible last minute applicant ... but it may be too late for that 13:19:27 well, what I wanted to say: thanks to everyone who has contributed to cockpit so far, I'm looking forward to seeing who actually applies 13:19:47 I think we may have four or five applicants 13:20:05 nice 13:20:11 [cockpit] stefwalter opened pull request #5170: ws: Fix testing race with ssh-agent unix socket (master...ssh-agent-socket-race) https://git.io/vPPjw 13:20:17 dperpeet, are all applicants for design tasks? 13:20:19 but we will only be able to take one UX project and at most one dev project 13:20:50 stefw, I can get back to that question next week once we know who has actually applied 13:20:54 ok 13:21:03 but all the contributions towards cockpit have been from UX applicants so far 13:21:22 and as with GSoC, we value prior contributions very highly when looking at applications 13:21:58 agree 13:21:58 andreasn and I discussed the possibility of taking more than one UX project 13:22:07 but we decided that we couldn't, with good conscience 13:22:25 we want to provide good mentorshop 13:22:30 *mentorship / mentoring 13:22:34 I think next round could be a good opportunity to do several, but this round it would be best to focus on one 13:23:10 but I'm really happy to see more than one good candidate! 13:23:32 the good news is that Outreachy is twice a year 13:23:57 end of topic 13:24:23 #topic small storage list pattern update 13:24:31 I am still working on that 13:24:45 had to stop myself from doing too much redesign already now 13:24:51 I didn't get around to review the latest changes yet 13:24:57 but I am quite happy where this is going 13:25:19 andreasn, I start to think that the Format button is hard to find in its new place 13:25:40 but I am already getting used to the new design 13:25:45 could be. I want to try it out in action 13:25:51 but I'm open to moving it if needed 13:26:19 e.g., it's not immediatly visible after creating a new logical volume 13:26:32 right, it breaks the logical flow a bit 13:26:40 [cockpit] stefwalter pushed 3 new commits to master: https://git.io/vPXe2 13:26:40 cockpit/master 28d202a Marius Vollmer: test: Update fedora-25 to fix storaged SELinux issues... 13:26:41 cockpit/master 57b4841 Marius Vollmer: test: Expect to be able to manage Docker storage on fedora-25... 13:26:41 cockpit/master 36abf2b Marius Vollmer: storaged: Allow for more creative rounding in the storage stack... 13:26:58 hard to tell what is the next logical step 13:27:47 so yeah, it's a concern 13:27:55 I'll take a look at the PR again 13:28:02 but this new design gives us so many more options for the future 13:28:09 really nice, IMO 13:28:35 end of topic 13:28:48 #topic docker redesign 13:29:20 I think it is coming along quite nicely 13:29:29 and I want to get the current state in, if nobody objects 13:29:48 what's the PR? 13:29:51 there are a couple of things from the new design missing (cards on top, additional tabs) 13:29:57 but those are not regressions 13:30:02 right 13:30:15 I think the cards are more of the atomic scan step 13:30:16 the one regression that dperpeet brought up would be the "danger mode", which is replaced by selection mode 13:30:34 but I'd like to postpone that, because it needs quite some changes to the listing view as well 13:30:44 (again, if nobody objects) 13:30:55 andreasn: the pr is 4952 13:30:58 thanks 13:30:58 [cockpit] stefwalter opened pull request #5171: test: Fix race where sosreport takes too long (master...race-sosreport-too-slow) https://git.io/vPXvJ 13:31:00 danger mode has always been dubious 13:31:13 in particular because rows disappeared as you were clicking buttons 13:31:17 I wouldn't consider that change a blocker 13:31:17 which really is risky 13:31:31 you can still delete containers from the overview, but you need to expand the rows 13:31:33 I think we need more top-down design to decide what we want to do there 13:31:38 yeah 13:31:40 dperpeet, yup 13:31:53 once we have a listing, we can tinker with it in a separate pr 13:31:54 stefw: I agree, and dperpeet had a good idea to alleviate that with simply waiting a while before deleting the container 13:32:11 which needs further design thought 13:32:16 oh, my press and hold button idea :) 13:32:19 if we do add a multi-select/danger mode to the listing view ... we should do it properly 13:32:30 and likely not change/remove rows while in that mode 13:32:36 yeah 13:32:41 just gray them out or something like that ... with a status of what happened 13:33:02 ok ... larsu so no blockers on this? 13:33:10 why is it listed as blocking on a closed pull request? 13:33:20 it's blocking on the listing view one 13:33:25 which is closed 13:33:33 24 days ago? 13:33:43 https://github.com/cockpit-project/cockpit/pull/5043 13:33:47 yeah, larsu do you mean a different pr? 13:34:12 oh yeah, how did that happen 13:34:20 I mean 5156 13:34:31 i can merge that 13:34:32 looks good 13:34:35 cool, thakns 13:35:02 stefw, did you try the playground on #5156? 13:35:23 this changes the basics of our select pattern implementation 13:35:36 i guess jump in on the review then 13:35:38 and changes API in lib/cockpit-components-select 13:35:49 yes, like stated earlier I want to try this out 13:35:52 those are fine for API changes 13:36:10 oh i guess your comment on the PR got hidden 13:36:13 Github things :S 13:36:14 * larsu think he caught everything using that 13:36:27 no, when we discussed this earlier today on irc :) 13:36:28 but yeah, please have another look 13:36:42 I can merge it once tests pass 13:36:45 and I've looked 13:36:48 stefw: that issue is mostly fixed with the new review system 13:36:53 dperpeet: thanks! 13:37:20 if you find this to not be ready, I could also amend the docker one to use the old way of doing things 13:37:44 anyway, getting this in so that I can base the image scanning stuff on top of that would be great 13:37:53 otherwise, end of topic from my side 13:38:11 yes, too many blockers here 13:38:15 yes, let's get it in soon 13:38:17 that's why i'm trying to jump in on the review 13:40:32 mvollmer, end of topic? 13:40:42 yeah 13:41:01 #topic any other buisness 13:41:07 *bushness 13:42:29 alright 13:42:34 thanks everyone! 13:42:44 #endmeeting