use Perl

• Alexander Cockburn (Score:1)

  by mr_bean (3802)

  I think the article by Alexander Cockburn that Ovid referenced to here has some things to say about distributed development, and they apply to development of perl itself.
  
        Linkname: Journal of Ovid (2709)
                  URL: http://use.perl.org/~Ovid/journal/30503 [perl.org]
   
• A familiar model (Score:2)

  by grantm (164)

  split site development of the same codebase

  Wouldn't that fairly accurately describe a project such as ... I don't know ... Perl!?!

  I believe you have some familiarity with how that works :-)

  I'd have thought that in a commercial project, the main difference would be that a project manager would be able to step in and "make a call" in the case of conflict or disagrement.
  • Re: (Score:1)

    by speters (1787)

    From my experience in working with Perl is that being several timezones apart from the others can be a bit of a challenge at times. At least with open source, people are generally available. At work, people tend to be available only during the eight to ten hours they are expected to be there. So, if your separated by eight hours or more, you may never reach some people in the office ever. That's where I guessing where the challenge comes in.
    • Re: (Score:2)

      by nicholas (3034)

      You've expressed the distinction better than I was going to. In my experience volunteer developed open source (seems) to be different and therefore easier for a couple of reasons:

      • People are generally available for more hours, so lack of overlap is not such a problem
      • People are generally working on individual subsections of the code, so don't conflict (and so don't need communication to resolve that)
      • People are generally not working full time, so the sheer pace of development is slower. (Or at least, the a