This is Fred. I'm one of the developers of BigBlueButton.
I wrote the moodle activity module for Moodle 1.9 and 2.0 from Blindside Networks. We wanted to ensure there was a high-quality integration of BigBlueButton with Moodle. Blindside Networks started the BigBlueButton project in 2007.
As a bit of background, we've also written integrations for WordPress and Joomal. We're also working on an integration of BigBlueButton with Drupal 7. We've gotten very good over the years at integrating BigBlueButton into other products. We also host these integrations on our site at Blindside Networks and on GitHub at
We thought about enhancing the module from Dual Code last year, but their activity module has clear messaging to promote DualCode's hosting of BigBlueButton. There's nothing wrong with that -- compaines that use open source need to make a living -- but we didn't feel it proper to make any modifications to their messaging.
Also, at the time I wrote the Moodle Activity module for 1.9 and 2.0 in January 2011, the DualCode only supported 1.9. Moodle 2.0 had been out for a few months and folks were asking for support for Moodle 2.0. So I decided to start from scratch and write an integration for both Moodle 1.9 and 2.0, and, using our experience with integrating BigBlueButton into othe products, make it as good I possible could.
By doing this, we also gave the Dual Code folks a bit of competition, and competition is good, but confusion is not.
The confusion over the directory structures is my fault. I used 'bigbluebutton' for the directory name and database name to achieve the name 'bigbluebutton' when installing the activity module.
It wasn't my intent to cause confusion or problems for administrators, and I'd be happy to change the structure in the next version of our activity modules so that administrators don't have any potential for conflict.