# Leave Policy

Occasionally, Electron maintainers take a leave of absence from the project for personal or professional reasons. When this happens, it is important to reduce the risk to the project of compromised accounts with administrative permissions since those accounts may be unmonitored during the maintainer's leave of absence. This is not intended as a judgement on any individual member, simply a risk-mitigation strategy for the project as a whole. This policy outlines the responsibilities of the Community and Safety Working Group when notified of an Electron maintainer taking a leave of absence from the project for any reason.

Because leaves of absence may be for private, personal reasons, notification of the Community and Safety Working Group may be made by sending an email to the [Code of Conduct notification email address][coc-email]. All communications through this email address are to be kept confidential.

[coc-email]: ../CODE_OF_CONDUCT.md#enforcement

## Notification

It is highly preferred, but not required, that the person who is taking the leave of absence notify the Community and Safety Working Group of that fact. If notified by a third party, the Working Group will:

1. Take reasonable steps to verify with the person taking leave _before_ taking action.
1. Notify the person taking leave of the exact action that was taken and link them to this policy.

## When notified that an Electron maintainer has begun their leave of absence

* If that maintainer is a Slack Owner or Admin, change their account type in Slack to Full Member.
* If that maintainer is an Admin of the @electron organization on GitHub, reduce their permissions to Write.

## When notified that an Electron maintainer has returned from their leave of absence

* Restore the Slack account type the maintainer had before their leave.
* Restore the @electron organization rights on GitHub to what they had before their leave.