selenium.yaml file is the source of truth on who owns which selenium* job. Duplicating the data on a wiki page means that it will probably get out of date with time, as people forget to update it when updating the file. The file should have owners' phabricator user name (as a comment).

I could create a very short wiki page saying what it means to be an owner and linking to the file. Or we could just document that in the file. Or both.

Owner of the job makes sure the job is passing. If the job fails, it has to be fixed as soon as possible. If the owner can not fix the job, they should ask for help.

In T142409#2567612, @zeljkofilipin wrote:

selenium.yaml file is the source of truth on who owns which selenium* job. Duplicating the data on a wiki page means that it will probably get out of date with time, as people forget to update it when updating the file. The file should have owners' phabricator user name (as a comment).

Good point.

I could create a very short wiki page saying what it means to be an owner and linking to the file. Or we could just document that in the file. Or both.

I think that makes sense (documenting on-wiki what it means to be an owner, cross linking it).

The purpose is just to make it more discoverable. A wiki page with a "what is this?" and a link to the file should be alright.

How does this look?

Continuous integration/Ownership of Selenium Jenkins job

Change 306648 had a related patch set uploaded (by Zfilipin):
Added Phabricator username for owners of Selenium jobs

https://gerrit.wikimedia.org/r/306648

Change 306648 merged by jenkins-bot:
Added Phabricator username for owners of Selenium jobs

https://gerrit.wikimedia.org/r/306648