codeisscience / manifesto

Code is Science - a manifesto for anyone who deals with code in a scientific scenario
https://codeisscience.github.io/manifesto/
Creative Commons Zero v1.0 Universal
57 stars 14 forks source link

Practical implementation: similar to TOP guidelines #19

Open npscience opened 6 years ago

npscience commented 6 years ago

As a manifesto, I think it's worthwhile to aim for a future you'd like to see, and I can't really comment on those ideals (they look great to me, but I'm not experienced with this area). I wonder if some of the elements may appear overwhelming to someone in today's research world, and if it would be worthwhile taking a pragmatic view to implementation.

The Center for Open Science's TOP guidelines are an interesting method to consider: accept we're not at perfection today, measure where we are (honest and transparent), and see where to take the next small step towards implementation of ideals.

Could something similar be drawn up for this? In particular, I feel there are some useful indicators for this in @khinsen's review #7.

Example, for publishers:

These are just starting ideas, but I think it would be really useful to assess where each stakeholder (publisher, PI, developer/researcher) is at present and what is needed to advance the ideals in the manifesto in each situation.