[mylar-dev] Stand alone bug tracking

[Jeff Pound <jpound@xxxxxxxxxx>]

To address the issue of a stand alone bug tracking plug-in for eclipse
we have a few different options with regards to Mylar's bug tracking
integration (http://www.eclipse.org/mylar/), and the Platform/Team
effort that has been continued at redhat.
(http://people.redhat.com/jpound)

It seems to be accepted that both the Mylar bug tracker and the stand
alone bug tracker can share a back end model, but the front end could
take any one of a number of approaches:

A: have the Mylar Tasks plug-in as the main view for a stand alone bug
tracker.

B: have a common (bug) back end for the Bug tracker and for Mylar but
have different UIs (Mylar tasks view for Mylar and the Platform/Team UI
for stand alone)

C: integrate the platform/team UI as the main bug view in Mylar (and use
it for both Mylar and stand alone)

D: Pull features from both bug UI's and build something new, though one
would likely serve as the basis.

E: something entirely different... (?)


Here's a quick summary of the current state of eclipse-bugzilla (from
memory, hopefully I don't miss too much ;)

o Presentation (UI).
  . Create folders, dnd organization
  . Handles any number of bugzilla providers
  . Allows custom names of elemtents (ex. queries, folders)
  . "quick view" shows info about selected elements and auto
    hides when not needed
  . Integrated query dialog has "simple" and "advanced" modes.
    Organizes options into tabs to avoid the cluttered presentation
    often associated with bugzilla query pages.
  . Bugzilla Browser, embedded browser can be launched to show
    selected elements.
  . misc nicities (grabs icon associated with bugzilla db for view,
    actions for elements displayed in context menu)

o Functional bits
  . Attachment handling (Apply Patches directly to a workspace,
    view logs (or other text/*) in the quick view, show attachments
    in the bugzilla browser) 
  . Integrated "read" operations in bugzilla (querying, viewing bug
    info, downloading attachments, etc..). No operations that 
    modify the db are integrated, awaiting bugzilla WebService.
  . Bugzilla Browser: web browser for viewing the actual bugzilla
    pages. DB modifying operations can be performed from here.
  . Persistent bug management/organization.
  . Support for bugzilla 2.16 -> 2.18

o Misc.
  . Code base originally developed by Platform/Team, now actively
    developed by redhat.
  . Currently only one committer/project maintainer (Jeff Pound)
  . Have received patches, bug reports, emails, and general
    interest from people at ibm, redhat, and others. (Ed Burnette
    has also contributed a couple patches)
  . Currently ships with Fedora Core 4 (natively compiled with gcj)
  . Targeted as java 1.4.2 / Eclipse 3.1 compliant code.
  . Installation / CVS details here http://people.redhat.com/jpound


-- 
Jeff Pound <jpound@xxxxxxxxxx>