-
Notifications
You must be signed in to change notification settings - Fork 219
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Outreachy remote interships for supporting diversity #715
Comments
This program looks great. I did a bit more research into the structure and this is my interpretation of the information on the Outreachy site. In order to mentor an intern, we would need to be become part of an outreachy community or start a new community. Starting a community seems like the more likely path forward, in which case we would need to provide funding for at least one intern ($6,500 USD). So, perhaps another action item is to pursue funding opportunities to support an intern and become a community on the September timeline. |
Ah yes, good spotting, Do you think we could tie this in with the NASA proposal somehow (i.e. use part of that grant to fund an Outreachy intern)? The intern doesn't have to be PyGMT specific, we could have her/him do core GMT stuff too. Might be a discussion point for the GMT community meeting tomorrow. Either way, this probably does need to get pushed out to September. |
We didn't put funding for an intern in the budget. We could also discuss whether it could tie in with the active NSF grant, should I add this to the agenda for tomorrow? |
Yep, please add it to the meeting agenda 😄 |
Following up about the conversation from the community meeting and @PaulWessel's question, here's some information about steps from the Outreachy website:
|
Cool, this checklist makes things much clearer! I need to read up more on the Outreachy Participation rules to understand the community-coordinator/mentor/intern relationship, seems very complicated. But happy to put my hand up to be 1 of the 2 mentors, and contribute to the funding application writing (need to start learning how the real world works). P.S. Since this thread might get long, should we move this to the forum or https://github.com/GenericMappingTools/gmt/discussions (since Outreachy doesn't have to be strictly for PyGMT)? Once we get the funding application/outreachy community sorted, we can then put an advertisement post on the forum or social media to find an intern. |
Probably not going to make the Aug 2021 round. Not that we've forgotten this though! An ESWN workshop will be held next week to train up new devs (see https://github.com/GenericMappingTools/2021-eswn-pygmt-workshop), and we are tentatively thinking of a workshop for 🌍 EGU22 (see https://forum.generic-mapping-tools.org/t/egu-2022-short-course-proposal/1948). There is also work going on by the GMT team behind the scenes to get some big funding (which would include supporting Outreachy interns), and I'm hopeful of getting some funding for more open source work. So stay tuned in 2022 😁 |
Description of the desired feature
Something to think about for proactively attracting new contributors - Outreachy is a remote internship program for supporting diversity in open source and free software. Similar to Google Summer of Code but more targeted at under-represented groups.
Action points
For community leaders @GenericMappingTools/python: We should try and put in a funding application by Feb 2021 for the mid-2021 round, or Sep 2021 for the end-2021 round (see https://www.outreachy.org/outreachy-december-2020-internship-round/ as a past template). Oh, and someone needs to volunteer to be a mentor 🙂
For interested intern applicants reading this: Let us know down in this post (or via email/social media) on what you would be interested to work on (e.g. documentation/tutorials/new features/workshops/etc).
Timeline
Follow up of #672 and inspired by @leouieda's comment in #677 (comment)_.
Are you willing to help implement and maintain this feature? Yes, but might need some help with writing the grant application
The text was updated successfully, but these errors were encountered: