Ulises Gascón

I enabled the CI to run in this PR :+1:

I opened a discussion on Slack (https://openjs-foundation.slack.com/archives/C02QB1731FH/p1711971438045899), I want to collect more feedback on this. Feel free to join us in slack. [invitation link](https://openjsf.org/collaboration)

> All of those need to remain as is until we start updating them for major bumps. When we go to v5 for `express` most of those will likely land...

I will relocate the pending things to 2 new issues (backlog for 5.x and Backlog for 6.0) :)

> With the new Triage team policy that should go away and so maybe it is enough. Yep, with the new nomination process in place this is not an issue...

I think that this initiative will be blocked until we have a solid plan for https://github.com/expressjs/discussions/issues/194

Here is a list of projects using Travis across the organization: - https://github.com/pillarjs/encodeurl - https://github.com/pillarjs/resolve-path - https://github.com/pillarjs/extend-proto - https://github.com/pillarjs/qs-strict - https://github.com/pillarjs/routington - https://github.com/pillarjs/templation - https://github.com/pillarjs/ssl-redirect - https://github.com/jshttp/basic-auth - https://github.com/jshttp/vary -...

Initial Big +1 from my side. I will check the documentation

I have a question regarding grouping or identification. I can see that sometimes the same contributors are shown twice like Wes or myself. Is there something that we can do...

Side note... I was exploring how to collect more detailed data about the GitHub activity for Node (see: https://github.com/nodejs/next-10/issues/271#issuecomment-2164871105) and I also took the opportunity to build a combined report...