BLOG POST: call for editors #401
Conversation
|
|
There was a problem hiding this comment.
Jesse - requesting changes on this one. i think i'd back out of the guest editor stuff given we really could use more full editors right now. Also i think what is important here is often people don't "see" themselves as editors - so maybe a bit more encouragement - if you aren't sure - but want to become an editor, there are pathways for you too... type of language that encourages people to apply even if they'd like support. we can even mentor a new editor. that will make it feel less daunting. we've gotten a handful of people that way who might not have otherwise applied. as this can be intimidating!
the last thing is - can you emphasize that we need reviewers right now in xxx domains ?? but we welcome anyone to apply. that should go towards the top as well.
overall this is great. i can review again and we can get this online
| * Supporting the submitting authors and reviewers in answering questions related to the review. | ||
| * Determining whether that package should be accepted into the pyOpenSci ecosystem once the review has wrapped up. | ||
|
|
||
| It's critical to our mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. We do not expect any single editor to be an expert in all of these areas! |
There was a problem hiding this comment.
| It's critical to our mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. We do not expect any single editor to be an expert in all of these areas! | |
| It's critical to our mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. | |
| IMPORTANT: We do not expect any single editor to be an expert in all of these areas! |
because people can be intimidated by this role but 9/10 times they are more than capable - like over the top capable to do the role. so i want to make sure that people know - they don't have to be expert in all of the technical stuff to run a great review.
|
|
||
| It's critical to our mission that our Editorial Board have a combined expertise in various scientific domains, technical expertise in Python packaging, awareness of the importance of documentation in package usability, and awareness of the importance of CI/test suites in order to ensure robust software development. We do not expect any single editor to be an expert in all of these areas! | ||
|
|
||
| ### Guest and Full editors |
There was a problem hiding this comment.
is this an SEO thing? because we really need full editors right now i think i might cut back on the guest stuff. that is also in the editor guidebook page that i mentioned above
i think what is important here is - if someone really wants to be an editor but needs more experience - we often get them to serve as a reviewer first. Also note that previous reviewers make great editors :)
There was a problem hiding this comment.
it isn't! the onboarding guide says that all editors have to start as Guest Editors for their first three months, or until they complete their first review, which is why I included it: https://www.pyopensci.org/software-peer-review/how-to/onboarding-guide.html
There was a problem hiding this comment.
i totally understand! yes that is how things go. people start as "guest" which really just gives them space to understand the role and decide that they want to stick around. And also if something really didn't work out it makes things easier. but typically / in reality, when people sign up they stick around (and we love for it to be that way!) I think i'm just concerned about people volunteering for a one-off review when we really need core editors added to our team! really great job pulling this together! the edits are excellent.
| ### Guest and Full editors | ||
| pyOpenSci has two primary types of editors: guest and full. Both types of editors are considered a part of the editorial board for pyOpenSci. The major difference between guest and full editors is that a guest editor may only join the board for a single review, and may be new to pyOpenSci’s review process and thus require a bit more support in their first review. | ||
|
|
||
| In addition, a new editor will be considered “guest” for the first 3 months of their tenure and/or until they have completed their first review. Once they have a completed a review they can be considered to be a full editor as deemed appropriate by the software review lead and the current editorial board. |
There was a problem hiding this comment.
i think the guest editor to get started would be a nice "note"
Note here
{: .notice }
|
oh just for reference as well - how joss does it - https://blog.joss.theoj.org/2023/10/call-for-editors |
expanded "volunteers" to "volunteer editors" Co-authored-by: Leah Wasser <leah@pyopensci.org>
accepted edits Co-authored-by: Leah Wasser <leah@pyopensci.org>
accepted edits Co-authored-by: Leah Wasser <leah@pyopensci.org>
…isi/pyopensci.github.io into 2024-05-23-call-for-editors
| Learn more about the Volunteer Editor role in our [Editor Guide](https://www.pyopensci.org/software-peer-review/how-to/editors-guide.html). | ||
| {: .notice} | ||
|
|
||
| The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks: |
There was a problem hiding this comment.
| The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks: | |
| ### About the pyOpenSci editorial board | |
| The pyOpenSci Editorial Board is comprised of a diverse group of volunteers, with each editor being responsible for the following tasks: |
|
ok if you rebase against main this will pass CI now as well. or you can just merge when you are ready (unless you'd like me to merge?) we have a LOT of blog content now. |
sooo much blog content - it's great! I'll go ahead and give it a rebase attempt, and can start promoting this (along with your amazing pycon post!) next week. |
drafted a blog post to use in the pyOpenSci campaign call for editors.