Clarify roles for guest editor recruitment

[noamross]

A few lines specifying what the Software Review Lead and Editor in Chief do in the case of bringing on a guest editor.

[noamross]

Also make sure EiC has appropriate permissions needed to onboard new and guest editors. (@adamhsparks, let's track missing permissions/steps here)

[maelle]

or, a way to request staff members to do so on their behalf. Less bureaucratic work for volunteers :smile_cat:

[maelle]

• Create a private slack channel named #guest-editor-<package-name>
• Invite editors to it
• Get name recs from archived similar slack channel
• After a decision has been reached and a guest editor has accepted, archive the channel

[maelle]

@mpadge could I assign this issue to you?

[maelle]

Have you tackled this?

[mpadge]

I think this is now all covered in #976. The only things that are not covered there are these comments by @maelle:

• Create a private slack channel named #guest-editor-<package-name>

  • Invite editors to it

  • Get name recs from archived similar slack channel

  • After a decision has been reached and a guest editor has accepted, archive the channel

Because I think that is more what we do for regular editor recruitment, in which case it's all documented anyway. Guest editor recruitment is more informal. That said, setting up a private channel like that would be the only way for editors to freely and privately express any concerns. Current docs offer no mode for that kind of communication. Thoughts @maelle @noamross ?

[maelle]

Well without surprise I think that we should recommend such a channel for guest editor recruitment too.

[mpadge]

Done via commit above. That will auto-close this issue once https://github.com/ropensci/dev_guide/pull/976 is merged.

[maelle]

Thank you! I have added the issue linking through the PR's first comment because it makes the PR appear in the issues list and also in the sidebar in the issue:

Much easier for triage. 😸