Code of Conduct
We want to take a moment to remind you that this meeting, like all project spaces is meant to be open, welcoming, diverse, inclusive, and it's important for us to have a healthy community. Like all SciPy spaces, and everyone participating in them, this meeting will follow our code of conduct. If you haven't read it yet, please take some time to do so later on as it already applies to you. For now, in short, please be kind and generous towards one another.
Agenda for April 2nd, 2025
please add your names (and github handle in parenthesis). This will make it easier to stay in touch later on issues and pull requests (PRs) 😉
This is optional since these notes will be recorded in our Github repository. If you'd like you can also paste your answer in the zoom chat 😉
Feel free to add items for discussion to this agenda
Present: Melissa, Tyler, Lucas Colley
Agenda for February 5th, 2025
Present: Melissa, Tyler
Feel free to add items for discussion to this agenda!
- Tyler Release pretty soon, no blockers
- Melissa Fold make dist into dev.py?
Agenda for January 8th, 2025
Present: Lucas, Melissa
Agenda for December 11th, 2024
please add your names (and github handle in parenthesis). This will make it easier to stay in touch later on issues and pull requests (PRs) 😉
This is optional since these notes will be recorded in our Github repository. If you'd like you can also paste your answer in the zoom chat 😉
Present: Kai Striega (@kai-striega), Tyler, Lucas (@lucascolley), Melissa, Evgeni
Feel free to add items for discussion to this agenda!
Agenda for November 13th, 2024
please add your names (and github handle in parenthesis). This will make it easier to stay in touch later on issues and pull requests (PRs) 😉
This is optional since these notes will be recorded in our Github repository. If you'd like you can also paste your answer in the zoom chat 😉
Present: Melissa (@melissawm), Ralf (@rgommers), Amine (@mathaziz), Evgeni (@ev-br)
Feel free to add items for discussion to this agenda!
- Melissa Change meeting frequency to monthly.
- Amine Interested in contributing, applied mathematics background.
- Will take a look at scipy.optimize
- Interested in Fortran->C/C++ conversion
- Ralf Items left for 1.15.0
Agenda for October 30th, 2024
Present: Tyler (@tylerjereddy)
Agenda for October 16th, 2024
Present: Melissa (@melissawm)
Agenda for October 2nd, 2024
Present: Melissa (@melissawm), Stéfan (@stefanv), Tyler Reddy (@tylerjereddy), Jake Bowhay (@j-bowhay)
-
Lucas
-
Jake Better way to document functions that support the Array API (vs not): which array types supported etc.
- Keeping the docs and what we test against in sync
- array-api-strict
- Exception may be immutability: Jax, e.g.
- Same challenge holds for dispatching to backends, such as ndimage replacements
-
Stéfan Asked about mystmd tutorial experiment, longer term vision of docs tooling
- https://github.com/numpy/numpy-tutorials/tree/mystjs
- Toolchain right now works: reproducible, testable tutorial content
- myst is sparsely maintained
- myst different from mystmd (markdown + js), new tools by Rowan Crockett & co. — separation is a bit confusing still
-
Stéfan How we can change review culture to best move PRs forward
- Fix pedantic recommendations yourself?
- Allow finishing PRs that have stalled?
- Lack of bandwidth / expertise is limiting
- Finding reviewers who understand the topic at depth can be challenging; mechanical reviews are easy
- How do we elevate real review needs to domain experts?
- X has open PR waiting on review to move on vs Y has open PR but isn't paying attention
- NumPy team gets good momentum from fortnightly triage meetings
- Sparse WG has been helpful to get a global view of
sparse (and developer) priorities
-
SPEC endorsements: SPECs 6, 7, and 8 are ready to look at
-
Melissa Moving the next Newcomers meeting by a week (Melissa will be traveling)
Agenda for September 4th, 2024
Present: Lucas (@lucascolley), Tyler (@tylerjereddy)
- Lucas, Tyler
- Lucas
xp assertions work seems to be converging- Currently at the NumFOCUS Summit (next few days)
Agenda for August 21st, 2024
Present: Lucas (@lucascolley), Melissa (@melissawm)
- Lucas Improving
xp assertions
- Lucas Dask progress
Agenda for August 7th, 2024
Present: Melissa, Tyler
- Melissa Had to leave for a conflicting work meeting, please take notes in case you come by :)
Agenda for July 24th, 2024
Present: Lucas, Jake, Ralf, Evgeni
- Lucas
- Jake
- Array API documentation
- Whilst there is a centeral list of functions that support the array API prehaps it would also be nice to have something in the docstring that indicates this?
- For functions that dispatch, clear documentation on which backends will dispatch and which will use SciPy implementation
- Array API support for generalised eigenvalue problems
Agenda for July 10th, 2024
Present: Melissa (@melissawm), Tyler (@tylerjereddy), Lucas (@lucascolley)
- Lucas
- Should we update
CODEOWNERS at some point?
- Some people may be pinged incorrectly. We're not sure exactly how to ask about it
- @lobpcg is looking for reviewers on
sparse.linalg PRs
- Dask support - went to their community meeting but it was empty (https://github.com/scipy/scipy/pull/20956)
- Melissa Blockers to move towards spin?
Agenda for June 26th, 2024
Present: nobody
Agenda for June 12th, 2024
Present: Ralf (@rgommers), Tyler (@tylerjereddy), Lucas (@lucascolley), Jake (@j-bowhay)
- rgommers Strategy for PRs that add array API support (discussion in gh-20935, gh-20946)
- try to keep refactoring in separate commits (or separate PRs) to array API conversion
- Lucas
- almost free from exams, plan to contribute regularly over the summer. Open to suggestions for priorities. I plan to implement
Dask support, tie up some loose ends from issues I have opened, and continue helping with the array API support effort. Would be nice to work on the backlog of first-time contributor PRs too.
- I've got funding from my college to travel to EuroScipy 2024 in Poland (end of August) in the summer 🎉
- rgommers Accelerate LAPACK 3.11 is in beta,
- Jake Scientific Python Summit
Agenda for May 29th, 2024
Present: Melissa (@melissawm), Shiv Katira (@shivkatira), Sebastian (github: SebastianMunozMora), Ralf Gommers (@rgommers), Rohit (@haozeke)
Agenda for May 15th, 2024
Present: Melissa (@melissawm), Tyler (@tylerjereddy)
- Melissa Release schedule
- Proposed scheduled will be kept for now, unless there are objections in the next few days.
Agenda for April 17th, 2024
Present: Melissa (@melissawm), Agriya (@agriyakhetarpal), Tyler (@tylerjereddy)
- Lucas I can't make it but here are a few things:
- I started looking at updating the core dev guide, https://github.com/scipy/scipy/pull/20199. I'm a bit out of my depth in the distributing section, if someone would like to take a look at that. We should also write down a list of code which is vendored, but not obviously so (not a git submodule), so that we know when to contribute fixes upstream rather than into SciPy (inspired by some confusion in gh-20227).
- Second part can be a follow up?
- JAX PR is pretty much just blocked on this array API issue.
- Pamphile cannot make it but: define a schedule for dropping the mailing list (read only mode)
- No big objections
- Proposal: freezing the mailing list next week (Thursday April 25).
- Melissa to send a reminder to the mailing list
- Melissa, Agriya MathJax
- When setting up JupyterLite features/converting .md files to executable notebooks, we noted MathJax is not loading properly. It looks like the MathJax path is hardcoded in MyST-NB (see https://github.com/executablebooks/MyST-NB/issues/590)
- A potential solution would be to implement a fallback logic: if we are connected to the internet, use the regular MathJax; if offline, use the scipy vendored MathJax. This means notebooks would only be broken for offline local docs builds.
- Agriya will be opening a PR for this based on the discussion and further actions can be decided upon in the PR thread
- Melissa, Agriya Proposal for Jupytext live notebooks in the docs
Agenda for April 3rd, 2024
Present: Melissa (@melissawm), Lucas (@lucascolley), Evgeni (@ev-br), Ralf (@rgommers)
- Lucas Separating docs releases from library releases?
- Lucas Problem with make dist https://github.com/scipy/scipy/issues/20379
- Melissa Moving mailing list to scientific-python discourse
- Pamphile xz backdoor:
- we need to bring more transparence and guarantee with our release process. It should be fully auditable by anyone. Trusted publisher mechanism should also be used to publish on PyPi.
- needs more security on who can actually push to pypi, otherwise any tags get automatically published as new releases
- Pamphile: if you use trusted publisher, it needs a GH environment and you can (and should) restrict the environment to only run if certain maintainers approve it. On GH you can also restrict who can push a tag if you want to restrict that part.
- we need to be carefull with the addition of new maintainers. We need, at the very least, to do real ID checks. Many orgs like Debian for instance have strong requirements.
- Ralf Work on nogil compatibility has started on NumPy (Lysandros, Nathan)
Agenda for March 20th, 2024
Present: Melissa (@melissawm), Tyler (@tylerjereddy), Jake (@j-bowhay), Lucas (@lucascolley)
- Tyler Release on track, first release candidate out, waiting on NumPy.
- Issues with openblas, but nothing urgent.
- Lucas Mailing list migration?
- Melissa reached out to Stéfan
- Lucas SciPy hackmd account?
- Melissa Contributor docs versioning (or lack thereof)
- Looking into it with Napari, but no elegant solution. Maybe pending a solution on the pydata-sphinx-theme side.
Agenda for March 6th, 2024
Present: Melissa (@melissawm), Ralf (@rgommers)
- Lucas Colley I can't make it, but all points from the previous agenda carry through, apart from the PyTorch tol issue.
- also, I've added labels to the first-time contributor project: https://github.com/orgs/scipy/projects/2/views/2, so it's much easier to see at a glance what is waiting for review. For example,
optimize and integrate have quite a few PRs which are waiting for a decision, while there is currently only 1 docs PR which isn't waiting for a decision.
- Melissa Thank you!
- rgommers We may want to touch on the next release, since creation of
maintenance/1.13.x is imminent. Anything blocking or important to merge/resolve?
- Melissa Use a SciPy hackmd space for all notes?
- discussed: sounds like a good idea
- Melissa Mailing list migration
- Melissa to investigate steps needed to set up discourse and archive existing content (probably in a new github repo for more permanent storage)
Agenda for February 21st, 2024
Present: nobody
- Lucas Colley I can't make it, but carrying over unresolved things from previous weeks:
Agenda for February 7th, 2024
Present: Lucas (@lucascolley), Yagiz (@yagizolmez)
- Yagiz A few PRs moving forward, no blockers currently
- Lucas
- @tyler I'm going to try to finish up the array API test infra PR for 1.13.0, but it may have to wait for 1.14 if I don't find the time
- Similarly for https://github.com/scipy/scipy/pull/19935
linalg array API will definitely have to wait until the summer now
- Lucas Ralf said that we should "retroactively" fix that some expired deprecations were missing in the 1.12 release notes. What does that fix consist of? (https://github.com/scipy/scipy/issues/19974)
- Lucas A reminder that there is still a circular-dependency issue with
scikit-umfpack as an optional test dependency (https://github.com/scipy/scipy/issues/19783)
Agenda for January 24th, 2024
Present: Melissa (@melissawm), Jake (@jbowhay), Tyler (@tylerjereddy), Lucas Colley (@lucascolley), Albert (@steppi)
- Lucas updates from me :)
- thanks Axel for checking through old milestones for things that have been missed!
- PyData-sphinx-theme update is finally in! Good time to think about any docs improvements now that we have current and (🤞) stable docs rendering. I can give the version-warning banners a look when I have time but I'm more than happy for someone else to have a look at that.
- Melissa for the version warning banner, we may want to check if we want to backport or find a solution similar to what numpy did before the pydata sphinx theme, for example https://numpy.org/doc/1.18/index.html
- We also may want to check plausible and see if the older versions of the docs are being visited. If not, we don't need to touch them.
- array API is slowly pushing forwards - gh-19682 should help reduce all future diffs and make testing more complete (just waiting for confirmation from Ralf w.r.t how we want to test array-likes going forwards)
- Special failure with
torch backend: https://github.com/scipy/scipy/issues/19928. Still not sure what's causing it, maybe has been fixed in a more recent PyTorch version.
- Melissa, Lucas New PyData Sphinx Theme and dark mode/colors
- Tyler NumPy 2.0 delayed
- We'll put out a minor release to compensate for that
- 1.13.0 will go out then NumPy 2.0 is on PyPI
- Albert Interactive documentation
Agenda for January 10th, 2024
Present: Melissa (@melissawm), Lucas Roberts (@rlucas7), Ralf Gommers (@rgommers), Evgeni (@ev-br)
- Lucas Colley I can't make it, but here are some updates:
- I archived the community notes for 2023 on the archive repo. Update this notebook for 2024 (or start a new notebook)?
- Melissa Thanks! I cleared up this one.
- I triaged all of the PRs in the First time contributor project: 43 waiting for author, 61 need review.
- I went through most open PRs that are > 1 month old and added
needs-work or need-decision labels. The ones without either label are generally PRs that seem uncontroversial and just need a review.
- I wasn't able to host the newcomers meeting last week as the zoom meeting wasn't open.
- Melissa I will investigate, this should not happen :(
- Lucas Roberts scipy.special, Stirling numbers of the first kind
- Might reach out to Albert to ask questions
- Evgeni Changes incoming for interpolate
Notes for December 27th, 2023
Present: Melissa (@melissawm), Jake (@j-bowhay), Lucas (@lucascolley)
-
Lucas M1 Mac + venv build issues
- I reproduced issues that someone was running into during the PyLadies sprint by following the
venv build instructions.
-
Lucas -pie being ignored build warnings
-
Lucas Directing to development version of the contributor docs from other versions
-
Lucas Incorrect test in cluster
-
Lucas DX PR: requirements/*.txt files
-
Jake https://github.com/scipy/scipy/issues/19223
Please remember to archive this file and commit it to https://github.com/scipy/archive
Useful Resources
Communication channels
How will we communicate asynchronously while working on the project?
- Developer mailing list
- We publish information which is important for contributors on this list. People from other projects might also share useful information or questions here.
- Slack (Invitation link)
-
Any changes
Be notified of any changes
-
Mention me
Be notified of mention me
-
Unsubscribe
Subscribe