Except, I am actively maintaining it to the best of my abilities. It's still my responsability and I will be using it for work. In addition, I want to be involved in the direction that it takes as a module I do maintain depends on it. It's never quite that simple.
in reply to Re^2: Responsibilities of a module author
in thread Responsibilities of a module author
Oh, and PDF::Writer has no documentation as the API is completely random and will change every release for a while as I refactor.
My criteria for good software:
- Does it work?
- Can someone else come in, make a change, and be reasonably certain no bugs were introduced?