Some project resources could be collections of general resources with conventional types, so they can be surfaced by other applications with ease.
- Real time Chat <- Discord, Matrix, etc
- DMs/calls infra <- Signal
- social infra <- bsky
- docs/playgrounds/talks/etc
- Repos (git level), and for each repo:
- Collaboration infra (github level: PRs, issues, discussions/forum). These are bundled with the repo in GitHub, GitLab, tangled. Forum is sometimes unbundle, as in Discourse. So we may have these three as separate resources.
- packages <- npm, pypi, crates
How a Project, Repositories, and Packages relate is very important for npmx. A Project could have several repos and packages. All interconnected. These could be in different platforms (GitHub, GitLab, etc) and different registries if they use diff languages or they publish to several of the same lang (npm, jsr). This map isn't anywhere right now and would be very useful if we can render an npmx Project profile that has this as one of the central pieces to guide users and devs to discover this graph of repos/packages.
Some project resources could be collections of general resources with conventional types, so they can be surfaced by other applications with ease.
How a Project, Repositories, and Packages relate is very important for npmx. A Project could have several repos and packages. All interconnected. These could be in different platforms (GitHub, GitLab, etc) and different registries if they use diff languages or they publish to several of the same lang (npm, jsr). This map isn't anywhere right now and would be very useful if we can render an npmx Project profile that has this as one of the central pieces to guide users and devs to discover this graph of repos/packages.