Dustin Ingram

Seems like this is still an issue: > I look up 'rfc6266' because I was told about the module and I want to know more about it. Said module appears...

Ah, this is because our Elasticsearch provider doesn't work with newer versions of `elasticsearch`: https://github.com/pypi/warehouse/pull/10312 Might be time to replace our search backend...

Hi folks, I'm locking discussion on this issue -- while I appreciate the intention behind the replies, we don't need more examples of this happening as there are likely thousands,...

This issue is still open.

> @di - should all of the above cases also be covered in the if/elif branches? Ideally, yes. I think your plan sounds good!

> the template has ` {% elif event.tag == "account:reauthenticate:failure" %}`, but the reauth constant is commented out `# ReauthenticateFailure = "account:reauthenticate:failure"` -- should it be reactivated? It should not...

I think we probably need a bit more discussion before continuing work on this, see https://github.com/pypa/warehouse/issues/7116#issuecomment-570303891.

I think to address this issue, we'd probably need to provide an API for testing credentials separate from #726, as it doesn't quite solve the problem of "once we built...

My general thoughts here is that for metadata that we can 'verify', we should probably elevate that metadata in the UI over 'unverified' metadata. We can already validate email addresses...

Following on to [my previous comment](https://github.com/pypi/warehouse/issues/8635#issuecomment-1315889259), here's a mockup of what I'm imagining to separate the metadata we can verify today (source repository, maintainer email, GitHub statistics, Owner/Maintainers) from the...