dev_guide icon indicating copy to clipboard operation
dev_guide copied to clipboard

Revise Guide for Editors Chapter

Open mpadge opened this issue 2 years ago • 3 comments

Beyond #486, the chapter could do with a restructure. In particular:

  • [ ] Ensure chapter follows actual typical workflow, so EiC first, then editor (plus further considerations below)
  • [ ] Revise current "out-of-scope" primary sub-section to make part of EiC responsiblities
  • [ ] Expand that sub-section to consider other aspects of general question of fit or not, including aspects such as "thin wrappers" (#478), and explicitly describing/demonstrating how the statisical summary can be used to judge whether packages may not have enough code, functions, whatever to be worth reviewing.
  • [ ] Move current "Answering reviewers' questions primary sub-section within broader "Handling Editors" sub-section
  • [ ] Rename "Handling Editors Checklist" primary sub-section to something more general ("Handling Editors Responibilities")
  • [ ] Maybe separate Handling Editor sub-section into several distinct sub-sections (Upon Submission; Finding and Assigning Reviews; Managing the Review Process).

Any initial thoughts @maelle @noamross?

mpadge avatar Jun 30 '22 11:06 mpadge

Thank you!!

Does it mean we should assign #478 to you so you might handle both issues in a single PR?

maelle avatar Jul 04 '22 14:07 maelle

All changes sound good to me.

maelle avatar Jul 04 '22 14:07 maelle

@mpadge ready to make a PR for this? I'd then run babeldown::deepl_update() :grin:

maelle avatar Dec 12 '23 11:12 maelle