diff options
Diffstat (limited to 'docs/sgml/variants.sgml')
-rw-r--r-- | docs/sgml/variants.sgml | 117 |
1 files changed, 61 insertions, 56 deletions
diff --git a/docs/sgml/variants.sgml b/docs/sgml/variants.sgml index fec867946..a5b346023 100644 --- a/docs/sgml/variants.sgml +++ b/docs/sgml/variants.sgml @@ -1,72 +1,77 @@ <!-- <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook V4.1//EN">--> -<chapter id="variants"> - <title>Bugzilla Variants</title> - <note> - <para> - I <emphasis>know</emphasis> there are more variants than just RedHat Bugzilla out there. - Please help me get information about them, their project status, and benefits there - might be in using them or in using their code in main-tree Bugzilla. - </para> - </note> +<chapter id="variants" xreflabel="Bugzilla Variants and Competitors"> + <title>Bugzilla Variants and Competitors</title> + <para>I created this section to answer questions about Bugzilla + competitors and variants, then found a wonderful site which covers + an awful lot of what I wanted to discuss. Rather than quote it in + its entirety, I'll simply refer you here: <ulink + url="http://linas.org/linux/pm.html">http://linas.org/linux/pm.html</ulink></para> - <section id="rhbugzilla"> + <section id="rhbugzilla" xreflabel="Red Hat Bugzilla"> <title>Red Hat Bugzilla</title> <para> - Red Hat Bugzilla is probably the most popular Bugzilla variant, aside from Mozilla Bugzilla, - on the planet. - One of the major benefits of Red Hat Bugzilla is the ability to work with Oracle as a - database, as well as MySQL. - Here's what Dave Lawrence had to say about the status of Red Hat Bugzilla, - <blockquote> - <literallayout> - Hello. I apologize that I am getting back to you so late. It has been difficult to keep -up with email this past week. I have checked out your updated documentation and I will -have to say very good work. A few notes and additions as follows. - -(ed: from the FAQ) ->For the record, we are not using any template type implementation for the cosmetic changes ->maded to Bugzilla. It is just alot of html changes in the code itself. I admit I may have ->gotten a little carried away with it but the corporate types asked for a more standardized ->interface to match up with other projects relating to Red Hat web sites. A lot of other web ->based internal tools I am working on also look like Bugzilla. - + Red Hat Bugzilla is probably the most popular Bugzilla variant + on the planet. One of the major benefits of Red Hat Bugzilla is + the ability to work with Oracle, MySQL, and PostGreSQL databases + serving as the back-end, instead of just MySQL. Dave Lawrence + has worked very hard to keep Red Hat Bugzilla up-to-date, and + many people prefer the snappier-looking page layout of Red Hat + Bugzilla to the default Mozilla-standard formatting. + </para> + <para>URL: <ulink + url="http://bugzilla.redhat.com/bugzilla/">http://bugzilla.redhat.com/bugzilla/</ulink></para> + </section> -This should probably be changed since we are now in fact using Text::Template for most -of the html rendering. You actually state this later in your numbered list. + <section id="variant_fenris" xreflabel="Loki Bugzilla, a.k.a. Fenris"> + <title>Loki Bugzilla (Fenris)</title> + <para>Fenris can be found at <ulink + url="http://fenris.lokigames.com/">http://fenris.lokigames.com</ulink>. It is a fork from Bugzilla.</para> + </section> -Also number 6 contradicts number 8 where number 6 would be the most up to date status -on the Oracle port. + <section id="variant_issuezilla" xreflabel="Issuezilla"> + <title>Issuezilla</title> + <para>Issuezilla is another fork from Bugzilla, and seems nearly + as popular as the Red Hat Bugzilla fork. Some Issuezilla team + members are regular contributors to the Bugzilla mailing + list/newsgroup. Issuezilla is not the primary focus of + bug-tracking at tigris.org, however. Their Java-based + bug-tracker, <xref linkend="variant_scarab">, is under heavy development + and looks promising!</para> + <para>URL: <ulink url="http://issuezilla.tigris.org/servlets/ProjectHome">http://issuezilla.tigris.org/servlets/ProjectHome</ulink></para> + </section> -Additional Information: ------------------------------ -1. Comments are now stored in varchar fields of 4k in size each. If the comment is more -than 4k it is broken up into chunks and given a sort number so each comment can be re -assembled in the correct order. This was done because originally I was storing the comments -in a long datatype which unfortunately cannot be indexed or joined with another table. This -cause the search of text within the long description to be disabled for a long time. That -is now working and is nto showing any noticeble performance hit that I can tell. + <section id="variant_scarab" xreflabel="Scarab, a newfangled Java-based issue tracker"> + <title>Scarab</title> + <para>Scarab is a promising new bug-tracking system built using + Java Serlet technology. As of this writing, no source code has + been released as a package, but you can obtain the code from + CVS. + </para> + <para>URL: <ulink url="http://scarab.tigris.org/">http://scarab.tigris.org</ulink></para> + </section> -2. Work is being started on internationalizing the Bugzilla source we have to allow our -Japanese customers to enter bug reports into a single bugzilla system. This will probably -be done by using the nvarchar data types supported by Oracle which allows storage of -double byte characters and also the use of the Accept-Language in the http header for -detection by Bugilla of which language to render. + <section id="variant_perforce" xreflabel="Using Perforce to track bugs"> + <title>Perforce SCM</title> + <para>Although Perforce isn't really a bug tracker, it can be used + as such through the <quote>jobs</quote> functionality.</para> + <para><ulink + url="http://www.perforce.com/perforce/technotes/note052.html"></ulink>http://www.perforce.com/perforce/technotes/note052.html</para> + </section> -3. Of course even more cosmetic changes. It is difficult to keep up with the ever -changing faces of www.redhat.com. + <section id="variant_sourceforge" xreflabel="SourceForge"> + <title>SourceForge</title> + <para>SourceForge is more of a way of coordinating geographically + distributed free software and open source projects over the + Internet than strictly a bug tracker, but if you're hunting for + bug-tracking for your open project, it may be just what the + software engineer ordered!</para> + <para>URL: <ulink + url="http://www.sourceforge.net">http://www.sourceforge.net</ulink></para> + </section> -4. Some convenience enhancements in the administration utilities. And more integration -with other internal/external Red Hat web sites. -I hope this information may prove helpful for your documentation. Please contact -me if you have any more question or I can do anything else. -Regards - </literallayout> - </blockquote> - </para> - </section> </chapter> <!-- Keep this comment at the end of the file |