18:00:41 #startmeeting 18:00:41 Let the Jenkins meeting commence! 18:00:56 #chairs danielbeck 18:01:00 #chair danielbeck 18:01:00 Current chairs: danielbeck rtyler 18:01:17 #topic Last meeting actions 18:01:21 o/ 18:01:54 I saw that markewaite proposed the docs sig 18:02:05 Yes I did... 18:02:20 did I miss a blog post on GSoD? 18:02:30 we were not accepted 18:02:34 ah 18:02:45 There is a scheduled retrospective meeting for tomorrow 18:03:08 Still have the action item to submit the pull request to create the docs SIG structure. First meeting of Docs SIG is Friday at 13:00 UTC (and retrospective). See Gitter and docs mailing list for details 18:03:17 okie doke 18:03:21 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/c7DaQeZIrQE 18:03:24 I think that covers the last meeting actions 18:03:41 #topic LTS status check 18:05:15 um, I'm not sure there's anything we need to cover here from danielbeck's or ogondza__'s standpoint? 18:06:42 hmm 18:06:58 Today is the next baseline selection 18:07:08 So I assume we have something to cover 18:07:19 yeah, next topic 18:07:31 #topic LTS baseline selection 18:08:05 No thread in the dev list about it 18:08:13 09:33 (@danielbec ) will not be able to make it to today's meeting, but as to baseline choice, recent weeklies look reasonable except for JENKINS-57244 which is only a problem in 2.175. Would go with 2.176 and the usual "we might change our minds until RC" disclaimer 18:08:14 only https://groups.google.com/forum/#!topic/jenkinsci-dev/NKf22rIafiE for backporting 18:08:17 09:33 ( jenkins-a ) JENKINS-57244:java.io.NotSerializableException: The calling thread Thread has no 18:08:45 I agree with 2.176 especially because of JENKINS-57244 18:08:52 It is 2.174 or 2.176 for me 18:09:14 I see no reason to NOT take 2.176 18:09:22 agreed 18:09:33 I'd like to not miss the Debian/Ubuntu launcher in 2.175, thus 2.176 for me 18:09:38 Rick will need to backport one Chinese localization patch tho 18:10:03 I don't understand the backport comment. Isn't that already in 2.176? 18:10:27 hrm, without ogondza around, I'm not sure what we can do other than strongly suggest 2.176 as the next baseline then? 18:10:56 no reported regressions, no negative community ratings 18:11:03 So i am +1 w.r.t 2.176 18:11:23 +1 for me on 2.176 as well, though it is only 3 days old... 18:11:56 Well, we have 2 weeks for testing and backporting issues 18:12:21 * rtyler nods 18:12:26 Jenkins core test coverage got improved since last years, so it should be acceptable 18:12:26 * markewaite nods 18:12:34 * oleg-nenashev nods as well 18:12:48 #info recommend for release officer to take 2.176 as the next baseline 18:12:56 tracymiranda: are you awake too? :) 18:13:53 yep 18:14:01 i think :) 18:14:56 #topic GSoC Update 18:15:01 Okay 18:15:07 #info GSoC projects have been announced. There will be 7 projects in Jenkins this year: https://summerofcode.withgoogle.com/organizations/5489320354381824/ 18:16:10 Artifact Promotion plugin for Jenkins Pipeline 18:16:10 Cloud Features for External Workspace Manager Plugin 18:16:10 Multi-branch Pipeline support for Gitlab 18:16:10 Plugins Installation Manager CLI Tool/Library 18:16:10 Remoting over Apache Kafka with Kubernetes features 18:16:11 Role Strategy Plugin Performance Improvement 18:16:11 Working Hours Plugin - UI Improvements 18:16:30 *dance* 18:16:33 So, we target a number of important changes 18:16:43 who are our mentors this time around? 18:17:09 We have around 18 active mentors in the projects 18:17:21 * tracymiranda claps 18:17:26 dang 18:17:43 We will have a blog post with all links and mentions, it is in progress 18:18:00 Also, there are Jenkins-related projects in other organizations (Eclipse, FOSSi, CivicCRM): https://summerofcode.withgoogle.com/projects/?sp-search=Jenkins#! 18:18:09 So thanks to everybody involved! 18:18:34 Ok... back to the governance side 18:19:21 We will be distributing some swag to mentors. I would proceed according to JEP-8 if this process is still OK after CDF. rtyler tracymiranda WDYT? 18:19:21 neat 18:19:37 I think that should be totally fine 18:19:42 To mentors and students who were not accepted this year 18:20:27 not familiar with JEP-8, so looking up - but if done in the past should be good 18:20:35 We had 32 mentors, and we also have few dozens of students who deserve some recognition after their hard work during GSoC application 18:20:53 Is this highest participation ever? 18:21:04 definitely 18:21:06 Speaking of that... tomorrow I plan to bring up a Community Bridge topic at the Advocacy and Outreach SIG 18:21:45 Even with 7 slots, it is less than we requested. And we may want to run some extra projects if there is an opportunity 18:21:55 Same for GSoD, we have at least one lead there 18:22:19 #info https://communitybridge.org/ 18:22:35 let's add to the agenda for tomorrow https://docs.google.com/document/d/1K5dTSqe56chFhDSGNfg_MCy-LmseUs_S3ys_tg60sTs/edit#heading=h.9jh09t587y90 18:22:48 Yeah, that's my plan 18:23:11 But yeah, this is definitely the biggest GSoC ever, looking forward to see how many projects suceed 18:23:33 does anybody have any questions for oleg-nenashev about GSoC while we're on the topic? 18:24:05 In addition to 7 students, we also bring in 5 new mentors who were not active Jenkins contributors before though they were active users 18:24:26 basically, that's it from me 18:24:41 sounds amazing, no questions from me 18:24:47 Stay tuned for the website updates and for the blogpost 18:25:23 agreed, this is wunderbar 18:25:25 great work oleg-nenashev 18:25:45 yeah, happy to do so 18:25:47 #topic Google Season of Docs Update 18:25:56 markewaite: any items for the record? :) 18:26:42 I think they were already covered in the earlier comments I made. Sorry I stepped out of turn. Meeting Friday, includes retro on our "miss" for GSoD and what we're doing even without GSoD 18:27:06 great, that's good for now I think 18:27:11 Gathering mentors, identifying and encouraging contributors, and trying to learn from mistakes 18:27:13 where/when is the retro 18:27:40 Friday during docs SIG meeting 18:27:42 I also received a belated email letting us know we didn't make it. They said they had almost 200 applications for the 50 organization slots 18:27:53 wow 18:27:56 1pm utc on friday 18:28:21 #action oleg_nenashev to add Docs SIG meeting to the Jenkins calendar 18:28:53 #action markewaite get agreement on a regularly scheduled time for Docs SIG meeting 18:29:19 that's all I have to report on Docs SIG 18:29:33 #topic Outreachy Update 18:30:14 #info we have 2 outreachy interns for this round 18:30:23 https://www.outreachy.org/alums/ 18:30:40 We did not received Outreachy funding for the 2nd 18:30:52 #info Both candidates will be funded by the Jenkins community 18:31:20 Matt Sicker will be lead mentor for both interns 18:31:59 With support from other community members 18:32:12 Has the funding been approved at the Governance meeting? 18:32:17 I mean the second student 18:32:25 yes, at last meeting 18:33:02 thanks! 18:33:17 I am looking forward to finally see a release of this plugin 18:33:33 So all-in-all add to GSoC and we have lots of new energy & activity in the community 18:34:24 any other questions about outreachy? 18:34:35 nope 18:34:51 Maybe an ask to have more content on jenkins.io about it 18:35:46 maybe we can have the interns reshare their outreachy posts on jenkins.io 18:36:40 also, it would be nice to have a page for it, maybe under Advocacy & Outreach 18:38:10 I think this covers it 18:38:13 anything else tracymiranda ? 18:38:38 I can do some CDF updates or take questions on CDF... 18:38:53 or if you meant on outreachy, nothing else 18:38:55 that's the next topic 18:38:56 :) 18:39:01 #topic CDF Update 18:39:37 So some random CDF updates building on email to dev list 18:40:03 #info Jenkins project is still in transition to CDF, still expected to take a few weeks as legal & other issues are worked through 18:40:22 we're basically waiting for their lawyers to talk to our lawyers, yadda yadda yadda :) 18:40:33 yep, lawyers in the loop now 18:41:10 in meantime, lots of ongoing discussions have kicked off, including tomorrow's outreach & advocacy SIG 18:41:22 we will discuss evolving SIGs & JAMs in context of CDF 18:41:35 do we have "our layers"? :D 18:41:44 technically SPI's 18:41:46 * lawyers 18:42:14 #info 2 new Technical Oversight Committee seats have been filled: Kris Nova & Tara Hernandez 18:42:33 It was a well contested election with 12 different candidates put forward by governing board members 18:43:21 Is there any timeline for the Outreach committee? Many of Jenkins activities would benefit if there were established channels for Outreach/Marketing activities in CDF 18:44:01 the outreach committee has had a kickoff meeting 18:44:16 it will start regular monthly meetings from June 18:44:37 the formal committee & mailing list is open to reps from member companies 18:45:07 what I recommend is that we use the Jenkins Advocacy & Outreach SIG to come up with what we would like to do 18:45:08 So, no community mailing list? 18:45:23 then communicate that through Alyssa to outreach committee 18:45:23 Even for readonly? 18:45:26 no 18:45:31 not that i am aware of 18:45:43 we are trying to get key notices posted to toc list 18:46:08 plus through website, social media channels 18:46:41 One thing I can share is that any newsworthy items can be sent to pr@cd.foundation for request to publicize 18:47:03 It requires alyssat_ to be consistently present in the Jenkins community 18:47:23 but generally CDF are monitoring jenkins accounts and blogs to promote them 18:47:42 I mean, Advocacy & Outreach, SIGs and mailing lists, Governance meetings, chats 18:48:25 I will help with that as well, plus Alyssa will attend the US timezone sig meetings 18:48:26 oleg-nenashev: noted. 18:48:46 tracymiranda: I think what might be a good action for you or alyssa might be to document the expected relationship between the CDF outreach committee and existing project-specific efforts 18:48:51 i'll try to be better at this 18:49:02 And TBH it is still not what I have expected from the migration to CDF 18:49:10 I don't have a strong opinion in any direction at the moment, but it would be helpful to know where the seams ight overlap 18:50:04 I think we should say what we need at the SIG meeting then myself & others can figure out how to get what we need from CDF 18:51:21 yup 18:51:26 we can definitely try that 18:52:22 any other updates tracymiranda ? 18:52:29 #info An nomination process and election will shortly be run for a seat on the Governing Board to be filled by a project contributor 18:52:44 I believe KK will soon send out details to mailing list 18:52:54 Did we get a response about the new trademark process in CDF? 18:53:35 yes, CDF is setting up a legal committee and that will approve a new trademark process (plus other licensing stuff) 18:54:01 Are there any pending requests that make this more urgent? 18:54:01 Just to be specific, I would like to make Jenkins RU official to avoid any collision risks 18:54:18 And there was a request from Rick several weeks ago IIRC 18:54:19 Jenkins RU? 18:54:32 do you have link to Rick's request? 18:54:44 Will try to find it 18:55:00 IIRC it was at Advocacy and Oureach SIG meeting 18:55:12 darn, we need a TLA for this SIG name 18:55:38 I saw a request about SIGs in CDF but not for trademark request... but please let me know 18:56:07 my request is not urgent, but I am ready to be a guinea pig for the new process 18:56:20 that's great, thanks! 18:57:05 #action oleg_nenashev to find the trademark question from Rick 18:57:42 #action tracymiranda to follow up on project contributor seat on GB 18:57:55 #action alyssat_ to join https://groups.google.com/forum/#!forum/jenkins-advocacy-and-outreach-sig 18:58:47 the clock says we have one minute 18:58:47 and https://gitter.im/jenkinsci/advocacy-and-outreach-sig , I'd guess 18:58:50 any last words? :D 18:59:15 next meeting as usual? 18:59:22 nothing more from me 18:59:25 done! i've joined https://groups.google.com/forum/#!forum/jenkins-advocacy-and-outreach-sig 18:59:36 hehe 18:59:42 :) 18:59:44 honk 18:59:50 #topic Next meeting 19:00:13 #info our next meeting should be at the same time, same place, on May 22nd 19:00:16 #endmeeting