in reply to Adopting Modules
in thread Seekers of Perl Wisdom
When I took over PDF::Template, the changeset was nearly 99.9% of the code and the author didn't have time. Now, once you've taken over maintainership, you're the boss. Sure, you definitely have to look at backwards compatibility, but that's true if you originally wrote it or not.
Writing more tests, adding new build methods, reorganizing the directory ... as long as you're not ripping out stuff just because it ain't yours, I'd say go for it! If you're not sure, ask your users.
Oh, yeah - make sure you have a mailing list and that you invite anyone and everyone you can think of to be on it. And, make sure that mailing list is prominently listed in the POD. Mailing lists are an absolute MUST when you've got something opensource. GoogleGroups, Yahoo!Groups ... both are excellent free mailing lists. (Perl6 and Parrot both use GoogleGroups, if that tells you anything.)
Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.
|
|---|