18:00:21 #startmeeting 18:00:21 Let the Jenkins meeting commence! 18:00:24 hi everyone! 18:00:32 hello 18:00:36 #char rtyler kohsuke 18:00:39 #chair rtyler kohsuke 18:00:39 Current chairs: danielbeck kohsuke rtyler 18:00:54 agenda: https://wiki.jenkins-ci.org/display/JENKINS/Governance+Meeting+Agenda 18:00:59 #action Recap last meeting's actions 18:01:04 wait 18:01:06 #topic Recap last meeting's actions 18:01:13 It's been a long day :) 18:01:35 slide had an action to send email on bug triage team to the dev list 18:01:48 yes not around yet 18:01:52 so let's move on 18:02:00 # LTS Status check 18:02:03 #topic LTS Status check 18:02:19 I have done the testing all looks good. no complains for people 18:02:29 we are good to go as long as I am concerned 18:02:34 yup, it's already out 18:02:40 with blog post and everything 18:02:55 KK is travelling so we had to start early 18:03:19 should be on all mirrors by now 18:03:24 ok, cool 18:03:37 and we've started publishing warnings for it as well, as 2.43 and earlier already have support for that 18:04:09 #topic GSoC update 18:04:19 oleg-nenashev is this yours? 18:05:23 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/cPN7IZHGDWE 18:05:48 #info https://docs.google.com/document/d/13mkt5DBjVAnr7dSiJ0oO4R5-nn80kGQ5OFhBoUzInIU/edit#heading=h.w10hxu7oxi77 18:05:48 oleg-nenashev says in that mail that he can't attend today 18:05:53 oh, okay 18:06:01 oh well, here's the #info then :-) 18:06:11 looks like those two documents are his status update. call for mentors to come tomorrow. sounds good 18:06:20 mentors and project ideas, that is 18:06:30 apparently rtyler is supposed to discuss this? 18:06:39 he's appears away too 18:07:17 let's move on 18:07:24 to… 18:07:27 #topic Infrastructure update 18:07:38 that's going to be quick too, as rtyler isn't around apparently 18:07:53 let's just skip his topics 18:08:07 if he shows up before we're done we can always go back 18:08:41 #topic Request for 50 private repos in the jenkinsci-cert GitHub org (1200 USD/year, up from 20 repos for 600 USD/year) 18:08:45 This is mine 18:09:01 Right now, we have 20 private repos in the jenkinsci–cert organization on GitHub 18:09:30 This has already required us to "archive' (screenshot PRs and backup clones) of some repos, but it's still not enough 18:09:54 There's a number of repos we need to have persistent, as they're needed in most updates 18:10:19 The security team also offers plugin devs private repos to allow collaboration in private to fix vulnerabilities 18:10:34 and then of course there's one-off repos we need to jsut prepare fixes 18:10:54 And we're learning that 20 is just too restrictive 18:11:19 so I wanted to get approval to upgrade the plan to 50 repos, which is the next greater size, for 1200 USD per year, a 600 USD increase 18:12:44 sounds good to me in general, but I thought GitHub changed their pricing last year to be per-user, rather than per-repo? 18:12:53 That's opt in for existing orgs 18:13:12 as long as I don't click the "I'm an idiot" button we still have the old plans available 18:13:36 And the new plan would be a _lot_ more expensive, given the number of external contributors we invite to individual private repos 18:13:54 yeah, I see now that with 11+ contributors, the new plan is more expensive 18:14:23 in any case, AFAIK, the money is there, and the usage makes sense; +1 18:15:21 any other opinions on this? 18:16:29 Doesn't look like it. You're a difficult crowd today ;-) 18:16:50 I think I'll just table this until two weeks from now, and email the dev list separately 18:17:00 sounds good 18:17:05 #topic next meeting 18:17:25 Feb 15, same time, same channel 18:17:35 #endmeeting