Eric Pugh

@DmitryKey I am going to be Europe from May 1 to May 8th, so we could pair on this analysis together if you want. Right now on the home page...

I was thinking about looking more into this.... Had some discussions about "Workflow" in Quepid, and routing different types of docs to specific judges etc...

Oooh! Thanks for finding this one... This screen/feature I don't think was ever tested with Quepid, as it's somewhat of an advanced use case. Most folks are running a query...

We did get `docker-compose` replaced with `docker compose` recently!

we've made a lot fo progress

FYI, I was working on trying to get an update to the latest version of the gem and found a perfectly good workaround, just to ignore the rules in this...

Here is the new format for RRE: ``` { "id_field": "id", "index": "tmdb", "template": "template.json", "queries": [ { "placeholders": { "$query": "=cmd" } }, { "placeholders": { "$query": "First Query"...

so i don't have topics, and i thought some of that was optional.. honestly, i haven't tested it casue it's been a while that i've used RRE....

so, i wonder if i should just support the direct rankquest format instead?

Okay, I think the better route to go is to introduce a RankQuest format.. that way each can evolve as market demand drives it.. Do you have an example of...