# PyGMT Community Meeting Jun 27 (UTC 19:30)

**URL:** <https://forum.generic-mapping-tools.org/t/pygmt-community-meeting-jun-27-utc-19-30/589>\
**Category:** Governance\
**Created:** [June 26, 2020, 9:23pm UTC](https://forum.generic-mapping-tools.org/t/pygmt-community-meeting-jun-27-utc-19-30/589 "2020-06-26T21:23:29Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pwessel](https://yyz1.discourse-cdn.com/flex047/user_avatar/forum.generic-mapping-tools.org/pwessel/32/30_2.png) [@pwessel](https://forum.generic-mapping-tools.org/u/pwessel)\
**Post date:** [June 26, 2020, 10:21pm UTC](https://forum.generic-mapping-tools.org/t/pygmt-community-meeting-jun-27-utc-19-30/589/2 "2020-06-26T22:21:44Z")

</div>

Great! A few comments:

> - GMT C API - a deep rabbit hole

He-he. I have a red pill and a blue pill for you - choose wisely.

Postdoc is 3-years. Their allocation time to GMT/PyGMT should be flexible and depends on skill set. I imagine the GMT team will discuss this once we select the winner. I can imagine that person would want to do Python stuff and not be down in the bunker with me.

---

_[View the full topic](https://forum.generic-mapping-tools.org/t/pygmt-community-meeting-jun-27-utc-19-30/589)._