18:00:22 #startmeeting 18:00:22 Let the Jenkins meeting commence! 18:00:34 #chair danielbeck rtyler 18:00:34 Current chairs: danielbeck kohsuke rtyler 18:00:48 #info https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda 18:01:07 Lots to go through today, huh 18:01:16 #topic Recap last meeting actions 18:02:08 #info http://meetings.jenkins-ci.org/jenkins-meeting/2019/jenkins-meeting.2019-01-02-18.06.html 18:02:14 I guess not much of an action 18:02:39 #topic LTS status check 18:02:56 who's here? 18:03:21 ogondza is not here 18:03:23 o/ 18:03:35 I have no idea what is going in LTS tho 18:04:11 all right 18:04:16 I guess we need to skip this 18:04:27 #topic Platform SIG status report - Java 11 and more 18:04:34 markewaite? 18:04:36 The platform SIG will meet Thursday to review the current state of Java 11, Windows installers, and multi-platform Docker images. Java 11 support and development is continuing. There are still some blockers open which prevent general availability of Jenkins weekly with JDK 11. 18:05:00 Good progress has been made. @batmat and I are leading the platform SIG and progressing 18:05:22 oh that's cool 18:05:28 Congrats 18:05:40 I'm a little nervous that we don't have enough test time yet, but there is good progress on many fronts. 18:05:48 end of status report... 18:06:07 Moving on... 18:06:13 #topic GSoC status report 18:06:25 Hi all 18:06:30 o/ 18:06:46 So... We will be applying to GSoC this year 18:07:08 #info Jenkins Project will apply to GSoC 2019. https://groups.google.com/forum/#!topic/jenkinsci-dev/dS_NluO4RW0 18:07:31 Cool stats. We already have 20 project ideas and 23 mentors. More than in 2016 and 2018 all together 18:07:39 And it's counting 18:07:41 :clap: 18:07:59 All documentation is updated 18:08:22 #info Application draft: https://jenkins.io/projects/gsoc/2019/application/ 18:08:48 I see that the pool of mentors are expanding and they are bringing the project idea. Nice 18:08:48 As discussed at the today's meeting, the application draft will be slightly reworked to reflect all sub-projects 18:08:56 Yeah 18:09:04 There's something to be said about repeating and sticking... 18:09:29 And we cooperate a lot with SIGs and sub-projects to get project ideas and stakeholders for projects 18:09:38 In some cases it works really well 18:09:47 "repeating until sticking" is what I meant 18:09:54 exactly 18:10:09 I hope we will hit the 30 projects target this year 18:10:28 And we want to make projects more diverse in terms of the technologies 18:10:42 #info Project ideas: https://jenkins.io/projects/gsoc/2019/project-ideas/ 18:11:24 We are looking for few particular project ideas, especially around Jenkins X and Python 18:11:51 Both of them get interest from students, but we have not been able to secure project ideas so far 18:12:16 Does anyone have any project ideas or any questions? :) 18:12:50 We are also interested in Jenkins INFRA projects 18:12:58 ^ olblak rtyler 18:13:12 I suspect Jenkins X folks aren't watching here nor the dev list. Maybe you can reach out to James Rowlings about where to "advertise" GSoC+Jenkins X to reach their audience 18:13:26 kohsuke: Be sure we used all known channels 18:13:39 OK, well then. I think you already have a big list 18:13:54 Shall we move on? 18:14:01 We ping them almost every week at Slack and meetings, so I keep hope 18:14:10 Nothing else from me 18:14:23 #topic Status report: Advocacy and Outreach SIG 18:14:37 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/84vjWz_Ho1k 18:14:51 bitwiseman: would you like to drive it? 18:15:06 sure. 18:15:39 one sec. 18:16:27 had to find the agenda tab again . 18:17:16 Okay, the advocacy and outreach sig has been created. 18:18:00 The thread you pointed to covers discussion so far and there is a PR up add a sig page. 18:19:07 #info https://github.com/jenkins-infra/jenkins.io/pull/2034 18:19:26 Yes, I believe we will officially publish the SIG this week 18:19:46 sorry for the delay o/ 18:20:13 We'll discuss on gitter when to hold the first meeting. 18:20:57 Marky has volunteered to co-lead. Yay! 18:20:58 And it should become a central place for Advocacy/Evangelism and community outreach topics. We already have few discussions and related patches on jenkins.io (like getting communication channels explicit everywhere we can) 18:21:39 Full scope is TBD. But, if you are interested in propmoting and expanding the Jenkins community, you may want to join this SIG 18:22:55 I got distracted a little, anything more about this? 18:24:05 having a clearer gitter channel name is already paying off in lower static. 18:24:18 :) 18:24:20 That's it's from me. 18:24:23 for sure 18:24:47 I had a question to alyssat_ , but I am not sure she is around 18:25:30 is this a swag question :-) 18:25:36 nope 18:25:46 Jenkins Ambassadors one. I will follow-up in email 18:25:49 In the mean time we shall move on then 18:25:51 hello. i'm here 18:25:56 ... or not 18:26:31 alyssat_: So... It would be great Jenkins Ambassadors to be an active part of the Advocacy/Outreach SIG 18:26:46 Unfortunately, I do not have contacts of all ambassadors 18:27:03 It would be great to reach out to them and invite them to join 18:27:03 I can help provide that info to you 18:27:17 Would be great, I will follow-up in email 18:27:30 sounds good 18:27:33 thanks! 18:27:52 nothing else from me 18:28:01 #topic Update: Hardware&EDA and Embedded SIGs 18:28:07 Okay 18:28:12 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/a69DXm6qQms 18:28:26 So, this is actually an Advocacy&Outreach topic again 18:28:48 I would like to experiment with creating **user-focused** special interest groups 18:29:22 And, since we had a lot of discussions about Embedded and HW&EDA topics, I decided to go forward and to get them created 18:29:37 This update is a heads-up that it is happening 18:29:50 If anybody is interested to join, please let me know 18:30:18 Also, I am interested in creating C/C++ SIG which would be also a user-focusing SIG 18:30:44 I think this is all great, I just want to remind you that your one day is still 24hrs like the rest of us... 18:30:47 As many Jenkins contributors know, my Java still looks like C sometimes :P 18:31:34 kohsuke: I am not doing it alone, and currently I reconsider what would be my priorities in the Jenkins community. https://groups.google.com/forum/#!topic/jenkinsci-dev/uc6NsMoCFQI 18:32:26 I cannot really do maintenance of components nowadays, but facilitating SIGs does not require long timeslots. So I decided to try it 18:32:41 OK 18:33:20 So, be sure it is not a commitment on the top of other commitments. Interested to do more community work 18:33:52 so yeah, that's it from me 18:34:20 All right, then 18:34:29 #topic Request for Rick to be listed as Jenkins press contact for China 18:35:18 There is no Jenkins Dev ML thread for that 18:35:51 I think that's a reasonable idea 18:35:54 Just to provide some context, Rick has reached out to me today, and then tracymiranda and bitwiseman joined the discussion (Advocacy and Outreach SIG) 18:36:09 I totally support the idea as well 18:36:15 I think it makes sense that we have reps in that region who understands the language 18:36:27 Yes 18:36:44 What that tells me is that we need to build more bridge with him -- I don't know him anywhere near the same level I know others listed in press contacts 18:36:49 my only request would be for Rick to send updates to the dev list or something like that 18:37:00 to raise the awareness of press stuff in China for Jenkins 18:37:01 We already have few Jenkins Ambassadors, but AFAIK they are not active much in the community channels now 18:37:26 How well is Rick connected to those folks? 18:37:31 Rick is already a leder of the Chinese Localization SIG BYW 18:37:35 *BTW 18:37:46 Rick definitely has contacts of them 18:38:04 But I am not sure how they coordinate the efforts nowadays 18:38:30 Right, OK 18:38:39 Rick is active in the community every day, so I am +1 for the request 18:39:05 +1 18:39:08 If Jenkins Ambassadors want to be press contacts, we can have multiple ones in the region. So it's a bit orthogonal 18:40:02 +1 18:40:17 should we ask Rick to mail dev-lists still? 18:40:46 Yeah, I'll write to him 18:40:53 ok thanks 18:40:59 I asked him to mail the SIG ML on the morning. But dev list works as well 18:41:38 So that he understands where that request is coming. It's not so much where the email goes matter IMO. I think the root of rtyler's request and mine are the same 18:42:17 yeah, public trace. Which is totally reasonable 18:42:37 Oh, and I missed to ask the obvious -- he's willing to be listed as press contact, right? 18:43:01 yup 18:43:16 #agreed rick to be listed as a Chinese press contact in https://jenkins.io/press/ 18:43:21 #info https://jenkins.io/press/#press-contacts 18:43:38 yey 18:44:03 #action kohsuke to write to rick asking that we work toward better visibility and more bridges 18:44:18 It's great to see those new leaders grow 18:44:29 yup 18:44:36 Lots going on in China in particular for the past few years 18:44:53 Anything else on this? 18:44:54 Rick also coordinates some technical projects (e.g. Gitlab Multi-Branch project idea in GSoC) 18:45:05 Or anything else for that matter? 18:45:18 #topic next meeting 18:45:41 Jan 30th same time 18:45:47 ... which is almost FOSDEM 18:45:58 dun dun dunnnn 18:46:02 thanks for running the meeting today kohsuke 18:46:41 #info If you haven't checked out, look at alyssat_ 's FOSDEM email for events around FOSDEM that are getting organized 18:46:53 I think that's the end of this 18:46:55 Bye all 18:47:00 bye 18:47:07 #endmeeting