Repository navigation
PyGMT sprints at SciPy 2020 #433
Description
SciPy 2020 is virtual this year. However, remote sprints are still taking place on July 11–12. What if we sign up for PyGMT sprints? I'm imagining we could do something simple and tangible, such as addressing #292. It would also be a cool way to expose more folks to PyGMT.
@GenericMappingTools/python-contributors what do you think? I'd be happy to start us off by filling out the form. But I'll likely need help to prepare for this as well as assist during the sprints.
Activity
weiji14 commentedon May 19, 2020
That sounds awesome, go for it!
If you need a 'guide' for filling the form, you can refer to my old abstract at https://2019.foss4g-oceania.org/community-day, or refer to #317. Happy to share any materials or lessons learnt from that previous workshop too.
liamtoney commentedon May 25, 2020
Okay, I've filled out the form for this! I've emphasized contributions to the gallery / examples. I state that one of the goals is to introduce more folks to PyGMT.
weiji14 commentedon Jun 18, 2020
Hi @liamtoney, just checking in here to see if we need to prepare anything else beforehand? I can see that we're listed on the Sprints Schedule.
Been thinking whether we should cut a v0.1.2 release to get the documentation up to scratch (e.g. #479 (comment)) before the sprint. Also might be good to have a version that supports GMT 6.0.0 before we shift everything to GMT 6.1.0. We could set up a Zoom/Jitsi call to discuss other matters too.
liamtoney commentedon Jun 19, 2020
Yeah, I saw that they added us. I don't see any super critical need to have the release ready prior to the sprint specifically, though releases are of course a good thing. :)
Zoom would be great. Could you flick me an email please? Rightmost icon on my personal site.
weiji14 commentedon Jun 26, 2020
Cool @liamtoney, as discussed during the meeting (minutes at https://forum.generic-mapping-tools.org/t/pygmt-community-meeting-jun-27-utc-19-30/589/2), we've added you to the @GenericMappingTools/python team and you'll be a moderator on the forum too! 🎉 You can start labeling issues on Github and do all sorts of other stuff. We kinda wanted to have an induction guide as mentioned in #346 but haven't got around to it. If you feel something is weird (e.g. missing permissions), just give us a shout on that issue.
seisman commentedon Jul 11, 2020
FYI, in b74bc3e, I bumped the minimum required GMT version to 6.1.0. Some outdated baseline images are untouched, so there are still ~27 failures. These failures are currently ignored by marking them
@pytext.mark.xfail. A few tests may crash on Windows, so I also disabled the Windows builds temporarily.weiji14 commentedon Jul 11, 2020
A bit late to the game (timezones are tricky), but if there's anyone in the Asia Pacific timezone (or anywhere in the world really) looking at where to start contributing to PyGMT, have look at our issues labelled scipy-sprint, or come up with your own as @tjnewton is doing in #516!
Just a note that you're not forced to submit a PR. Opening a feature request issue is also great, and maybe someone will look at it and decide to implement it for you! Feel free to leave a comment below too if that's easier. Happy sprinting everyone 🎉
liamtoney commentedon Jul 13, 2020
Thanks to all who participated in our sprint! We had several folks learning how to use PyGMT, and lots of interest from conference attendees. Special thanks to @tjnewton for his contribution wrapping
mecaso we can plot focal mechanisms! 🎾tjnewton commentedon Jul 13, 2020
My pleasure! Thanks for you guidance.