search

2i2c-org / infrastructure

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

Tag all image related support tickets that come in #2767

Open yuvipanda opened 1 year ago

yuvipanda commented 1 year ago

One of the criterion for success in the Q3 Image managemetn goal (https://docs.google.com/document/d/1nQvGWGNhQf4yrZ4xUa0bUikGb9xt1aBwOTvYNrATY6s/edit?skip_itp2_check=true&pli=1) is to reduce the number of support tickets we get that are related to image management. For this, we should measure this and code them appropriately.

We do not want to increase the load on the support steward, so this should be done in a 'batched' fashion by someone once every two weeks, ideally before the retrospective for the goal. This might move to being a support steward responsibility eventually.

https://github.com/2i2c-org/infrastructure/issues/2582 has more information.

- [ ] Build list of tags we want to track, create
- [ ] Decide on schedule and create calendar entry
- [ ] Decide on how to tackle GitHub PRs that are not from 2i2c engineers
yuvipanda commented 1 year ago

Possible list of tags:

tag description
package-install Addition of a new package, upgrade of package version only
image-consult Any questions about changing an image that isn't just a package-install
upstream-image-bump Bump to using a new version of an upstream image, regardless of profileList being used or not
custom-image-bump Bump to using a new version of a custom image, regardless of profileList being used or not
yuvipanda commented 1 year ago

I think for the duration of this tag, the goal lead for this goal should just go through the tickets and categorize these as necessary, to not add more load onto the support steward.