Rich Trott

> **nodejs-pt** just let me know that their [repo is inactive, and ok to be archived](https://github.com/nodejs/nodejs-pt/issues/83#issuecomment-1008608225). 👍 I've archived that repo. One thing this brings up though is that we...

I've archived all the nodejs-XX repos with the exception of nodejs-ko. That one seems relatively active but might be archivable or moveable to someplace outside the org. Someone ought to...

One way to a quick resolution might be a landing page that links to both. It will be an extra click, but I think that would be OK. If we...

I just tried looking at codecov.io stats in detail for the first time in a while and it looks like maybe our config needs a tweak? Clicking through to JavaScript...

Seems like my branches question can be ignored. The way the line coverage vs. partial line coverage stuff is displayed in codecov.io seems to surface the same information in a...

> So what's the consensus here -- are we ready to replace coverage.nodejs.org with codecov.io? As one of only two people keeping coverage.nodejs.org working I'd be in favouring of switching...

> I'll still defer to those who use coverage regularly That would be me. I wrote: > I'm on board with whatever minimizes the maintenance burden of providing this information....

Not directly relevant to the "should we switch or not" question, but if there's a way to edit the home/dashboard page, that would be helpful, I think. Specifically, the coverage...

@nodejs/jenkins-admins

I added `build-agenda` label so this at least gets on the next meeting agenda if no one replies between now and then.