-
Notifications
You must be signed in to change notification settings - Fork 344
Plugins
This page links to OpenVBX plugin pages for discussion of specific issues, FAQs, non-bug requests and ideas. The purpose of this chain of wiki pages is to provide a common, focused resource where developers and users can discuss, create, and improve OpenVBX plugins.
These pages are for plugin developers as well as users, and everyone is encouraged to visit, Watch, and update the pages. Plugin authors are especially encouraged to keep an eye on "their" pages, to quickly respond to comments and questions about their work. If you are not working on your plugin, or you have no intent to make specific updates, please make that known to give someone else an opportunity to volunteer. If you are planning to make code changes, please update the To Do section of the plugin page to let people know that you intend to do some work in a specific area. That may help to eliminate requests and reports.
- Plugin Ideas summarizes requests and ideas for plugins that don't yet exist.
- Plugin Development has notes by developers in addition to notes at OpenVBX.com
- Plugin MyCaption Transcriptions Now you can get your voicemails transcribed securely by human operators for a dramatic increase in quality!
- Plugin Outbound Flows Lets you call out with a flow or send messages to someone else from a flow.
- Plugin Google Analytics Track the current activity in the flow in Google Analytics.
- Plugin Subscriptions OpenVBX Subscriptions plugin adds text message marketing and auto-dialing to OpenVBX. Create opt-in subscription lists to send text updates or automated phone calls using any OpenVBX flow.
- Plugin Automatic Upgrade One click updates for OpenVBX.
- Plugin Polls Allows for phone and text message polling.
- Plugin Cookies Store, retrieve, and check a caller's cookies.
TO DO Add a lot more plugins here.
- Create a new page with title "Plugin The Name". (Do not repeat the word plugin, as in "Plugin Great Plugin".)
- Copy the source from any other plugin page and paste it as a template.
- Replace the details as required.
- Title should be same as title "Plugin The Name"
- Set the link to where the software can be downloaded.
- Change the description.
- Change the author
- Remove everything else except section headings.
- Go into Preview mode and check your work. (Mouse over links to verify accuracy.)
- After saving the page, come back to this page and add it to the index above. Note how the links are made using brackets.
When updating wiki pages, it's not mandatory but very helpful if you add your name (or a link to your GitHub provide) to content that you provide. This will help authors to follow-up with you on comments.
If you have an interesting use for a plugin, you are welcome to post in the "How this can be used" section.
Issues can be reported in Issues, Quirks, and Problems, or in the GitHub issue tracker, if the plugin is hosted here of course. If you are reporting something that's more of an irritation or a quirk, it may not be something that you want to file in the tracker. Please be sure to note whether or not a tracker item exists. Someone else may want to create a tracker item before changing code.
If you have an idea for improving the plugin, post it to Enhancement Ideas and Requests.
General questions can be asked in the Open Questions section. Once a question is answered it should be moved to the Closed Questions section. Feel free to add detail to the Closed Questions. If you have a follow-on question, please post it to Open Questions. Discussions should be taken to GetSatisfaction and resolutions to the discussions can be brought back here. If you are aware of a discussion about the plugin, please refer to it in Open and Closed Questions so that the Q&A can be put in context with other information.
Comments, Reviews, and Kudos are placed in their own section. Again, discussion should be in GetSatisfaction.
The To Do section is mainly for authors to let people know what is intended for the plugin. This is not for users to create a to-do list for developers.
Plugin authors can post their information in the Author section. This can include email address, Twitter page, GetSatisfaction ID, Skype/IM ID, websites, and/or references to other plugins or work.
If you have lengthy comments, code samples, testimonials, or anything else that's longer than a paragraph, please create a new page and link to it from the plugin page. That will help to keep the pages easy to read.
If you believe we need some new section for each plugin, or you have other comments for improving these pages, please contact Tony Gravagno.