Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Checklist for Sabbaticals #766

Closed
6 tasks
JMParr opened this issue Mar 29, 2018 · 7 comments
Closed
6 tasks

Checklist for Sabbaticals #766

JMParr opened this issue Mar 29, 2018 · 7 comments
Assignees

Comments

@JMParr
Copy link
Contributor

JMParr commented Mar 29, 2018

Editors who are taking sabbatical should please ensure that they have done the following:

  • Please make sure that you communicate with the rest of the team how long your sabbatical will last.

  • Indicate whether your sabbatical will mean you will be completely away from the PH, or if you plan to participate in board meetings.

  • You should indicate a date by which you expect to return to your editing duties.

  • Close out all open reviews and issues before you start your sabbatical.

  • Set a reminder for yourself to check in with the rest of the editing team as your sabbatical comes to a close.

  • If you decide to leave the editorial board completely, please let the rest of the team know in a timely manner.

@JMParr JMParr added the policy label Mar 29, 2018
@JMParr JMParr self-assigned this Mar 29, 2018
@mdlincoln
Copy link
Contributor

once we settle on the generic list of things we want to do, I'll put this list template into the wiki. And then we should open an instance of these checklists, even just in our listserv (since we may not want to discuss these in public issues always)

@JMParr
Copy link
Contributor Author

JMParr commented Mar 29, 2018 via email

@acrymble
Copy link

We can also note that we will never refuse a sabbatical and that all editors have a right to take them. This is really just about communicating availability to the project.

@walshbr
Copy link
Contributor

walshbr commented Mar 29, 2018

Personally, codifying the terms and process like this probably would make me more likely to ask for one. Visibility of these sorts of things is important.

@acrymble
Copy link

acrymble commented Apr 3, 2018

A comment on the above suggestions. I think it's acceptable to ask someone to either close out issues / finish tasks, or find someone to pass them off to. What we don't want is tasks half done and have no one aware about what's happening to them.

Since @jerielizabeth and @vgayolrs are on sabbatical, it would be great to get their views.

@jerielizabeth
Copy link
Contributor

Hi all! If this aids communication within the team, it makes sense to me. If I’ve been noticeably less present, I’ve recently changed notifications so I only get emails from GitHub when pinged directly (as in this case.) we’re a chatty bunch and my inbox was getting overwhelming :)

I’ve had a few lessons resurface while “away” and so I have kept doing that bit of editorial work. My sense is that it would be hard to switch editors on people (different expectations and all that) but deciding how to handle that should probably be in the checklist.

@acrymble
Copy link

Thanks everyone for your comments. I have added this to our Wiki: https://github.com/programminghistorian/jekyll/wiki/Checklist-for-Sabbaticals

Please add any amendments there.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants