DBI / S::S / DBD::CSV ... related hackathon

Hi all,

as I know some of us are located close together, I suggested
a hackathon especially for Pure-Perl drivers, their tests and
integration.

My goals were:

1) having a lot of DBD::CSV tests (DBI related like ChopBlanks)
    moved or copied and maintained in DBI

    ==> a lot of tests simply test former DBD::File features,
        from times where DBD::File and DBD::CSV were much closer
        together and not so many other Pure-Perl DBD's in wildlife

        But now - there're DBD::DBM, DBD::AnyData, DBD::Sys, ...
        and upcoming DBD::Mem - which all should benefit from the
        impressive test cases written in DBD::CSV (and not only
        a turn later with next DBI release ^^)

2) let DBD::CSV use DBI::DBD to create tests for DBI::Nano, Gofer,
    different baackends/serializers ...

    ==> DBI::DBD has a neat feature function (dbd_edit_mm_attribs)
        to create tests using some different whatsoever:

        Prefix -> means
        * p => DBI_PUREPERL=2
        * g => DBI_AUTOPROXY='dbi:Gofer:transport=null;policy=pedantic'
        * n => DBI_SQL_NANO=1

        All with restrictions for filename patterns etc.

        This function needs to be refactored to provide that
        functionality for other modules, too - and then used for
        DBD::DBM (create test combos for several backends and
        serializers), DBD::CSV (create test combos for S::S vs.
        Nano and Text::CSV vs. Text::CSV_XS), maybe SQL::Statement
        to create test combos for each available S::S using DBD
        (like currently done by looping e.g. t/02execute.t in
        SQL-Statement)

We (Merijn and myself) discussed that roughly in IRC - but decided
it would be a good idea to increase the count of affected/invited
people (like end-users of our services as ribasushi or Dijkmat ^^).

I suggested to find a location like the Unperfekthaus
(http://www.unperfekthaus.de/) in reachable distance to all
attendees.

So at first I would be great if all interested persons can
tell if they would like to join - let's say until end of January
(for a date in March/April 2013) with a limit how far they're
willing to travel.

Everyone is invited (regardless of his/her personal participation)
to suggest topics.

Second step is to create a more or less complete plan for those
who want which goals shall be reached (to approve whether there're
prerequisites which needs to be fulfilled before ...).

Thanks for attention,
Jens