18:00:14 #startmeeting 18:00:14 Let the Jenkins meeting commence! 18:00:22 #info https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda 18:00:46 danielbeck sent me his regret so I'm running this today. It's been a while! 18:00:54 #topic Recap last meeting actions 18:01:03 #info http://meetings.jenkins-ci.org/jenkins-meeting/2018/jenkins-meeting.2018-11-07-18.00.html 18:01:05 kohsuke: thanks for doing it 18:01:05 Let's see 18:01:31 two actions for Daniel I don't know much about 18:01:42 My part of the action is done and I believe we now have WeChat account!! 18:01:44 3rd one was about the LTS RC 18:02:04 I have a wechat account myself, so I should subscribe to that and see what it's like 18:02:11 Yes, WeChat links were also added to jenkins.io 18:02:13 hats off to Rick for pushing this ball 18:02:26 With that, I think we can move on to the next topic... 18:02:34 #topic LTS status check 18:02:50 right, Daniel saved the day last time 18:03:05 we are ready for 2.15.1 18:03:18 +1 18:03:21 the problematic firefox fix was reverted 18:03:32 I have just mailed the details to the dev list 18:03:34 I tested it a bit... with Java11 . Works well anyway 18:03:43 splendid 18:03:49 Yay! 18:04:00 Wait, 2.150.1 works with Java 11!? 18:04:05 unless there are objections, I will push the RC tomorrow UTC morning 18:04:11 kohsuke: Yes 18:04:22 That is... wow... 18:04:28 I will do a short update later :) 18:04:54 I feel like there should be some celebration of this effort 18:05:03 "this effort" meaning Java 11 support 18:05:04 that is great, does it change anything for the LTS cycle? announcements, etc? 18:05:12 Not yet 18:05:25 I think we won't be announcing it till the next LTS baseline 18:05:26 alright, we can move on in that case 18:05:35 oh, ok 18:05:38 TBD 18:05:43 ogondza: move on to the next topic, you mean? 18:05:49 yep 18:05:55 Alright, let's do it 18:05:59 #topic GSoC update 18:06:06 OK, that's me 18:06:16 #info GSoC 2019 was announced. https://developers.google.com/open-source/gsoc/timeline 18:06:52 #info We want to participate, and we are looking for mentors and project ideas. https://jenkins.io/projects/gsoc/proposing-project-ideas/ 18:07:18 It almost feels like one just finished and the next one starts right off! 18:07:19 All the guidelines are under progress, but we have many things figured out already 18:07:32 GSoC never ends for org admins :) 18:07:49 I see that now 18:08:12 This year we have 4 org admins so far. Shout out to Martin d'Anjou, Jeff Pearce and Lloyd Chang who joined the effort this year 18:08:27 One slot is vacant so far, so let us know if you are interested 18:08:36 And you, oleg-nenashev, for your tireless effort 18:08:37 But, we need project ideas 18:08:42 thanks! 18:09:15 #info Weekly meetings will happen at 2PM UTC on wednesdays. Starting from today, here are meeting notes: https://docs.google.com/document/d/1FARi55vDjsdzi6Nj9ZB9e1wh2dU8nyWK6mq_cge0ceg/edit?usp=sharing 18:09:28 Do you feel like you will get enough project ideas? Or are you looking for more ways to get project ideas? 18:09:57 kohsuke: We will be working a lot with SIGs and subprojects this year to get more project ideas and mentors 18:10:18 OK 18:10:18 Our main takeaway from the previous year is to have more GSoC activities on the SIG level 18:10:37 We already have ~10 project ideas, but I want to double it at least 18:11:02 contributor summits at DW-JW were really helpful 18:11:17 So, any questions so far? 18:11:22 I was just wondering maybe there are ways to solicit "moon shot" projects from users 18:11:41 Yes, we will try to help to polish them 18:11:42 Maybe not exactly "moon shot" because something that's out of the box and developers are blinded to 18:11:53 anyway 18:12:02 Just my 2 cents 18:12:18 s/because/but/ 18:12:19 whatever idea about code, bring it on :) We will help to refactor it to a GSoC project idea 18:12:40 Anything else? 18:12:51 Also, there may be Google Season of Documentation this year. Stay tuned 18:13:01 Yeeeessss. 18:13:02 nothing else from me 18:13:09 GSoC, GSoD, ... 18:13:27 Also GCI and Outreachy 18:13:30 All right, moving on.. 18:13:37 Next year is going to be busy :) 18:13:43 #topic Platform SIG update 18:13:59 OK, that's me again 18:14:19 #info #info https://jenkins.io/sigs/platform/ 18:14:55 #info we have 3 ongoing projects now: Java 11, Windows installers revamp, and Multi-architecture Docker packaging 18:15:12 #info Status updates from Monday: https://docs.google.com/document/d/1FARi55vDjsdzi6Nj9ZB9e1wh2dU8nyWK6mq_cge0ceg/edit?usp=sharing 18:15:43 Windows Installers and Chocolatey distribution got great progress, thanks Slide-O-Mix ! 18:16:28 * kohsuke learns Windows now have a package manager 18:16:42 Same with Docker packaging, a lot of codebase has been integrated. So me may get Arm and s390 official images soon. Thanks to durgadas and jmreicha 18:16:51 kohsuke: several 18:16:59 too many actually 18:17:04 I think I've used one of them back then 18:17:28 #info: https://chocolatey.org/packages/jenkins 18:17:44 We still want to have it a part of the official distribution 18:17:56 And we need help with the Jenkins Infra team. 18:18:31 Actually, all 3 projects in Platform SIG would benefit from some kind of transparancy for what happens on Trusted CI 18:18:36 CC olblak ^ 18:19:26 oleg-nenashev: so the idea is that you want to those builds to be on trusted.ci.jenkins.io? 18:19:49 We have issues with updating the flows now, and it already caused issues. It would be great if we could find a way to somehow get read-only access there OR if we have a way to build a dev environment which would duplicate it 18:19:49 I guess Chocolatey build 18:20:12 trusted build is for ones that involve signing keys 18:20:30 kohsuke: Chocolatey could be outside, but we need to automate/synchonize releases to make it official 18:20:31 Are we trying to get Chocolatey package signed? 18:20:35 nope 18:21:02 ah, you know releases still happen on my computer today, and there's ongoing project to move it 18:21:04 Trusted CI is the only instance which hosts credentials. For Chocolatey we could work it around by webhooks tho 18:21:21 kohsuke: Docker releases happen on trusted.ci 18:21:34 So maybe what you want is to integrate Chocolatey in jenkinsci/packaging? 18:21:35 oh ok 18:21:44 And hence Java 11 and multi-architecture JARs 18:22:02 So, I will probably reach out to olblak and rtyler to discuss options 18:22:08 sounds good 18:22:23 #action oleg_nenashev to explore options to get Platform SIG access to trusted ci 18:22:33 Last but not lease, Java 11... 18:23:14 #info Java 11 status slides from the Platform SIG meeting: https://docs.google.com/presentation/d/1lw4unaFhsQk7a8HzhxhgTK4X2X2ocv_W_VW7aoH2WkM/edit?usp=sharing 18:23:38 writing summary 18:24:16 #info TL;DR: All critical Jenkins core patches were upstreamed, JEP-211 is ready to be accepted. We are waiting for the last feedback: https://github.com/jenkinsci/jep/tree/master/jep/211 18:24:36 And yes, Java 11 works on Jenkins 2.150.x, yey 18:24:51 But we still have some blockers to resolve before announcing 18:25:06 1. Pipeline: Support patches need to be released somehow 18:25:29 2. Test tools and test automation. We have JTH ready, good progress with PCT 18:26:09 ATH is still TODO, but ogondza did some progress on it at the DW-JW Nice hackfest. We will have some follow-ups this week, I hope 18:26:38 So, if everything goes well, we will be able to announce preview availability in December 18:27:06 And then, we have some follow-up things to do (like getting JAXB patches over the fence) 18:27:13 Like I said, I think this one calls for a celebration 18:27:36 If it's coming in Dec, I'm already picturing Santa Jenkins with "11" :-) 18:27:57 Heck, I'd pay for T-shirts and send them to people you think we should thank 18:27:59 Something to consider for sure :) 18:28:28 We are working with alyssat_ and tracymiranda to get the events aligned 18:28:28 Also a good opportunity to highlight participation from Oracle folks 18:28:39 OK, sounds like you are way ahead of the game 18:28:48 w.r.t.12 EA testing, Last time I checked (Java 9) there was an early adopter program to highlight the offort as KK said 18:29:05 we are a part of it 18:29:09 That's great. Let me know if I can help -- I just don't want this to be a dry one line changelog entry 18:29:18 oh, good, good 18:29:20 #info https://wiki.openjdk.java.net/display/quality/Quality+Outreach 18:29:35 It won't be a changelog entry for sure 18:29:52 Maybe we can even run a FOSDEM launch party for LTS, let's see 18:30:08 So far we are trying to get the test automation in place 18:30:18 We know that there are regressions in some places 18:30:29 So there will be maintenance & Co 18:30:39 There always are 18:30:43 yup 18:30:55 Surprise, Maven Integration Plugin works well 18:30:55 by FOSDEM will be time for Java 12 ;) 18:31:08 let's see 18:31:14 Java upgrades _and_ GSOC never end 18:31:20 Quality Outreach pings us for reports periodically 18:31:35 And it's something we need to keep in pmind 18:31:42 Java 11 is a priority tho 18:32:01 #info https://jenkins.io/blog/2018/06/17/running-jenkins-with-java10-11/ if you want to try it out 18:32:10 Needs a new post, I'd guess 18:32:31 So... any questions? :) Or do we just celebrate in advance 18:32:32 Yes :-) 18:32:57 Alright, I guess then moving on ... 18:33:03 #topic Outreachy update 18:33:25 So happy to announce we have 2 Outreachy interns confirmed! 18:33:31 Woot! 18:33:32 Latha Sekar and David Olorundare 18:33:38 congrats! 18:34:02 We had 2 very strong candidates both for audit logging 18:34:21 And had to sign up some co-mentors so outreachy were happy we could bear the load 18:34:46 So many thanks to Matt Sicker, Liam Newman, Mark Waite and Daniel Beck for taking on the mentoring & co mentoring 18:34:51 Looks like this is their info: https://www.outreachy.org/alums/ 18:35:09 Jenkins community is sponsoring one internship, the other is being funded from Outreachy general fund 18:35:33 An invoice will be forthcoming later in December 18:35:59 So far it is all working out beautifully, better than I could have hoped! 18:37:14 Coding begins 4th Dec 18:37:25 Well internship begins then 18:37:34 That's the update 18:37:41 great 18:38:15 thumbs up 18:38:24 I suggest you consider a blog post introducing those two people 18:38:41 good idea! 18:38:46 It looks like we haven't talked about Outreachy on jenkins.io 18:38:59 we did actually 18:39:07 OK, that's great. 18:39:35 there is an open AI on tracymiranda and me to discuss how we arrange all these activities 18:39:36 will be good to do a nice introduction post, esp so folks in the community get to know them 18:39:57 With GSoC and Outreachy we can point out how we are better at working with new people, and if folks are interested in learning/joining, they don't necessarily have to wait for a program 18:40:27 Are they working in the core part? 18:40:39 blog post would be great 18:40:53 Would be nice if we could also map it to a SIG somehow 18:41:08 so that there is a number of involved stakeholders 18:42:22 Maybe just Security SIG? especially if Daniel is open to run public events for security hardening and management topics 18:43:31 * oleg-nenashev apologies for an offtopic 18:43:43 Maybe and Advocacy SIG. 18:43:53 I wonder if GSoC SIG should morph into the onboarding/outreach SIG 18:44:09 we were discussing it in summer 18:44:19 yeah, have it include Outreachy, hacktoberfest, etc 18:44:31 IIUC oleg-nenashev your picture is that these new people need some cocoon and a "place" to be productive 18:44:33 I am +1 for that, but other org admins were against at this point 18:45:08 kohsuke: Not exactly a cocoon. But a place where community bonding happens 18:45:10 I'm +1. 18:45:17 So it's not just them and mentors 18:45:41 Personally I am fine with Outreach SIG 18:46:00 see my "Community Development SIG" proposal somewhere in the mailing lists 18:46:07 Right, I don't mean cocoon as the wall to shut off others, it's the home base for new people 18:46:32 yep, it would be nice if we could start it 18:46:34 Let's pick up the topic again on the ML or gitter. 18:46:37 I'd like to understand objections for org admins 18:46:50 Anyway, sounds like you've already thought and talked about it, so I'm happy to let it sit and cook for a while 18:47:07 +1 to what bitwiseman said 18:47:34 tracymiranda: bandwidth. GSoC requires a lot of time on its own and they cannot participate much in other activities 18:47:45 But we can have an umbrella SIG 18:48:09 E.g. JCasC is formally a part of Cloud Native SIG, but it runs on its own with some overlaps 18:48:16 ok, good to know. 18:48:18 So I do not think it's impossible 18:48:33 Let's take it to the ML again 18:48:59 #action oleg_nenashev to restart the discussion of the Outreach / Community Development SIG 18:49:23 thanks for bringing it up kohsuke and tracymiranda ! 18:49:26 all right, anything else? 18:49:44 #topic next meeting time 18:50:05 #info next meeting is Dec 5th the usual time 18:50:26 great, thanks all! 18:50:31 Thanks everyone, see you then. Have a happy Thanksgiving 18:50:46 Or happy Hacksgiving ;) 18:50:49 Or enjoy your work if you don't observe that! 18:50:56 #endmeeting