-
Notifications
You must be signed in to change notification settings - Fork 229
Team Leader Selection Process
Adam Crymble edited this page Feb 3, 2022
·
2 revisions
This process was discussed and agreed in https://github.com/programminghistorian/jekyll/issues/1986 by the Project Team. It affects the appointment of the following roles:
- Global Lead
- Comms Lead (discontinued 2021)
- Tech Lead
- ProgHist Chair
- Project Manager at Large
- As the affected roles are currently occupied by people on undefined terms, we continue as normal. If and when those individuals want to step down from those roles, they inform the Project Team at a Project Team meeting and it is noted in the meeting minutes. We would appreciate notice of at least 6 months if possible.
- Project Team then assigns a sub-team of 2-3 people to investigate and make recommendations on the continued / altered need for said role and brings them to the next Project Team meeting for discussion. Outcome may be: no need to replace (role ends), replace as-is (new candidate), replace with amendments (new but closely related role).
- If a new candidate is needed, a role description and ideal term length is written & approved and circulated internally to all Members for expressions of interest. Candidates submit roughly 250 word vision for the role for consideration by membership. If more than one candidate, then a private ballot determines the winner. If no candidates come forward, we proceed with an external advertisement.
- All roles will be 3 year terms unless agreed otherwise. Role holders are encouraged to take up to 12 month leaves / sabbaticals as needed, in line with our sabbatical policy, in which case an interim person may be appointed using a similar method.
- This task of chairing and administering the replacement process will be agreed between current team leaders and led by the Project Manager at Large.
- 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