- * It has great documentation *
- The author is responsive
- Has a clear change log for each version released
- You can verify that its reverse dependencies all pass their tests after a change
Also, s/full coverage/very good coverage/, s/long-standing open issues/long-standing open bugs/ (I have 94 outstanding "issues" across ~80 repositories, but I'd say 15 are bugs, and none are show-stoppers).
Regarding the last list point, that can be done by downloading the most recent code in question instead of using your own repository.
| [reply] [d/l] [select] |
Good points, thanks. I've added documentation as that was a definite oversight. In doing so I think this arguably includes the change log? Similarly having a recent release and/or no open bugs (better than "issues" I agree) mostly covers the "responsive" point for me but maybe you have another metric?
Of course, there's being responsive and there's being usefully responsive. Yes, I do have a project leader in mind but it isn't a Perl project so I'll say no more.
| [reply] |
Hey hippo,
Because a poll can't have 18,000 selections (well, not feasibly anyhow ;), the change log item could probably fall under the documentation section as it is part of it.
Also, in regards to being responsive, I just meant that replies to new issues and/or emails relatively promptly, tries to answer as honestly as possible, keeps in touch if life gets in the way so that the end-user knows they haven't been abandoned and makes the interaction between the end-user and software developer a reasonably enjoyable one.
Your call on that one, just thought I'd raise it because there are definitely some authors who publish regularly but to get a hold of them is akin to watching paint dry (that said, that's been 1/100 or so for me, ie. it does not happen often at all).
| [reply] |
s{install}{update}. The reasons might be completely different. You *install* a new module if it fits all your needs. If there are multiple candidates, you probably use the above checklist. Once it is installed, you don't want to break your stuff, and you'd probably want to do tests based on the above list, but the main thing is:
- If it fixes bug that hinders me and does not break other stuff.
Enjoy, Have FUN! H.Merijn
| [reply] [d/l] |