Clarifying Process for stepping down / being stepped down

[acrymble]

In the interest of transparency and fairness, I want to revise the wiki page on "Privileges and Responsibilities of Membership" and "Checklist for Sabbaticals" in light of the logistics of managing these processes.

1. Privileges and Responsibilities of Membership

I propose adding a section as follows:

Members who have not been meeting their responsibilities to the Project for at least one month may be approached by the Team Development Manager or their Team Leader and asked if they need support, to take a sabbatical, or to consider taking on a new role within the project that better suits their available time and expertise. This discussion will take place through email using the email address that the member has registered to the GoogleGroup with. If the member does not respond in a timely manner (3 weeks), the Team Development Manager or Team Leader will send another email reminder with a 2 week deadline asking for a response. If no response is forthcoming the team member will be removed from their roles and retired from the project.

2. Checklist for Sabbaticals

I propose adding a section as follows

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.

---

I welcome comments on this. This is mean to clarify processes and to maintain fairness.

[acrymble]

I would like to put this on the agenda for our next meeting, with the aim of getting approval for these changes. #1589

[acrymble]

I'll also add a suggestion of opening a ticket to find missing members, as that was what helped us track down @vgayolrs so it seems like a good idea.

[acrymble]

I've added these to the wiki. Thanks everyone.