Catalog of relevant projects

[lheagy]

At the meeting on October 26, one of the avenues we identified for enabling folks to engage is to create a list of related projects. Two questions:

1. What should the top-level organization be?

   • @lheagy suggestion: Jupyter, Python, Domain Science ?

2. What should the criteria be for listing a "relevant project"?

   • @lheagy suggestion: projects we have made contributions to under this project (e.g. if one of us has contributed: code / documentation / tutorial)?

[consideRatio]

Below are some projects I've made code contributions to related to work in the JupyterHub ecosystem and JMTE. The links contains a view of pull requests made. Is it too much to go for this level of detail when listing projects? Hmm...

What constitutes a project? There are some projects that have many repos but really are just one project, like helm/helm and helm/helm-www. In general I think it could make sense to mention various ecosystems for a courser overview and then list parts of under the ecosystem category. With such structure, we probably need a misc category also.

Thorough research into issues? A noteworthy contribution not classified as a code / documentation / tutorial excluded from the list below I've made is to traefik/traefik where I've spent significant time debugging and providing reproducible issue reports.

---

• jupyterhub/zero-to-jupyterhub-k8s
• jupyterhub/pebble-helm-chart
• jupyterhub/chartpress
• jupyterhub/action-k8s-namespace-report
• jupyterhub/action-k3s-helm
• jupyterhub/jupyterhub
• jupyterhub/binderhub
• jupyterhub/mybinder.org-deploy
• jupyterhub/kubespawner
• jupyterhub/configurable-http-proxy
• jupyterhub/helm-chart
• jupyterhub/jupyter-server-proxy
• jupyterhub/nbgitpuller
• jupyterhub/traefik-proxy
• yuvipanda/hubploy
• yuvipanda/jupyterhub-ssh
• executablebooks/github-activity
• executablebooks/jupyter-book
• dask/helm-chart
• dask/dask-gateway
• pangeo-data/helm-chart
• pangeo-data/pangeo-cloud-federation
• helm/helm
• kubernetes-sigs/nfs-ganesha-server-and-external-provisioner
• grafana/grafana
• k3s-io/k3s

[lheagy]

This is a really good question @consideRatio! And I am not sure quite what the right level of detail is here. To me, there seem to be two high-level ways to parse information:

• at the ~org level (might not be exact) but grouping related repos such ad those under "executablebooks" under one umbrella
• at the individual repo level

I think much of this comes down to who the audience is that we want to serve: the first serves a more general scientific audience who just want to get a flavour of what is going on; the second would be helpful for us with reporting, and might also be nice for giving a bit of an idea of how broad and interconnected the ecosystem is.

I lean towards the more detailed list, but could be convinced with way. What do others think?

[lheagy]

@kmpaul, @andersy005: from the pangeo site / pythia connections, do you have a page like this for any projects? and suggestions / thoughts on what level of detail you think would be most helpful here?