# scikit-image community meeting, 2022-02-02

Join via [Zoom](https://monash.zoom.us/j/86773951773?pwd=Njc4eThpckxvU2dFWW9VZ2NTRDFmdz09)

Present: Alex, Juan, Greg, Stéfan

## Agenda

- Moving core-dev mailing list to scientific-python.org -> please move! Or... will we move?
- E-mails to the group that also stay at discuss
- [e-mail]
- https://discuss.scientific-python.org/g/skimage-core/messages/inbox
- Deactivate Github Discussions, Issue [#6167](https://github.com/scikit-image/scikit-image/issues/6167)
- Related: add SUPPORT.md (helps point users from GitHub to appropriate support resources), PR [#6171](https://github.com/scikit-image/scikit-image/pull/6171)
- What happens to the existing one? Do they get closed, or deleted? We want to make sure we don't lose critical user info
- Alex, Juan, Stéfan, Greg: Aye
- skimage1 vs. skimage2, the verdict
- 1.0 (3–4 months), scikit-image 2.0 warns and sends people to skimage2
- `pip install -U scikit-image` gives you `scikit-image 2.0`, which warns

        Are you interested in `skimage2` instead? Otherwise pin `scikit-image < 2`

- import skimage will aim for 1.x, import skimage2 for 2.x
- NumFOCUS fee agreement
- Will try to ping Emma, and if cannot reach by end of week set up new list of signatories and re-sign
- What to do with Juan's NumFOCUS money + travel grants
- improve the benchmarking action to show webpage + plots
- Python R-tree
- Stéfan to email Lars about bandwidth

<-- We stopped here -->

- Add example of scikit-image interactive tool build using Panel and HoloViews to the docs, Issue [#6023](https://github.com/scikit-image/scikit-image/issues/6023)
- What do we need for this?
- remove skimage viewer in tutorials, PR [skimage-tutorials#55](https://github.com/scikit-image/skimage-tutorials/pull/55)
- `morphology.reconstruction` crashes python, Issue [#4078](https://github.com/scikit-image/scikit-image/issues/4078)
- API consistency: `seed` vs `random_seed` vs `sample_seed`, Issue [#5359](https://github.com/scikit-image/scikit-image/issues/5359)
- Add SUPPORT file to help users, Issue [#6058](https://github.com/scikit-image/scikit-image/issues/6058)
- skimage API categorisation into "protocols" and overall cleanup, see [this doc](https://hackmd.io/qnGRs1X1RayFxoe9yWxHVw) started by Juan and Greg
- We *must* tackle or have a backward compatible plan for metadata

## Questions

## Action items

## Items from the previous meeting(s...?)

- [ ] API questions in [#3544](https://github.com/scikit-image/scikit-image/pull/3544)
- [ ] JNI Example PR that shows how the `_` modules can be used to avoid ultra long and confusing tracebacks.
- [ ] Create issue + ~~mailing list~~ discuss.scientific-python.org post about `register_translation`.

---

After the meeting, please commit the contents of this document into the [meeting notes](https://github.com/scikit-image/meeting-notes) repo. Then clear out this document so that it can be re-used for the next meeting.