Nice to meet you!

Mathew Lenning and Family

About Me

My name is Mathew Lenning. I am a 33 year old dreamer, a dedicated husband, father of two really crazy boys and firm believer in the power of education to change lives.

About Babel-University

I started the Babel-University project in 2010, because I wanted to create a website to help my students study English in their free time.

Little did I know that what started out as one man's mission to teach English to his Japanese students would exploded into a one man mission to provide the most dependable learning management solutions for the Joomla!® content management system.

I've always wanted to dedicate my life to something that really matters. I believe this project is the realization of that dream.

I am honored that so many have put their faith in my extensions. I could not have created Babel-University without you. Thank you for all your inspiration, feedback and support.

Mathew Lenning
Suite 3472
1100 W. Kent
Missoula, MT 59806
LinkedIn Profile

Join our newsletter


Powered by MailChimp

Education Equality Program

Equal Education Program

The success of my business is measured in the number of people who I've helped live a more fulfilling life.

That is why I’m really excited about the education equality program. This program gives schools and education organizations in developing countries access to our learning management solutions.

If your organization is working for quality and equality in education, I want to help. Please contact me to see if you qualify for a subscription fee waiver.

Versioning and Compatiblity

In order to improve communication between our supporters and the Babel-University project, we have adopted the Semantic Versioning guidelines set forth on Semver.org

Version Numbers

All of our extensions are released under a version number consisting of three parts and following the MAJOR.MINOR.PATCH format.

  1. MAJOR version changes when we make incompatible API changes
  2. MINOR version changes when we add functionality in a backwards-compatible manner
  3. PATCH version  changes when we make backwards-compatible bug fixes

Joomla Compatibility

Because we cannot directly control the development of the Joomla content management system, we cannot include Joomla compatibility information in our version numbers. Instead we list all supported Joomla versions on the extension description page. 

Backwards Compatibility

We will maintain backwards compatibility with the all supported Joomla versions throughout an extensions major releases life cycle.This means that if a 1.0.0 version of an extension supports both Joomla 2.5 (J2.5) and Joomla 3.x (J3.x), you can count on that extension continuing to support both J2.5 and J3.x until at least version 2.0.0

However it is important to note that this does not mean that Joomla compatibility will change with every major release, it just means that you don't have to worry about backwards compatibility in minor releases. In the event that Joomla compatibility does change with a major release, we will do our best to provide a migration path to help transition from the older version to the newer version with minimum data loss.

Third Party Extension Compatibility

In a perfect world every Joomla extension would work side by side without issues. Unfortunately we don't live in a perfect world, so to reduce the likely hood of Third Party Extension incompatibilities, we follow a side-effect free development policy.

Side-Effect Free Policy

That is our extensions are designed so that they do not change the Joomla environment in any way during their execution cycle. This means that there is no possibility of our extensions causing negative side-effects on other Third Party extensions, because the application environment is exactly as it would be with our extensions uninstalled.This approach drastically reduces the likelihood of compatibility issues. 

Known Issues Reporting

Unfortunately other extension developers may not follow the same policy, so there may be instances where side-effects in another extension causes issues with a Babel-U-Extension. When we learn of such incompatibilities, we will publish them on our blog under the "Known Issues" tag, provide a work around (if available) and inform the other extension's developer of the issue.

Since customer voices are often more effective at bringing about change, If you intend to use an extension with known compatibility issues along side a Babel-U-Extension, then it would help if you could contact the developer to express your desire for a resolution and a link to our known issue report.