describe process of recruiting new editors for #998 - #1042
Conversation
|
For #998 |
|
@mpadge please link this PR to the issue, see https://docs.github.com/en/issues/tracking-your-work-with-issues/using-issues/linking-a-pull-request-to-an-issue |
maelle
left a comment
maelle
left a comment
There was a problem hiding this comment.
Thank you!!
Please add a news item.
| - Editorial committee members generally start by being [guest editors](#guesteditor). | ||
| - Start a private Slack channel for discussion (so that it does not have a history in the editors channel that future editors will join, which could be awkward). | ||
|
|
||
| - Ping in general editors channel to ensure all get notified of new private channel. |
There was a problem hiding this comment.
why not add them to the channel instead? they'd also get a notification.
There was a problem hiding this comment.
Just a duplicated notification that I've found helpful - people can wonder why they've been auto-added to a random channel. A direct ping adds extra information that has proven to be useful.
There was a problem hiding this comment.
Ok then this should clarify the editors have to be added to the channel.
| To search for a new editor, the Software Review Lead should: | ||
|
|
||
| ## Inviting a new editor {#inviting-a-new-editor} | ||
| - Look in the [_Community Leaderboard_ page of our editorial dashboard](https://dashboard.ropensci.org/community.html) to identify people who have contributed a lot yet not helped as editors. |
There was a problem hiding this comment.
yeah, but we don't have a formal version of that, as far as i know?
There was a problem hiding this comment.
See the bottom of https://devguide.ropensci.org/softwarereview_intro.html#editors-and-reviewers for instance. Now I see I have some debugging to do
Co-authored-by: Maëlle Salmon <maelle.salmon@yahoo.se>
2 participants
Checklist for dev guide maintainers, do not delete 😸