I would like to see some integration of the apps database with bugzilla. The way I see it the best way for this to work is for the apps database to be a front end to bugzilla for users. If a user has a problem with the application they could search to see if the problem was already reported or enter a new bug . Dependancys for getting the application working 100% could be integrated in this way. The application maintainer could help make sense of useless bug reports, identify duplicate bug reports and help decide when a bug was resolved.
Any comments?
Tony Lambregts
I think that is a great idea. The only problem is that there's not a really good way to maintain a list in bugzilla that people can add to. I guess the app list could be a big metabug. But this might mean less flexible queries.
Tony lambregts wrote:
I would like to see some integration of the apps database with bugzilla. The way I see it the best way for this to work is for the apps database to be a front end to bugzilla for users. If a user has a problem with the application they could search to see if the problem was already reported or enter a new bug . Dependancys for getting the application working 100% could be integrated in this way. The application maintainer could help make sense of useless bug reports, identify duplicate bug reports and help decide when a bug was resolved.
Any comments?
Tony Lambregts
Michael Cardenas wrote:
I think that is a great idea. The only problem is that there's not a really good way to maintain a list in bugzilla that people can add to. I guess the app list could be a big metabug. But this might mean less flexible queries.
I don't think I would like the metabug approach. What is the problem with this, right now people cannot just add an app to the list. I first have to go through a submission process to get my app put into the database right now. It seems to me that maintaining the list in buzilla could be done when the app was actually added to the database. Could you enlighten me more about this please.
Tony Lambregts.
Tony lambregts wrote:
Michael Cardenas wrote:
I think that is a great idea. The only problem is that there's not a really good way to maintain a list in bugzilla that people can add to. I guess the app list could be a big metabug. But this might mean less flexible queries.
I don't think I would like the metabug approach. What is the problem with this, right now people cannot just add an app to the list. I first have to go through a submission process to get my app put into the database right now. It seems to me that maintaining the list in buzilla could be done when the app was actually added to the database. Could you enlighten me more about this please.
Tony Lambregts.
The more I think about this the more I would like it.
Reasons for integrating the app database with bugzilla.
- No problems with alternate spelling of app (M$ word, MS WORD, microshaft word, etc...) - Better quality bug reports (forces user to give at correct program name and version) - Keeps app database current. - Reduces need for metabug messiness. - Maintainer/s for app have central place to maintain app - Easy to locate bugs with app. - Easier to locate duplicate bugs. - Encourage users to become maintainers.
Did I forget anything?
I think the long term benefits far outwiegh the short term amount of work to get this done.
What can I do ?
Tony Lambregts
In theory, the design and layout of the appdb should allow for this integration (we planned for it, just decided to keep the implementation as simple as possible).
The problem is that they are two completely different systems, so seamless integration is hard. However, I think that some 'bailing wire and coat hangers' to stitch the two together would get us 90% of what we want with 10% of the effort.
One idea could be that each app could have a bugzilla id, and then any bugs entered for that app could automatically block the main bugzilla bug id. Then Bugzilla does a really nice job of letting you see dependency graphs and such.
So, the app db could gain a "Enter a bug for this app", and "See all the bugs listed for this app" button.
Possibly, the bug entered for the app could also have a URL that points back to the app db as well, to facilitate cross pollination.
What can I do ?
Jeremy Newman, you've got a live one. Maybe get Tony an account on winehq and see if he can help with the appdb code.
Tony, I think the appdb is mostly PHP/MySQL. I gather that Bugzilla is a whole bucket of other stuff.
The only hitch you might run into is that Jer is planning an overhaul of the appdb code, so it may be a bit tricky to work through that.
Cheers,
Jer
Jeremy White wrote:
In theory, the design and layout of the appdb should allow for this integration (we planned for it, just decided to keep the implementation as simple as possible).
The problem is that they are two completely different systems, so seamless integration is hard. However, I think that some 'bailing wire and coat hangers' to stitch the two together would get us 90% of what we want with 10% of the effort.
One idea could be that each app could have a bugzilla id, and then any bugs entered for that app could automatically block the main bugzilla bug id. Then Bugzilla does a really nice job of letting you see dependency graphs and such.
So, the app db could gain a "Enter a bug for this app", and "See all the bugs listed for this app" button.
Possibly, the bug entered for the app could also have a URL that points back to the app db as well, to facilitate cross pollination.
Hell I think thats good enough . The biggest problem with this is having two accounts with two passwords any thougths on having them synced.
What can I do ?
Jeremy Newman, you've got a live one. Maybe get Tony an account on winehq and see if he can help with the appdb code.
Tony, I think the appdb is mostly PHP/MySQL. I gather that Bugzilla is a whole bucket of other stuff.
Only problem with this is I haven't really coded in two years (I'm a stay at home dad and my youngest is just getting old enough that I don't have to watch him every minute.) Oh well, I guess I asked for it. Anybody got a PHP manual I could borrow?
The only hitch you might run into is that Jer is planning an overhaul of the appdb code, so it may be a bit tricky to work through that.
Cheers,
Jer
Tony, I think the appdb is mostly PHP/MySQL. I gather that Bugzilla is a whole bucket of other stuff.
Only problem with this is I haven't really coded in two years (I'm a stay at home dad and my youngest is just getting old enough that I
don't
have to watch him every minute.) Oh well, I guess I asked for it. Anybody got a PHP manual I could borrow?
Sorry Tony, you've been drafted. =)
_________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
On Thu, 2002-03-21 at 07:58, Jeremy White wrote:
Tony, I think the appdb is mostly PHP/MySQL. I gather that Bugzilla is a whole bucket of other stuff.
Bugzilla a MESS of crufty Perl code. I've found it very difficult to extend that code any further without breaking it.
The only hitch you might run into is that Jer is planning an overhaul of the appdb code, so it may be a bit tricky to work through that.
Exactly, we have quite a few updates planed for AppDB. I will add a BugZilla link field to each App Version soon. I'll need someone with MUCHO spare time on his hands to actually go though and link each App Version Id to a Bugzilla Bug Id. This is NOT a small amount of work.
Near impossible if you actually want to tie it into the current Bugzilla database :)
Although I suppose a few perl scripts to do some reorganisation of the IDs based on simple text matching might make some sense of it. I don't know how consistant Bugzilla remains if you go manually changing ID's in the database tho :P
Exactly, we have quite a few updates planed for AppDB. I will add a BugZilla link field to each App Version soon. I'll need someone with MUCHO spare time on his hands to actually go though and link each App Version Id to a Bugzilla Bug Id. This is NOT a small amount of work.
Jeremy Newman wrote:
On Thu, 2002-03-21 at 07:58, Jeremy White wrote:
Tony, I think the appdb is mostly PHP/MySQL. I gather that Bugzilla is a whole bucket of other stuff.
Bugzilla a MESS of crufty Perl code. I've found it very difficult to extend that code any further without breaking it.
The only hitch you might run into is that Jer is planning an overhaul of the appdb code, so it may be a bit tricky to work through that.
Exactly, we have quite a few updates planed for AppDB. I will add a BugZilla link field to each App Version soon. I'll need someone with MUCHO spare time on his hands to actually go though and link each App Version Id to a Bugzilla Bug Id. This is NOT a small amount of work.
Ah! grunt work. Thank goodness there's only 512 of them. oops 513...
Honestly not that bad. a lot of them are not even app bugs. meta bugs etc... What should I do with them? Of course there are probably some that have no AppDB entry. Swell, I 've already added one so I already know how to do that.
I need an account to get started and maybe a few pointers.
Tony Lambregts
Bugzilla has two-level classification. What if we make an entry in the first level "Windows Applications" and components - list of all the applications from the AppDB?
We can connect the bugzilla "Component" category and AppDB entry by application id.
Sounds pretty easy to me. Small matter of Bugzilla configuration ;-)
Andriy Palamarchuk
__________________________________________________ Do You Yahoo!? Yahoo! Movies - coverage of the 74th Academy Awards� http://movies.yahoo.com/
-
Andriy Palamarchuk -
J.Brown (Ender/Amigo) -
Jeremy Newman -
Jeremy White -
Michael Cardenas -
Steven Edwards -
Tony lambregts