Skip to content

define review process #2

Description

@timm
  • open review
  • fast review
    - papers submitted by the first day of month N will have feedback by first day on month N+1, if not sooner
    • so submission size short: 10 pages content + 2 pages refs)
  • debate-oriented
    - after some initial private reflections, authors and reviewers can discuss, at length,
    useful ways to improve a paper
  • papers are never rejected
    - default status = "accept after changes"
    - but...
    - only some papers ever move to "accept"
    - after a year with no activity, papers will be moved to "inactive"
  • open source
    • built using free, readily available tools (so anyone can fork their own journal if they do not like ours)
  • overlay journal (papers stored in arxiv.org, this journal aims to certify some percent of them as "most worthy"

how's this for a rpocess

initial

  1. post to arxiv.org (not blinded)
  2. fill in a google form with that abstract title, url

then

  1. create a new issue in github, assign reviewers (reviewer use
    anonymous git ids; authors told that anything them post BEFORE the
    editor labels with this "rebuttall period" will be DELETED and IGNORED
  2. reviewers review. reviewers list 2-3 things which, of changed,
    would alter their view of the paper
  3. a preliminary decision is made authors get to look on, in silent

debate

  1. "rebuttal period" starts, issue assigned to author, author asked if
    they want to comment (lots of back and forwards) OR if they want to
    revise arxiv with a version that addresses reviewers "change points"
  2. reviewer told they should not reply to authors UNLESS it is about
    something that could change their decision

decide

  1. "rebuttal period" ends. editors may change decision. or not

update

  1. authors may offer a substative change, in which chase they
    - update arxiv
    - post a github reply to reviewer comments

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions