> Thoughts: > > 1. I can understand your not wanting to mention the name of the > module, but we might be able to provide more help if we know it, > particularly if someone on this list is aware of what happened. > 2. You could fork the module on the CPAN (which means maintaining it, > something you might not want to do). > 3. You could fork the module for your company's internal use, which I > know many programmers do. > 4. You could tell us what functionality you added. I do know that > some authors just won't respond to what they consider unimportant or > bad requests (I'm not saying your changes are unimportant or bad; the > author might just see them that way.) > > I might add that if a fork happens, many people might be happy to see > the fork on the CPAN. The theory is that many people can benefit. > However, that means you have to maintain it and that can be more > trouble than it's worth. More than once I've begged people for > patches, only to be ignored. Plenty of other authors have had the same > experience. Maintaining modules can be frustrating. > > sorry the module is DNS::ZoneParse. I could fork it, no problem. I am using it all the time in my company, so it is better for public that changes appear on CPAN, not only my private svn.
signature.asc
Description: PGP signature
signature.asc
Description: OpenPGP digital signature
