On Fri, 06 Apr 2018 07:42:34 -0600, Charles R Harris wrote:

On Fri, Apr 6, 2018 at 12:08 AM, Stefan van der Walt wrote:

...

We are very excited about this opportunity to develop NumPy further, together with the NumPy community, and look forward to making in-person introductions at SciPy2018 in July.

It begins ... :) Congratulations and welcome to Matti and Tyler. I expect the first couple of days will be spent dealing with organizational details. What is first on the agenda after that?

On a high level, we have the following focuses: - To support the community by providing developer time to do code review, triage issues, fix bugs, help with releases, implement infrastructure (e.g., improve benchmarking, inter-package testing, project analytics), etc. The first work done will be mainly in this category. - To solve medium- and large-scale issues through the design and implementation of community-approved NEPs. This might include items such as duck arrays, parameterized dtypes, and missing value support. - To provide logistical (and some financial) support for the organization of NumPy developer meetings, coding sprints, sabbaticals, technical talks, and similar community-building activities. We started with the recent NEP writing sprint; this is to be followed by an Airspeed Velocity sprint with Mike Droettboom at BIDS around mid-June, and a NumPy developer meeting at SciPy2018 on July 14–15. We would love community input on identifying the best areas & issues to pay attention to, and I invite developers who want to meet with the team at Berkeley to contact me. Best regards, Stéfan

On 08/04/18 21:02, 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,

Stefan,

What is the best way to provide this, and how will the decisions be made?

Eric _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion

Hi. I feel very lucky to be able to dedicate the next phase of my career to working on NumPy. Even though BIDS has hired me, I view myself as working for the community, in an open and transparent way. In thinking about how to help make NumPy contributors more productive, we laid out these tasks: - triage open issues and pull requests, picking up some of the long-standing issues and trying to resolve them - help with code review - review and suggest improvements to the NumPy documentation - if needed, help with releases and infrastructure maintenance tasks Down the road, the next level of things would be - setting up a benchmark site like speed.python.org - add more downstream package testing to the NumPy CI so we can verify that new releases work with packages such as scipy, scikit-learn, astropy To document my work, I have set up a wikihttps://github.com/mattip/numpy/wiki that lists some longer-term tasks and ideas. I look forward to meeting and working with Tyler as well as SciPy2018 where there will be both a BOF meeting to discuss NumPy and a two-day sprint. BIDS is ultimately responsible to the funders to make sure my work achieves the goals Stefan laid out, but I am going to try to be as responsive as possible to any input from the wider community, either directly (mattip on github and #numpy on IRC), via email, or this mailing list. Matti

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? Best regards, Stéfan

On Tue, 10 Apr 2018 10:03:06 -0700, Nathan Goldbaum wrote:

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.

Thanks for the suggestion, Nathan. We are coordinating with SciPy2018 to have both a BoF and sprint at the end of the conference. On Tue, 10 Apr 2018 18:05:14 +0100, Matthew Brett wrote:

How about weekly open developer hangouts, recorded, to keep it all public?

Thanks for that idea, Matthew. While we are ramping up, there's a lot of noise in sorting things out. So how about we do dedicated monthly hangouts, where everyone can weigh in on the discussion, and where the signal-to-noise ratio is higher for interested parties? We are tracking all work items here on Trello: https://trello.com/b/Azg4fYZH/numpy-at-bids (Of course, a lot happens directly on NumPy issues too, but this board is for publicly tracking "work to support the work"). Best regards, Stéfan

Hi Matthew, On Wed, 18 Apr 2018 16:42:49 +0100, Matthew Brett wrote:

Hum - I see the Trello board is for bite- to meal- size practical issues, but not for the general process of how to engage the community in guiding the the project - is that fair?

That's correct; it's just another window onto local discussions / planning.

I was thinking about the engage community part, because it seems to me it would be good to spend time on that first, and if it was me, I think I'd go for more regular public meetings / discussions at this stage rather than less.

Right, so what do you think of the suggested monthly developer meeting, to start off with. Why don't we try it and see how much interest there is? Best regards, Stéfan

Yo, How about weekly open developer hangouts, recorded, to keep it all public? Cheers, Matthew On Tue, Apr 10, 2018 at 5:59 PM, Stefan van der Walt wrote:

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?

Best regards, Stéfan _______________________________________________ NumPy-Discussion mailing list NumPy-Discussion@python.org https://mail.python.org/mailman/listinfo/numpy-discussion