krisahoch wrote: be aware that I will be quoting you.
Okay, you can quote me: how can we possibly give any informed responses without being informed of:
- The list of features
- Some code
- An accurate description of what problem space you are working with and why PerlDesk is better
And I wouldn't mind seeing the schema, either.
Don't get me wrong, Bugzilla leaves a lot to be desired, but I am hard-pressed to believe that someone can spend two weeks on a software package and produce a reasonable alternative. Of course, I know it can be done, but you'll have to offer some evidence of that (see the bullet points above.
The last point, about your problem space, is really important. If PerlDesk is tremendously inferior to Bugzilla for most of us, it still may be a better option for you, depending on your needs.
Cheers,
Ovid
Join the Perlmonks Setiathome Group or just click on the the link and check out our stats.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.