On the right hand sidebar of the project page (towards the bottom) you'll see a Source code link. For example, let's look at the Feeds module.
To see the number of commits, you'll need to view the source code project page.
#Aquai drupal download#
If the project has an active maintainer or high download numbers (usage indicator) then you may still choose to use the module because it has the promise of community support. Low commits is not a disqualifying factor.
Understanding the quality of the module, the volume of the community around it, the activity of that community and the module’s stability establishes the risk involved in using the module. Each project has its own set of maintainers and a sub-community that uses the module, interacts through issues and contributes bug fixes and feature enhancements.
#Aquai drupal free#
They are free to download and use at your own risk. Lower Drupal competencies means you need greater community support and more stable modules.Īll modules on are open source and fall under the GPLv2 open source license. When you deploy a Drupal site into production, who is responsible for maintaining it? How long will that site live for? These types of questions shape the risk tolerances of the project. When looking to use a module from the Drupal community there are a number of factors to consider, beyond its functional use, that determine suitable quality and support for your organisation to use.