Other dev teams have expressed interest in using our plugin manager in their ecosystem. To that end, we offered to provide a plugin-manager UI that is uncoupled from napari as much as possible. The end goal would be a napari-plugin-manager that depends and extends a hypothetical, application agnostic plugin-manager-dialog (name tbd).
To do:
These will become their own items as needed
[ ] Investigate coupled areas and design API for plugin-manager-dialog
[ ] Refactor napari-plugin-manager into two packages (still in the same repo) following the design proposed above. These two steps can happen iteratively (implementation informs design and viceversa)
[ ] Decide maintenance and release model: two repositories, fully independent? One repository, coupled releases? Single repo but uncoupled releases?
Other dev teams have expressed interest in using our plugin manager in their ecosystem. To that end, we offered to provide a plugin-manager UI that is uncoupled from napari as much as possible. The end goal would be a
napari-plugin-managerthat depends and extends a hypothetical, application agnosticplugin-manager-dialog(name tbd).To do:
plugin-manager-dialognapari-plugin-managerinto two packages (still in the same repo) following the design proposed above. These two steps can happen iteratively (implementation informs design and viceversa)