Just to clarify: the notebook is replacing the paper, not supplementing it?
There is no requirement for a paper at this point. This is just for review of some computational work.
Would the reviewer possibly re-execute it and therefore need access to more than just the notebook (e.g., environment, dependencies, ala Binder)?
yes
Given the Github/OpenJournal approach, I assume this would be fully open peer review where all are comfortable with Git issues and PRs (ala JOSS)?
That would be one option, but maybe there are others too?
With a fully-open review process managed via Git and OpenJournal, couldn’t you just make the “repo” a Binder?
That’s the first comment in Guidelines for submitting a notebook for peer review today
Once it’s through the review process, it gets published to Zenodo, same as the JOSS software artifacts, and can easily be re-executed later or possibly integrated into the OpenJournal interface via some sort of widget.
I think this is possible - if we chose this, a next question could be what tooling would be needed to make this work