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
_______________________________________________
NumPy-Discussion mailing list
NumPy-Discussion@python.org
https://mail.python.org/mailman/listinfo/numpy-discussion
