You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Based on napari/napari#6693, I think we should (a) provide npe2 tags to mark a plugin as abandoned/archive/inactive, and (b) have a way to override this on the hub/npe2api side, in case e.g. maintainers become completely unresponsive. This could be done through maintenance of a "patch file" that could override plugin details, much in the same way that conda-forge recipes are able to patch projects before building them.
Obviously, we would have to be very judicious in using this, but I think that any concerns there can be managed (e.g. through an easy appeals process in case a project is inaccurately marked as inactive).
Then the hub would not show inactive plugins, of which there's bound to be quite a few over time.
The text was updated successfully, but these errors were encountered:
Based on napari/napari#6693, I think we should (a) provide npe2 tags to mark a plugin as abandoned/archive/inactive, and (b) have a way to override this on the hub/npe2api side, in case e.g. maintainers become completely unresponsive. This could be done through maintenance of a "patch file" that could override plugin details, much in the same way that conda-forge recipes are able to patch projects before building them.
Obviously, we would have to be very judicious in using this, but I think that any concerns there can be managed (e.g. through an easy appeals process in case a project is inaccurately marked as inactive).
Then the hub would not show inactive plugins, of which there's bound to be quite a few over time.
The text was updated successfully, but these errors were encountered: