18:00:04 #startmeeting 18:00:04 Let the Jenkins meeting commence! 18:00:07 hi everyone! 18:00:30 \o/ 18:00:30 #info https://wiki.jenkins.io/display/JENKINS/Governance+Meeting+Agenda#GovernanceMeetingAgenda-Jun6thmeeting 18:00:39 #topic Recap last meeting's actions 18:00:44 #chairs rtyler kohsuke 18:00:45 ops 18:00:49 #chair 18:00:53 #chair rtyler kohsuke 18:00:53 Current chairs: danielbeck kohsuke rtyler 18:00:58 that command has a response at least :) 18:00:59 tracymiranda: o/ 18:01:04 #info http://meetings.jenkins-ci.org/jenkins-meeting/2018/jenkins-meeting.2018-05-23-18.02.html 18:01:19 so, not much from last meeting 18:01:26 #topic LTS status check 18:01:28 heh 18:01:31 ogondza around? 18:01:37 it was a quick one 18:02:21 It's LTS o'clock already 18:02:34 right, I was late publishing the RC bits 18:02:35 heh 18:02:56 ogondza are we still on for today, or should we postpone? 18:03:07 though no problems ware reported 18:03:23 I do not see that to be a reason to postpone the release 18:03:43 is the LTS empty? or is https://issues.jenkins-ci.org/issues/?jql=labels%20%3D%202.121.1-fixed wrong? 18:04:10 it is wrong 18:04:12 We still need upgrade guidelines 18:04:24 oleg-nenashev yep, I'm late :-/ 18:04:26 fixed packaging and performance improvement on /pluginmanager/installed 18:04:33 #action danielbeck to write upgrade guide and changelog 18:04:46 At least: exception serialization in Remoting - JENKINS-50237, permission changes - JENKINS-14713 18:04:48 #action ogondza to fix up Jira labels for 2.121.1 related issues 18:05:06 ogondza so we're ready to release? 18:05:20 yep, fixing the labels right away 18:06:00 FYI I have resolved tickets for all Weekly releases since 2.121 and added lts-candidate labels 18:06:11 There is quite a number of them 18:06:59 hope to see as many of them tomorrow as I can manage... 18:07:27 ogondza so we're good to release based on testing? 18:07:38 danielbeck, yes we are 18:07:43 #action kohsuke to release 2.121.1 18:07:50 this is the first release with the packaging ref, right? 18:07:58 yes 18:08:06 wooo 18:08:20 anything else about 2.121.1 or can we move on? 18:08:28 discussed it with KK last time, it should be fine 18:08:45 lets move on, then 18:08:56 is that my cue? 18:08:58 #topic Trademark sublicensing request "CloudBees Jenkins Support" 18:09:01 tracymiranda it is! 18:09:07 #info https://groups.google.com/forum/#!msg/jenkinsci-dev/d1rrCcY-VyM/Pu4RdH2LBwAJ 18:09:28 yes as per that thread I would like to seek approval on behalf of CloudBees 18:09:51 discussion or straight to vote? 18:09:52 wait, wrong link 18:10:01 what did I link!? 18:10:12 #info https://groups.google.com/d/msgid/jenkinsci-dev/bbed285d-2bc6-46c9-9334-484cbc014cf9%40googlegroups.com 18:10:29 THis is the correct link, there's two in the agenda: https://groups.google.com/d/msg/jenkinsci-dev/dvnua3N32C0/D-FBELTECwAJ 18:10:42 sorry about that 18:11:04 our trademark guidelines can be found: https://jenkins.io/project/governance/#trademark 18:11:04 danielbeck: you scared me for a minute there :) 18:11:09 probably my copy & pasting 18:11:42 alyssat_ just making sure you're awake :) 18:11:58 so any questions, objections, etc? 18:12:19 I abstain 18:12:44 the mark being "CloudBees Jenkins Support" I don't see any problem with 18:13:02 yes PM withdrew other request 18:15:01 +1 18:15:59 * danielbeck wonders whether ogondza orrc or schristou have an opinion 18:16:18 also orrc ^ 18:16:25 oh 18:16:29 +1 18:17:50 heh 18:17:56 well, an enthusiastic response this is not, but tracymiranda gave plenty of notice and nobody rejected it, so this looks to be passing? 18:18:08 last chance to speak up :) 18:18:48 seems reasonable to me 18:19:26 this is a pretty perfunctory process 18:19:48 #agreed The trademark sublicensing request for "CloudBees Jenkins Support" is approved 18:19:58 #action danielbeck to edit the wiki to record this decision 18:20:27 #topic Jenkins Ambassador program update 18:20:48 complete with a dead link to bitwiseman's GitHub repo :P 18:20:54 hahaha 18:20:57 bitwiseman alyssat_ could you provide the reference for this? :) 18:20:59 w00ps 18:21:03 #info https://github.com/jenkinsci/jep/edit/master/jep/5/README.adoc 18:21:05 sorry my fault 18:21:11 bitwiseman thanks 18:21:24 #info https://github.com/jenkinsci/jep/blob/master/jep/5/README.adoc really 18:21:41 heh, links are awesome all around today. 18:21:55 I'm so glad I'm in good company! 18:22:08 * oleg-nenashev checks his links 18:22:12 alyssat_ bitwiseman you have the floor 18:22:25 The Jenkins Ambassador program is kicking off. 18:22:39 hm 18:22:58 I'm currently making edits with the latest updates and decisions and will submit a PR today. 18:23:30 (the name is definitely Jenkins Ambassador, for example) 18:23:41 bitwiseman ok. what's your agenda for today? raise awareness of the program? get some sort of approval? 18:23:46 the process looks good 18:23:59 the name I had one last thought about... 18:24:25 At a recent community team meeting in SJC we came up with some ideas for nominees. 18:24:36 Some of my comments have not been addressed yet, but I am looking forward to see bitwiseman's pull request 18:24:57 oleg-nenashev: you can expect the edits to match what you got in email. 18:25:03 yey 18:25:14 was that on the ML? 18:25:15 since that meeting was wondering if name should just be 'Jenkins Champion' as that will be familiar to e.g. Java community 18:25:33 I'd say our goal for today is to raise awareness about the program and that we'd like to begin implementing and getting some Ambassadors awarded sometime soon 18:25:46 tracymiranda: there are lots of advocates out there (like me originally) who had no real relationship to the Java ecosystem 18:25:49 * rtyler shrugs 18:25:59 (I still don't) 18:26:02 and that final approval of new ambassadors will be done in this meeting. 18:26:09 future meetings. 18:26:10 I would prefer Champion to Ambassador, but some differenciation would be useful 18:26:41 We already have JEP which overlap with Java 18:27:12 aren't our JEPs based more on PEPs? 18:27:13 #info Discussion thread: https://groups.google.com/d/topic/jenkinsci-dev/12D2tWxO6mM/discussion 18:27:20 danielbeck: they are 18:27:33 for sure 18:27:36 "based" is really more copied 100% :P 18:27:59 we changed a lot in JEP-1, so not 100% for sure :) 18:28:06 But the acronym is same 18:28:17 danielbeck: the acronym collides with Java Enhancement Proposal. 18:28:26 (FTR Java's JEP-200 also a train wreck :P) 18:28:46 JEP-261 is a train wreck 18:28:47 Returning to the topic at hand. 18:28:48 what the heck does the JEP acronym have to do with our current topic? 18:28:52 JEP-200 is fine actually 18:29:12 Yeah, sorry 18:29:15 bitwiseman so it looks like we can expect some updates soon? 18:29:28 danielbeck: Ye. 18:30:00 danielbeck: key among them is that this group will be making the final approvals of new Ambassadors. 18:31:11 bitwiseman will the format be similar to our usual approach of proposing on the dev list, then hopefully having a clear consensus here? 18:31:36 danielbeck: exactly. 18:33:13 bitwiseman is that part of your upcoming updates? 18:33:39 seems to me there's still quite a few moving parts in that proposal 18:33:49 danielbeck: yes, it is also, in alyssa's last reply on the thread linked. 18:34:28 ok 18:34:42 I assume we'll get an update on the dev list once the next version is out? 18:34:58 yes. 18:35:34 bitwiseman alyssat_ anything else we should look out for in that proposal? Otherwise we still have a bit of agenda to get through today, so I propose we move on 18:35:45 Also, start thinking of nomminees. 18:35:58 good point 18:36:06 I don't have anything 18:36:13 And that is it for me. 18:36:23 thanks! 18:36:27 #topic GSoC status check 18:36:30 oleg-nenashev this is yours 18:36:36 o/ 18:36:50 #info: GSoC: https://jenkins.io/projects/gsoc/ 18:37:43 So now we have 3 active projects. So good so far. All projects got progress and some community traction, I hope we will have alpha releases in Mid June 18:37:51 \o/ 18:37:54 \o/ 18:38:17 #info June 15 is a evaluation deadline 18:38:34 #action oleg_nenashev to set up public meeting with project demos 18:38:51 #actions students to create blog posts, etc. 18:38:53 is there a demo day sometime? 18:39:02 Yes 18:39:04 TBA 18:39:09 great 18:39:12 Likely end of the next week 18:39:19 Of course, we will do HoA 18:39:29 But probably it's too early for JOM 18:39:42 * tracymiranda is struggling with the TLAs 18:39:51 Jenkins Online Meetup 18:39:55 Hangout on Air 18:39:58 :) 18:39:59 thx 18:40:02 yw 18:40:15 Any questions? 18:40:39 looking forward to the demos :) 18:40:51 yes, same! 18:40:56 Yeah, we have much more collaboration this year 18:40:58 so other than "are we there yet?", no questions 18:41:39 E.g. in Simple PR Job Plugin we apparently use Configuration As Code plugin for some integrations 18:42:07 "are we there yet?" ? 18:42:15 joke :) 18:42:19 will that tie student success to casc releases? 18:42:28 nope 18:42:35 ok, then that should be fine 18:42:36 Risk Management 101 18:42:49 is there a plugin for that? 18:42:56 ;) 18:43:07 * rtyler booes 18:43:10 it's a thing, so there's a plugin for it 18:43:11 * rtyler throws tomatoes at tracymiranda 18:43:13 moving on… 18:43:18 #topic Update: Jenkins & Java 10 Online Hackathon 18:43:21 There are many plugins for risk mismanagement around :) 18:43:23 another one from oleg-nenashev 18:43:53 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/FdCvQlscl_I 18:44:08 Wow, I didn't mess up the link 18:44:21 boo 18:44:25 hehe 18:44:29 I'm already signed up! 18:44:41 heh 18:44:53 So yeah, in 2 weeks we are going to have an online hackathon to get some progress on Java 10 stories 18:45:04 oleg-nenashev: just out of my own curiosity, do you think there are going to be tons of core PRs that weeks? 18:45:27 As a guy who routes Jenkins JIRA issues , I am personally invested to get some progress there :) 18:45:50 rtyler: TBD, but we will likely have some PRs 18:46:00 depends what swag we offer :) 18:46:09 rtyler any particular reason you're asking? 18:46:25 I am the core maintainer, so I will do the core reviews & help ready PRs to get landed 18:46:27 For example a need to get some organized code review going? 18:46:29 Same for Rmoting 18:46:58 For Pipeline we are also going to find some review capacity 18:47:06 danielbeck: capcaity planning on ci.jenkins.io 18:47:09 rtyler ah 18:47:12 core PRs are pretty heavy 18:47:14 I anticipate Pipeline to be the most hot area 18:47:17 rtyler perhaps also a java 10 option to build core? :) 18:47:22 just want to make sure we can support the hackers as much as possible 18:48:08 rtyler: I will make sure to land https://github.com/jenkinsci/jenkins/pull/3438 so that we do not run ATH each time 18:48:17 Should help a bit, right? 18:48:31 oleg-nenashev do we already have responses? or still too early? 18:48:39 danielbeck: 4 responses 18:48:50 cool, just one hour in! 18:48:55 #info We already have 4 responders to the hackathon invite 18:48:59 nice 18:49:11 #action oleg_nenashev to blogpost the announcement 18:49:23 i will also promote next week at eclipsecon, see if I can arm twist some folks there to join 18:49:43 #action oleg_nenashev to work with Infra team to ensure that our INFRA is ready 18:49:49 INFRA! 18:49:58 thanks tracymiranda! 18:50:35 oleg-nenashev: should a create a blog post based on your email? 18:50:41 shall I? 18:50:47 Will create INFRA ticket and appropriate Sprints & Co 18:51:19 bitwiseman: If you have some capacity, go for it? I am working on some artwork & Co to prettify the announcement 18:51:31 no "?" 18:52:01 a nice image with dates would be good for sharing on social media 18:52:36 tracymiranda: +1 18:52:48 #action all interested contributors to RSVP here: https://docs.google.com/forms/d/1ReYyuyCGC0PIz2quh6XehnjpH2K52inx-veHLPlNreE/ 18:53:03 \o/ 18:53:12 oleg-nenashev I think that's it? Or anything else we need to know about this? 18:53:14 oleg-nenashev: not that link 18:53:23 I am thinking about reworked https://jenkins.io/images/logos/formal/formal.png with a Java cup 18:53:25 That is the edit link. :( 18:53:29 Suggestions welcome 18:54:06 bitwiseman post the correct link please 18:54:17 bitwiseman: Open in the incognito mode. I just granted you permissions :P 18:54:18 #action all interested RSVP here: https://goo.gl/forms/ybEfKw6TB6WZaszM2 18:54:39 bitwiseman thanks 18:54:43 good idea for logo 18:55:01 the links point to the same place tho 18:55:07 whatever 18:55:23 So, any other questions? 18:55:48 doesn't look like it 18:56:00 thanks everyone for your participation today! 18:56:05 #topic next meeting 18:56:15 that would be June 20, same time 18:56:25 \o/ 18:56:38 thanks all 18:56:42 #endmeeting