-
-
Notifications
You must be signed in to change notification settings - Fork 8
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.
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
Registered Reports in Primate Neurophysiology #28
Comments
Draft vision statement:
Link to repo: https://github.com/da5nsy/Registered-Reports-in-Primate-Neurophysiology |
I tried putting my vision statement through the upgoer5 process and I'm quite happy with the result:
I've broken it up because as a single sentence it is quite a mouthful! |
Hi @da5nsy, excited to see what comes from this project! My background is in cognitive neuroscience, so slightly adjacent to your field, but we have a similar need for more RR support in our field. My colleague held a panel session on developing RR templates at the recent OHBM Open Science Room conference, which might be informative and I'll link here when the recording becomes available. Regarding your vision statement -- to be honest I think the first version is better! Personally I don't see a problem using terms like 'neurophysiologists' and 'metascientists' in your vision statement because these are your target market, and also think it's better as a single concise statement -- but just my opinion :) And finally, wanted to highlight a possible synergy between your project and mine (#5), which aims to support open science behaviours through collective action. The basic premise is that individuals (especially ECRs) might not feel comfortable adopting new behaviours due to potential costs, whether real or imagined (e.g., supervisors don't support it, it costs them time, can't publish in prestigious journals), but these costs can be mitigated if enough people act together to make the behaviour a new norm. I'd love to discuss a campaign to support RR in neurophysiology -- we could even build the campaign around the template you develop, which would mutually support the community as it grows (and provide additional pressure on journals to adopt the format). We recently started discussing a similar domain-general idea here, in case you have any feedback. |
the link is now available here, just in case you're interested :) |
Open Canvas: link |
@all-contributors please add @da5nsy for idea and content. |
I've put up a pull request to add @da5nsy! 🎉 |
Comments on Open Canvas: @da5nsy, I really like where this canvas is directing you too. I am adding a few suggestion hoping this can help in the next weeks while you develop your idea.
|
Project Lead: @da5nsy
Mentor: @ivotron
Welcome to OLS-2! This issue will be used to track your project and progress during the program. Please use this checklist over the next few weeks as you start Open Life Science program 🎉.
Week 1 (31 August - 4 September 2020): Meet your mentor!
If you're a group, each teammate should complete this assessment individually. This is here to help you set your own personal goals during the program. No need to share your results, but be ready to share your thoughts with your mentor.
Before Week 2 (7 - 11 September 2020): Cohort Call (Welcome to Open Life Science!)
Create an issue on the OLS-2 GitHub repository for your OLS work and share the link to your mentor.
Draft a brief vision statement using your goals
This lesson from the Open Leadership Training Series (OLTS) might be helpful
Leave a comment on this issue with your draft vision statement & be ready to share this on the call
Check the Syllabus for notes and connection info for all the cohort calls.
Before Week 3 (14 - 18 September 2020): Meet your mentor!
Before Week 4 (21 - 25 September 2020): Cohort Call (Tooling and roadmapping for Open projects)
Week 5 and later
README.md
file, or landing page, for your projectLICENSE.md
CODE_OF_CONDUCT.md
This issue is here to help you keep track of work as you start Open Life Science program. Please refer to the OLS-2 Syllabus for more detailed weekly notes and assignments past week 4.
The text was updated successfully, but these errors were encountered: