use Perl

• Max's Response (Score:1)

  by avatraxiom (7875)

  I actually have heard of and did know about most of the modules and frameworks that were suggested by many of the commenters on my blog, as do several other Bugzilla contributors. Remember, Bugzilla is written by a community, not by just me.
  
  When I first started to work on Bugzilla's code several years ago, it was not in a state where a project like "Use DBIx::Class and Catalyst" was a feasible project. A huge amount of cleanup was required before anybody could even see the architecture of Bugzilla.
  
  I'm glad
  • Re: (Score:2)

    by TeeJay (2309)

    I'm not sure how it can be easier to port to a new language that the developers and users know less, than to a framework written in a language the system is written in and developers and users already have some familiarity with.
    
    As it happens, if I was to write Bugzilla again tomorrow, it's not the language I would change, it's the database schema, relationships and workflow - I'd be looking at closer integration with project documentation (specifications, screenshots, UML documentation), version control and

    --
    
    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;
    • Re:Max's Response (Score:1)

      by avatraxiom (7875) on 2007.05.08 14:35 (#54944)

      Hi TeeJay. I think more of our users know Python than Perl, but it's true that more of our developers know Perl than Python.
      
      Have you looked at the database schema of Bugzilla in any depth?
      
      We're working on custom workflow right now.
      
      Our goal is to be a bug-tracker, not a project management system, so we don't work on those other things. If we had three times as many programmers, and we had them consistently available, we could consider branching out into those project-management areas, but right now our focus is on bug tracking.
      
      -Max

      Reply to This

      Parent