What Is the Proposal of Value of the Code Review in Open LMS? Why I Cannot Add All the Moodle Community Plugins That I Want?
These are frequent questions from our customers about plugins, and I would like to open a conversation about it.
In Open LMS, we are working on continuous improvement to our customer experience, and we are interested in keeping the growth of the ecosystem having additional solutions. However, we need to do it with responsibility, making sure that the plugins are secure, offer excellent performance, and could be maintained in the long term, which allows us to provide a sustainable solution and achieve the Service Levels Agreements to our customers.
A few key concepts:
Stability: One of our essential commitments with our customers is the Service Level Agreement (SLA), from the security assurance up to the performance for users. Offer 99.9% of availability in the system (Lees than 8 hours and 46 minutes per year of downtime) and 100% of concurrence for the contracted users, is a huge challenge if we also consider the growth of the system with new features and integrations.
Moodle community: One of the best things about Moodle is the great community around it, thousands of instructors and academics, and hundreds of developers contributing around the world solving issues and adding new plugins only with the intention of help is almost magical. The community implemented a lot of great functionalities even added to the Moodle core. Though not all the Moodle community plugins follow the Moodle alignments, and in some cases, could compromise the stability of the LMS, security, or even the information integrity.
Ecosystem and integrations: There are a lot of solutions that contribute to the virtual educational ecosystem. Solutions for anti-plagiarism, proctoring, web conferencing, business intelligence, among others, are part of a big picture, where each company or institution can select the best fit for their specific needs. These solutions can be integrated using LTI or Moodle plugins.
So what is the proposal of value for the Code Review?
The Code review has the propose to ensure the quality of the plugins and, inherently, the stability of our customers’ environments in the long term. However, we aim to improve the process with three current initiatives:
- A new plugin Matrix: To be transparent with our customers, we are working in a new Matrix with the plugin versions installed, type of plugins, the fee (if applicable) for the annual support and maintenance, and eventually the number of customers using it.
- Code review semi-automation: We are using tools that help us with the Code review and increase the revision speed with less manual effort.
- Cost-effectiveness: We are focusing the Code Review service to be sustainable instead of a profitable solution since the value of having more plugins with good quality is more relevant than upset customers.
We will be able also to decrease the annual maintenance fee of plugins based on the number of customers using it. For example, if your institution is paying 2k USD annually for plugin maintenance, and the number of customers using it increase, we will decrease the fee, or even remove it in your renewal, depending on specific rules that we are setting down. We will make these decisions considering the principle of being sustainable instead of profitable with the Code Review.
In the last months, we achieved the possibility to reduce the pricing of Code Review, around 40% because of these initiatives, and reduce the Code review time around 25%. Our main objective is automatizing the process as much as possible.
Let me know your insights and comments, your feedback makes us better to improve your experience with Open LMS.
Germán from Open LMS Team.