14:03:53 #startmeeting Cockpit weekly meeting 160321 14:03:53 Meeting started Mon Mar 21 14:03:53 2016 UTC. The chair is andreasn. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:53 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:53 The meeting name has been set to 'cockpit_weekly_meeting_160321' 14:04:06 .hello dperpeet 14:04:07 dperpeet: dperpeet 'None' 14:04:13 .hello andreasn 14:04:14 andreasn: andreasn 'Andreas Nilsson' 14:04:27 .hello stefw 14:04:27 stefw: stefw 'Stef Walter' 14:04:53 #topic agenda 14:05:35 * known issues 14:05:44 * selinux troubleshooting 14:06:00 .hello mulhern 14:06:01 mulhern: mulhern 'None' 14:06:17 * GSoC 14:06:21 yup, that's me. 14:06:32 * Debian builds 14:06:43 mulhern, yay, I'm not the only 'None' person here. 14:06:50 :) 14:07:59 ok, lets start 14:08:04 #topic Known Issues 14:08:14 This is related to our integration tests 14:08:29 as you know, some issues happen fairly often and thus clobber the github issue threads 14:08:40 that made us learn about the comment limit =) 14:08:56 I've done some work to reduce the verbosity: https://github.com/cockpit-project/cockpit/pull/4049 14:09:10 Posts look like this: https://github.com/cockpit-project/cockpit/issues/4001#issuecomment-199257031 14:09:28 the idea is to have one comment per context (e.g. fedora-atomic or fedora-24) 14:09:41 this will get updated as the error occurs 14:09:59 and it'll keep the first and last 10 occurrences of the error 14:10:07 with links to the logs, if present 14:10:32 for each traceback, there'll be a different "section" 14:10:34 looks much nicer 14:10:40 thanks 14:10:54 as an added bonus, I think comment edits don't generate notification e-mails 14:11:15 if you're waiting for an error to happen, this might be a bad thing, so let me know if this concerns you 14:11:34 we could add a mechanism to ping users 14:11:51 but in my opinion our problem was/is rather too much notification traffic 14:12:03 end of topic from my side 14:12:36 #topic SELinux Troubleshooting 14:12:49 There's still the work in progress here: https://github.com/cockpit-project/cockpit/pull/3962 14:13:08 updated test images have been merged today https://github.com/cockpit-project/cockpit/pull/4046 14:13:34 and last weekend I figured out (thanks petervo) how to make the integration tests work 14:13:56 we need(ed) a bind shim in cockpit.js https://github.com/cockpit-project/cockpit/pull/3962/files#diff-34cbdb779d20a4a75591fcba50bd25d4 14:14:10 so phantomjs works with the bind syntax I used 14:14:43 I've opened a pull request with the setroubleshoot project to fix some message capitalization that I talked about with andreasn: https://github.com/fedora-selinux/setroubleshoot/pull/11 14:15:07 and we'll probably get another dbus api update soon 14:15:23 I just subscribed to that pull 14:15:30 so we get alert severity, timestamps and the ability to dismiss alerts properly 14:15:41 we also spoke about some layout fixes on irc on Friday 14:15:58 I'm in dialog with plautrba for a workaround that lets us dismiss alerts on current systems 14:16:08 cool 14:16:39 yes, I've been iterating on the layout and design with andreasn 14:17:06 this will probably have to change in a followup as we play around with it some more 14:17:11 end of topic from my side 14:17:21 nice 14:17:34 oh, plautrba was happy with the current state of how we implemented it 14:17:40 #topic GSoC 14:17:47 nice to hear! 14:17:56 the student registration deadline is fast approaching for GSoC 14:18:17 as expected, activity is picking up and we're seeing more potential applicants in irc 14:18:40 thanks for your interest, students! 14:19:06 the timeline is here https://developers.google.com/open-source/gsoc/timeline 14:19:38 and as a reminder, the Cockpit topics are here: https://fedoraproject.org/wiki/Summer_coding_ideas_for_2016#Idea_list_for_Cockpit 14:19:51 as part of the Fedora org in GSoC 2016 14:20:17 #link https://fedoraproject.org/wiki/Summer_coding_ideas_for_2016#Idea_list_for_Cockpit 14:20:33 petervo, anything to add? 14:20:50 nope 14:20:53 maybe to make it clear: 25 March 19:00 UTC Student application deadline. 14:21:08 after that the internal discussion will begin 14:21:37 end of topic from my side 14:21:56 #topic Debian builds 14:22:13 dperpeet has already given feedback on my shared proposal. petervo, would you like to add anything ? 14:22:41 larsu, anything of note on the debian package builds? 14:22:53 yep, I have the release script generate a binary repository for unstable 14:22:54 abhishekg5, as feedback is proposal specific, any mentor who wants to comment can do so in the document itself 14:23:07 and copy that to fedorapeople.org (which obviously I can't test yet) 14:23:23 putting on the finishing touches right now 14:23:38 cool. by the way it's easy to get a fedora account 14:23:40 larsu, why can't you test copying to fedorapeople? 14:23:48 https://admin.fedoraproject.org/accounts/user/new 14:23:55 dperpeet, okay cool 14:24:01 larsu: do you have a url for that? I have a friend who's a debian guy and he's really interested 14:24:14 larsu: he declined my offer for him to maintain it though :) 14:24:30 dperpeet: need to make an account :) 14:24:34 really interested in trying cockpit that is 14:24:51 dperpeet: also, I'd want it under the cockpit-project user 14:24:51 larsu, let me know if you need help with that after the meeting 14:25:09 andreasn: soon. I'll post to cockpit-devel, but can let you know separately, too 14:25:15 dperpeet: thanks 14:25:16 I've fared well trying new stuff under my own fedora user first :) 14:25:17 larsu: thanks! 14:25:24 that way you can clean up your own home nicely 14:25:46 oh, I do have an account. Does that come with fedorapeople space? 14:25:58 it should 14:26:09 cool :) 14:27:07 I'm looking forward to getting that repo up and running automatically 14:27:24 thanks for wading through those steps! 14:27:46 ya! biggest problem was actually a weird test failure inside the chroot 14:30:03 anything else on Debian? 14:30:21 don't think so 14:30:23 #topic Open Floor 14:31:09 Mostly just an FYI: Cockpit wasn't accessible by default on F24 alpha builds until the other day, but this was my fault not yours. It's fixed. 14:31:43 good to know 14:31:47 is it working well in general? 14:32:05 andreasn: A few hiccups I reported last week 14:32:09 what's the easiest way to get my hands on the install image? 14:32:13 Particularly around some NetworkManager stuff 14:32:30 andreasn: https://kojipkgs.fedoraproject.org/compose/24/Fedora-24-20160316.3/compose/ 14:32:38 thanks! 14:32:39 Specifically Server: https://kojipkgs.fedoraproject.org/compose/24/Fedora-24-20160316.3/compose/Server/x86_64/iso/ 14:32:58 (This one is fixed and launches Cockpit properly) 14:33:14 nice 14:33:37 that's all I guess 14:33:40 wait 14:33:43 I noticed one thing today 14:33:54 I couldn't get fedora-testing images to build 14:34:06 but that might be related to the fact that we're basing them off virt-builder fedora-23 images 14:34:15 I didn't dive deeped, just fyi in case anyone else runs into this 14:34:26 *dive deeper 14:34:56 thanks 14:35:30 thanks for the meeting, everyone! 14:35:33 #endmeeting