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.

Sign up for GitHub

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

Jump to bottom

Add details for MEE process #862

Open
wants to merge 9 commits into
base: main
Choose a base branch
from
Open

Add details for MEE process #862

wants to merge 9 commits into from
+59 −10

Conversation

robitalec
Copy link
Member

Adds details for MEE process in Guide for Authors and Guide for Editors

@robitalec robitalec mentioned this pull request Jan 30, 2025
Closed
@robitalec
Copy link
Member Author

Let me know how this looks @mpadge and @maelle. It's pretty simple, but I feel like the main thing that authors/editors should know is the timing for submitting to MEE (after review, before/after approval).

@maelle
Copy link
Member

maelle commented Jan 31, 2025

Thanks! I'm planning to review this on Monday.

@maelle
Copy link
Member

maelle commented Feb 3, 2025

Thank you! I like it but adding an item makes me realize this section would benefit from sub-headers, I'll add them.

@maelle
Copy link
Member

maelle commented Feb 3, 2025

@mpadge @robitalec what do you think of the splitting+re-ordering I did?

Once we agree on a version I will update the Spanish translation and Portuguese draft translation. Thank you!

@robitalec
Copy link
Member Author

This looks better to me after reorganizing it @maelle !

mpadge
mpadge approved these changes Feb 3, 2025
View reviewed changes
Copy link
Member

@mpadge mpadge left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That looks great, thanks both @robitalec and @maelle

@maelle maelle requested a review from yabellini February 3, 2025 12:34
yabellini
yabellini reviewed Feb 3, 2025
View reviewed changes
Copy link
Member

@yabellini yabellini left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is a part of the new text I don't understand in English, so I still need to finish that part. I already reviewed the rest; it looks good and is a very nice addition to the guide!
Thanks so much for writing it!

softwarereview_author.es.Rmd Outdated Show resolved Hide resolved
softwarereview_author.es.Rmd Outdated Show resolved Hide resolved
softwarereview_author.es.Rmd Outdated Show resolved Hide resolved
softwarereview_author.es.Rmd Outdated Show resolved Hide resolved
softwarereview_author.es.Rmd Outdated Show resolved Hide resolved
softwarereview_author.Rmd

- For a submission to Journal of Open-Source Software (JOSS), do not submit it to JOSS consideration until after the rOpenSci review process is over: if your package is deemed in scope by JOSS editors, only the accompanying short paper would be reviewed, (not the software that will have been extended reviewed by rOpenSci by that time). Not all rOpenSci packages will meet the criteria for JOSS.

- For a submission to Methods in Ecology and Evolution (MEE), submit it to MEE only after the rOpenSci review process is over, either before or after the package has been accepted. The review collaboration with MEE was introduced in a [blog post](https://ropensci.org/blog/2017/11/29/review-collaboration-mee/). The relevant article type for MEE is [Application](https://besjournals.onlinelibrary.wiley.com/hub/journal/2041210X/features/applicationpapers) for more details.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I do not understand this text: first, we said, "Only send the package after our review is over," and then we said, "Either before or after the package has been accepted." So when should the author send it? Does it send the package for review again, or does it have to send an article just like JOSS? It looks like It is the same as JOSS, so perhaps we could shorten this text and use it for both?

If they are not the same, I don't understand the difference.

I will wait for your changes to this text before continuing with the Spanish review.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@robitalec did we mean accepted to CRAN?

softwarereview_editor.es.Rmd Outdated Show resolved Hide resolved
@maelle @yabellini
Apply suggestions from code review
fb4e762 
Co-authored-by: Yanina Bellini Saibene <[email protected]>
@maelle
Copy link
Member

maelle commented Feb 14, 2025

Thanks @yabellini!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@yabellini yabellini yabellini left review comments

@maelle maelle maelle left review comments

@mpadge mpadge mpadge approved these changes

Assignees
No one assigned
Labels
content 📃 ro-hackathon-2025
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
4 participants
@robitalec @maelle @yabellini @mpadge