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

Setting editor availability status #683

Closed
noamross opened this issue Jul 27, 2023 · 5 comments
Closed

Setting editor availability status #683

noamross opened this issue Jul 27, 2023 · 5 comments
Assignees
Milestone

Comments

@noamross
Copy link
Contributor

noamross commented Jul 27, 2023

It would be good to have a mechanism for editors to flag vacation/busy/available status so that (a) reviewers and authors would be aware of it so as to expect a slower response, and (b) EiCs could use it to determine whether to assign something. Outside of vacation, we would have defined expectations (e.g., ~2 business day response), and for extended (>2 week) periods we could have another policy to make sure someone steps in to take over review threads if needed.

GitHub status (https://docs.github.com/en/account-and-profile/setting-up-and-managing-your-github-profile/customizing-your-profile/personalizing-your-profile#setting-a-status) might be one way to do this.

Another would be Slack statuses

@noamross
Copy link
Contributor Author

@ropensci/editors What do you think? What's the easiest way to indicate this? Mauro has made this nice automated repository that checks whether editors are active: https://github.com/maurolepore/editors . GitHub status would be the easiest way to add something like ON VACATION.

@maurolepore
Copy link
Member

Thanks Noam, I like the idea.
Also I like that the implementations you suggest are simple.
It seems to me that Slack status would allow a more granular control. I can imagine taking a vacation from my paid work but not from my rOpeSci duties or the other way around.

@maelle
Copy link
Member

maelle commented Jan 23, 2024

@noamross should your recent experiments be documented here?

@mpadge
Copy link
Member

mpadge commented Jan 23, 2024

@maelle This will all become part of the dashboard, which will include documentation of how, where, when. This issue can stay open until it's been addressed there. Thanks!

@maelle maelle added this to the 1.0.0 milestone Feb 6, 2024
@mpadge
Copy link
Member

mpadge commented Apr 11, 2024

This has now all been addressed in https://ropensci-review-tools.github.io/dashboard/editors.html, so closing now. Description of the dashboard in DevGuide will be done via #828

@mpadge mpadge closed this as completed Apr 11, 2024
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

4 participants