scverse / ecosystem-packages Goto Github PK

Why does this repo track repositories using the template? I think this is for tracking ecosystem packages, and using the template is neither sufficient or required to be an ecosystem package.

@grst @flying-sheep

https://schist.readthedocs.io/en/latest/tutorials.html#nested-model

We probably want some sort of badge which people can pin to their approved repositories. Any suggestions how this could look like?

I think we should close the open "add {package}" issues since we've moved to a submission rather than nomination based model. I do think it could make sense to open issues on the respective repositories asking for them to submit.

Wdyt @grst, @mikelkou?

• #106
• #43
• #80
• #40

I think we should include a statement on "authors of ecosystem packages agree to abide by the scverse code of conduct on all scverse communication channels"

We want to find them to give them cruft update PRs. We currently use GH search to find those packages. However, the search has time limits (180 days without commit), so only using it could make us miss repositories.

We should use the scverse bot to maintain the list here to be more flexible: e.g. people can theoretically add the bot as a contributor to their private repo, and we can blocklist entries.

The list should be a human readable file in this repo. (JSON, TOML, or YAML). I’m -1 on JSON because the lack of trailing commas obscures what’s going on in diffs.

Should we be versioning the json-schema?

This would come in handy once we start updating it.

I think it would be good to connect this with the discourse forum.

Something like?

Registered ecosystem packages can get their own tag to use on the scverse forum for user discussion.

https://github.com/YosefLab/Hotspot

https://github.com/gao-lab/GLUE

• It should be "point of contact" only, not all contributors
• email addresses instead of github handles

We should be adding authors of packages registered here to the github org, right?

Currently the ecosystem on the website is static. That means we manually need to rebuild the website every time we want new packages to show up.

There are two solutions to this:

• make the website dynamically load the json from https://scverse.org/ecosystem-packages/ecosystem.json
• Trigger a website build via github actions every time a PR gets merged into ecosystem-packages.