dask / dask/community

Dask community manager

Open
#131 7 comments 1 reaction 0 assignees View on GitHub
Dominant language
No language data
Stars
25
Forks
3
PR merge metrics
No merged PRs in 30d

Description

At this month's Dask community meeting, @mrocklin brought up the topic of hiring a Dask community manager. This would be a semi-technical role to track the issue tracker, curate other systems like Slack/Discourse, engage with developers, organize blog posts, and more.

Overall there was general interest in such a position existing, though there was some discussion on whether we should hire this position through a company (e.g. Coiled, Anaconda, etc.) or through NumFOCUS. The main takeaway being it's easier from an administrative standpoint to hire through a company, while hiring through NumFOCUS might look better from an OSS community perspective.

The relevant section from the meeting notes are copied below. Opening this issue so we can continue the discussion.

Community meeting notes:

Dask community manager (Matt)
- Matt would like to hire someone to curate the Dask community. This would be a semi-technical person to track the issue tracker, curate other systems like Slack/Discourse, find developers who would be good to invite, organize blogposts, and so on
- We can either hire this person at Coiled, or through Dask/NumFOCUS.
- Tom: Scikit-Learn tried this in the last six months or so. Probably through Inria (https://scikit-learn.fondation-inria.fr/people/)
- Ben: PyPI might also have something similar. Big +1
- Mike: +1
- Ian: Jupyter has tried to hire project managers. Not exactly the same. It’s hard to find someone with the right skillset.
- Eric: Try pinging Scopatz. He did something similar at Quansight
- NumFOCUS vs Corporate infrastructure
- Julia: management burden doesn’t need to rely on Matt in particular.
- Matt: there is administrative burden

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.