14:03:49 #startmeeting Cockpit weekly IRC meeting 2016-01-25 14:03:49 Meeting started Mon Jan 25 14:03:49 2016 UTC. The chair is andreasn. Information about MeetBot at http://wiki.debian.org/MeetBot. 14:03:49 Useful Commands: #action #agreed #halp #info #idea #link #topic. 14:03:49 The meeting name has been set to 'cockpit_weekly_irc_meeting_2016-01-25' 14:03:55 .hello stefw 14:03:55 .hello andreasn 14:03:56 stefw: stefw 'Stef Walter' 14:03:59 andreasn: andreasn 'Andreas Nilsson' 14:04:22 .hello mvo 14:04:23 mvollmer: mvo 'Marius Vollmer' 14:05:33 #topic agenda 14:06:27 * tuned maybe 14:06:39 * image refreshes 14:06:52 Google Summer of Code 14:07:49 ok, lets go 14:07:53 #topic tuned 14:08:01 I saw this just got in 14:08:04 excellent! 14:08:12 i'll be making a video of it 14:08:18 okay! 14:08:24 because i need to for the talks anyway 14:08:57 the tuned people are working on improvements, right? 14:09:12 localized descriptions for the profiles? 14:09:20 better d-bus api? 14:09:28 yeah, apparently it's in fedora-testing https://github.com/cockpit-project/cockpit/pull/3279#issuecomment-169048948 14:09:29 I am not really "in the loop". 14:09:32 or was 20 days ago 14:09:58 one thing that's really missing is the polkit stuff 14:10:06 it should be possible for anyone to query the profile in use, not just root 14:10:09 tuned-2.6.0 was the version 14:10:32 alright 14:11:22 auto activation and properties would be nice 14:11:57 I can write a detailed proposal. 14:11:57 should we open bugs about that to keep track of it? 14:12:02 sure 14:12:14 where should I send that text? 14:12:27 I can figure it out 14:12:32 bugzilla, i think 14:12:55 #action mvollmer to write detailed d-bus enhancement proposal for tuned 14:13:44 sounds good 14:13:50 all, right, next topic? 14:14:27 mvollmer, i think we should differentiate between nice to haves and musthaves 14:14:33 for example non-root access, and activation 14:14:36 vs. properties and API changes 14:15:09 yes 14:15:19 hi, tuned developer here ;) 14:15:24 let's review what I'll write 14:15:31 jskarvad, hi! 14:15:45 I did some API extension to 2.6.0 14:15:51 could extend it more 14:15:54 polkit support by any chance? 14:16:12 initial goal: non-root user should be able to retrieve the current profile 14:16:26 regarding non root acess (polkit) I will address it in 2.6.1, hopefully this week (sorry I was busy with other tasks) 14:16:33 nice, that's great news 14:16:52 i would like us to be able to eventually display the main serverc summary screen without escalating privileges 14:16:59 i think there is another blocker, but i need to do research on that 14:17:13 so having tuned readable without root gets us in that direction 14:17:14 ok, np, feel free to contact me directly 14:17:16 jskarvad: do you need karma for the update in updates-testing in F23? 14:17:31 so it's not stuck in updates-testing or so 14:17:44 andreasn: that would be great 14:17:56 do you have a url handy? 14:17:59 andreasn: I probably missed "updates in testing....." mail 14:18:02 sec 14:18:14 or I can push it to stable 14:18:22 checking 14:18:50 [cockpit] stefwalter closed pull request #3556: test: Clean up test image dependencies (master...avocado_deps) https://git.io/vz6oy 14:18:51 yeh, bodhi fault, it didn't send me the notification mail 14:19:00 sorry about that, I am maintaining too much packages :) 14:19:09 2.6.0 pushed to stable now 14:19:14 stefw, FYI, for the registry interface I have an AD server integrated and cloud storage backend working. 14:19:37 jskarvad: nice! 14:19:38 it appears to "just work" 14:19:49 andreasn, should we move on to the next meeting topic? 14:19:56 yup 14:20:05 #topic image refreshes 14:20:06 okay, so I'll update tuned to use the new API if available 14:20:16 I mean "update cockpit tuned support" 14:20:16 mvollmer: thanks 14:20:45 jskarvad, thanks for implementing this! 14:20:56 mvollmer: no problem 14:21:22 #action mvollmer to update tuned support to use name/description API if available 14:23:14 done with the topic, right? 14:23:27 yeah, now we're on image refreshes 14:23:41 upps, missed that, sorry. 14:23:43 okay 14:23:51 so I have resumed working on that 14:24:04 with a new plan, full of good ideas by stef 14:24:27 the best thing would be to improve the sink as well, and why not 14:24:53 so I am moving code around a bit 14:25:13 instead of getting the feature working with the least amoount of changes 14:25:38 there is a new label, "bot". 14:25:45 you can ignore all issues with that label 14:26:13 github-task will create them when working on new images 14:27:16 how is it deciding when to create new images? 14:27:25 once the image is done, the issue will turn into a pull request 14:27:37 it scans all issues with the "bot" label 14:27:57 and includes a task for a new image when the issues are too old 14:28:39 nothing more fancy than that 14:29:07 it wont retry automatically if a image couldn't be created, or its verification failed. 14:29:24 initially, that is :) 14:29:44 the sink will create the issues, actually, and add a comment to them with a link to the log. 14:30:28 next up? 14:31:00 yep 14:31:12 #topic Google Summer of Code 14:31:50 i was asked whether we're going a summer of code thing this year 14:31:53 by a prospective student 14:32:02 i think we did one in 2015 in the Fedora project 14:32:06 is that something we're interested in doing again? 14:32:19 do we have any requirements on the tasks or applicants? 14:33:26 the task should be solvable without fixing up 3-4 different subsystems 14:33:32 ideally 14:33:35 i think we should participate, esp if someone is already interested 14:34:03 so maybe an interface to something that has dbus support already 14:34:10 true, or maybe docker work 14:34:20 rolekit could be one obviously 14:35:10 firewall? 14:35:28 maybe the student has an idea/interest? 14:36:42 is there a potential student already? or am I mixing it up with something else in my head? 14:36:51 I recall seeing something 14:36:52 we have a potential student 14:37:04 i suggested to him that he start to contribute small patches to cockpit 14:37:11 yeah, that's good 14:37:14 maybe 5 to 10 before we sign up for a GSoC 14:38:13 right 14:38:35 does anyone have any thoughts on how we can do better than last year? 14:38:42 it seemed that the students both failed, right? 14:39:03 yep 14:39:34 making sure the student is active and motivated is a good start 14:40:02 why did they fail? did they just disappear? 14:40:17 failed on delivery in time I think 14:40:20 making sure the expectations are clear up front so they don't try to do too much at once 14:41:05 failed to show up as well 14:41:22 so breaking it up in clear subtasks and have clear time estimates for all those subtasks? 14:41:35 "by week 3 this part needs to be done" 14:41:43 well 14:41:52 is that how we work? :-) 14:42:36 it's more sprinty, not sure if it would produce a better result or not 14:43:17 right, if it's a sprint plan, like "next goal is to do ..." 14:43:28 not a deadline, "meet this or else" 14:43:51 I'd say let's just try again 14:43:56 the main thing is the see regular progress from them 14:44:09 right 14:44:22 to* 14:44:39 i would say communication trumps genius 14:44:41 i was a mentor once, many years ago, and my conclusion was "not again". :-/ 14:44:58 have to search my memories to remember why 14:45:55 or I can just be one again. :) 14:46:31 in any case it's cool that it's still happening. i think it was 2005 for me 14:47:11 it can be challenging with some students, but also really good when it just works 14:47:38 I'm helping mentoring some gnome interns right now, and both of them are really good 14:49:02 so I'm up for helping with a gsoc project I think 14:49:06 it wasn't about the student for me, that was great, just the process around it. it felt weird. 14:50:02 Sorry, I meant to chime in here and my system crashed 14:50:19 So, Fedora has tightened its GSoC policy this year, because we had so many bad apples last year. 14:50:31 anyway, don't listen to me here, of course 14:50:40 (People who tried to basically collect the cash without delivering work) 14:50:42 I am happy to mentor. 14:51:02 Release complete: 0.93 - http://fedorapeople.org/groups/cockpit/logs/release-0.93/ 14:51:05 So this year, we will only accept students who have a strong pre-existing relationship with the project they are applying for. 14:51:25 It's up to the project to decide what that means, but a good rule of thumb is that they have to have contributed something non-trivial before 14:51:26 i don't feel like administering google's money 14:51:32 sgallagh, ++ 14:51:32 i guess that's the part. 14:52:06 sgallagh: so more than just a spelling fix, but more like something where they had to put a bit more effort into it? 14:52:34 andreasn: Yeah, something on the order of a new feature or significant bugfix. 14:52:54 I see 14:53:38 andreasn: Unfortunately, GSoC has grown a culture of people who sign up, do a half-assed job for the first half, collect half of the 14:53:44 money and then disappear completely. 14:54:20 So to prevent that, we want to make sure that anyone who gets accepted already has a proven history of doing actual work 14:54:38 Otherwise we're wasting Google's money and the mentor's time 14:54:41 yeah 14:56:06 EOF 14:56:48 anything else on that subject? 14:57:05 i just wanted to get the discussion started, i don't think we have to take any action yet 14:57:18 I guess we can gather up some project ideas on an etherpad or in the wiki 14:57:20 stefw: Well, probably a good idea to reply to that student. 14:57:23 except for highly recommend that would be students become contributors 14:57:29 sgallagh, i already did, and CC'd you 14:57:32 See if they're willing to pick up a Trello ticket and run through it 14:58:37 OK, I think I remember seeing that. 14:58:41 /me drowns in email 15:00:15 ok, open floor next, since we're up at the hour 15:00:19 #topic open floor 15:01:21 we only have 9 pull requests open 15:01:22 yay :) 15:01:45 nice! 15:02:22 do we need to announce the hackfest at devconf, or our other talks? 15:02:30 i think we did a bit, but may be worth doing more? 15:03:00 I posted about your fosdem talk last week (I think it was last week) 15:03:24 i tweeted 15:03:41 but i think we should probably all do a bit of promotion for the hackfest s ince it's so early 15:03:47 the devconf guys gave us a 9:00 AM slot after a party 15:04:08 i can close two more PRs... 15:04:36 [cockpit] mvollmer closed pull request #3470: test: Support for image creation tasks (master...test-image-refresh) https://git.io/vzim1 15:04:40 what do we do with this one? https://github.com/cockpit-project/cockpit/pull/2062 15:04:49 1 tests failed - http://fedorapeople.org/groups/cockpit/logs/master-ac7869c2-verify-debian-unstable/log.html 15:05:01 [cockpit] mvollmer closed pull request #3474: test: Support for creating image refreshment pull requests (master...test-github-image-refresh) https://git.io/vzimS 15:05:19 I'll post on twitter and G+ about the hackfest at devconf 15:07:33 1 tests failed - http://fedorapeople.org/groups/cockpit/logs/master-ac7869c2-verify-fedora-atomic/log.html 15:10:47 ok, I guess that's it 15:10:49 #endmeeting