Preparation of the final publication

[jchiquet]

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 OpenReview)

• 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 (yearmonth in format YYYYMM; use only hyphens, e.g. published-202407-legrand-wildfires)
• 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 (make sure that gh-pages is enabled for the repo ; that there exists a gh-pages branches, and that the repository is public)
• the AE set the metadata appropriately (draft: false, repos, doi, google-scholar: true; date: publication date under format MM-DD-YYYY; date-modified: last-modified.)
• the AE formats the exchanges between authors and reviewers as an Issue in the repository, following this model
• the AE adds the label "Review" to each such issue
• 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; make sure that gh-pages is enabled for the repo)
• 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 proofread (Issue closed)

• the AE informs the Editor and creates a release of the firstly published version, tagged v1.0, on GitHub
  git tag v1.0 -a -s -m "Publication v1.0"
• 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