Skip to content
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

Submission process #2

Open
21 tasks done
mathurinm opened this issue Feb 9, 2024 · 0 comments
Open
21 tasks done

Submission process #2

mathurinm opened this issue Feb 9, 2024 · 0 comments

Comments

@mathurinm
Copy link
Collaborator

mathurinm commented Feb 9, 2024

Phase 1: acceptance

When the Associate Editor (AE) is satisfied with the author's answers to the reviewers comments, he/she exchanges with authors that (via the discussion tool on Scholastica)

  • authors are informed of final acceptance
  • affiliation, author-url, affiliation-url and other metadata are correctly filled in on the author git repository
  • the manuscript is formatted using the latest Computo extension
  • CI/github-action validates the reproducibility of the manuscript

The authors inform the AE upon completion of the tasks required on their side.

Phase 2: production start-up

  • the AE creates a private repository in computorg's group named published-yearmonth-first_author_last_name_manuscript_keyword, with CC-by 4 licence
  • the AE asks the editor a DOI for this publication
  • the Editor adds an entry to the in_production.bib so that the manuscript appears "in the pipeline" here https://computo.sfds.asso.fr/publications/
  • the AE makes a copy of the authors' repository (without the history: clone --depth 1) into the above repository
  • the AE, assisted by the technical team, ensure that CI works
  • the AE set the metadata appropriately (draft: false, repos, doi, google-scholar: true; date: publication-date; date-modified: last-modified.)
  • the AE formats the exchanges between authors and reviewers as an Issue in the repository, following this model
  • the AE requests validation from the reviewers for the publication of the reports and asks if reviewers want to remain anonymous or not
  • the AE completes the README.md according to this template, with appropriate badges

Phase 3: final publication

Once the above tasks are completed, then do

  • the AE turns the private repository into a public repository (could be done as soon as a DOI is available)
  • the AE invites the corresponding author to be an external collaborator to the repository with read only access
  • the AE makes an Issue asking for final proofreading by the authors (possibly with some minor additional questions), made as a pull-request on Computorg's repository

Once the manuscript is proofreaded (Issue closed)

  • the AE informs the Editor and tags the firstly published version
  • the AE archives the repository on software heritage
  • the AE add an item to the website news announcing the publication of a new article
  • the Editor moves the BibTeX entry from file "in production" to "published" on Computo website, by completing if needed
  • the Editor ensures that the usual communication about the new publication is made
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant