|
| 1 | +### Title |
| 2 | +Hire a community manager |
| 3 | + |
| 4 | +### Project Team |
| 5 | +This is an open hire, to be lead by Kelle Cruz (@kelle), Erik Tollerud (@eteq), Adrian Price-Whelan (@adrn), and any others who are interested |
| 6 | + |
| 7 | +### Project Description |
| 8 | +The [community engagement coordinator position](https://www.astropy.org/team.html#Community_engagement_coordinator) is currently unfilled and there's not clear eveidence that anyone wants to fill it. While this may seem like a position that requires specialized knowledge of our community, the general position of open source community manager has a lot of history of specialist professionals who work at it - e.g. [Red Hat](https://www.redhat.com/en/blog/many-faces-community-manager), [FOSSlife](https://www.fosslife.org/what-open-source-community-manager), [The Linux Foundation](https://www.linuxfoundation.org/tools/building-leadership-in-an-open-source-community/). So this proposal aims to do an open hire drawing from this pool. |
| 9 | + |
| 10 | +Some tasks the holder of this role would take on include: |
| 11 | +* Monthly updates requested by NumFOCUS for their newsletter |
| 12 | +* Discourse, Stack Exchange, and Facebook group moderation and crossposting |
| 13 | +* Slack moderation and crossposting |
| 14 | +* Twitter post of announcements and replies to mentions |
| 15 | +* Help with Coordination Meetings |
| 16 | +* Help expanding workshops to more varied users |
| 17 | +* Help publicizing Learn Astropy resources |
| 18 | +* Coordinating website content refresh and updates with web site maintainers |
| 19 | +* Community and/or User Survey |
| 20 | +* Coordinate update to the Astropy Code of Conduct |
| 21 | +* More regular updates on a blog or the main Astropy website |
| 22 | +* New community-oriented initiatives as they come up |
| 23 | + |
| 24 | +Which of these a particular candidate takes on may depend on their background knowledge and skillset. |
| 25 | + |
| 26 | +### Selection Process |
| 27 | +Our selection process would be informed by the [resources provided by the Center for Scientific Collaboration and Community Engagement (CSCCE)](https://www.cscce.org/resources/hiring-becoming-a-community-manager/). The CSCCE hosts an active Slack workspace with over 450 members and we plan to use that community for recruiting and adverisement, in addition to posting to the AAS Job Register. |
| 28 | + |
| 29 | +Selection criteria for a hire would include: |
| 30 | +* Experience working with or in open source projects analogous to Astropy |
| 31 | +* Experience with or training on community manager work like that listed in the links above |
| 32 | +* Understanding of the goals of Astropy |
| 33 | +* Understanding of both our user and developer communities |
| 34 | + |
| 35 | + |
| 36 | +### Approximate Budget |
| 37 | +The budget has flexibility. Our minimum request is for $15,000/year to find someone to take the lead on only a few of the above listed tasks. At the high end, with $60,000/year, we could find someone to spending approximately 50% time on Astropy and to make progress on most of the tasks. |
| 38 | + |
| 39 | +### Approved Budget |
| 40 | + |
| 41 | +This project was approved for a *total* budget of $48,000. |
| 42 | + |
| 43 | +Note that — unlike the budget suggested by the proposers — that is a sum, rather than a rate. Discussion of the period of performance will follow on the implementation issue. |
0 commit comments