Meeting Minute 2021-10-27
===
###### tags: `working-group` `plugin`
:::info
- **Date:** 2021-10-27
- **Agenda**
- history
- [last week](https://hackmd.io/HUlZsBUlQIKrhFqSIp-fRA)
- [yesterday](https://hackmd.io/O62pU57wTIOTpjCGBIm6ZQ)
- meeting time
- manifest overview
- [npe2](https://github.com/tlambert03/npe2)
- [spec draft](https://hackmd.io/UK4NhwUaSpGkaqUGkx_1OA)
- **Participants:**
- Alister Burt
- Nathan Clack
- Alister Burt
- Lorenzo Gaifas
- Robert Haase
- Eric Perlman
- Nicolas Sofroniew
- Matthias Bussonnier
- Talley Lambert
- Pam Wadwha
- Gregory Lee
- Grzegorz Bokota
:::
<!-- Discussion goes here-->
Meeting times
After wed comm mtg a good time
Robert Hasse
- Menus
- not stable ordering across systems in Plugins menu
- Tools menu
- command (how, plugin)
- eg Remove Noise (Median, cupy)
- Lesson learned already: name too long
- separating lines ("Groups" in the napari proposal)
- alphabetical ordering so stable order
- command search plugin
- Search for plugins that contain a certain name, hit Arrow Up/down to select, hit Enter to run. <- very popular among Fiji folks
- hub integration, could search for commands from plugins that are not installed
- npe2 menus
- no control over top level menus (napari defines top level)
- seperators between categories of functionality (Protocol) in the menus, categories based on ontology
- Q: [Matthias] if a plugin makes a submenu how does another plugin interact?
- subgroups?
- [Grzegorz] Some plugins have system dependencies, a kind of extenstion plugin, need plugins to be able to interact with each other's menus
- [Talley] Context's may address some of these system/environment interactions
- [Allister] would be nice to get a clear list of contribution categories
- a process for adding new contribution kinds
- napari types to help define categories of plugin contributions
- buy in without napari specific types
- Variadic Generics
- https://www.python.org/dev/peps/pep-0646/
- https://github.com/napari/napari/issues/3525
- Q: default menu placement vs explicit
- [Matthias] prefer explicit and can back off of that later by adding behavior
- simple first
- [Alister] linting/tooling could suggest explicit menu placement
## Next steps
<!-- Action items go here -->
- [ ] make issue: stable order for current plugin menu
- [x] announce new meeting time: Wed 9:30a PDT (GMT-7)
## Notes
<!-- Other important details discussed during the meeting can be entered here. -->
- [x] After the meeting add the minutes to the 'working-group/plugins' folder of [napari/meeting-notes](https://github.com/napari/meeting-notes).
## Links
* [Calendar](https://calendar.google.com/calendar/u/0?cid=Y18zNXI5M2VjNnZ0cDhzbWhtN2R2NXVvdDB2NEBncm91cC5jYWxlbmRhci5nb29nbGUuY29t)
* [HackMD space](https://hackmd.io/team/napari-wg-plugin)
* [Recorded meeting notes](https://github.com/napari/meeting-notes/tree/master/2021/working-groups/plugins)