[phpBT-dev] Comments and Questions

[Cameron M. <li...@un...>]

Hello,
I started testing out phpbt this week with the purpose of using it to
track bugs/tasks in the web development department where I work.  I
tried out a couple other packages like phpbt and found them overly
complex (in setup and use) or just generally lacking in too many areas.
Phpbt appears to be a simple, yet powerful solution.  I tried looking
back through some of the CVS commit messages in the list archives but
got tired of SF's interface.  Is this list archived anywhere else?

Anyway, I wanted to ask what plans you have for the near future.  I'm an
unashamed Perl hacker, but I don't have any major qualls with hacking on
PHP.  I'd like to lend a hand once I get my head our the way things are
done inside phpbt.

Here's my current list of phpbt issues:

- HTML chars are not handled correctly when used in the bug summary
- Need directory/permission checks in index.php:build_image(); took me
  a while to figure out phpbt kept dying every time I turned on jpgraph;
  turns out I didn't have a jpgimages/ directory.
- Main page needs the option of showing the project next to the latest
  items (probably in a <table/>)
- Would like the ability to colorize by Priority (known issue)
- Would like a 'show all unassigned bugs' query (known issue)
- Would like a 'site name' option in the Configuration section and
  replace 'phpBugTracker' with that value
- Default theme is a little crude in places

I'm still waiting to get the go-ahead from the head web guy whether he
likes phpbt or not, but I'm expecting him to okay it.  Once it's okayed
(and I get authentication working correctly with the CVS version), I
hope to help fix some of the issues listed above.
-- 
Cameron Moore
[ Can you buy an entire chess set in a pawn shop? ]