Since we have no officially funded extension reviewers, some extensions sit in the PR queue waiting for us to review and merge them. This isn't good for contributors, since they often hope to have their extensions published for a journal submission or conference deadline. It's not good for users either, because it means they don't have an easy way to test extensions until they are approved for use.
This is particularly problematic for pure python extension, which are technically very easy to install and use without even restarting Slicer, but our mechanism are currently set up to handle full C++ extensions.
I'd like to see a feature in Slicer that would show the current PRs and indicate if they are pure python and available for easy testing. If so, I'd like a button to install them.
Also, if the feature detects that I'm running a locally built slicer, it should have a button to check out and build the extension and load it for testing.
This could reuse the existing Extension Manager infrastructure or it could be something simpler that just uses Qt since it's mostly aimed at slicer maintainers.
Since we have no officially funded extension reviewers, some extensions sit in the PR queue waiting for us to review and merge them. This isn't good for contributors, since they often hope to have their extensions published for a journal submission or conference deadline. It's not good for users either, because it means they don't have an easy way to test extensions until they are approved for use.
This is particularly problematic for pure python extension, which are technically very easy to install and use without even restarting Slicer, but our mechanism are currently set up to handle full C++ extensions.
I'd like to see a feature in Slicer that would show the current PRs and indicate if they are pure python and available for easy testing. If so, I'd like a button to install them.
Also, if the feature detects that I'm running a locally built slicer, it should have a button to check out and build the extension and load it for testing.
This could reuse the existing Extension Manager infrastructure or it could be something simpler that just uses Qt since it's mostly aimed at slicer maintainers.