I'm OK with either choice, but I'm not owner of this repo. I am not familiar with the code either.

I pinged you just because you seem to be taking care of resultsdb, and this kinda goes with it, it feels like.

I'm not sure if anyone is using this anymore. I believe this is deployed in https://docs.resultsdb20.apiary.io/ but Firefox complains about its certificate:

Websites prove their identity via certificates. Firefox does not trust this site because it uses a certificate that is not valid for docs.resultsdb20.apiary.io. The certificate is only valid for the following names: apiary.io, *.apiary.io

Error code: SSL_ERROR_BAD_CERT_DOMAIN

On internal servers, we have a simple API documentation part of new v3 API that supports OIDC auth. But it is not enabled in fedora infra.

Sure, we use it every day. It's a client library, it doesn't need to be "deployed" anywhere, that's just the docs. Our openQA result reporting code for e.g. uses it hundreds of times a day.

Adam, if OpenQA uses it and we're not aware of anyone else using it, I guess we'll need to own this and migrate it to our Quality Forge. Thoughts?

I'd be a bit surprised if nobody else is using it? AFAIK resultsdb is used internally at RH for various purposes. Unless none of that code is written in Python or it all just uses an HTTP library and handles its own auth?

OK, well, I guess we'll take it.

Done. Will update references in code I know about.