discuss: a periodic event for looking into CI reliability issues

[joyeecheung]

In the collaboration summit we brainstormed some ideas about improving CI reliability, one that came up is having a periodic event for looking into CI reliability issues.

The rough idea is, on the second Friday of each month, we self-organize a collective effort to look into the CI reliability issues. We can call this CI Gardening Friday. This should be a low-commitment event, just to create some momentum for contributors to allocate some time on this day to take care of the CI. The general protocol of improving CI reliability can be found in https://github.com/nodejs/reliability/#protocols-in-improving-ci-reliability. We can open a tracking issue on this day in the core repo, and use the #nodejs-ci-flake and #nodejs-build channels in the OpenJS slack to coordinate our efforts.

Feedback about the frequency and the date of this event is welcomed (the "second Friday of each month" part is just an option inspired by V8's cleanup friday).

[joyeecheung]

So we were about to kick it off this Friday, but then the CI is going to be locked down for a security release, so it will be deferred to next Friday (if CI is out of embargo then).

[mhdawson]

@joyeecheung I'm wondering if we need a way to make sure any many collaborators as possible know we are planning to get together next Friday. Either an at mention to all collabortors, post in the slack channels, calendar entry, tweet or maybe all of the above. What do you think would be best ? As a start I added the tsc-agenda tag so that it will show up on the agenda for next week and TSC members should be aware.

[joyeecheung]

Either an at mention to all collabortors

I think we should avoid this in general

post in the slack channels, calendar entry, tweet or maybe all of the above.

but all the rest SGTM:)

[targos]

Either an at mention to all collaborators

I think we should avoid this in general

We can create a team with interested people to avoid mentioning everyone.

[mhdawson]

@targos, @joyeecheung I think an initial at mention to all collaborators makes sense as otherwise how do they find out and tell us they are interested?

[mhdawson]

We discussed an initial mention to all collaborators in the TSC meeting today and there were no objections.

@nodejs/collaborators, @joyeecheung is planning the initial event for Friday Oct 20th. Please check this issue on the day for details on how to join/collaborate.

[mhdawson]

Created calendar entry and posted to nodejs-core slack channel

[MrJithil]

I'm not yet a collaborator. But I'm interested in involving this regular activity.

My time zone is Sydney, Australia. If this meeting timing aligns with my hours, I can participate in the meetings.

[himself65]

I'm interested on this

[joyeecheung]

I'll be on a plane most of this Friday, though I may still be around for some hours

[joyeecheung]

Oops, didn't notice that this is now pinging all collaborators - let's try not to reply to this issue and open a new one for the occurrence of the next event.