How should a fork of DBIx::Simple be handled?

[metaperl]

Due to time constraints at work, I will be applying patches to DBIx::Simple in order to address a bug which directly affects some commercial software I am developing.

I have imported the CPAN sources for DBIx::Simple and plan to patch in a systematic fashion so Juerd can follow them and perhaps apply them to his distro. I thought of contacting the various people that have submitted bugs and solicit patches but I'm not sure if that's spamming them.

One change from DBIx::Simple that I'm excited about is replacing SQL::Abstract with SQL::Abstract::More so that I can take advantage of its expanded query-generation power, which includes a join syntax!

So for the time being, I suppose I will just develop and patch at github and use my forked version in our production software for a few months and document each change thoroughly. Any feedback on the proper way to handle forking this module is appreciated.

[Juerd]

How about just sending the patches you had in mind, to the author of DBIx::Simple, i.e. me?

[Anonymous Monk]

You may have missed Re: DBIx::Simple - Your opinions/review please and the followup I should have been more Handy::Dandy in dealing with DBIx::Simple and Juerd

[Corion]

So the only lesson you take away from these two threads is to continue avoiding direct contact with Juerd? I'm still wondering what your goal is with these posts. But then, I already said so in 917893.