-
Notifications
You must be signed in to change notification settings - Fork 32
Open
Labels
elife-sprint-2020Issue opened as part of the 2020 eLife SprintIssue opened as part of the 2020 eLife Sprintnon-code-taskGreat task if you like open source but don't write code.Great task if you like open source but don't write code.quiet-time-suitable-taskelife sprint task suitable even if no project leads are aroundelife sprint task suitable even if no project leads are around
Description
Many journals say they require open source code but it isn't always checked by reviewers or enforced by editors.
How does one prove whether or not journals tend to check these things? Selections of recent articles that do/don't comply? Other? How does one model this in a database in a quantifiable way?
Please leave a comment on this issue if you have ideas for how to handle this.
This issue is part of the 2020 eLife Innovation Sprint. For more info about this project and the sprint, or to get help, please see the Code Is Science eLife Sprint Plan
Metadata
Metadata
Assignees
Labels
elife-sprint-2020Issue opened as part of the 2020 eLife SprintIssue opened as part of the 2020 eLife Sprintnon-code-taskGreat task if you like open source but don't write code.Great task if you like open source but don't write code.quiet-time-suitable-taskelife sprint task suitable even if no project leads are aroundelife sprint task suitable even if no project leads are around