We're discussing with the Vite team and trying to get funding to do a more generic version of ecosystem-ci. The new version should have reports in a website instead of in Discord or a table in PR comments. npmx could be a good place for these reports as the users are going to be already oauth into GitHub and could do admin for the projects directly.
As an example of a Project relationship with Downstream, in Vite, we need to map these downstream projects to core. Maybe this is ecosystem-ci specific, but it seems more generic and we could have a field to include it in the ecosystem-ci runs instead of what we do now of commenting these packages in config files.
In the context of ecosystem-ci, downstream is represented by a package in a repo. Each repo in a potential new version would have by convention a config file stating how to install each package deps, build it, and test it.
We're discussing with the Vite team and trying to get funding to do a more generic version of ecosystem-ci. The new version should have reports in a website instead of in Discord or a table in PR comments. npmx could be a good place for these reports as the users are going to be already oauth into GitHub and could do admin for the projects directly.
As an example of a Project relationship with Downstream, in Vite, we need to map these downstream projects to core. Maybe this is ecosystem-ci specific, but it seems more generic and we could have a field to include it in the ecosystem-ci runs instead of what we do now of commenting these packages in config files.
In the context of ecosystem-ci, downstream is represented by a package in a repo. Each repo in a potential new version would have by convention a config file stating how to install each package deps, build it, and test it.