2i2c-org / infrastructure

Infrastructure for configuring and deploying our community JupyterHubs.
https://infrastructure.2i2c.org
BSD 3-Clause "New" or "Revised" License
103 stars 63 forks source link

Document the specific packages we 'support' as part of our infrastructure #2566

Open yuvipanda opened 1 year ago

yuvipanda commented 1 year ago

Our infrastructure is composed of many different moving pieces, layered in fun cake-like ways. However, this sometimes makes it difficult to figure out which parts we actively support and which parts we do not.

We should make a fairly explicit list of things (infrastructure services & software packages at least) that are 'our' (2i2c) responsibility, and things falling outside this are not directly supported by us.

pnasrat commented 1 year ago

Related I'm wondering if we can get the information of what communities are running through observability (logs, metrics, traces) or real user monitoring to be able to better identify patterns and components we might want to move into support. Obviously this can be paired with qualitative data from community engagement (surveys, interviews, discussion, participant observing, etc)