But I strongly suspect that a knowledgable, labels-shy observer with a good view of the project, and a good knowledge of you, would attribute the good and steady progress it has made since your involvement, down to your personality and drive and programming skills; not the currently trendy label, set of checklists or headline statistics for what at its crux, amounts to no more than having a well-thought through set of development procedures. And using them.
I have trouble separating my "personality and drive and programming skills" from the "well-thought through set of development procedures" I use. If we committers can make and meet commitments regularly, perhaps we're doing something right. (Having a comprehensive test suite, reviewing patches, checking smoke tests, developing on branches and landing only when tests pass, and managing our bug queue are not Herculean tasks only supermen can perform.)
In reply to Re^5: Some reflections on the Brainbench Perl Test
by chromatic
in thread Some reflections on the Brainbench Perl Test
by metaperl
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |