Navigation Menu

Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Differentiate different type of extensions in extensions manager: Concept of channel #2334

Open
slicerbot opened this issue Mar 12, 2020 · 1 comment
Open

Differentiate different type of extensions in extensions manager: Concept of channel #2334

slicerbot opened this issue Mar 12, 2020 · 1 comment
Milestone
Backlog

Comments

@slicerbot
Copy link
Collaborator

This issue was created automatically from an original Mantis Issue. Further discussion may take place here.
@slicerbot slicerbot added this to the Slicer 5.1.0 milestone Mar 12, 2020
@jcfr jcfr changed the title Differentiate different type of extenions in extension manager: Concept of channel Differentiate different type of extensions in extensions manager: Concept of channel May 20, 2022
@jamesobutler
Copy link
Contributor

Currently, the following types of extension are visible for the end user:

  • Extension officially build by the factory:
    • For end user
    • Testing
  • Extension submitted using "ExperimentalUpload"

It should be possible to selectively display these extensions in the manager. By default only extensions made for end user should be visible.

Are extensions uploaded by experimental (aka non-factory) build machines actually available in the extensions manager for download? Anyone could do this? Is there a security concern related to this type of upload and distribution?

@lassoan lassoan modified the milestones: Slicer 5.1, Backlog Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Milestone
Backlog
Development

No branches or pull requests
3 participants
@lassoan @slicerbot @jamesobutler