Repository navigation
Volunteer for CI Reliability Strategic Initiative #59004
Description
The CI situation nodejs/TSC#1614 has been discussed in many TSC meetings. To help it move forward pragmatically, the TSC has agreed to make it a strategic initiative.
If you're interested in leading the CI Reliability Strategic Initiative, please submit a PR to add an entry to:
https://github.com/nodejs/node/blob/HEAD/doc/contributing/strategic-initiatives.md
As the lead, you'll be empowered to take actions such as forming a dedicated team, spreading awareness among contributors, or taking any other steps necessary to improve the CI situation.
Activity
juanarbol commentedon Jul 9, 2025
My bandwidth is a bit limited, I can't fully commit into this, but I could spare some of my time and help a bit <3
0hmX commentedon Jul 10, 2025
Same will drop some help with the flaky tests!
bnoordhuis commentedon Jul 11, 2025
Does that mean funding finally has been made available? The linked issue is unclear.
RaisinTen commentedon Jul 12, 2025
The availability of funding did not trigger the opening of this issue. The funding-related discussion was happening in nodejs/TSC#1629. I don't know if I can disclose the amount of available funds, will ask.
RaisinTen commentedon Jul 16, 2025
The TSC does have some limited discretionary funds available. Some has already been earmarked for security related work. The remainder is still up for discussion. Proposals for work that would benefit from funding should be submitted to the TSC for consideration.
Ethan-Arrowood commentedon Sep 12, 2025
I'm not able to lead this, but absolutely can contribute test fixes and other things. Please feel free to ping me when a team gets put together.
github-actions commentedon Apr 19, 2026
This issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.
github-actions commentedon May 19, 2026
This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 240 days).
If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.