On Wed, Mar 19, 2025 at 12:29 AM Dan <gri...@gmail.com> wrote:

> Hello,
>
> I (DBOOK) am interested in adopting ZEFRAM's DateTime related modules,
> which are not depended on much by CPAN and have no outstanding issues
> (other than Data::Pond), but which I depend on for work code.
>
> I primarily directly use DateTime::TimeZone::Olson, which depends on these
> other modules for its functionality and which I am also prepared to
> maintain: DateTime::TimeZone::Tzfile, DateTime::TimeZone::SystemV, and
> Time::OlsonTZ::Data.
>
> Additionally, Time::OlsonTZ::Download and Data::Pond are used for the
> Time::OlsonTZ::Data prebuild process, and I would like to adopt these as
> well, primarily to fix an outstanding issue in Data::Pond that prevents it
> from building on recent versions of perl, and to ensure Time::OlsonTZ::Data
> releases can continue unimpeded with updates to the Olson timezone
> database. I don't feel particularly qualified to maintain Data::Pond as it
> is an XS module, but I will seek assistance from more experienced parties
> as needed.
>
> Finally, I would like to adopt App::olson which is the primary user of all
> of these modules on CPAN, in the off chance that it requires future
> maintenance.
>
> I do not have any current plans to make new releases of these modules
> other than to fix the Data::Pond issue and update Time::OlsonTZ::Data when
> it is next required. I will also note that Time::OlsonTZ::Data appears to
> have an automatic release process when the Olson timezone database updates,
> and I do not know whether it will continue to attempt making releases.
>

I will additionally request to adopt Date::ISO8601 and IPC::Filter for
completeness - both relatively simple modules with no known issues that are
also not used by much of anything on CPAN other than these datetime modules.

-Dan

Reply via email to