The role of the ombudsperson is to help our team ensure it meets the highest standards of ethical open access scholarly publishing. The ombudsperson acts as a point of contact in case someone has a concern about something that is or has happened with one of the Programming Historian publications.

Each of our publications has its own dedicated ombudsperson, who acts as a point of contact whenever someone has a concern about either our publishing or our processes and policies. This could be an author who is dissatisfied with the peer review process, an editor who needs advice on handling a sensitive matter with an author or reviewer, or a concern between team members.

The ombudsperson will not have to proactively seek out or identify issues, but instead will be listed as a point of contact on the website and in peer review tickets. In the past, someone has turned to the ombudsperson approximately once per year.

We at the Programming Historian are committed to accepting the judgment of the ombudsperson (as long as it's legal), so we trust you'll guide us faithfully!

Key points of reference are our various editorial guidelines and our values:

• https://programminghistorian.org/en/contribute
• https://programminghistorian.org/en/about
• https://github.com/programminghistorian/jekyll/wiki

If you are one of our ombudspersons and you would like specific guidance or training about Programming Historian please contact the Managing Editor of the relevant publication in the first instance.