<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Mar 25, 2013, at 2:32 PM, jpbida wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><span class="Apple-style-span" style="border-collapse: separate; font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; ">What are your favorite set-ups for managing multiple developers contributing to a single perl code base? What is a good resource for doing this right? I'm really interested in projects using Dancer/Catalyst Frameworks. </span></blockquote></div><br><div>No simple answer here. Aside from a few Perl-centric tools (like maybe Smolder) none of these are any better or worse just because you're using Perl.</div><div><br></div><div>If you want to know what people's favorite version control system is, or what they like for bug tracking, that is a slightly different question.</div><div><br></div><div>You've identified most of the major types of tools it the development stack, so you've already won half the battle.</div><div><br></div><div>So now, you just make sure you use them :)</div><div><br></div><div>-Jeff</div></body></html>