Self-Introduction: Eric Black

[Eric Black]

    * Eric Black

    * New Haven, CT, US
    * Software Engineer
    * Higherone, Inc
    * I'm not sure yet, maybe someone will tell me :)
    * Historical qualifications
          o Mostly Perl and Java web applications, C/C++ long ago
          o I'm a senior level developer in Perl with extensive *nix skills
          o My role for the past 10 years at different companies has been to mediate and automate developer and ops processes  
    
I'm really just starting to look at Bugzilla since I'm responsible for it now. We have a 2.18.3 version installed and it's highly customized, used for many different processes, including many non-technical uses. My task at the moment is to upgrade it to the latest version and to make the customizations non-intrusive for later upgrades of Bugzilla. After I accomplish the upgrade, there is a slew of more customizations that are requested by the organization.

Additionally, I need a workflow engine and I intend to customize, hopefully by the use of hooks, bugzilla as the engine, even if it's a separate instance. That was one suggestion from the developers of a deployment engine I've been implementing, ControlTier (http://apps.sourceforge.net/mediawiki/controltier/index.php?title=Main_Page). 

So as I said, I don't really have much to offer yet, but I hope to soon. Also, assuming I don't find a bug for something that I need to customize, does it make more sense to run it by this list before submitting a bug, or should I submit the bug first?