Blackboard Open LMS Approved Plugin Program (MAP)

Document created by scott.hurrey on Dec 3, 2015Last modified by mlakin on Apr 8, 2019
Version 47Show Document
  • View in full screen mode

Blackboard Open LMS is committed to providing its clients with everything they need. As an open-source SaaS provider, we have the opportunity to enhance our Blackboard Open LMS platform through modular code updates and third-party plugin integrations. We are committed to ensuring the security, stability, and performance of our Blackboard Open LMS platform for all clients. That’s why we want you on the Blackboard Open LMS MAP.


What is the Blackboard Open LMS Approved Plugin (MAP) Program?

The MAP Program is managed by our Client Development team to oversee plugins added to the Blackboard Open LMS codebase from our community or vendor partners. To join the MAP program and add a plugin to the Blackboard Open LMS codebase requires a Statement of Work (SOW) for a Code Review, plus Annual Support and Maintenance to continue in the program.  Once added, clients can request to enable any approved plugin listed on our Blackboard Open LMS Plugin Matrix


Code Review Process

      • Blackboard Open LMS performs code reviews of all code received from an outside party. If you wish to submit code, integrate a 3rd party tool, or integrate a Moodle plugin, the code must first be submitted to the MAP Program and pass a code review process. Download a copy of the code review guide.
      • GDPR Compliance - All plugins must comply with the requirements specified in this document.
      • If you are developing a Moodle plugin, download and read the Blackboard Open LMS best practices and code review guidelines to ensure that your code complies. For more information, download the complete code review process guide.
      • Note that starting with Blackboard Open LMS 3.2 release requires PHP 7.1. Plugins must be compatible with that version of PHP.
      • Once we receive your submission, our Blackboard Open LMS Client Development team estimates the effort to review the code. They will then deliver a statement of work (SOW). Code review estimates are based on the length, complexity, and quality of the code. Once a signed SOW is in place, the Blackboard Open LMS team will review the code and determine whether it performs sufficiently within our hosted installation and meets our code quality standards. We add code that passes review to our codebase at the next Blackboard Open LMS release. If we do not pass your code, we will provide a detailed summary indicating the changes to make to assure its inclusion.


Annual Support & Maintenance

      • Blackboard reviews all plugins included in the Open LMS codebase to ensure issues are not introduced for our client base. 
      • When an issue is identified with a plugin, the plugin maintainer is provided information of fixes required.  An updated plugin should be submitted for review and inclusion in the next Blackboard Open LMS release.
      • Plugin maintainers can submit an updated plugin by submitting a support case through the Behind the Blackboard portal.


Release Dates and Code Submission Due Dates

Blackboard Open LMS releases two major releases and smaller maintenance pack releases throughout the year. To include your code requests in an upcoming scheduled release, you must submit your code at least 2 months prior to the desired release date. Release dates are listed on the Blackboard Open LMS Community Page.


You can look at our Plugin Matrix. It shows plugins currently available through the MAP Program. For more information refer to the plug-in matrix.

Who Supports What?

We support various plugins to various levels of support. We use the following support levels.


Support Levels

      • Full Support
      • Moodle Core Plugin Support
      • Hosted Components Support and Channel Partner Support
      • Blackboard Open LMS Maintained Vendor Support
      • Community Plugin Support and Vendor Plugin Support


Support levels available for each approved plug-in are listed on our plugin matrix. (To see the support levels, click the link on the right, or scroll to the bottom of the page.)


Contacting Support

Reference the MAP Support Case Process