Post-acceptance TODOs for PyGMT paper

[seisman]

🎆 The good news is that the PyGMT paper is accepted in G-cubed and will be published in a few weeks. This PR tracks the remaining post-acceptance tasks and follow-up work.

Feel free to make edits and add more related tasks

Before proof

• Get the paper DOI from G-cubed 10.1029/2026GC013105

• Update CITATION.cff with final journal reference Add the citation information of the PyGMT paper to CITATION.cff and README.md #4713

• Update README citation block (preferred citation + DOI + Zenodo + journal link) Add the citation information of the PyGMT paper to CITATION.cff and README.md #4713

• Update Zenodo metadata to link to final journal version of record. [Done in the v0.18.0 record]
  

• Finalize scripts in the pygmt-paper-figure repository

• Confirm all manuscript scripts run correctly with v0.19.0 (no dev version dependencies)

• Verify all figures are fully reproducible from clean environment (fresh install test)

• Archive pygmt-paper-figure on Zenodo and obtain DOI

• For the pygmt-paper-figure archive, decide whether to cite: Zenodo concept DOI, or version-specific DOI

• Release v0.19.0 (Release PyGMT v0.19.0 #4649)

During proof

• Fix ruff to Ruff Fix package names ruff->Ruff and ghostscript->Ghostscript #4682
• In “Availability Statement”, cite PyGMT v0.19.0 (not dev or RC version)
• In "Acknowledgments", add codespell and typos used for finding common misspellings [maybe not, because they're not the de-facto standard tool for correcting typos and we may drop one of them and even switch to other tools shortly]
• Ensure all URLs (Zenodo, GitHub, documentation) are up to date and resolvable
• If possible / allowed: Update the PyGMT logo in Figure 2 to the final version (in case there were changes since the revision)
• If possible / allowed: Update the GitHub starts data in Figure 7 (have to check how much has changed since the revision) [7 more stars for GMT, 3 for PyGMT, and 3 for GMT.jl. I don't think it's worth the time to update Fig. 7]
• Double check that affiliations, names and ORCIDs are correct and consistent; especially the one of Joaquim
• In "Acknowledgments" (or somewhere else, should check the G3 guidelines), some statement regarding (not) using AI / ML tools?

Post-publication

• Announce paper in What we need for a first PyGMT paper? #677 and close the issue
• Announce paper on the GMT Forum
• Announce paper on the GMT website
• Add PyGMT Ecosystem figure (Fig. 2 in the paper) to the PyGMT Ecosystem page [Check licensing/reuse policy OR regenerate a version if needed]

[seisman]

I've received the paper DOI 10.1029/2026GC013105 from G-Cubed. Of course, it is not resolvable yet.

I manually added the paper information to Zotero, and the exported BibTeX entry is:

@article{Tian_Froehlich_Leong_Grund_Schlitzer_Jones_Uieda_Luis_2026,
  title   = {PyGMT: Bridging Python and the Generic Mapping Tools for Geospatial Visualization and Analysis},
  journal = {Geochemistry, Geophysics, Geosystems},
  volume  = {27},
  number  = {XX},
  pages   = {e2026GC013105},
  year    = {2026},
  publisher = {American Geophysical Union},
  doi     = {10.1029/2026GC013105},
  author  = {Tian, Dongdong and Fr{\"o}hlich, Yvonne and Leong, Wei Ji and Grund, Michael and Schlitzer, William and Jones, Max and Uieda, Leonardo and Luis, Joaquim F.}
}

And the citation in AGU style is:

Tian, D., Fröhlich, Y., Leong, W. J., Grund, M., Schlitzer, W., Jones, M., et al. (2026). PyGMT: Bridging Python and the Generic Mapping Tools for Geospatial Visualization and Analysis. Geochemistry, Geophysics, Geosystems, 27(XX), e2026GC013105. https://doi.org/10.1029/2026GC013105

A few notes:

• The volume is 27 for the year 2026 (see: https://agupubs.onlinelibrary.wiley.com/loi/15252027).
• The issue number is not known yet, but it's likely 7 if published online in July. It seems the AGU citation tool often omit it even when available (e.g., visit https://agupubs.onlinelibrary.wiley.com/doi/10.1029/2025GC012743 and click "Cite"), so we can likely drop it too.
• The manuscript number is the DOI with the prefix e, i.e., e2026GC013105.
• The AGU/Zotero citation style typically lists only the first few authors, but I think we should include all authors for completeness, i.e.,

Tian, D., Fröhlich, Y., Leong, W. J., Grund, M., Schlitzer, W., Jones, M., Uieda, L., Luis, J. F. (2026). PyGMT: Bridging Python and the Generic Mapping Tools for Geospatial Visualization and Analysis. Geochemistry, Geophysics, Geosystems, 27, e2026GC013105. https://doi.org/10.1029/2026GC013105

Since we now have the citation information, I think we can include it in the PyGMT v0.19.0 release, even though the DOI may not be resolvable at the time of the release.

[seisman]

Here is my planned timeline based on the current estimated publication schedule.

• July 4 (Saturday): Merge PRs Implement Figure.pygmtlogo for the PyGMT logo #4616, DOC: Add PyGMT logo to README & docs #3845, Reformat the CITATION.cff file using cffinit #4712, and Add the citation information of the PyGMT paper to CITATION.cff and README.md #4713, and finalize PR WIP: Changelog entry for v0.19.0 #4709 so that PyGMT v0.19.0 is release-ready and can be published within a few minutes.
• July 5 (Sunday): Verify that all scripts in the pygmt-paper-figures repository run successfully with the pygmt main branch (the upcoming v0.19.0).
• Before receiving the proofs (estimated July 5–12): The proofs may arrive within the next one to two weeks. During this waiting period, we can continue improving the documentation and, if needed, tweak the logo design or other non-essential changes.
• When the proofs arrive (estimated July 12–14): We will likely have only 2–3 working days to return the corrected proofs. At that point we should:
  • Release PyGMT v0.19.0 (<1 hour)
  • Perform one final verification of pygmt-paper-figures (~30 minutes)
  • Archive pygmt-paper-figures on Zenodo and update the manuscript with the final DOI (~30 minutes)
  • Complete the proof review and submit the corrections
• After submitting the corrected proofs (estimated July 14): Complete the remaining post-release tasks.
• When the paper is published online (estimated July 20): Announce PyGMT v0.19.0 together with the paper.

[seisman]

Hi @GenericMappingTools/pygmt-maintainers, I have received the proofreading and ideally will return it within 48 hours. Plan to do the release in 24 hours.