> Am 22.04.2015 um 12:21 schrieb H.Merijn Brand <h.m.br...@xs4all.nl>: > > On Wed, 22 Apr 2015 12:01:46 +0200, Jens Rehsack <rehs...@gmail.com> > wrote: > >> Hi Merijn, >> >> since Wendy told me yesterday that every new module must (should) >> have a co-maint, > > It was decided upon to be *advisory* for upstream modules: those that > have modules on CPAN that depend on it or where is known that DarkPAN > users have publicly shown that they are using the module. > > The latter is not (yet) visible on any of the current CPAN clients. > > co-maint is not obligatory. certainly not for new modules.
Than I misunderstood probably something. Anyway - it might be a good idea, either - for keeping an eye on it or whatsoever :) > FWIW, I am in serious doubt if I want to have anyone co-maint > Text::CSV_XS at all. Come on - I had commit bit for years on repo.or.cz and didn't misuse it in any way. >> could I count on you for upcoming AnyData2 / DBD::AnyData2? > > /me is in serious doubt, as the main purpose of these modules is way > out of my focus area: I never use them. My primary reason to use DBD::CSV from time to time is to keep on track how the users problems look like ;) For the typical problems I solve using it, it's overkill ... You're familiar with the separation of storage / parsing engine, you're familiar with DBI::DBD::SqlEngine and you're more or less familiar with SQL::Statement ... > Do you know of any CPAN author that is using them or has shown interest > in these? That would IMHO be a better choice. Seriously: Nope. Only DarkPAN :( >> I don't want to start on dbi-dev@ a general discussion - so >> AD2: yes or no? Cheers -- Jens Rehsack rehs...@gmail.com
