Paul, one of the reasons I haven't released the source code yet (fully intend on it)...is I'm hoping to gain support of other developers that have a real interest in supporting the module as a team, instead of splintering (multiple versions).  I am working to get all of the kinks out of the 3.2 version and fully support all of the DNN Module features.  Then:

1) The Source will be posted on the internal DNN Project Site (for Event Project Developers)
2) The module will then be modified to support the existing DNN Event module migration to the this module
3) A Roadmap will be defined for new features and tasks handed out to the team for development of the next release(s)
4) Releases of the module will be fully documented and source code available to all developers.

Some of the features you discussed are great features...Have you (and other developers) signed up for the Module Team?  Please consider it.  I'm looking for help on organizing the team and helping to define the direction/roadmap.  All functions must fully support localization/cultures, just like DNN and existing Event/Calendar functions.  I believe this thing can only grow if it is a team effort...just like DNN...otherwise we'll get a lot of versions and users will be confused and left with poor support.

Good suggestions...I am getting overwhelmed with the module.  I have a bunch of requests...the hardest peices that continually byte me in the butt are considerations for localization...very tedious and time-consumming.  I really need another developer that can help code/debug/test for diff. languages, date formats, etc.

Alan, don't forget to look to the other team leads and your access to those forums... if the core team ( or other teams ) can be of assistance, we're all in this together!  Thank you for your dilligence!

Cheers