You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Andrew Belt 799bcfcc19 Slightly change plugin thread process. 4 years ago
manifests Update manifest for PdArray, OrangeLine 4 years ago
repos Review and update cf to version 1.1.1. #392 4 years ago
scripts Update scripts. 4 years ago
.gitignore Update Hora 4 years ago
.gitmodules Review and integrate PdArray at version 1.0.1. #606 4 years ago
README.md Slightly change plugin thread process. 4 years ago

README.md

VCV Library database

The VCV Library maintainers are responsible for curating Rack plugins into the VCV Library. Anyone is welcome to become a maintainer.

All Rack plugins are welcome assuming they

Adding your plugin to the VCV Library (for open-source plugins)

Create exactly one thread in the Issue Tracker per plugin, with a title equal to your plugin's slug (not name). Post the URL to your source code, and follow the “Pushing an update” section below. This will be your permanent communication channel with VCV Library maintainers.

A Library maintainer will handle your request and post a comment when updated.

Pushing an update

To inform us of an update to your plugin, make sure to increment the "version" in your plugin.json manifest file (e.g. from 1.2.3 to 1.2.4), and push a commit to your repository. Post a comment in your plugin's thread (we will re-open it for you) with

  • the new version
  • the commit hash (given by git log or git rev-parse HEAD). Please do not just give the name of a branch like master.

A Library maintainer will handle your request and post a comment when updated. The issue will be closed when the build is updated.

Adding your plugin to the VCV Library (for closed-source freeware and commercial plugins)

Email contact@vcvrack.com to be added to the VCV Library or sold through the VCV Store. You do not need to create a plugin thread.