<!doctype html public "-//w3c//dtd html 4.0 transitional//en"> <html> Greetings Matt, How about, rather than replacing bugzilla, jabberize bugzilla.  Maybe so that instead of having your bugzilla installations each have their own databases, use a jabber layer that intercepts all the mysql stuff and redirects all data flow to your centralized database. Jabber client monitoring could all be implemented within that layer, and with data filters, the client communications could be customized (for example, I might only want to see activity on resolutions within a certain component).  Bugzilla's query logic could even be leveraged for allowing jabber users to customize and set up the activity they want monitored. This, along with something to let me monitor CVS activity would be very useful to me :-) later.    sk.... Matthew Miller wrote: <blockquote TYPE=CITE> OK, this got a little off-topic (maybe I shouldn't be in digest mode, eh? (-: ).Anyways, the intent of my bug-tracking system is really to be a "replacement" (not the best word, but "oh well") to something like bugzilla, except the entire system is distributed.  Once a bug is added (using a web-based front-end at first, then more native/distributed systems later), it gets "passed around" using Jabber.Now, before anyone starts slamming me with "but, but, but where's the centralization?  This can't work without centralization!!!" stuff, STORAGE of bugs is going to be centralized.  Jabber (from the client's perspective) is used in a similar manner to Al's monitoring bot (at first, anyway): notification. Like I said earlier, the whole thing's still in the design phase.  I am trying to get a feel for anyone that would be interested in using a system like this.  This isn't (YET) a call for beta-testers, more like a survey asking if such-and-such a feature would be good and/or useful.Matt <blockquote style="MARGIN-RIGHT: 0px"> <div class="OutlookMessageHeader" dir="ltr">-----Original Message----- From: Colin Madere [<A HREF="mailto:colin@vedalabs.com">mailto:colin@vedalabs.com</A>] Sent: Thursday, May 31, 2001 2:29 PM To: 'jdev@jabber.org' Subject: RE: [JDEV] Bug-tracking project  </div> Examples never hurt anyone :) Don't burn time on it though, if you're busy.. it'll be at least a few days before I start knocking this around. Thanks, Colin -----Original Message----- From: Al Sutton [<a href="mailto:al@alsutton.com">mailto:al@alsutton.com</a>] Sent: Thursday, May 31, 2001 3:45 PM To: jdev@jabber.org Subject: Re: [JDEV] Bug-tracking project I used my own libraries which you can download from my website (<a href="http://www.alsutton.com/" target="_blank">http://www.alsutton.com/</a>), I could strip the code out of the stuff I'm doing and upload it as well if you think it'd be useful.   Al. ----- Original Message ----- From: Colin Madere To: 'jdev@jabber.org' Sent: Thursday, May 31, 2001 9:29 PM Subject: RE: [JDEV] Bug-tracking project Neat.  Did you use JabberBeans for this?  (or is it JabberServlets...?) I'd be interested in using this type of thing since I plan to do some Servlet/IM integration (starting it in a few days). > -----Original Message----- > From: Al Sutton [<a href="mailto:al@alsutton.com">mailto:al@alsutton.com</a>] > Sent: Thursday, May 31, 2001 2:36 PM > To: jdev@jabber.org > Subject: Re: [JDEV] Bug-tracking project > > > Matthew, > > I've developed a bug reporting system for the servlets on my > web pages. When > an error occurs they report it via jabber to one (or more) JIDs for > analysis. > > Is this the kind of thing you're looking at, or are you thinking of > something wider? > > Al. > > ----- Original Message ----- > From: "Matthew Miller" <MatthewM@vdr.com> > To: <jdev@jabber.org> > Sent: Thursday, May 31, 2001 6:48 PM > Subject: [JDEV] Bug-tracking project > > > > OK, here it comes... > > > > I have been working off-and-on on a distributed > bug-tracking system.  Now > > that I am more familiar with Jabber's protocols (and now > that I have an > > "active" audience awaiting an actual system!), I am looking at using > Jabber > > for the messaging layer. > > > > So, why send this around here?  Well, I am looking for more > interested > > parties (on running the system), and any advice some of you > may have on > > Jabber's involvement. > > > > It's currently in the "concept design" phase right now > (does anything ever > > truly leave that phase? (-: ), so this is the perfect time > to espouse your > > requests. > > > > Thanks, > > > > ______________________ > > |\/| /\  |   | > > _______________________________________________ > > jdev mailing list > > jdev@jabber.org > > <a href="http://mailman.jabber.org/listinfo/jdev" target="_blank">http://mailman.jabber.org/listinfo/jdev</a> > > _______________________________________________ > jdev mailing list > jdev@jabber.org > <a href="http://mailman.jabber.org/listinfo/jdev" target="_blank">http://mailman.jabber.org/listinfo/jdev</a> ></blockquote> </blockquote> </html>