As a follow-up to what we just discussed in the meeting, here's how to set up email notifications on Gerrit:

1. Log in to review.trustedfirmware.org 2. Click on the little Settings gear on the top right (next to your name) 3. Scroll down to Notifications 4. Type the repo name (e.g. TF-A/trusted-firmware-a) into the Repo field (you have to wait for it to auto-complete and then select it, can't just copy&paste the full name in) 5. Type a search expression for things to monitor into the field on the right 6. Click Add 7. Repeat with as many expressions as you want to monitor 8. Select checkboxes for the events you want to monitor (e.g. I believe "Changes" just sends one email when it is first uploaded, "Patches" sends one for every new patch set) 9. Click Save Changes

For the search expression I usually use something like path:"^plat/common/.*" or path:"^drivers/(arm/pl011|console|coreboot|delay_timer|gpio|ti).*" to monitor the subdirectories I'm interested in, but any valid Gerrit search expression works. You can try out the expression in the normal search field to make sure it detects all the changes you intended.

I also inquired about the coreboot documentation setup. They just use a cron job to rebuild the documentation in regular intervals, which I think would probably suffice for Trusted Firmware as well. (But if we really need it the moment the patch is merged, we could probably find a way to kick it off from Jenkins as well.)

coreboot runs the documentation server in a docker instance, the setup files for that can be found at https://review.coreboot.org/cgit/coreboot.git/tree/util/docker/doc.coreboot.... . If we're also using docker in our infrastructure, we could probably almost directly copy those. If not, it's still just one time setup of a few pip packages and running make in a cron job.