Picking up the ball...or reinventing the wheel?

I need to find more time to read through the flood of messages...but
wanted to mention right away that things look to be going astray.
Apologies if it is not so.

What's the goal here?  If it is creating a base class for date/time
modules to standardize on, that won't work.  I don't think the authors
of the existing modules are interested.  That way only leads to the
creation of Date::Yet::Another::Module.

If it is creating a module to provide some glue between existing
modules, great--but make sure that's the focus.  Does that need to be
more complicated than:

   $from_object = Date::ICal->new( ical => '19971024T120000' );
   Date::Glue::->make_a('Date::Calc::Object', $from_object)

where Date::Glue understands the get/set API of as many as possible of
the OO date modules out there?

Another goal I see as worthwhile would be a non-partisan document
comparing the strengths and weaknesses of the existing modules, with a
link to it from the date and time categories on CPAN.

• Picking up the ball...or reinventing the wheel? by sthoenna
• Re: Picking up the ball...or reinventing the wheel? by Dave Rolsky
• Re: Picking up the ball...or reinventing the wheel? by Rich Bowen