Michael Froh

> [@msfroh](https://github.com/msfroh) Can we carve out some "good first issues" here? Sure thing! I'll try out the "Create sub-issue" feature and tag them.

> The harder one is RemoteSnasphotDirectory. I strongly disagree with the extended compatibility feature on principle. That said, if we're going to let users shoot themselves in the foot anyway,...

Incidentally, I think there is a little bit more cleanup to do here. Since I've been learning more about the OpenSearch Gradle build and the various custom tasks that we've...

Recognizing that moving security (or the security plumbing with pluggable specifics) into core would be a major breaking change, how receptive are folks to making that kind of change in...

Interesting ... that implementation of `advance` on `AbstractNumericDocValues` should theoretically never get called, because every possible subclass should either override it or guarantee that it doesn't get called (by only...

Incidentally, this looks related to https://github.com/opensearch-project/OpenSearch/pull/12089, which was released in 2.12.

> Oh, I think you may mean line 690 and not 609 – is that right? I was looking at the 2.13 branch initially, to try to see if I...

If you need any help to get started on a fix, please let us know!

> I see [here](https://github.com/opensearch-project/OpenSearch/blob/main/CONTRIBUTING.md#tips-for-success-tips) that there are various test files I can update, but how do people manually test their changes to ensure the change has the effect they want?...

@jdddog -- Checking the code, it looks like you can put `"include_named_queries_score":true` in the body of a search request. I just wanted to check if that's a valid initial workaround....