-
Notifications
You must be signed in to change notification settings - Fork 229
Checklist for Sabbaticals
The Programming Historian is pleased to offer the option of sabbaticals for members who need to step away from the project temporarily. We will never refuse a sabbatical, and all members have a right to take them. So that we can maintain a healthy team and understand our capacity, we ask that members who would like to take sabbatical should please ensure that they have done the following:
- Please make sure that you communicate with the rest of the team how long your sabbatical will last. This should include a specific date at which you intend to return.
- Indicate whether your sabbatical will mean you will be completely away from the project, or if you plan to participate in board meetings, or otherwise continue certain tasks.
- Close out all open reviews and issues before you start your sabbatical, or (where possible) find someone to cover for you.
- Set a reminder for yourself to check in with the rest of the editing team as your sabbatical comes to a close.
- If you decide to leave the proect team completely, please let the rest of the team know in a timely manner.
Sabbaticals must be agreed in advance with the relevant Team Leaders, and must have defined beginning and end dates. Sabbaticals cannot be taken retrospectively. Members are reminded of the Privileges and Responsibilities of Membership.
Any member holding a directorship of ProgHist Ltd is able to take a sabbatical, but in order to ensure they are able to fulfill their legal obligations as the director of a company, they will still be provided with any information relevant to the running of the company during their sabbatical. While the Board of Directors of ProgHist Ltd will make every effort to ensure no 'work' is assigned to board members on sabbatical, this may not always be possible for legal reasons.
The Chair of the Board, Secretary, and Treasurer will have to put in place a clear plan to manage their duties before going on sabbatical.
- 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
- Funding
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