Add talks/posters/workshops section to AUTHORSHIP.md

[maxrjones]

Description of the desired feature

The authorship policy added in #726 is really helpful to have for releases and future papers. I found it a bit more confusing how authorship works for conference presentations. For the AGU 2021 Abstract and the SciPy 2022 abstract that I'll submit in a few hours, I shared the drafts and asked that the PyGMT authors who are interested in being involved sign on to the abstracts. This is the same approach that @weiji14 took for EGU 2022. My question is whether it's worth adding recommendations for these types of presentations to AUTHORSHIP.md. I think the goals would be to help future developers who haven't presented on software projects before and to make it clear that we would welcome anyone teaching PyGMT without needing to involve all the PyGMT authors.

[seisman]

I think the goals would be to help future developers who haven't presented on software projects before and to make it clear that we would welcome anyone teaching PyGMT without needing to involve all the PyGMT authors.

I'm not sure about this "we would welcome anyone teaching PyGMT without needing to involve all the PyGMT authors". It sounds weird that someone who is not a "PyGMT author" gives a talk about PyGMT.

[maxrjones]

I think the goals would be to help future developers who haven't presented on software projects before and to make it clear that we would welcome anyone teaching PyGMT without needing to involve all the PyGMT authors.

I'm not sure about this "we would welcome anyone teaching PyGMT without needing to involve all the PyGMT authors". It sounds weird that someone who is not a "PyGMT author" gives a talk about PyGMT.

I was more imagining tutorials rather than talks for the teaching PyGMT section. I don't really understand the motivation to limit teaching PyGMT to authors of the library. For example, the Carpentries model is really successful for broadening use of techniques and software without such a restriction. We've specifically proposed emulating their model on the GMT side.

I apologize for accidentally editing your comment - I've corrected in back to the original statement.

[seisman]

I was more imagining tutorials rather than talks for the teaching PyGMT section. I don't really understand the motivation to limit teaching PyGMT to authors of the library.

I agree. Everyone is welcome to teach PyGMT.

[seisman]

For the AGU 2021 Abstract and the SciPy 2022 abstract that I'll submit in a few hours, I shared the drafts and asked that the PyGMT authors who are interested in being involved sign on to the abstracts. This is the same approach that @weiji14 took for EGU 2022.

We have followed similar process for the AGU24 PyGMT talk and GMT/PyGMT workshop, which seems work well. So I feel we can document it in the AUTHORSHIP.md.