PREreview: post, read, and engage with preprint reviews
Closed this issue · 2 comments
[ Project Contact ] @SamanthaHindle
[ GitHub Repo ] https://github.com/SamanthaHindle/preprint_JournalClub
[ Track ] Openness,
[ Location ] I will be in New York, but I will likely be sprinting later in the evening. Other members of the team will hopefully be sprinting from the UK and Canada
[ Coach ] @tpoisot
Description
PREreview seeks to diversify peer review in academia by crowdsourcing pre-publication feedback to improve the quality of published scientific output. To enable this diversification, we aim to train early-career researchers in how to review others’ scientific work, and help them gain recognition and entry into the peer review process. We believe that empowering early-career researchers with these skills will facilitate a cultural shift towards a more open and constructive peer review process.
Want to contribute to this project during #mozsprint?
Join us at the Global Sprint, May 10-11. Leave a comment below if you're interested in contributing to this project during #mozsprint 2018!
Note to the Project Lead 🎉
Congrats, @SamanthaHindle! This is your official project listing for the Mozilla Global Sprint 2018. To confirm your registration, please complete and check off the following:
- Complete Open Leadership 101
- Provide a GitHub repository for work and discussion on your project (in a comment or at the top of this issue)
- Create a README file in your project repository. This file should help newcomers understand what your project is, why it's important, and kinds of help you're looking for.
- Create file: LICENSE to give your project an open license, allowing for sharing and remixing.
- Turn on your Issue Tracker and create at least three issues to describe each task that you need help with and how a contributor can get started on that task.
- Create a label called
mozsprintand apply it to your issues.
Checklist for FEATURED Projects 📋
To have your project FEATURED on Mozilla Pulse, complete the following documentation. In past Sprints, well-documented featured projects have 5 times more contributions than other projects. Details about each item and more information about how to create them are on our Project Requirements Page.
- In your README, link to the Mozilla Community Participation Guidelines or write your own code of conduct.
- Create file: CONTRIBUTING.md so others know how they can contribute. If you'd like, you can remix this template
- Follow these instructions to submit your project to Mozilla Pulse.
Once all of the above is complete,
- Leave a comment with the text
This is ready to be featured on Mozilla Pulse. Your Project Coach will review this issue and approve your project if everything looks good 🎈
If you get stuck at any point, feel free to look at the requirements page and project templates or reach out to your Project Coach, @tpoisot. We're here to help you through this process.
Hi @acabunoc Can you please delete this issue as I accidentally submitted twice. Issue 271 should be kept instead. Thanks, and sorry for the extra work! 💐 💝
haha, no worries @SamanthaHindle !