Meeting Minute 2021-08-17
===

###### tags: `working-group` `plugin`

:::info
- **Date:** 2021-08-17
- **Agenda**
- WG
- calendar
- Review of last weeks "next steps"
- [last week's notes](https://hackmd.io/YIf_ylQEQcu6HvarAZO5Jw)
- What should go into the metadata schema
- **Participants:**
- Nathan Clack
- Talley
- Matthias Bussonnier
- Justin Kiggins
:::

## calendar

- hackmd team page access is weird

## Last week

## What should go in the manifest:

What does nto have a parallel to VS Code:
- The existing provides DockWidgets hooks. We can look at how VS code does the view.
- An example of plugins that is affinder.
- Desired full name of the plugin (aka display name vs name & publisher where <publisher>.<name> will be a unique ID.)
- How does that interract with package name (not the import name, we likely want the the name to mathc the PyPI name).

https://www.python.org/dev/peps/pep-0423/ forthe naming.

- Versions of things that we care about
- Napari
- Manifest file format/schema
- Napari Plugin API version
- The plugin version
<!-- Discussion goes here-->

## Next steps
<!-- Action items go here -->
- [ ] consider the possibility of a "plugin API version" that is independent of napari version *and* independent of the manifest schema and napari plugin engine. This would handle something like the exact types that various functions expect/return.
- [ ] take a stab at writing a schema for reader/writer plugins, or widgets.

## Notes
<!-- Other important details discussed during the meeting can be entered here. -->

- [ ] 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)