18:01:23 #startmeeting 18:01:24 Let the Jenkins meeting commence! 18:01:47 #info Agenda: #startmeeting 18:01:56 #info Agenda: https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit#heading=h.vylsknw2s91m 18:02:10 #topic Recap of previous action items 18:02:28 do we have ones? 18:02:49 #info Previous meeting: http://meetings.jenkins-ci.org/jenkins-meeting/2019/jenkins-meeting.2019-12-18-18.02.html 18:02:56 no action items 18:03:20 #topic New meeting time 18:03:37 #info: Discussion: https://groups.google.com/forum/#!topic/jenkinsci-dev/RuWQ124gUsw 18:03:48 IIUC we still need to send out Doodle 18:04:03 Nope, it was sent 18:04:13 #info Doodle for the new meeting slot: https://doodle.com/poll/pq2g45anu92yz2b8 18:04:28 So far 2 votes 18:04:33 * oleg-nenashev did not vote 18:04:59 I thought your initial times setup is your vote? 18:05:28 Not exactly 18:05:54 I just took common slots with good EMEA/APAC and Americas/EMEA overlap 18:06:05 But I will make any slot work if needed 18:06:42 It looks like the current time is the best :-) 18:06:49 Basically the current options are 5PM UTC or 6PM UTC on Monday to Thursday 18:07:03 Unless somebody else votes, +1 for keeping the time 18:07:27 Should we postpone it till the next meeting (and keep the slot as is for now)? 18:07:42 I think that's a good idea 18:08:10 that means today is an excception? 18:08:23 Today is a regular slot drulli 18:08:27 6PM UTC 18:08:41 Who is asking for an update to the meeting time? Or, who is the current slot bad for? 18:09:21 Well, it was rather an attempt to have more people on the call 18:10:03 It is not ideal for Europe - right after the common working hours. So all School/shopping runs & Co. But not a big deal for me 18:10:32 drulli Slide-O-Mix : so, do we keep it for now? 18:10:51 Well it is not ideal for me (kids are going to bed right now…) but we can handle 18:11:00 it twice a month ;-) 18:11:21 So let us keep it... 18:11:37 Or move 1h earlier? 18:11:57 for me it would be better one hour later 18:12:17 but as I said, it is not that often 18:12:30 #action oleg_nenashev to add a 7PM UTC option to the poll 18:12:48 ok 18:12:50 Let's keep it as is for now, and keep the poll going 18:13:08 #agreed We keep 6PM UTC for now, please vote in the poll! 18:13:21 #topic Updates in the Governance Meeting tooling 18:13:55 #info Now we use Google Doc for the agenda. See the new Governance Board Meetings page here: https://jenkins.io/project/governance-meeting/ 18:14:05 That's it, I;d guess 18:14:10 This is ok for me 18:14:19 Is everyone comfortable with the new tooling? 18:14:29 it's fine for me as well 18:14:50 It is a part of our Wiki migration/evacuation 18:15:21 Moving on in 30 sec if no comments 18:15:57 #topic Approval request: CommunityBridge funding page 18:16:02 It is by me 18:16:14 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/iLutO2X0bdg 18:16:37 I would like to get approval to setup a funding page prototype on CommunityBridge 18:17:07 #info Current page (for mentorship only): https://funding.communitybridge.org/projects/jenkins 18:17:38 The plan is to enable other categories and to reference the flow from jenkins.io/donate as an experimental one 18:18:02 Sounds like a good plan to me 18:18:08 I think it make sense to move everything to CDF 18:18:41 We will have to move, because SPI is expected to stop accepting donations sooner or later 18:18:53 They agreed to stop doing so in May 2019 18:19:02 But they still do that tho :) 18:19:26 +1 for me as donations has been sent via email previously. This is much better looking then sending an email to SPI 18:20:00 So far there was no negative feedback in the thread. Do we need any clarification? or should we just vote? 18:20:50 P.S: You may see a 3K USD self-donation. This is a stipend for our first CommunityBridge mentee (Sladyn Nunes) 18:21:06 VOTE: Approve beta testing of the CommunityBridge as a reference implementation 18:21:12 +1 18:21:13 * oleg-nenashev abstains 18:21:19 +1 18:21:19 +1 18:21:32 +1 18:21:52 let's wait for 30 sec 18:22:31 Would it be possible or does it make sense to show the totals of the donations somewhere on the web page? In the style of wikipedia? So that the people see how many income we have? 18:23:01 drulli: You mean donations from multiple channels? or just SPI? 18:23:12 uhm, just CommunityBridge 18:23:17 From all channels 18:23:30 ah ok, sorry 18:23:58 CommunityBridge publishes summary: https://usercontent.irccloud-cdn.com/file/lJSc9awR/image.png 18:24:24 For all channels we could do quarterly reports, but it would require manual actions 18:24:50 rtyler: used to do the treasury report for SPI 18:24:55 I see, that link is already sufficient. 18:25:20 So we can improve it as we go 18:25:40 Linux Foundation also seeks feedback about improvements they could make on the portal 18:26:12 The payments backend for them is Expensify. We use it, and IMHO it's awesome 18:26:27 Especially being compared to other systems I used before 18:26:38 Any other questions? 18:27:22 ok, let's proceed 18:32:19 Hi all 18:32:26 IRCCloud went down 18:32:34 do I was dropped off 18:32:47 same for markewaite and lyssat 18:33:00 _alyssat 18:33:38 is everyone back? 18:33:52 yes I am still here 18:33:58 lucky you 18:33:59 i'm in 18:34:06 I'm still here 18:34:13 I had to fallback to another IRC service 18:34:27 OK, let;s continue 18:34:42 #agreed Beta testing of CommunityBridge funding is approved 18:34:58 #action oleg_nenashev to setup a reference implementation and draft a JEP 18:37:28 hmm 18:37:42 this meeting becomes fun 18:37:56 ;D 18:37:58 so many oleg's! 18:38:05 Did the "agreed" message arrive? 18:38:15 No 18:38:42 #agreed CommunityBridge Funding beta testing is approved 18:39:02 #action oleg_nenashev to setup the reference implementation and draft a JEP 18:39:04 uff 18:39:08 oof, sorry, I lost track of time 18:39:10 p/ 18:39:28 Slide-O-Mix drulli rtyler Could someone please take it over? 18:39:46 take what over? 18:39:50 the meeting 18:39:56 what is the doc link for the agenda? 18:39:57 yey 18:40:29 https://docs.google.com/document/d/11Nr8QpqYgBiZjORplL_3Zkwys2qK1vEvK-NYyYa4rzg/edit 18:40:54 Ok, are we ready to move to the next topic? 18:40:56 I am still here, just afraid of network issues 18:40:58 oleg-nenashev39: you need to #chair some people 18:41:07 I think we are :( 18:41:35 #topic Jenkins Evergreen Infra Status 18:41:47 hmmm, need #chair oleg-nenashev39 18:41:48 oleg-nenashev39 needs to invoke the #chair command 18:42:00 #chair Slide-O-Mix 18:42:07 #topic Jenkins Evergreen Infra Status 18:42:15 robobutler: are you alive?! 18:42:15 Slide-O-Mix: Error: "are" is not a valid command. 18:42:19 change your nick back oleg-nenashev39 18:42:20 ineed 18:42:21 indeed 18:42:27 OK, I will try 18:42:31 I am still the chair 18:42:45 `oleg-nenashev` is the chair 18:42:46 Switch back fails, thanks IRC Cloud 18:42:50 #topic Jenkins Evergreen Infra status. Do we shut down the Evergreen infra? (Olivier Vernin, Oleg Nenashev) 18:43:34 Well, we can proceed without topic 18:43:36 oleg-nenashev39: /msg nickserv ghost oleg-nenashev 18:43:41 The meetings will be a mess tho 18:43:55 then change your nick 18:45:47 wip 18:46:12 #chair Slide-O-Mix 18:46:12 Current chairs: Slide-O-Mix oleg-nenashev 18:46:16 #chair rtyler 18:46:16 Current chairs: Slide-O-Mix oleg-nenashev rtyler 18:46:20 thanks 18:46:21 that was stupid 18:46:26 Slide-O-Mix: please continue :) 18:46:42 My IRCfu is so rusty 18:46:52 #topic Jenkins Evergreen Infra status. Do we shut down the Evergreen infra? (Olivier Vernin, Oleg Nenashev) 18:47:01 robobutler doesn't have real access controls, anybody could have changed nicks to yours and taken it over :) 18:47:01 rtyler: Error: "doesn't" is not a valid command. 18:47:39 #info https://groups.google.com/forum/#!msg/jenkinsci-dev/OlG1IEFmSiQ/8RHA_urCBQAJ 18:47:47 I am not sure whether olblak is around 18:47:55 olblak: ping? 18:48:01 I'm in favor of shutting it down, and closing the Evergreen experiment down 18:48:08 I can/should write a blog post to that topic 18:48:13 What's the current usage of it? 18:48:20 Is it heavily used, or minimal usage? 18:48:23 broken :) 18:48:28 batmat and I haven't been pushing updates 18:48:31 Long story short, we are migrating from ACS to AKS, and we need to either shut down the service or find maintainers 18:48:39 the service was already broken 18:48:46 ok, so even if people are "using" it, it is not useful at all? 18:49:08 I have heard a rumor of 8 users 1 year ago 18:49:11 shutting down evergreen servers doesn't do anything but return their Jenkins environments to what they otherwise are, stagnate and un-updating :p 18:49:27 I'm in favor of shutting it down 18:49:35 the experiment taught me some good things at least, not sure what lessons others learned :) 18:49:36 We will still need to somewhat announce the project shutdown 18:49:46 Also, the code stays with us 18:50:04 rtyler and batmat did everything-as-code IIRC 18:50:24 oleg-nenashev39: I think olblak should be free to disable the services, I will then write a blog post on the subject 18:50:32 we don't need to block decommissioning ACS 18:50:46 rtyler I think we can send a notice in advance 18:51:04 oleg-nenashev39: I am not committing to that 18:51:05 If we approve it, we can send a blog in few days and let the service die on Jan 31 18:51:09 Is there a target for migrating to AKS? 18:51:24 Jan 31 is a deadline 18:51:24 I don't think you're understanding the state of things 18:51:36 users are NOT getting updates right now, and haven't gotten them in many many months 18:51:40 the service is fundamentally broken 18:51:46 blocking olblak in any way is pointless and saves us nothing 18:51:59 I agree 18:52:22 If we want to sign-off immediate shutdown, I am also fine 18:52:42 I say shut it down now 18:52:50 ditto\ 18:52:51 There is no point keeping it up if its broken right now 18:52:56 sorry for confusion rtyler 18:53:41 So, vote for "Sign-off immediate shutdown of Evergreen Infra OR any other decommission process preferred by the Infra Officer" 18:54:00 Just to leave olblak option to "do nothing until it dies on its own" 18:54:14 +1 Sign-off immediate shutdown 18:54:15 +1 18:54:19 +1 18:54:48 obvs +1 18:55:09 #action rtyler to archive evergreen repository 18:55:45 #action oleg_nenashev to update jenkins.io projects (archive Evergreen there) 18:56:01 rtyler do you take the blogpost? 18:56:37 #action rtyler to eventually write a blog post wrapping up the Evergreen experiment, updating the website too 18:57:20 OK, I will just move Evergreen out of active projects 18:57:43 so, next topic? 18:58:03 sounds good 18:58:12 uhm, also we need to stop Sentry accounts 18:58:25 ? 18:58:31 Or reuse them fo ci.jenkins.io like it was discussed on Tuesday 18:58:32 that's only used by Evergreen IIRC 18:58:57 we can definitely use it for other purposes, we have an open source gratis license with Sentry 18:59:00 drulli: sentry.io 18:59:08 drulli Sentry is a event logging / reporting system which was used for Evergreen 18:59:23 E.g. we caught some JEP-200 and Java 11 issues through it 18:59:39 rtyler I would prefer to keep it for now if you are fine 18:59:46 yeah, no problem with that 18:59:49 ty 18:59:53 I never turn away free stuff :) 19:00:13 #agreed keep Sentry account for now (could be used for other systems) 19:00:25 So we have a meetup topic 19:00:38 Would be nice to vote there if everyone has few minutes 19:00:56 Sorry for the IRC mess and delays it caused 19:01:22 let's keep rolling, Slide-O-Mix if you'll do the honors 19:01:31 #topic Jenkins Area Meetup removal follow-up (Alyssa Tong, Oleg Nenashev) 19:01:46 #info https://groups.google.com/forum/#!topic/jenkinsci-dev/cviU5XUX8vQ 19:01:59 The history summary is in the thread 19:02:10 Thank you Oleg for writing out that email..very comprehensive :] 19:02:20 happy to help 19:02:43 We are following up on the fallout after the account removal together with Alyssat 19:03:06 But it is a good time to start shutting down inactive accounts IMHO 19:03:10 I'm all for cleanup, and if Alyssat says it's good, then I'm +1 on whatever she wants :) 19:03:23 So, 2 votes here 19:03:25 VOTE: Approve the suggested process in general && delegate the final process decision to the event officer and Advocacy and Outreach SIG (immediate/short-term step down for meetups which never happened, grace period for stale ones) 19:03:25 channels 19:03:41 +1 on both from me 19:03:43 The JAMS w/ data corruption is still being worked on by meetup.com..this may take them some time to recover 19:03:48 +1 19:03:55 The latter one is to just do some housekeeping and reduce the number of channels we have to maintain 19:04:22 I am +1 for both, obviously 19:06:20 good to go then? 19:06:26 I think so 19:06:33 thank you all 19:06:39 #topic FOSDEM updates (Oleg Nenashev) 19:06:47 thank you too Alyssat 19:06:58 most importantly, I won't be able to join in FOSDEM :'( 19:06:59 :] 19:07:19 #info https://jenkins.io/blog/2020/01/10/fosdem-is-coming/ 19:07:20 I've never been to FOSDEM, I should look at attending in the future 19:07:30 Slide-O-Mix yes you should! 19:07:37 it's a delightful chaos 19:07:55 wouldn't be this year, but maybe next 19:08:02 lots of good food and beer :] 19:08:10 There is also Delirium. Best place to pay all the beer debts you accumulate over the year 19:08:50 #info We have a small contributor summit on 31st. https://www.meetup.com/jenkinsmeetup/events/267684785/ 19:08:58 So it is not just about beers 19:09:13 is markewaite doing a pipeline training? I couldn't tell who might be running that 19:09:27 rtyler Yes, it is Mark 19:09:40 #info On the Thursday 30 of January, there will be two workshops one about Jenkins Pipelines lead by Mark Waite, and a second one about JenkinsX by Viktor Farcic. 19:09:50 #info Finally the FOSDEM, the 01 and 02 of February, we’ll all be at FOSDEM. So come and say "hi" at the Jenkins/JenkinsX stand, inside the CICD Devroom. 19:10:16 I like just copy-pasting olblak's post :) thanks for writing it olblak! 19:10:29 IMHO we should definitely promote Marks' training from @jenkinsci (assuming it's relevant to Jenkins users and not CloudBees proprietary) 19:10:33 So, is anyone going to SCALE? 19:10:46 rtyler Yes, I have it in my list for Tweets 19:11:15 We had CB posts few days ago, so I delayed jenkinsci tweets a bit 19:11:38 I will be there to help out w/ the trainings and the booth..we'll have Jenkins socks =D 19:12:13 rtyler Slide-O-Mix markewaite What about SCALE? 19:12:21 I will not be attending SCALE 19:12:38 We will be at SCALE as well..at least Mark and I will 19:12:42 I have not heard of SCALE... 19:12:50 Mark will be doing he same training 19:12:59 Slide-O-Mix: in Pasadena, which is closeish for ya IIRC 19:13:03 It's like FOSDEM, but less beers and Clubmate 19:13:13 yeah, much closer than FOSDEM for sure 19:13:21 and we have the usual Jenkins booth. We'd love to have more folks to help us with booth staff 19:13:29 it is also a great event 19:13:37 far more kid friendly than FOSDEM too 19:14:22 I may go to SCALE this year, to be confirmed if timing for other trips is fine 19:14:32 any other details on this topic? 19:14:38 we're straying into advocacyland 19:14:39 Will be happy to help if I am there 19:14:44 (y) 19:14:53 yup, nothing from me 19:14:56 Thanks all! 19:15:32 And thanks to Slide-O-Mix for taking it over... second time in a row :bow: 19:15:41 glad to help 19:15:48 are we all done? 19:16:01 Last thing on the agenda is Next meeting 19:16:05 #topic Next meeting 19:16:13 I;d guess we discussed it in the beginning 19:16:18 true 19:16:21 We agreed to keep 6PM UTC for now 19:16:30 ok, we'll end meeting then 19:16:37 #endmeeting