Procedure for adding a new engine to the list

[jszczerbinsky]

In CONTRIBUTING.md it's said, that one of the ways to contribute is to provide data about old/new engines, but it's not explained how to do it. Maybe designing some specific procedure for this process would make it easier both for You and people who wish to contribute with some engines data.

I would suggest maybe some csv file in the repo, where everyone could add the engines via pull request. This file would always contain engines, that haven't been processed or evaluated yet and they could be successively removed from there when their rating is finally evaluated - like a TODO list.

[jszczerbinsky]

or is the procedure just adding the .md file to engines/ directory?

[computer-chess-index]

Set up an initial version https://github.com/computer-chess-index/cci/issues/new?template=submit_engine.yml, and also the automatic import during the daily routine: #6
Really appreciate it, it opens up so many further possibilities.

[jszczerbinsky]

Okay, I've added some engine in #7, based on Your test submission, let's see how it goes!

So are You setting up the engines manually? or maybe Your tool can fetch the data from the issue automatically?

[computer-chess-index]

Cinnamon was added, the issue was closed, and the enginePage was created automatically.

For github repos it is automated, and the tool fetches the data from the issue without any manual intervention.

[jszczerbinsky]

Perfect!
How it's choosing the correct executable form the release? For example many engines are shipped in multiple variants - separate executable optimized for BMI2, AVX512 etc

[computer-chess-index]

That part is still done manually - I would not automate running unknown executables without any control. That would at least require a completely virtualized sandbox environment, I lack the ressources to provide that. The automation pipeline only provides them ready for testing.