-
Notifications
You must be signed in to change notification settings - Fork 227
Ombudspersons
Contents of this page:
What is a Programming Historian Ombudsperson?
The ombudsperson acts independently of editorial decision-making processes. They are guided by principles of fairness, impartiality, and confidentiality, and aim to support constructive resolution of concerns wherever possible. Their role is focused on maintaining trust, transparency, and respectful collaboration across the journal community.
An ombudsperson is appointed to each journal team to help ensure that our publishing practices remain open, transparent, and fair.
They act as a point of contact for anyone with a concern or complaint relating to a process, policy, or an individual’s conduct. Contributors – including authors, editors, translators, and reviewers – may approach the ombudsperson in confidence, and doing so will not influence the outcome of peer review or editorial decisions.
Concerns raised may include, for example, dissatisfaction with the peer review process, requests for guidance on handling sensitive situations, or issues arising between members of the team.
When contacted, the ombudsperson may offer independent advice, help facilitate constructive resolution, or, where appropriate, raise concerns with relevant members of the editorial team while maintaining confidentiality as far as possible.
The ombudsperson does not proactively monitor or investigate matters. Rather, they agree to be named as a point of contact on the journal website and within peer review materials in our GitHub repository, and to offer independent perspective and guidance when approached.
- Copyediting
- Copyedit comments
- Typesetting
- Archival Hyperlinks
- Copyright
- DOI
- Gallery image
- Checklist comment
- Handover comment
- Closing comment
- Opening comment Phase 0
- Phase change comment 1 to 2
- Phase change comment 2 to 3
- Phase change comment 3 to 4
- Opening comment Phase 4
- Phase change comment 4 to 5
- Phase change comment 5 to 6
- Phase change comment 6 to 7
- Tracking lesson phase changes
- Organisational Structure
- Trustee Responsibilities
- Trustee and Staff Roles
- Services to Publications
- Ombudspersons
Training
- Onboarding-Process-for-New-Editors
- Leading-a-Shadowing-process
- Board-of-Director---Continuing-Development
The Ombudsperson Role
Technical Guidance
- Making Technical Contributions
- Creating Blog Posts
- Service Integrations
- Brand Guidelines
- French Translation Documentation
- Technical Tutorial on Translation Links
- Technical Tutorial on Setting Up a New Language
- Technical Tutorial on Search
- Twitter Bot
- Achieving-Accessibility-Alt-text-Colour-Contrast
- Achieving-Accessibility:-Training-Options
Editorial Guidance
- Achieving Sustainability: Copyediting, Typesetting, Archival Links, Copyright Agreements
- Achieving Sustainability: Lesson Maintenance Workflow
- Achieving Sustainability-Agreed-terminology-PH-em-português
- Training and Support for Editorial Work
- The-Programming-Historian-Digital-Object-Identifier-Policy-(April-2020)
- How to Request a New DOI
- Service-Agreement-Publisher-and-Publications
- ProgHist-services-to-Publications
- Technical Tutorial on Setting Up a New Language
- Editorial Recruitment
Social Guidance
Finances
- Project Costs
- Spending-Requests-and-Reimbursement
- Funding Opportunities
- Invoice Template
- Donations and Fundraising Policies
Human Resources
- Privileges-and-Responsibilities-of-Membership
- Admin-when-team-members-step-down
- Team-Leader-Selection-Process
- Managing-Editor-Handover
- Checklist-for-Sabbaticals
- New Publications Policy
- Parental-Leave-Policy
Project Management
Project Structure
Board of Trustees