Showing content from https://github.com/GenericMappingTools/pygmt/issues/677 below:
What we need for a first PyGMT paper? · Issue #677 · GenericMappingTools/pygmt · GitHub
In #653 we started discussing a possible PyGMT paper. The key question is "when should we publish our first paper?". Here are a few things we need before that can be done:
- An authorship policy. It's really important that we agree on this before doing any work a paper. See the Fatiando policy which was generated after long discussion and research into similar policies. (Done at Add authorship policy #726)
- Define a minimum viable product. What does PyGMT need to have in order to be fully usable? I'd say we're pretty close to having a usable alternative to Cartopy (if not there already). We don't necessarily need a "complete" product (when is software ever "done"?) but the package should be in usable state.
- Documentation! There is a lot of work to be done here and if we ignore the docs now and keep piling on features it will be hard to do it later. I would suggest basing the structure on the Divio system. Thinking about this now will help us define the mvp.
- Decide on a journal. I see 2 options:
- JOSS (pro = easy + free + actual code review | con = not as well known yet)
- G³ (pro = highly visible in geoscience + GMT is already published there | con = expensive + no code review)
RetroSearch is an open source project built by @garambo
| Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4