I don't see a reason why not, if its in the project file ( or in the automation/*.emails after we get rid of the yaml files ).

these are std-ci jobs, I'd rather not go down the path of making this configurable from YAML.

you recently enabled email plugin to other jobs no? let's drop the idea of getting the list of maintainers from Gerrit for now cause it seems to be more complex and probably overkill. can you help with sending a patch to specific people? ( we can fetch the list of maintainers from the Gerrit for starts )

It can be done with some API calls to check who is in which group.
I don`t think it will load Gerrit that much - every job run already does a git clone - and it a much heavier operation then a simple API call.

How will we do that? doesn't it mean it needs a dynamic configuration to update the job configuration?
It will need to find the maintainers on each job run, it will add significant load issues to Gerrit just to get a static info.

And we need to be able to figure out the maintainers automatically from Gerrit

I don't think this kind of thing should be specified in the repo itself - because std-ci is supposed to be portable and agnostic to the environment it runs in.

Instead, we might consider setting up such a notification across the board to project maintainers.

do we have support to emailing to list of recipients on check-merged.sh scripts?
Can we add it per job on the yaml file?

Worth considering adding .emails or .alerts to std ci so project owners can subscribe to emails alerts from CI on failures.