bugzilla_issuezilla_collabnet

This is part of The Pile, a partial archive of some open source mailing lists and newsgroups.



To: Jake <jake@acutex.net>, <mozilla-webtools@mozilla.org>
From: Jon Stevens <jon@latchkey.com>
Subject: Re: IssueZilla
Date: Tue, 06 Feb 2001 13:57:11 -0800

on 2/6/01 11:21 AM, "Jake" <jake@acutex.net> wrote:

> It's probably something where somebody took the bugzilla source and made a
> bunch of modifications then changed the name... all the while never
> submitting the changes back to the original bugzilla for all to benefit
> from.
> 
> I know nothing about IssueZilla but do know that this has been done at other
> sites (Red Hat,  for example).

Hello,

IssueZilla is a version of Bugzilla that has been *heavily* modified to work
within CollabNet's Sourcecast system. The changes to Bugzilla to make it
work within our system are quite specific to our system and therefore are
probably not of use to the general population of Bugzilla.

The full source code to IssueZilla is available here:
@see <http://sandbox.tigris.org/source/browse/sandbox/issuezilla/>

:-)

The point being that we are not "somebody" who is just taking the source
code and stealing it for our own benefit and not giving back to the
community. You may have missed that IssueZilla is being used on the recently
deployed Mozdev.org site as well. In other words, we (CollabNet) love the
Mozilla community and we are strongly founded on Open Source principles...

:-)

Introduction Time:

I know that Brian B. has posted here before, but I just wanted to introduce
myself and tell you about a project that I am working on for CollabNet...

I'm a member of the Apache Software Foundation and work primarily within the
Java side of the projects within the ASF. I have been working on Open Source
in one way or another for the last 6 or 7 years. I also manage several large
Java OSS projects under the ASF and also helped convince Sun to give the
Jakarta project its Servlet Engine, Tomcat.

I am also currently working on a "competitor" to Bugzilla that happens to be
based on Java technologies instead of Perl because the rest of our system is
also done on Java and we need closer integration within our system as well
as a more template driven solution that can do things like support multiple
OS's easily as well as multiple database backends transparently.

@see <http://scarab.tigris.org/>

Another goal of Scarab is to have a complete MVC separation implemented
using the Pull model. The point being that we want to allow designers to be
able to modify not only the look and feel of the site but also the flow of
the site without having to touch the backend code. This is something that is
currently very hard coded within Bugzilla and would take a complete rewrite
to achieve...

@see <http://java.apache.org/turbine/pullmodel.html>

Nothing wrong with having different implementations of the same thing in
different languages. :-) I'm very interested in working with the Bugzilla
project and really do not have any urges to re-implement the things that I
see you guys doing well. As soon as we are a bit further along with Scarab,
I'm sure that you will hear a lot from me with regards to things like the
XML export from Bugzilla. :-)

:-)

Since I'm the lead developer on Scarab, feel free to ask me any questions.
Up until now, I have just been a lurker on this list and will probably
remain so in order to stay out of everyone's hair...

:-)

thanks,

-jon stevens
jon@collab.net

===

To: mozilla-webtools@mozilla.org
From: "Jake" <jake@acutex.net>
Subject: Re: IssueZilla
Date: Tue, 6 Feb 2001 17:13:34 -0500

"Jon Stevens" <jon@latchkey.com>

> Another goal of Scarab is to have a complete MVC
> separation implemented using the Pull model. The point
> being that we want to allow designers to be able to modify
> not only the look and feel of the site but also the flow
> of the site without having to touch the backend code. This
> is something that is currently very hard coded within
> Bugzilla and would take a complete rewrite to achieve...

'Tis true... one of the reasons for the upcoming 3.0 rewrite.
http://www.hixie.ch/scripts/bugzilla/


===

To: <mozilla-webtools@mozilla.org>
From: Brian Behlendorf <brian@collab.net>
Subject: Re: IssueZilla
Date: Tue, 6 Feb 2001 14:54:22 -0800 (PST)

Actually, I posted here awhile ago about our patches; we've not taken the
time to make each of our changes atomic and lobby for them to be included,
because a) most of them are oriented towards integrating into the rest of
the Tigris suite (www.tigris.org), thus are not generically useful for all
Bugzilla installations, and b) it seemed like people were not interested
in pushing the 2.x branch all that much further.  The full source code is
available - check out the "sandbox" module from CVSROOT
:pserver:guest@cvs.tigris.org:/cvs, password "guest".  The docs are
skimpy, we admit, but it's there.

To be honest, I wouldn't advocate that people try to use it outside of the
rest of the Tigris suite.  We've not put the work in to make it
generically useful outside of that environment - sorry.  We would welcome
any patches along these lines, of course.

The name comes from the fact that we wanted to use it for more than just
bugs, but for all sorts of issues.

On Tue, 6 Feb 2001, Jake wrote:
> It's probably something where somebody took the bugzilla source and made a
> bunch of modifications then changed the name... all the while never
> submitting the changes back to the original bugzilla for all to benefit
> from.
>
> I know nothing about IssueZilla but do know that this has been done at other
> sites (Red Hat,  for example).

Red Hat uses their own fork of Bugzilla, I think.


===

To: "'Barry Katz'" <bskatz@attglobal.net>,
<mozilla-webtools@mozilla.org>
From: "Mike Zhang" <mike.zhang@returnpath.net>
Subject: RE: IssueZilla
Date: Tue, 6 Feb 2001 14:22:25 -0500

Try this:

http://www.possenet.org/issues/

===


the rest of The Pile (a partial mailing list archive)

doom@kzsu.stanford.edu