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

The Case for a Plugin Manager #1679

blaquee opened this Issue Aug 4, 2017 · 1 comment


None yet
2 participants

blaquee commented Aug 4, 2017

Based on a Discussion from the chatroom. Some would like to see the introduction of a plugin management system. However the design concept is the challenging part.

Ideally, ease of management and moderate security is the goal here. The Plugin Manager would be a plugin itself.

Plugin Manager Goals:

  • Download Plugins from Third Party sources

  • Update Plugins

  • Load and UnLoad plugins

  • Verify authenticity of plugins (signature enforced)

Current Ideas shared on Chat:

  1. Host a Github Repository that accepts binary PR's from plugin authors. Plugin Manager would source plugins from this repo
  2. Host a JSON file that points to author submitted JSON Files that contain plugin information.

Both share their pros and cons however I'm leaning towards option 2.
Users would be liable and should know that these are third party modules from 'un'trusted sources and proceed accordingly.

Any thoughts and ideas welcome. Or someone can just code it and we can close this issue. :)

@mrexodia mrexodia added the fun label Aug 4, 2017


This comment has been minimized.

Show comment
Hide comment

mrexodia Aug 5, 2017


I started development over here.


mrexodia commented Aug 5, 2017

I started development over here.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment