Actively maintained

This project is a wrapper for Boomerang, a Javascript program which "measures the performance of your website from your end user's point of view." The statistics gathered include:

• Round trip time of the page ("t_done")
• User's measured bandwidth in bytes per second ("bw")
• User's measured HTTP latency in milliseconds ("lat")
• etc.

This project consists of two modules, Boomerang and Boomerang Beacon. The Boomerang module adds Javascript to pages to send statistics to the beacon. The Boomerang Beacon module collects and stores the data. The modules are designed to be autonomous, so they can be run on separate sites. The Beacon is designed to be general purpose, so it can collect data regardless of where the "boomerangs" are coming from.

Thanks to the Exceptional Performance team at Yahoo! for releasing the Boomerang script which this module is created around.

Media: SoundCloud adds SoundCloud as a supported media provider.

This module adds an option to nodes and comments to provide an integrated dice roller. The dice roller options are based on the standards set at http://openrpg.com for dice rolling. (OpenRPG is under GNU GPL.)

Once the roll is made, there is no option for the user to go back to remove the roll from the post nor any option to modify the roll. This is to prevent tampering with results, negating the risk of cheating.

Voting Rules provides Rules integration for the VotingAPI module.

UUID Features 7.x-1.0-alpha3 fixes some HTML code that made the module completely unusable. Please update ASAP. If you're experiencing WSOD simply remove the module files completely then upload the latest version. The latest version now works with UUID 7.x-1.0-alpha3. Please report any bug you encounter in the issue queue.

Comparison with other modules with similar functionalities: #1311428: Comparison with Node export (and possibly other modules with similar functionalities)?

We need patches and reviews! Please contribute here!

Co-maintainer(s) wanted! Please contact us.

The UUID Features Integration module provides a mechanism for exporting content (nodes, taxonomy, fields) into a features module. What's that you say? You thought features was only for configuration? This module is meant to be used in the cases where certain pieces of content straddle the line between pure content and configuration.

Examples:

• There are relatively static pages (like an About Us page) that have links from your primary navigation. If these were to go missing, your client would certainly say the site is broken.
• You maintain page nodes for items like Terms of Service or Privacy Policy. These nodes appear on several sites and should always be the same.