Max Jones

> > Just a note that this issue can be closed after the recommended structure (as used in [grdhisteq](https://github.com/GenericMappingTools/pygmt/pull/1433) and [triangulate](https://github.com/GenericMappingTools/pygmt/pull/731)) is added to the contributing guide. > > The...

I agree that the classes option is good. I have a couple further opinions about the implementation of long GMT arguments: 1. Based on this discussion, we will implement full-word...

> Yep, we should definitely have standardized aliases across all GMT wrappers. There was a lot of discussion around this in 2019/2020 on GitHub and the GMT forum (e.g. https://forum.generic-mapping-tools.org/t/standardized-human-readable-gmt-parameters-for-pygmt-matlab-julia-pyshtools-etc/77)...

This issue was mentioned in https://github.com/GenericMappingTools/pygmt/issues/1120, but it is not clear to me how this would be changed in a backwards compatible way. Does anyone have ideas for how to...

I would be pretty excited to see this in the next release, so I will get started on refactoring the tests. Here is a list of modules in `pygmt/tests/` that...

> > I would be pretty excited to see this in the next release, so I will get started on refactoring the tests. Here is a list of modules in...

Sounds good, thanks for the input. I will track that file with git and will leave this issue open for now.

I did not find a conversation that settled on this convention in a quick search of past issues (apologies if I missed this). While alphabetically by short option is easily...

> Should we add a separate section in `contributing.md` about writing the docstrings for a module (where this ordering convention would go)? I'm part-way through adding a section with general...

I ran into the following today when trying to use some data via [OPeNDAP](https://docs.xarray.dev/en/stable/user-guide/io.html#opendap). The try/except strategy in the accessor leads to a successful figure, but gmt's error messages are...