Members Admin

Administration and Documentation

Members Admin

---

Contents of this page:

• Orientation checklist
• Closing tasks checklist
• Closing PR template
• Closing commit template

---

Orientation checklist

**Title:**
Orientation tasks for Forename Surname

**Issue template:**
This Issue represents introductory tasks for the orientation of **Forename Surname** @name who is a new member of our English / Spanish / French / Portuguese editorial team.

## Welcome

Welcome / bienvenidos / bienvenue / bem-vindos, Forename! Welcome to the _Programming Historian_ Project Team! ✨ 

## What the PH team will do:

- [ ] Our Publishing Team will add your profile to [the Project Team pages](https://programminghistorian.org/en/project-team) of our website 
- [ ] @anisa-hawes will introduce you to our Active Lessons Project Board
- [ ] @anisa-hawes will introduce you to our ph-submissions repository and our editorial workflow
- [ ] @anisa-hawes will invite you to our GitHub organisation so you can contribute to the site
- [ ] @anisa-hawes will invite you to our Google Group, Slack and Discord communities
- [ ] @anisa-hawes will add your name to our Register of Members

## What you need to do:

- [ ] Provide/set up a Google-enabled email address for our Google Group
- [ ] Provide/set up a GitHub username for our Submissions Repository
- [ ] [Read the Overview of our Editorial Workflow](https://github.com/programminghistorian/ph-submissions/wiki/Overview-of-Editorial-workflow)
- [ ] Read the [author](https://programminghistorian.org/en/author-guidelines), [reviewer](https://programminghistorian.org/en/reviewer-guidelines) and [translator](https://programminghistorian.org/en/translator-guidelines) guidelines pages of our website 
- [ ] Read the [Privileges and Responsibilities of Membership page of our Wiki](https://github.com/programminghistorian/jekyll/wiki/Privileges-and-Responsibilities-of-Membership)
- [ ] Read the [Code of Conduct](https://github.com/programminghistorian/jekyll/blob/gh-pages/CODE_OF_CONDUCT.md)

## The Culture of our Project

We have invited you to join the team because we value your opinions. We encourage all of our editors to contribute to discussions on GitHub or via email, and to civilly express their views, even if they disagree with any or all other members. This right to express one's opinions is central to our project. Please take this to heart.

---

Closing tasks checklist

**Title:**
Closing tasks for Forename Surname

**Issue template:**
This Issue represents closing tasks as Forename Surname @name steps down from our English / Spanish / French / Portuguese editorial team.

Thank you, Forename!
---
Sincere thanks for your contributions to _Programming Historian in English / en español / en français / em português_! We wish you the very best in your next steps, and we hope you will keep in touch with the project.

What the PH team will do:
--
- [ ] @ManagingEditor will review any open issues assigned to @name and reassign
- [ ] @anisa-hawes will remove your membership to our Github Organisation
- [ ] @anisa-hawes will remove your Write access to ph_submissions
- [ ] @anisa-hawes will remove your name from ProgHist Ltd's Register of Members
- [ ] Our Publishing Team will add your name to the Membership History list on the Project Team pages
- [ ] @anisa-hawes will remove you from our Project Team Google Group
- [ ] @anisa-hawes will remove your access to our internal social channels 

---

Closing PR template

I am updating `ph_authors.yml` to reflect that Forename Surname is stepping down from the English / French / Spanish / Portuguese editorial team.

To do this, I've changed their `team:` status to `false`, and added a new line that reads `team_end:` YYYY

Closes #ISSUE

---

Closing commit template

Remove Forename Surname from the list of active editors

- Update `team:` status to `false`
- Add `team_end:`