Skip to content

Admin when team members step down

Anisa Hawes edited this page Dec 1, 2022 · 14 revisions

The following is a list of actions that need to be taken when a team member steps down from the project

  • Remove Google Groups access (@anisa-hawes)
  • Remove Google Analytics access (@acrymble) - only applicable to longer-serving members
  • Remove Github Jekyll access (@acrymble) - only applicable to longer-serving members
  • Remove Github ph-submissions access (@anisa-hawes)
  • Remove yourself from the Project Team Member list https://github.com/orgs/programminghistorian/teams/project-team/members (@NAME)
  • Remove from ProgHist Ltd register of members (@drjwbaker)
  • Remove Twitter access (@anisa-hawes)
  • Change team: true to team: false, and add team_end: YYYY to the _data/ph_authors.yml file to remove the person from the Project Team page (@anisa-hawes)
  • Check that they have no open issues assigned to them on either the Jekyll repository or the Submissions Repository (team leader).
  • Review service integrations page to ensure that they do not have any associated integrations tied to their accounts (@anisa-hawes).
  • If they hold any other team roles, inform @anisa-hawes that a replacement is needed.

Wish them well, and invite them to keep in touch.

New Wiki (in-progress)

Publishing Tasks

Phase 1 Submission

Phase 6 Sustainability Accessibility

Phase change templates

Communications

Social Media

Bulletin

Events

Call Packages

Administration and Documentation

Members

Internal records

Resource indexes

Lesson Production and Development

Language and Writing

Accessibility

Governance

ProgHist Ltd


Old Wiki

Training

The Ombudsperson Role

Technical Guidance

Editorial Guidance

Social Guidance

Finances

Human Resources

Project Management

Project Structure

Board of Trustees

Clone this wiki locally