# Managing core and contributed Kaleidoscope plugins

**URL:** <https://community.keyboard.io/t/managing-core-and-contributed-kaleidoscope-plugins/408>\
**Category:** Programming\
**Created:** [October 11, 2017, 12:44am UTC](https://community.keyboard.io/t/managing-core-and-contributed-kaleidoscope-plugins/408 "2017-10-11T00:44:54Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![noseglasses](https://yyz1.discourse-cdn.com/flex031/user_avatar/community.keyboard.io/noseglasses/32/429_2.png) [@noseglasses](https://community.keyboard.io/u/noseglasses)\
**Post date:** [November 19, 2017, 12:48pm UTC](https://community.keyboard.io/t/managing-core-and-contributed-kaleidoscope-plugins/408/26 "2017-11-19T12:48:47Z")

</div>

I started a new topic

> [@User plugin database](https://community.keyboard.io/t/user-plugin-database/777):
>
> Lately there has been some discussion in the forum about a collection/database/installer of/for user plugins. I am pondering for a while now on how that could be done and I am interested to discuss the matter with you. Let’s start with the information I would regard important about a user plugin: name description required/supported Kaleidoscope version git URL current maintainer (directions for issue reports, PRs, etc.) dependencies (other plugins) compatibilities (can replace other plugins) …

---

_[View the full topic](https://community.keyboard.io/t/managing-core-and-contributed-kaleidoscope-plugins/408)._