On Tue, Apr 10, 2018 at 9:59 AM, Stefan van der Walt <stef...@berkeley.edu>
> Hi Eric,
> On Sun, 08 Apr 2018 08:02:19 -1000, Eric Firing wrote:
> > On 2018/04/07 9:19 PM, Stefan van der Walt wrote:
> > > We would love community input on identifying the best areas & issues to
> > > pay attention to,
> > What is the best way to provide this, and how will the decisions be
> > made?
> These are good questions. We are also new at this, so while we have
> some ideas on how things could work, we may have to refine the process
> along the way.
> We want to operate as openly as we can, so discussing ideas on the
> mailing list is a preferred first option. But we're also open to
> inchoate ideas and recommendations (including on how we run things on
> our end) via email. Unless instructed explicitly otherwise, those ideas
> will likely bubble up into posts here anyway.
> Since we're learning the ropes, we'd like to expose the team to a wide
> variety of ideas. Visitors to the team are most welcome---please reach
> out to me if you want to talk to us, either in person or via video chat.
> Can you help us think of good ways to learn "community priorities"?
> E.g., for GitHub issues, should we take monthly polls, count the number
> of "thumbs up"s, consider issues with the most comments, or tally the
> number of explicit mentions of team members?
Keep in mind that only a subset of the community engages on GitHub (mostly
developers who are already engaged in the numpy community).
You may want to explore other venues for this sort of feedback, e.g. a
SciPy BoF session, which will capture a different subset of the community.
> Best regards,
> NumPy-Discussion mailing list
NumPy-Discussion mailing list