Enforced style, especially where it is automatic, can be good. So I say. With such a system, everyone can have their own little style quirks in one's own editor that won't constantly show up as meaningless changes in commit diffs. The temptation to bikeshed indentation or brace placement, etc, goes away, and the risk with having your own cperl-mode or whatever also goes away. Mostly, kinda, sorta.
Documentation cannot be automated (well). I think a Pod coverage test that fails when subs/methods aren't documented (or license/synopsis/etc is missing/erroneous) is fine and I appreciate it because I forget to do that most of the time without a test.
I also think your previous practice of allowing "loose" commits was the best choice. Nagging is preferable to locked doors at the dev stage. Hard barriers make for unhappy work, and as you mentioned: gaming the rules. (Auto-)guides and peer pressure are better/friendlier for group standards.
The real problem with setting boundaries, AKA PROCESS, is that it almost guarantees sclerosis. Process gets less flexible and covers more ground over time, blocking out possibilities for improvement and innovation in work flow. So revisiting and being open to revising or trimming boundaries is something to consider and reconsider often.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
Outside of code tags, you may need to use entities for some characters:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
| & || & |
| < || < |
| > || > |
| [ || [ |
| ] || ] ||