From m.thomas at valueclick.com Sun Apr 5 00:24:37 2009 From: m.thomas at valueclick.com (Michael Thomas) Date: Sat, 4 Apr 2009 17:24:37 -0700 Subject: Self-Introduction: Michael Thomas Message-ID: * Michael Thomas * Westlake, CA United States * Systems Administrator (sometimes developer) * ValueClick, Inc * MSSQL Support for Bugzilla * Historical qualifications o Various internal web and desktop applications o Perl, PHP, C#, VB.NET, ASP.NET so on so forth. o MSSQL/MySQL o Expert Windows OS I'd like to pick up Issue 285122 https://bugzilla.mozilla.org/show_bug.cgi?id=285122 I have successfully gotten Bugzilla to work with MSSQL to the point that basic operations are working. DB modules for all platforms will need to be tweaked a bit, the primary things of concern\interest is the support for datetime operations as they seem to be the biggest blockers. Example areas to work on are, as they don't exist in MSSQL: DATE_FORMAT NOW INTERVAL REGEXP Others but limited to are: INSTR LIMIT FK (Multi Path CASCADE is not allowed on UPDATE or DELETE in MSSQL, triggers are best practice for MSSQL. Most or all functionality can be replicated in user-defined function and store procedures, triggers. Perl side, existing calls need to be moved into the DB modules and out of the hard coded strings to allow for variance in the calls depending on the db. This email and any files included with it may contain privileged, proprietary and/or confidential information that is for the sole use of the intended recipient(s). Any disclosure, copying, distribution, posting, or use of the information contained in or attached to this email is prohibited unless permitted by the sender. If you have received this email in error, please immediately notify the sender via return email, telephone, or fax and destroy this original transmission and its included files without reading or saving it in any manner. Thank you. From gerv at mozilla.org Sun Apr 5 14:39:55 2009 From: gerv at mozilla.org (Gervase Markham) Date: Sun, 05 Apr 2009 15:39:55 +0100 Subject: Installation usability testing Message-ID: A friend of mine complained that he had tried and failed to install Bugzilla. I sat down as a sort of "hallway usability test" and watched him try and do it again, and I must say my eyes were opened as to the clarity, or otherwise, of our installation documentation. [His experience is with PHP-based things, which normally have web-based graphical installers. Have any of you ever installed Gallery ? I have. The process is wonderful.] I'd like to make some updates to our docs. Is the procedure still to file a bug, make a patch and get it reviewed? Or have we adopted a more wiki-style make-changes-and-fix-up-if-bad approach to documentation? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Sun Apr 5 15:11:25 2009 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sun, 05 Apr 2009 17:11:25 +0200 Subject: Installation usability testing In-Reply-To: References: Message-ID: <49D8CA1D.3040204@gmail.com> Le 05. 04. 09 16:39, Gervase Markham a ?crit : > I'd like to make some updates to our docs. Is the procedure still to > file a bug, make a patch and get it reviewed? Or have we adopted a more > wiki-style make-changes-and-fix-up-if-bad approach to documentation? Everything which goes into CVS must be reviewed. File a bug. LpSolit From mkanat at bugzilla.org Sun Apr 5 21:32:26 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Sun, 05 Apr 2009 14:32:26 -0700 Subject: Self-Introduction: Michael Thomas In-Reply-To: References: Message-ID: <49D9236A.3000905@bugzilla.org> Michael Thomas wrote: > * Michael Thomas Welcome! :-) > existing calls need to be moved into the DB modules and out of the > hard coded strings to allow for variance in the calls depending on the > db. If you mean that we need more sql_* functions, we can do that, although we like to avoid that as much as possible. Anything you can do with user-defined functions, that's ideal (see how we did the Oracle implementation). -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From vitaly.fedrushkov at gmail.com Mon Apr 6 04:41:53 2009 From: vitaly.fedrushkov at gmail.com (SnowyOwl) Date: Sun, 5 Apr 2009 21:41:53 -0700 (PDT) Subject: Installation usability testing References: Message-ID: On Apr 5, 9:11?pm, "Fr?d?ric Buclin" wrote: > Le 05. 04. 09 16:39, Gervase Markham a ?crit : > > I'd like to make some updates to our docs. Is the procedure still to > > file a bug, make a patch and get it reviewed? Or have we adopted a more > > wiki-style make-changes-and-fix-up-if-bad approach to documentation? > Everything which goes into CVS must be reviewed. File a bug. Documents like https://wiki.mozilla.org/Bugzilla:Win32Install already live on Wiki. It may be better/faster to put something there and then discuss and edit in bazaar style. Then let the dust settle. Then (a) make a patch for doc/* or (b) declare the whole chapter obsolete and omit it entirely, in favor of well done Wikibook (or 'Wiki book'?). _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Mon Apr 6 09:50:12 2009 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 06 Apr 2009 10:50:12 +0100 Subject: Installation usability testing In-Reply-To: References: Message-ID: On 05/04/09 16:11, Fr?d?ric Buclin wrote: > Everything which goes into CVS must be reviewed. File a bug. Have we considered using wiki-style change control? There are important differences between code and documentation. Documentation is far more accessible, and any flaws in it are far more obvious to far more people, than code. The skills necessary to improve documentation are more widely spread, and exist in a far larger proportion of the Bugzilla user base, than for the code - particularly if it's an easy-to-edit form. And the problems which may occur from less-than-perfect documentation are much less than for less-than-perfect code. This is why Wikipedia produces a pretty good encyclopaedia, but trying to do code development in that style (anyone can register and just check in) would quickly lead to an unmaintainable and buggy mess. Reading the install documentation, it hasn't changed much since I last overhauled it several years ago. There are several bits which are just plain wrong, and have been for years.[0] Now, I could produce a patch to fix them - but surely the fact that they are and have remained wrong for a significant period of time might indicate that we are not using the most appropriate maintenance model for our documentation? The appropriate amount of review for a particular type of change varies depending on time and circumstances. For example, the main project is now (belatedly) relaxing some of the super-review requirements which were originally put in place to stop incompetent Netscape engineers messing up the tree, because times have moved on. Is it time for a change here as well? Gerv [0] For example, it still recommends Bundle::Bugzilla rather than install-module.pl, which is the better solution and which we have had for 18 months (thanks, Max :-). _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Mon Apr 6 10:07:29 2009 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Mon, 06 Apr 2009 12:07:29 +0200 Subject: Installation usability testing In-Reply-To: References: Message-ID: <49D9D461.4050503@gmail.com> Le 06. 04. 09 11:50, Gervase Markham a ?crit : > The skills necessary to improve > documentation are more widely spread, and exist in a far larger > proportion of the Bugzilla user base, than for the code We still need to review it. If you write it wrong, the doc won't compile, Tinderbox will turn red, and as soon as we release a new version of Bugzilla, we cannot revert the doc (in that version). Wiki is not tied to a single release (which has advantages and disavantages, because you may talk about something which is not available in your specific version) and can be updated at any time. So as long as something is checked in into CVS, being docs or code, it must be reviewed. Colin and others are pretty fast to do such reviews anyway. > Reading the install documentation, it hasn't changed much since I last > overhauled it several years ago. There are several bits which are just > plain wrong, and have been for years. So feel free to file a bug and attach a patch. :) We all agree that some imperfect doc is better than no doc at all, and we rarely deny review based on this criteria (unless it's plain wrong or too complex to read). When we deny review, it's rather because the doc won't compile or the doc is written at the wrong location. LpSolit From gerv at mozilla.org Mon Apr 6 10:16:54 2009 From: gerv at mozilla.org (Gervase Markham) Date: Mon, 06 Apr 2009 11:16:54 +0100 Subject: Installation usability testing In-Reply-To: References: Message-ID: <49D9D696.9020006@mozilla.org> On 06/04/09 11:07, Fr?d?ric Buclin wrote: > We still need to review it. If you write it wrong, the doc won't > compile, Tinderbox will turn red, The difficulty of fixing the documentation is tied to our method of maintaining it. There's a reason Wikipedia is not maintained as a series of compilable XML documents in a CVS repository. But even so, even if we didn't start keeping them in a wiki, review is not necessary to make sure a doc compiles. A rule that "the docs must compile and all the tests run" would still make updates far more friction-free than the current system. > Wiki is > not tied to a single release (which has advantages and disavantages, > because you may talk about something which is not available in your > specific version) and can be updated at any time. I would anticipate that when we shipped a release, we could export the current version of the wiki to a static version. If there were post-release tweaks to make, we could edit the HTML of that static version directly, but this would be a rare thing. >> Reading the install documentation, it hasn't changed much since I last >> overhauled it several years ago. There are several bits which are just >> plain wrong, and have been for years. > > So feel free to file a bug and attach a patch. :) OK, but what about my major point? Loads of people have installed Bugzilla over the past 18 months, and not one of them has done this. Why not? My suggestion is because fixing the docs is far too complicated, but you may have a different suggestion. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From LpSolit at gmail.com Mon Apr 6 11:30:41 2009 From: LpSolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Mon, 06 Apr 2009 13:30:41 +0200 Subject: Installation usability testing In-Reply-To: <49D9D696.9020006@mozilla.org> References: <49D9D696.9020006@mozilla.org> Message-ID: <49D9E7E1.5030005@gmail.com> Le 06. 04. 09 12:16, Gervase Markham a ?crit : > not necessary to make sure a doc compiles. A rule that "the docs must > compile and all the tests run" would still make updates far more > friction-free than the current system. Except that almost nobody compiles the doc besides Colin, me and a few other reviewers. Many contributors have no working installation (doc-related, due to dependencies to compile them). Colin has plans to make things simpler, but I didn't hear from him for a long time. Colin? > I would anticipate that when we shipped a release, we could export the > current version of the wiki to a static version. That's not ideal, IMO. And someone would have to check all contributions to make sure someone is not adding some stupid stuff in it. > OK, but what about my major point? Loads of people have installed > Bugzilla over the past 18 months, and not one of them has done this. Why > not? Because people don't care too much about updating the doc as soon as they understood how Bugzilla works, IMHO. We have a lot of stuff on Wiki now, and the number of contributions is not larger than for the doc in CVS, I think (based on pages I watch). LpSolit _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mkanat at bugzilla.org Mon Apr 6 17:11:36 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 06 Apr 2009 10:11:36 -0700 Subject: Installation usability testing In-Reply-To: References: Message-ID: <49DA37C8.8090004@bugzilla.org> Gervase Markham wrote: > Have we considered using wiki-style change control? We considered using the Wiki for all our docs. I think there was a thread on it on this list, maybe several years ago. If it's not here, there's a chance it was a meeting that we talked about it in, and it will be in the minutes or logs somewhere. I agree that it should be easier to edit the docs. I do want to keep the following features of DocBook, however: 1) Localization. We just changed the directory structure of the docs to allow localization, so it'd be nice to keep allowing that whatever we decide. 2) Different docs for different branches. 3) (This isn't required, but it's nice.) Different formats, like text, PDF, etc. There are lots of tools and processes that the Fedora Docs project has developed that might be able to help us out, but first we have to move to having our docs compile with xmlto instead of jade. We might be able to consider adopting a commit-then-review policy for certain committers, on the docs. We'd want to be sure of their language skills, their knowledge of Bugzilla, and their technical documentation abilities, first. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From dwierenga at valueclick.com Mon Apr 6 19:54:24 2009 From: dwierenga at valueclick.com (Dan Wierenga) Date: Mon, 6 Apr 2009 12:54:24 -0700 Subject: Self-Introduction: Dan Wierenga Message-ID: <24CF2B9B9D2BCC4B8F6EA9528B63C8360CFDBF1E@LA-EXCLUST01.corp.valueclick.com> * Dan Wierenga * dwierenga on irc * Westlake, CA, U.S. * Software Engineer, part-time DBA * ValueClick, Inc. * MSSQL support for Bugzilla, but also some areas of AD/LDAP/Kerberos integration and general webservices improvement. * I've been a full-time Perl developer for 8 or so years, and a part-time MySQL/MSSQL DBA for many of those years. * I work with Michael Thomas on developing/maintaining ValueClick's internal Bugzilla installation. This email and any files included with it may contain privileged, proprietary and/or confidential information that is for the sole use of the intended recipient(s). Any disclosure, copying, distribution, posting, or use of the information contained in or attached to this email is prohibited unless permitted by the sender. If you have received this email in error, please immediately notify the sender via return email, telephone, or fax and destroy this original transmission and its included files without reading or saving it in any manner. Thank you. -------------- next part -------------- An HTML attachment was scrubbed... URL: From gerv at mozilla.org Tue Apr 7 10:23:06 2009 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 07 Apr 2009 11:23:06 +0100 Subject: Installation usability testing In-Reply-To: References: Message-ID: <49DB298A.5060103@mozilla.org> On 06/04/09 18:11, Max Kanat-Alexander wrote: > I agree that it should be easier to edit the docs. I do want to keep the > following features of DocBook, however: I don't think any of these are impossible in principle... > 1) Localization. We just changed the directory structure of the docs to > allow localization, so it'd be nice to keep allowing that whatever we > decide. MDC manages this, so I'm sure it can be done. > 2) Different docs for different branches. This is a good question. Has anyone come across a wiki which has good branching facilities? > 3) (This isn't required, but it's nice.) Different formats, like text, > PDF, etc. Is there anyone who would read a text version of the install doc in preference to the HTML these days? Wikipedia has, I just noticed, a PDF export function (which appends the entire GFDL to a 3-line article :-) so again, this is certainly possible. > There are lots of tools and processes that the Fedora Docs project has > developed that might be able to help us out, but first we have to move > to having our docs compile with xmlto instead of jade. Are Fedora Docs kept in Docbook, then? Can you tell us more about these tools? > We might be able to consider adopting a commit-then-review policy for > certain committers, on the docs. We'd want to be sure of their language > skills, their knowledge of Bugzilla, and their technical documentation > abilities, first. :-) Of course, this involves a certain amount of trust. There are many people who know a lot about one bit of Bugzilla but very little about other bits. Having just done a Unix install, I'm freshly familiar with that, but probably wouldn't be able to update the Bugzilla Security section other than improving the clarity of the English or by checking facts. One would have to trust people not to edit docs to change things they didn't know about. But I'm sure that would be fine. Social controls are better than technical ones. Another thing we might try is a "documentation conference call" or IRC meeting or similar collaboration. Several people all work on different bits of the docs at once, being present to answer questions from others like "er, is it still true that...?", then review each other's work there and then, and suggest improvements. A sort of "code sprint" for docs. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Tue Apr 7 10:25:45 2009 From: gerv at mozilla.org (Gervase Markham) Date: Tue, 07 Apr 2009 11:25:45 +0100 Subject: Installation usability testing In-Reply-To: <49D9E7E1.5030005@gmail.com> References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> Message-ID: On 06/04/09 12:30, Fr?d?ric Buclin wrote: > Le 06. 04. 09 12:16, Gervase Markham a ?crit : > > not necessary to make sure a doc compiles. A rule that "the docs must > > compile and all the tests run" would still make updates far more > > friction-free than the current system. > > Except that almost nobody compiles the doc besides Colin, me and a few > other reviewers. Many contributors have no working installation > (doc-related, due to dependencies to compile them). Right. You are arguing my point for me :-) It's too hard to contribute to the docs. > > I would anticipate that when we shipped a release, we could export the > > current version of the wiki to a static version. > > That's not ideal, IMO. And someone would have to check all contributions > to make sure someone is not adding some stupid stuff in it. Why would you have to do that particularly in that system? Just like in the current system, if you find a problem, you fix it when you find it. > > OK, but what about my major point? Loads of people have installed > > Bugzilla over the past 18 months, and not one of them has done this. Why > > not? > > Because people don't care too much about updating the doc as soon as > they understood how Bugzilla works, IMHO. We have a lot of stuff on Wiki > now, and the number of contributions is not larger than for the doc in > CVS, I think (based on pages I watch). Well, I didn't even know there were docs in the wiki, and they aren't linked to from here: http://www.bugzilla.org/docs/ so perhaps it's because people don't know about them? What docs do we currently keep in wiki form? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From eblack at higherone.com Tue Apr 7 16:33:45 2009 From: eblack at higherone.com (Eric Black) Date: Tue, 7 Apr 2009 12:33:45 -0400 Subject: Installation usability testing In-Reply-To: <49DB298A.5060103@mozilla.org> References: , <49DB298A.5060103@mozilla.org> Message-ID: <4F91EB003F5C784084736E717AB5AFCA313207B9@mail02.higherone.com> >Is there anyone who would read a text version of the install doc in >preference to the HTML these days? Just my two cents, but yes, I prefer text to HTML because I can read it in emacs or from the command line without a utility, which on some of our servers, we might not have. If I want a portable doc, I always prefer pdf. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From m.thomas at valueclick.com Tue Apr 7 16:42:49 2009 From: m.thomas at valueclick.com (Michael Thomas) Date: Tue, 7 Apr 2009 09:42:49 -0700 Subject: Installation usability testing In-Reply-To: <4F91EB003F5C784084736E717AB5AFCA313207B9@mail02.higherone.com> References: , <49DB298A.5060103@mozilla.org> <4F91EB003F5C784084736E717AB5AFCA313207B9@mail02.higherone.com> Message-ID: If you're on a command line, like many of us are, then yes it likely that text is preferred. Not to say that both wouldn't be a bad idea. Though possibly annoying to maintain. -----Original Message----- From: dev-apps-bugzilla-bounces+m.thomas=valueclick.com at lists.mozilla.org [mailto:dev-apps-bugzilla-bounces+m.thomas=valueclick.com at lists.mozilla. org] On Behalf Of Eric Black Sent: Tuesday, April 07, 2009 9:34 AM To: dev-apps-bugzilla at lists.mozilla.org Subject: RE: Installation usability testing >Is there anyone who would read a text version of the install doc in >preference to the HTML these days? Just my two cents, but yes, I prefer text to HTML because I can read it in emacs or from the command line without a utility, which on some of our servers, we might not have. If I want a portable doc, I always prefer pdf. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla This email and any files included with it may contain privileged, proprietary and/or confidential information that is for the sole use of the intended recipient(s). Any disclosure, copying, distribution, posting, or use of the information contained in or attached to this email is prohibited unless permitted by the sender. If you have received this email in error, please immediately notify the sender via return email, telephone, or fax and destroy this original transmission and its included files without reading or saving it in any manner. Thank you. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From eblack at higherone.com Tue Apr 7 20:50:57 2009 From: eblack at higherone.com (Eric Black) Date: Tue, 7 Apr 2009 16:50:57 -0400 Subject: Self-Introduction: Eric Black Message-ID: <4F91EB003F5C784084736E717AB5AFCA313207BE@mail02.higherone.com> * Eric Black * New Haven, CT, US * Software Engineer * Higherone, Inc * I'm not sure yet, maybe someone will tell me :) * Historical qualifications o Mostly Perl and Java web applications, C/C++ long ago o I'm a senior level developer in Perl with extensive *nix skills o My role for the past 10 years at different companies has been to mediate and automate developer and ops processes I'm really just starting to look at Bugzilla since I'm responsible for it now. We have a 2.18.3 version installed and it's highly customized, used for many different processes, including many non-technical uses. My task at the moment is to upgrade it to the latest version and to make the customizations non-intrusive for later upgrades of Bugzilla. After I accomplish the upgrade, there is a slew of more customizations that are requested by the organization. Additionally, I need a workflow engine and I intend to customize, hopefully by the use of hooks, bugzilla as the engine, even if it's a separate instance. That was one suggestion from the developers of a deployment engine I've been implementing, ControlTier (http://apps.sourceforge.net/mediawiki/controltier/index.php?title=Main_Page). So as I said, I don't really have much to offer yet, but I hope to soon. Also, assuming I don't find a bug for something that I need to customize, does it make more sense to run it by this list before submitting a bug, or should I submit the bug first? From mkanat at bugzilla.org Tue Apr 7 23:59:30 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 07 Apr 2009 16:59:30 -0700 Subject: Installation usability testing In-Reply-To: References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> Message-ID: <49DBE8E2.2030704@bugzilla.org> Gervase Markham wrote: > Well, I didn't even know there were docs in the wiki, and they aren't > linked to from here: http://www.bugzilla.org/docs/ so perhaps it's > because people don't know about them? Actually, we do link them, but the link is kind of hard to see even though it's right at the top of the page. "Frequently Asked Questions." > What docs do we currently keep in wiki form? http://wiki.mozilla.org/Bugzilla Mostly things that are more appropriate to wiki-ness. Development-related things, short tips and tricks for people, particularly user-contributed ones. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From mkanat at bugzilla.org Wed Apr 8 00:05:12 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 07 Apr 2009 17:05:12 -0700 Subject: Self-Introduction: Eric Black In-Reply-To: <4F91EB003F5C784084736E717AB5AFCA313207BE@mail02.higherone.com> References: <4F91EB003F5C784084736E717AB5AFCA313207BE@mail02.higherone.com> Message-ID: <49DBEA38.2020005@bugzilla.org> Eric Black wrote: > * I'm not sure yet, maybe someone will tell me :) Well, the Good Intro Bugs are always a good place to start! :-) https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3ABugzilla+whiteboard%3A%22[Good+Intro+Bug]%22 > Additionally, I need a workflow engine and I intend to customize, > hopefully by the use of hooks, bugzilla as the engine, even if it's a > separate instance. That was one suggestion from the developers of a > deployment engine I've been implementing, ControlTier (http://apps.sourceforge.net/mediawiki/controltier/index.php?title=Main_Page). You and Yahoo are both working on this, perhaps you could come to a consensus about it or pool your research. > Also, assuming I don't find a bug for something that I need to > customize, does it make more sense to run it by this list before > submitting a bug, or should I submit the bug first? Um, you could chat it up on IRC a little bit if you want first, that's usually the best way, if the devs are around when you're on. Otherwise you can file a bug. I'm assuming you mean that you want to add hooks or something. Often we won't implement upstream something that people customize, because it's valuable as a local customization, but not valuable everywhere in every Bugzilla. However, hooks are something we'll almost always approve (though I believe the current hooks system has a performance problem, so we wouldn't take hooks in performance-critical areas). -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From eblack at higherone.com Wed Apr 8 14:06:51 2009 From: eblack at higherone.com (Eric Black) Date: Wed, 8 Apr 2009 10:06:51 -0400 Subject: Self-Introduction: Eric Black In-Reply-To: <49DBEA38.2020005@bugzilla.org> References: <4F91EB003F5C784084736E717AB5AFCA313207BE@mail02.higherone.com>,<49DBEA38.2020005@bugzilla.org> Message-ID: <4F91EB003F5C784084736E717AB5AFCA313207C0@mail02.higherone.com> > Well, the Good Intro Bugs are always a good place to start! :-) > https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3ABugzilla+whiteboard%3A%22[Good+Intro+Bug]%22 Thanks. I'll look for something easy to get my feet wet. > You and Yahoo are both working on this, perhaps you could come to a >consensus about it or pool your research. I tried searching for information about this, but I couldn't find anything. Is there a link or anybody I could contact about this? Thanks for the additional information! From dmarshal at yahoo-inc.com Wed Apr 8 16:05:11 2009 From: dmarshal at yahoo-inc.com (David Marshall) Date: Wed, 08 Apr 2009 09:05:11 -0700 Subject: Self-Introduction: Eric Black In-Reply-To: <4F91EB003F5C784084736E717AB5AFCA313207C0@mail02.higherone.com> Message-ID: On 4/8/09 7:06 AM, "Eric Black" wrote: > >> Well, the Good Intro Bugs are always a good place to start! :-) >> >> https://bugzilla.mozilla.org/buglist.cgi?quicksearch=prod%3ABugzilla+whiteboa >> rd%3A%22[Good+Intro+Bug]%22 > > Thanks. I'll look for something easy to get my feet wet. > [regarding workflow engines] >> You and Yahoo are both working on this, perhaps you could come to a >> consensus about it or pool your research. > > I tried searching for information about this, but I couldn't find anything. Is > there a link or anybody I could contact about this? This is something on which we're just starting to the point that we haven't even begun gathering specific requirements. You can contact me (or Fergus Sullivan) about this, but I think it will be a while before we have anything concrete. From gerv at mozilla.org Wed Apr 8 18:44:46 2009 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 08 Apr 2009 19:44:46 +0100 Subject: Installation usability testing In-Reply-To: References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> Message-ID: On 08/04/09 00:59, Max Kanat-Alexander wrote: > Mostly things that are more appropriate to wiki-ness. > Development-related things, short tips and tricks for people, > particularly user-contributed ones. Before I go and write some, is there any current documentation on setting up the docs build environment? I looked in the directory itself, the Bugzilla Guide, on the wiki, and did some Googling but can't find anything. Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mkanat at bugzilla.org Wed Apr 8 23:09:21 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 08 Apr 2009 16:09:21 -0700 Subject: Installation usability testing In-Reply-To: References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> Message-ID: <49DD2EA1.7070001@bugzilla.org> Gervase Markham wrote: > Before I go and write some, is there any current documentation on > setting up the docs build environment? I looked in the directory itself, > the Bugzilla Guide, on the wiki, and did some Googling but can't find > anything. The README in the docs directory. I believe it's in docs/en these days. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From mkanat at bugzilla.org Thu Apr 9 02:03:37 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 08 Apr 2009 19:03:37 -0700 Subject: Installation usability testing In-Reply-To: References: Message-ID: <49DD5779.20402@bugzilla.org> By the way, I just want to make it clear in this thread that no matter what we do in the future, we absolutely should fix the installation instructions that we have ASAP. I'd be happy to help anybody do it if they need some assistance or reviews. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From bugzilla at colinogilvie.co.uk Thu Apr 9 07:03:47 2009 From: bugzilla at colinogilvie.co.uk (Colin Ogilvie) Date: Thu, 09 Apr 2009 08:03:47 +0100 Subject: Installation usability testing In-Reply-To: <49DD2EA1.7070001@bugzilla.org> References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> <49DD2EA1.7070001@bugzilla.org> Message-ID: <49DD9DD3.4070402@colinogilvie.co.uk> On 09/04/2009 00:09, Max Kanat-Alexander wrote: > Gervase Markham wrote: > >> Before I go and write some, is there any current documentation on >> setting up the docs build environment? I looked in the directory itself, >> the Bugzilla Guide, on the wiki, and did some Googling but can't find >> anything. >> > > The README in the docs directory. I believe it's in docs/en these days. > Yup, and I don't believe it's changed recently, as I've not made as much progress as I hoped on changing it! Work and personal life getting in the way, but hopefully I'll pick it up again in the next couple of weeks. I've found it easier to use landfill to build the docs though, than trying to set it up locally! I'll have to have a catch-up on what's been raised in this thread, though and respond at some point. Colin -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpsolit at gmail.com Thu Apr 9 09:37:55 2009 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Thu, 09 Apr 2009 11:37:55 +0200 Subject: Installation usability testing In-Reply-To: <49DD9DD3.4070402@colinogilvie.co.uk> References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> <49DD2EA1.7070001@bugzilla.org> <49DD9DD3.4070402@colinogilvie.co.uk> Message-ID: <49DDC1F3.4060702@gmail.com> Le 09. 04. 09 09:03, Colin Ogilvie a ?crit : >> The README in the docs directory. I believe it's in docs/en these days. I did exactly what is written in README, and I have a fully functional installation, locally. I don't think it needs a lot of changes. But I agree that it's not straightforward. :) LpSolit From jmdesp at alussinan.org Thu Apr 9 11:03:00 2009 From: jmdesp at alussinan.org (Jean-Marc Desperrier) Date: Thu, 09 Apr 2009 13:03:00 +0200 Subject: Installation usability testing In-Reply-To: <49D9E7E1.5030005@gmail.com> References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> Message-ID: Fr?d?ric Buclin wrote: > Because people don't care too much about updating the doc as soon as > they understood how Bugzilla works, IMHO. When people evaluate bugs system, they first thing they do is install them. And when they can not install them following the instructions, evaluation is over. Been there, *seen* that. That's why good install instructions are so important to win new users, and not as you describe here something completely subsidiary because hey old user don't care about it, they already know. Bugzilla is loosing a lot a potentil "market share" because of that. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From jmdesp at alussinan.org Thu Apr 9 11:10:40 2009 From: jmdesp at alussinan.org (Jean-Marc Desperrier) Date: Thu, 09 Apr 2009 13:10:40 +0200 Subject: Installation usability testing In-Reply-To: <49DB298A.5060103@mozilla.org> References: <49DB298A.5060103@mozilla.org> Message-ID: Gervase Markham wrote: > Has anyone come across a wiki which has good branching facilities? Making good use of hierarchy in the wiki could solve that problem. You always write the doc for the current development version in https://wiki.mozilla.org/Bugzilla:Install But when a new version is released, you duplicate the current state of it inside https://wiki.mozilla.org/Bugzilla:3.4:Install _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From eblack at higherone.com Thu Apr 9 13:27:54 2009 From: eblack at higherone.com (Eric Black) Date: Thu, 9 Apr 2009 09:27:54 -0400 Subject: Installation usability testing In-Reply-To: <49DDC1F3.4060702@gmail.com> References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> <49DD2EA1.7070001@bugzilla.org> <49DD9DD3.4070402@colinogilvie.co.uk>,<49DDC1F3.4060702@gmail.com> Message-ID: <4F91EB003F5C784084736E717AB5AFCA313207C3@mail02.higherone.com> > I did exactly what is written in README, and I have a fully functional > installation, locally. I don't think it needs a lot of changes. But I > agree that it's not straightforward. :) I sent this information to the support list for trying to build the docs on Gentoo, wondering if there was a wiki spot for it. The instructions didn't work very well for me. I'd be happy to help with setup, testing, and documentation, but I don't know docbook well or the packages it requires. Here's my earlier email: Hi, I'm not really sure what I what I should do with the information I obtained from trying to create the html documentation on Gentoo, but I'm sure someone else may attempt it and I thought it should be someplace that could help them. Could someone direct me to what I should do with it, like should I open a bug or put it in the wiki, or give it to someone to put someplace, etc. I'm happy where I'm at now, and I'm neither a Gentoo or DocBook master so the errors may be apparent for someone who knows more about it. These are my notes, followed by the warnings and errors: For the docs: Don't follow all the directions from the README.docs file. It's good starting point, but not much else. I had alot of problems with this, so from researching: # Write the dependencies for docbook-sgml-utils emerge -pe docbook-sgml-utils | grep -i 'sgml\|xml\|docbook|\template' > depends # Remove all the initial stuff vi depends # Add the = sign and create depends2 sed -e 's,^,=,' < depends > depends2 && rm depends # This is what would be left and then add the jade stuff =dev-perl/SGMLSpm-1.03-r5 =app-doc/xorg-sgml-doctools-1.2 =app-text/sgml-common-0.6.3-r5 =app-text/docbook-sgml-1.0 =app-text/docbook-sgml-dtd-4.4 =app-text/docbook-xml-simple-dtd-4.1.2.4-r2 =dev-libs/libxml2-2.7.3 =app-text/docbook-xml-simple-dtd-1.0-r1 =app-text/docbook-xml-dtd-4.4-r1 =app-text/docbook-dsssl-stylesheets-1.79 =app-text/jadetex-3.13-r2 =app-text/openjade-1.3.2-r1 =app-text/sgmltools-lite-3.0.3-r10 =app-text/docbook-sgml-utils-0.6.14 # Then run the emerge command emerge -avO1 $(< depends2) # Go get the ldp.dsl file from tdlp.org/resources (see README.docs) and put here: mkdir /usr/share/sgml/docbook/ldp # Then edit these lines in the file ]]> ]]> # Export your environment export PERL5LIB=/usr/local/bugzilla-3.2.2/perl/lib export SGML_CATALOG_FILES=/etc/sgml/catalog # This is in the /etc/profile.env file, but in case it isn't (it seemed to work the same without the variable set as well) export SGML_CATALOG_FILES='/etc/sgml/sgml-docbook-4.4.cat:/etc/sgml/openjade-1.3.2.cat:/etc/sgml/xml-simple-docbook-1.0.cat:/etc/sgml/sgml-ent.cat:/etc/sgml/xml-docbook-4.4.cat:/etc/sgml/xml-simple-docbook-4.1.2.4.cat:/etc/sgml/dsssl-docbook-stylesheets.cat:/etc/sgml/sgml-docbook.cat:/etc/sgml/sgml-lite.cat' export LDP_HOME=/usr/share/sgml/docbook/ldp export JADE_PUB=/usr/share/sgml # Run makedocs.pl # ./docs/makedocs.pl cp ../bugzilla.ent ./xml/ Creating API documentation... Creating separate HTML documentation ... jade -t sgml -i html -d /usr/share/sgml/docbook/ldp/ldp.dsl#html /usr/share/sgml/xml.dcl ../xml/Bugzilla-Guide.xml jade:../xml/Bugzilla-Guide.xml:2:61:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook XML V4.1.2//EN" jade:../xml/Bugzilla-Guide.xml:48:0:E: reference to entity "book" for which no system identifier could be generated jade:../xml/Bugzilla-Guide.xml:2:0: entity was defined here jade:../xml/installation.xml:2345:45:W: cannot generate system identifier for general entity "mdash" jade:../xml/installation.xml:2345:50:E: reference to entity "mdash" for which no system identifier could be generated jade:../xml/installation.xml:2345:44: entity was defined here jade:../xml/installation.xml:2347:22:E: reference to entity "mdash" for which no system identifier could be generated jade:../xml/installation.xml:2345:44: entity was defined here jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'gfdl' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/../common/dbtable.dsl:224:13:E: 2nd argument for primitive "ancestor" of wrong type: "#" not a singleton node list jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/../common/dbtable.dsl:224:13:E: 2nd argument for primitive "ancestor" of wrong type: "#" not a singleton node list jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'os-specific' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'configuration' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'win32-perl-modules' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'install-perlmodules-manual' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'suexec' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'mysql' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'postgresql' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'oracle' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-mysql' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'localconfig' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'localconfig' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-webserver-access' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-webserver-access' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'troubleshooting' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'extraconfig' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'whining' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'install-perlmodules' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-webserver-access' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'install-perlmodules-nonroot' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'sanitycheck' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-cvs' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-tarball' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-patches' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'template-method' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-cvs' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'configuration' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'sanitycheck' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'savedsearches' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'bzldap' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'classifications' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'components' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'components' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'versions' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'milestones' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'group-control-examples' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'flags-create' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'sanitycheck' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-values-list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-values-list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'bugreports' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-values-list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'param-group-security' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'users-and-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'useradmin' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'create-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-os-accounts' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-mysql-account-root' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-os-ports' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http-apache' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'lifecycle-image' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'savedsearches' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'userpreferences' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'cust-change-permissions' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation-whining' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation-whining-cron' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'template-http-accept' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'cvs' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'tinderbox' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'configuration' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http-apache' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'modules-manual-download' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http-apache' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-mysql' Creating big HTML documentation ... jade -V nochunks -t sgml -i html -d /usr/share/sgml/docbook/ldp/ldp.dsl#html /usr/share/sgml/xml.dcl ../xml/Bugzilla-Guide.xml > Bugzilla-Guide.html jade:../xml/Bugzilla-Guide.xml:2:61:W: cannot generate system identifier for public text "-//OASIS//DTD DocBook XML V4.1.2//EN" jade:../xml/Bugzilla-Guide.xml:48:0:E: reference to entity "book" for which no system identifier could be generated jade:../xml/Bugzilla-Guide.xml:2:0: entity was defined here jade:../xml/installation.xml:2345:45:W: cannot generate system identifier for general entity "mdash" jade:../xml/installation.xml:2345:50:E: reference to entity "mdash" for which no system identifier could be generated jade:../xml/installation.xml:2345:44: entity was defined here jade:../xml/installation.xml:2347:22:E: reference to entity "mdash" for which no system identifier could be generated jade:../xml/installation.xml:2345:44: entity was defined here jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'gfdl' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/../common/dbtable.dsl:224:13:E: 2nd argument for primitive "ancestor" of wrong type: "#" not a singleton node list jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/../common/dbtable.dsl:224:13:E: 2nd argument for primitive "ancestor" of wrong type: "#" not a singleton node list jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'os-specific' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'configuration' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'win32-perl-modules' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'install-perlmodules-manual' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'suexec' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'mysql' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'postgresql' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'oracle' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-mysql' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'localconfig' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'localconfig' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-webserver-access' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-webserver-access' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'troubleshooting' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'extraconfig' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'whining' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'install-perlmodules' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-webserver-access' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'install-perlmodules-nonroot' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'sanitycheck' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-cvs' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-tarball' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-patches' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'template-method' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'upgrade-cvs' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'configuration' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'sanitycheck' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'savedsearches' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'bzldap' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'classifications' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'components' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'components' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'versions' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'milestones' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'group-control-examples' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'flags-create' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'sanitycheck' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-values-list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-values-list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'bugreports' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-values-list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'param-group-security' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'users-and-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'parameters' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'useradmin' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'edit-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'create-groups' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'product-group-controls' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-os-accounts' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-mysql-account-root' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-os-ports' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http-apache' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'lifecycle-image' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'savedsearches' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'userpreferences' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'cust-change-permissions' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation-whining' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation-whining-cron' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'list' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'template-http-accept' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblists.dsl:331:40:E: no clause in cond expression matched jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'cvs' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'tinderbox' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'installation' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'configuration' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http-apache' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'modules-manual-download' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'http-apache' jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dbhtml.dsl:28:23:E: 1st argument for primitive "number->string" of wrong type: "#f" not a number jade:/usr/share/sgml/docbook/dsssl-stylesheets-1.79/html/dblink.dsl:203:1:E: XRef LinkEnd to missing ID 'security-mysql' Creating big text documentation ... lynx -dump -justify=off -nolist Bugzilla-Guide.html > ../txt/Bugzilla-Guide.txt Thanks, Eric From gerv at mozilla.org Fri Apr 10 13:51:03 2009 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 10 Apr 2009 14:51:03 +0100 Subject: Installation usability testing In-Reply-To: References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> Message-ID: <49DF4EC7.2010103@mozilla.org> On 09/04/09 00:09, Max Kanat-Alexander wrote: > The README in the docs directory. I believe it's in docs/en these days. Ah, right. I guess I expected docs/en to contain the Bugzilla docs in English, rather than the doc about building the docs. :-) Perhaps this needs to live with other "hacking on Bugzilla" documents in the wiki? Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From gerv at mozilla.org Fri Apr 10 13:51:25 2009 From: gerv at mozilla.org (Gervase Markham) Date: Fri, 10 Apr 2009 14:51:25 +0100 Subject: Installation usability testing In-Reply-To: References: <49D9D696.9020006@mozilla.org> <49D9E7E1.5030005@gmail.com> <49DD2EA1.7070001@bugzilla.org> Message-ID: On 09/04/09 08:03, Colin Ogilvie wrote: > I've found it easier to use landfill to build the docs though, than > trying to set it up locally! More evidence, if any were needed... :-) Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Fri Apr 10 23:05:37 2009 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Sat, 11 Apr 2009 01:05:37 +0200 Subject: Bugzilla meeting next Tuesday, April 14, 11:00 PDT Message-ID: <49DFD0C1.8000000@gmail.com> Hello, Our next Bugzilla meeting will take place on Tuesday, April 14, at 11:00 PDT (20:00 CEST, 18:00 GMT) in the #bugzilla-meeting channel on IRC (irc.mozilla.org). Everyone is free to attend, as usual. The agenda is available here: https://wiki.mozilla.org/Bugzilla:Meetings Everyone is free to add new items to it. See you on Tuesday, LpSolit From autocad at 2010.com Sun Apr 12 00:35:59 2009 From: autocad at 2010.com (autodesk autocad electrical 2010 full download ) Date: Sat, 11 Apr 2009 21:35:59 -0300 Subject: autocad electrical 2010 autodesk full download crack torrent rapidshare 87712586 Message-ID: email = xshowsoft at gmail.com email = xshowsoft at gmail.com autocad electrical 2010 full download crack torrent rapidshare autocad electrical 2010 download autocad electrical 2010 crack autocad electrical 2010 full download autocad electrical 2010 torrent download autocad electrical 2010 torrent autocad electrical 2010 rapidshare autocad electrical 2010 megaupload autocad electrical 2010 autodesk email = xshowsoft at gmail.com email = xshowsoft at gmail.com Artpro 7.6. Rev. 4 k[ed] Artpro 8.1 k[ed] Artpro 9.0 rev. 1 build 2 CREO (Kodak) Preps v5.3.2 Founder ElecRoc v4.626 Onyx ProductionHouse v7.1 EFI colorproof k[ed] PC only Esko Deskpack V7. r4 Mac only Esko Softwares Suite V7. r4. PC/Mac all options enabled Esko Ripmate V7 Heidelberg Prinect Workflow 4.0.540 included: - PrintReady 4.0 - Prinect Prepress Manager - Prinect Postpress Manager - Prinect Pressroom Manager - Prinect Production Manager - Prinect Cockpit 4 - Analyze Point 4.0.394.1 - JDF Connector Service 4.0.394.1 - JDF Storage Service 4.0.394.1 - JMF Message Service 4.0.394.1 - Master Data Service 4.0.394.1 - Service Tools Heidelberg DeltaRIP 8.5 Heidelberg PDF Toolbox v4.0 Heidelberg SignaStation v4 Others: ACC HSH Group PDF Tools 2.4 ACC HSH Group PuzzleFlow 2.3 Acrobotics PDF-SuperTool 1.0 Advanced PECOM 2.9 AGFA Apogee Create 1.0 Series 2 & 3 AGFA Apogee Cristal Raster 2.5 AGFA Apogee PDF RIP 2.0 Update 6 Series 3 AGFA Apogee Pilot 1.0 AGFA Apogee PrintDrive 1.0 Series 3 AGFA Apogee Taipan RIP 3.1 ALAP Imposer Pro 1.1.1 (InDesign plugin) Apago PDF Enhancer 2.6 Apago Piktor 3.0 ARTS Split Pro 1.3.1 Artwork Systems Nexus 7.5 Artwork Systems ArtPro 7.5 (MAC) Aurelon Signalize! RIP 5.7.0 BasICColor Catch 2.50 BasICColor Dcam 2.0.1 BasICColor Display 3.0.3 BasICColor Print3c 2.0.2 BasICColor Print4c 2.0.2 BasICColor Scan Plus 2.0.1 BasICColor Server 1.1.0 BrainNew EconoInk 1.3.7 BrainNew ImageHarbor PostRIP Imposition 5.01 CADlink SignLab 7.1 Cadvantage Win Printex 5.0 CGS ORIS Certified Proof 1.2 CGS ORIS Color Tuner 5.1.2 CGS ORIS PDF Tuner 4.2.6 CHROMiX ColorThink 2.1.2 ColorBlind Professional 5.1.3 ColorBurst RIP 7.50 ColorFacts Professional 5.50 - NEW ColorGATE PhotoRIP 3.8.4.613 ColorGATE PHOTOGATE 4.05 ColorGATE PRODUCTIONSERVER 4.06 (with FILMGATE) ColorGATE PROOFGATE 4.05 ColorGATE Screen & Sign 3.8.4.613 ColorMetrix ProofPass 1.8.10 + Trending 1.1.4 ColorSpan ColorMark Legacy SW RIP 8.82-LSR ColorSpan ColorMark PRO SW RIP 8.94 Colour Chameleon 2.0 Colour Matters CM32 3.24 Colorbytesoftware ImagePrint 5.6 Compose Express Colorflow 1.01 + all components Compose Express Flatout Express 2.2 Compose Express PDF Imposition 4.0 Compose Express Plate Controller 1.3 Compose Express PRI Station 2.1 Compose Express Raster PrintStation 2.2 Compose Express Workflow 2.4 Creo CopyDot ToolKit 4.0 Creo Pandora 2.7 Creo Preps 5.1.2 (PC & MAC) Creo Print Console 3.5 Creo Prinergy 3.0.2.1 Creo PS/M 7.1, 8.0 (for MAC) Creo Synapse Prepeare Pro 1.1 (for MAC) Creo TrapWise 3.6 CSIP Printer System 1.01 Dainippon SCREEN PixelStream 4.6 (Impos2000 Server, InkProof) Dainippon SCREEN SPEKTA 6.x Devstudio Power Plotter 5.4.26 DGS MatchPrint II 4.05 DGS Portrait 2 3.31 DGS Ramsete III 8.55 DigiFab Systems Evolution RIP 3.2.5.8 Digital Light & Color Profile Mechanic-Sanner 1.0.0.3 Dynagram DynaStrip 4.4.0 Ergosoft PosterPrint 11.0.1 Ergosoft StudioPrint 11.0.1 Ergosoft TexPrint 11.0.1 ECRM MAXWorkFlow 3.5 (all modules) EFI BEST ColorProof 5.0.1 SP2 (XXL and Laser) EFI BEST PhotoXposure XXL 5.0.1 SP2 EFI BEST ScreenProof 5.0.1 SP2 (Full and 4UP) EFI BEST Premium Addon 1.1.0 EFI ColorProof XF 2.6.1 SP1 - NEW Enfocus Instant PDF 3.02 (Acrobat plugin) Enfocus PitStop Server 3.0 EFI ColorProof XF 3.1 ESKO-Graphics FlexoPERfection 7.0 ESKO-Graphics ArtiosCAD 6.02 ESKO-Graphics ColorTone 2.1 ESKO-Graphics ColorQuartet Pro 5.2.2 ESKO-Graphics BackStage 2.0 (standalone) ESKO-Graphics BackStageEdit 4.0 ESKO-Graphics DeskPack Adoble Illustrator client for BackStage 1.2/2.0 ESKO-Graphics FlexoPERfection 3.2.08 - NEW ESKO-Graphics FlexRIP 5.2 ESKO-Graphics FlexRIP Pilot 2.0 (like BackStage 2.0 but needs FlexRIP) ESKO-Graphics PackEdge 4.0 ESKO-Graphics Plato 4.0 ESKO-Graphics RipMate 5.1 EUROSYSTEMS Pjannto RIP 1.4.3 ExtremeZ-IP 4.0.4x17 Eyes3D 1.0 EngView Synergy 3.6.15 EUROSYSTEMS CoCut 11 Pro EUROSYSTEMS EuroCUT 6.0.40 Pro EUROSYSTEMS SmartCUT 6.0.44 Pro Express Digital Darkroom Assembly Edition 8.61 Express Digital Darkroom Professional 8.61 FastFilms 3.5 (Photoshop plugin) FastRIP Regular/Pro/LF 8.0 Flip! Super 3D Genius 1.5 Franklin Estimator 4.04 Founder EagleDot 3.5 Founder EagleProof 3.5 Founder EagleRIP 3.0 (build 3418) Founder EagleRIP 4.0 + EagleFAM 1.0 Founder EagleRIP V8 + EagleFAM 1.0 Founder SuperLine 4.03 (Chinese) FotoWare Color Factory 3.1 FotoWare Distribution Manager 4.0 FotoWare FotoWeb 2.5 FotoWare Index Manager 4.5 Fuji ColourKit Profiler Suite 4.2 GMG Colorproof 3.3.75 Graphx RasterPlus 5.2.12 GretagMacbeth Color Quality 3.6 GretagMacbeth Color iMatch 3.64 GretagMacbeth iCPrint 1.2.0 GretagMacbeth iQueue 1.1.5 GretagMacbeth Ink Formulation 5.01 GretagMacbeth KeyWizard 2.5 GretagMacbeth MultiColor Separation/Proof 1.2 (Photoshop plugin) GretagMacbeth ProfileMaker Pro 5.0.4 (PC & MAC) GretagMacbeth ProPalette 5.2.3.1 GretagMacbeth SpectoChart 1.21 GretagMacbeth TabWizard 1.0 Gerber Scientific OMEGA 2.1 - NEW Husqvarna Viking VIP Embroidery System 6.2 Koppermann Tex-Define 6.0 - FULL CD Koppermann Tex-Design 6.0 - FULL CD Koppermann Tex-Store 6.0 - FULL CD MOST Visual Studio - Artist 3.3 MOST Visual Studio - Coloring & 3D 5.99 MOST Visual Studio - Dobby 5.99 MOST Visual Studio - Design 5.16 Harlequin Compose Express RIP 7.0 Harlequin ECRM RIP 6.4 Harlequin HighWater Designs Torrent RIP 7.0 Harlequin Dainippon HQ-510PC SCREEN 6.4 Harlequin JET RIP 5.51a Harlequin RTI RIP-Kit 6.2 Harlequin Xitron Navigator RIP 7.0 Harlequin Xitron SDP-RIP 6.0 Heidelberg Delta Technology 8.2 - NEW Heidelberg PDF Toolbox 2.0.38 (Acrobat plugin) Heidelberg Prinect Profile Toolbox 1.1 (PrintOpen 5.1 + QualityMonitor 1.1) Heidelberg Prinect Signa Station 1.5.2 Heidelberg PrepressInterface 3.2 - NEW Heidelberg SignaStation 9.0.4 OLD Heidelberg MetaDimension 5.2 - NEW Heidelberg MetaShooter 2.2 - NEW Heidelberg NewColor 7000 2.0.0 HighWater Designs Herkules Calibration Tool 1.0 HighWater Designs HWRoam 1.3 HighWater Designs InkMonitor 3.3.1 HighWater Designs PixelProof Print Server 1.3 HighWater Designs Q2 Output Controller 4.1.3 Heidelberg Delta Technology 8.2 Heidelberg MetaDimension 5.2 Heidelberg MetaShooter 2.2 Howtek Trident Drum & 2500 Scanner 3.7.1 Imposition Publisher 4.6.4 (PC & MAC) - NEW iProof PowerRIP ImageSet 7.2.5 iProof PowerRIP SilkScreen 7.2.5 ISITooolbox 5.0.02 build 4001 (Acrobat plugin) KODAK Professional Digital Print Production Software 5.1.27 KoreaSoft Artist RIP & Cut Pro 9.0 Krause Imposition Manager PDF 5.0.0 Kimoto AttractProof 3.5 LaserSoft SilverFast 6.4.1r2 MonacoDCcolor 1.0.0 MonacoEZcolor 2.5 MonacoPROFILER 4.6.1 Platinum (MAC) MonacoPROFILER 4.8.0 Platinum - NEW MonacoPROOF 3.7.1 Nfive Cardfive 6.3 ODESSA LaserPROOF 3.3.0.6 Onyx PosterShop 6.0 Onyx ProductionHouse 6.0 SP2 (all printers) PANTONE ColorDrive 1.5 PANTONE ColorVision ProfilerPRO 3.0.1 (Photoshop plugin) PANTONE HexWare 2.5 (Illustrator/Photoshop plugin) PerfectProof ProofMaster 2.0.7 Phase One C1 PRO 3.5 Plug-In Systems Packagizer 1.199 PosterJet RIP 6.5.7 PrePRESS Panther RIP 10.4 PrePRESS Panther PageImposer 10.3 PrintShop Mail 5.0.6 PrintSmith 6.3.2 PolyPattern 3.5v3 Q-Enhancer 2.1 RIPit OpenRIP Workflow 2000 3.0 RPM Remote Print Manager 4.5 ScanvecAmiable PhotoPRINT Server Pro 4.6v2 ScitexVision PressJet 2.6.1 Septone 7.0 Release 1.4 (Photoshop plugin) Seagull BarTender 7.72 Serendipity BlackMagic 3.1 - NEW Serendipity Megarip 4.1 - NEW Shiraz RIP 6.0 ThunderStorm RIP Pro 6.40 (Korean) TECHKON ExPresso 2.1 Teklynx CODESOFT 7.10 Ultimate Impostrip 8.1.0.4 Ultimate Impostrip On-Demand 4.2.0.0 Wasatch SoftRIP 5.1.5 - NEW Wincomsoft RipMaster 1.230.4.729 ScanvecAmiable FlexiSIGN Pro 7.6v2 ScanvecAmiable Inspire 1.6 SGS OptiTex 9.20 Smart Designer 12 Tajima DG/ML by Pulse X 11.0.5.2633 - NEW USM2 1.14 - 2D Grading/Engineering USM3 1.04 - 3D Shoe Design Wilcom ES-65 9.0S SP4 WingsXP 1.50.2002.29 Colorave Imaginator 7.6.2 ConeTech Piezography BW Pro24 4.2.0 ISIS Photoi Mini KIOSK (DigiCube) 1.0 ISIS Photoi Minilab 1.6 Master Flex D Minilab & Workstation 3.0.138 Micro-Art Imaging Composite 5.0 PhotoLynx Solutions 1.6 - CamLynx 4.0 PhotoLynx Solutions 1.6 - PhotoLynx ImageMatch 6.0 PhotoLynx Solutions 1.6 - PhotoLynx ProComposites 6.1 PhotoLynx Solutions 1.6 - PhotoLynx ProServices 6.0 PhotoLynx Solutions 1.6 - PhotoLynx School Image Software (SIS) 5.5 Timestone Software - CapturePost 2.6.0 Timestone Software - Collate 2.2.0 Timestone Software - CompositeBuilder 1.0.0 Timestone Software - DataPost 2.6.1 Timestone Software - NeoComposite 2.4.0 Timestone Software - NeoGroup 2.5.0 Timestone Software - NeoPack Professional 2.8.0 Timestone Software - OutPost 1.4.0 Timestone Software - PrintTime 1.11.0 Timestone Software - RIPTime 1.7.0 Ultimatte AdvantEdge 1.6.0 (plugin) Wasatch SoftRIP 5.1.5 X-Rite ColorShop 2.60 X-Rite PULSE ColorElite 1.0.2 Xinet FullPress 11.0.5 Xitron Raster Blaster 3.7 Xitron Xaps 2.1.3 Xitron XiFlow 2.5.0 - NEW ZBE WorkStream Digital Studio 2.1 email = xshowsoft at gmail.com email = xshowsoft at gmail.com i2 at Sf#1Lae3^Slg iSD,F:g at k!XML&d&1&J\1$+B _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From lpsolit at gmail.com Tue Apr 14 12:59:50 2009 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Tue, 14 Apr 2009 14:59:50 +0200 Subject: Reminder: Bugzilla meeting in 5 hours Message-ID: <49E488C6.4030406@gmail.com> Just a reminder: our Bugzilla meeting will take place today in 5 hours (11:00 PDT). There are a few more items added to the agenda since my last email: https://wiki.mozilla.org/Bugzilla:Meetings#What_will_be_discussed_during_our_next_meeting_.28agenda.29.3F See you soon, LpSolit From fedrushkov at users.sourceforge.net Tue Apr 14 19:54:34 2009 From: fedrushkov at users.sourceforge.net (Vitaly Fedrushkov) Date: Wed, 15 Apr 2009 01:54:34 +0600 Subject: Switching to Bazaar (bzr) In-Reply-To: References: Message-ID: <49E4E9FA.3030903@users.sourceforge.net> C?dric Corazza wrote: > A localization point of view. > I would only have a regret as a localizer: > We currently have to deal with CVS (for 1.9.0 Gecko branch), HG (for > 1.9.1 gecko branch), SVN for Mozilla Web files, and that would mean we > will have to deal now with a fourth VCS :-( . Update: bzr is recently implemented on SourceForge: http://apps.sourceforge.net/trac/sourceforge/wiki/Bazaar so we can try to abandon Subversion... _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From cedric.corazza at gmail.com Tue Apr 14 20:12:08 2009 From: cedric.corazza at gmail.com (=?ISO-8859-1?Q?C=E9dric_Corazza?=) Date: Tue, 14 Apr 2009 22:12:08 +0200 Subject: Switching to Bazaar (bzr) In-Reply-To: <49E4E9FA.3030903@users.sourceforge.net> References: <49E4E9FA.3030903@users.sourceforge.net> Message-ID: Le 14/04/2009 21:54, Vitaly Fedrushkov a ?crit : > C?dric Corazza wrote: >> A localization point of view. > >> I would only have a regret as a localizer: >> We currently have to deal with CVS (for 1.9.0 Gecko branch), HG (for >> 1.9.1 gecko branch), SVN for Mozilla Web files, and that would mean we >> will have to deal now with a fourth VCS :-( . > > Update: bzr is recently implemented on SourceForge: > http://apps.sourceforge.net/trac/sourceforge/wiki/Bazaar so we can try > to abandon Subversion... Vitaly, This is not about hosting facilities, this is about dealing with many versionning control systems. Currently, as a Mozilla contributor, I have to deal with CVS, SVN and Hg (for code and websites). This is already a barrier to most of new locales, especially the smaller ones with no or few computer skills. Adding another one, only for Bugzilla, will not bring more l10n contributors for Bugzilla. C?dric _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From jochen.wiedmann at gmail.com Tue Apr 14 20:22:30 2009 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Tue, 14 Apr 2009 22:22:30 +0200 Subject: Switching to Bazaar (bzr) In-Reply-To: References: <49E4E9FA.3030903@users.sourceforge.net> Message-ID: 2009/4/14 C?dric Corazza : > This is not about hosting facilities, this is about dealing with many > versionning control systems. Currently, as a Mozilla contributor, I have to > deal with CVS, SVN and Hg (for code and websites). This is already a barrier > to most of new locales, especially the smaller ones with no or few computer > skills. Adding another one, only for Bugzilla, will not bring more l10n > contributors for Bugzilla. I'd support C?dric's view and vote for choosing either of the three existing systems. Note that there are tools like git-svn, which allow to use DVCS against an SVN server. I do not know about Hg, or Bzr, but perhaps there are similar solutions? Jochen -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) From kristis.makris at asu.edu Tue Apr 14 23:12:25 2009 From: kristis.makris at asu.edu (Kristis Makris) Date: Tue, 14 Apr 2009 16:12:25 -0700 Subject: Switching to Bazaar (bzr) In-Reply-To: References: <49E4E9FA.3030903@users.sourceforge.net> Message-ID: <1239750745.4080.2.camel@localhost> On Tue, 2009-04-14 at 22:22 +0200, Jochen Wiedmann wrote: > 2009/4/14 C?dric Corazza : > > versionning control systems. Currently, as a Mozilla contributor, I have to > > deal with CVS, SVN and Hg (for code and websites). This is already a barrier For whatever it's worth, and if you want to use Scmbug for SCM to bug-tracking integration, Scmbug currently integrates with CVS, SVN, and Git. It is certainly possible to add integration with other SCM systems. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 189 bytes Desc: This is a digitally signed message part URL: From m.roth2006 at rcn.com Tue Apr 21 03:26:48 2009 From: m.roth2006 at rcn.com (mark) Date: Mon, 20 Apr 2009 22:26:48 -0500 Subject: Announcement - handler for HTML email Message-ID: <49ED3CF8.2020906@rcn.com> Hi, folks. My manager had me cut code so that "ordinary" users at work, many of whom insist on html email, can email bugs. I've got a brief, tested perl program that makes *zero* changes to any bugzilla code. To use it, in the bugzilla owner's home directory (we're using qmail), instead of simply piping email through email_in.pl, you pipe it through my dehtml.pl, and then through email_in.pl. It's not real fancy, but it gets rid of M$ test/alternative, turns jpegs (like wallpaper) into attachment (but leaves them in). As I said, it works. So, where do I submit it? It's not overly long, and *is* readable. mark From mkanat at bugzilla.org Tue Apr 21 04:36:38 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Mon, 20 Apr 2009 21:36:38 -0700 Subject: Announcement - handler for HTML email In-Reply-To: <49ED3CF8.2020906@rcn.com> References: <49ED3CF8.2020906@rcn.com> Message-ID: <49ED4D56.2080104@bugzilla.org> mark wrote: > So, where do I submit it? It's not overly long, and *is* readable. Probably the simplest thing would be to put it up somewhere and link to it from http://wiki.mozilla.org/Bugzilla:Addons -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From jochen.wiedmann at gmail.com Wed Apr 22 07:58:05 2009 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Wed, 22 Apr 2009 09:58:05 +0200 Subject: Bugzilla Web Services Client Message-ID: Hi, I am unaware of any Perl implementation of the client side of the Bugzilla web services API. Is that true, or am I missing something? Thanks, Jochen -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) From mkanat at bugzilla.org Wed Apr 22 12:09:15 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 22 Apr 2009 05:09:15 -0700 Subject: Bugzilla Web Services Client In-Reply-To: References: Message-ID: <49EF08EB.2090503@bugzilla.org> Jochen Wiedmann wrote: > I am unaware of any Perl implementation of the client side of the > Bugzilla web services API. Is that true, or am I missing something? No, I'm pretty sure you're right. Bugzilla 3.6 may have something inside of it, but I'd be happy to see a Bugzilla client on CPAN. There is contrib/bz_webservices_demo.pl in the Bugzilla distribution itself, but that's hardly a full client. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From mkanat at bugzilla.org Wed Apr 22 13:11:14 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 22 Apr 2009 06:11:14 -0700 Subject: How To Write A Bugzilla Extension Message-ID: <49EF1772.8030803@bugzilla.org> Hey all! I just wrote up some documentation on how to write an extension for Bugzilla! https://wiki.mozilla.org/Bugzilla:Writing_Extensions I'd love to see some more extensions out there! If you write any, be sure to list it on: http://wiki.mozilla.org/Bugzilla:Addons -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From jochen.wiedmann at gmail.com Wed Apr 22 21:29:07 2009 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Wed, 22 Apr 2009 23:29:07 +0200 Subject: Bugzilla Web Services Client In-Reply-To: <49EF08EB.2090503@bugzilla.org> References: <49EF08EB.2090503@bugzilla.org> Message-ID: On Wed, Apr 22, 2009 at 2:09 PM, Max Kanat-Alexander wrote: > ? ? ? ?No, I'm pretty sure you're right. Bugzilla 3.6 may have something > inside of it, but I'd be happy to see a Bugzilla client on CPAN. May be I'll be able to contribute one in the next days. But I wouldn't like to put it on CPAN: Causes all sorts of friendly mails from cpan-testers, RT, and so on, which I woudn't like to deal with. Jochen -- I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone. -- (Bjarne Stroustrup, http://www.research.att.com/~bs/bs_faq.html#really-say-that My guess: Nokia E50) From dkl at redhat.com Wed Apr 22 22:05:07 2009 From: dkl at redhat.com (David Lawrence) Date: Wed, 22 Apr 2009 18:05:07 -0400 Subject: Bugzilla Web Services Client In-Reply-To: References: <49EF08EB.2090503@bugzilla.org> Message-ID: <49EF9493.6010301@redhat.com> An HTML attachment was scrubbed... URL: From bugzillaquestion at yahoo.com Wed Apr 22 22:42:08 2009 From: bugzillaquestion at yahoo.com (Question Bugzilla) Date: Wed, 22 Apr 2009 15:42:08 -0700 (PDT) Subject: About Bugzilla 3.2.2 process_bug.cgi Message-ID: <523058.40773.qm@web43416.mail.sp1.yahoo.com> Hi We are using bugzilla internally behind our firewall We need to configure Bugzilla 3.2.2 or higher such that using our super user account, we need to be able to update the record using the process_bug.cgi thru URL, but without passing the token. So we won't be getting the "Confirmation" page. Is this possible? If so, how do we configure it? Thanks very much Bugzilla User -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpsolit at gmail.com Wed Apr 22 22:46:38 2009 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 23 Apr 2009 00:46:38 +0200 Subject: About Bugzilla 3.2.2 process_bug.cgi In-Reply-To: <523058.40773.qm@web43416.mail.sp1.yahoo.com> References: <523058.40773.qm@web43416.mail.sp1.yahoo.com> Message-ID: <49EF9E4E.7070001@gmail.com> Le 23. 04. 09 00:42, Question Bugzilla a ?crit : > We need to configure Bugzilla 3.2.2 or higher such that using our super user account, we need to be able to update the record using the process_bug.cgi thru URL, but without passing the token. So we won't be getting the "Confirmation" page. Is this possible? If so, how do we configure it? The token is here on purpose. You cannot bypass the validation check. LpSolit From bugzillaquestion at yahoo.com Wed Apr 22 23:02:11 2009 From: bugzillaquestion at yahoo.com (Question Bugzilla) Date: Wed, 22 Apr 2009 16:02:11 -0700 (PDT) Subject: About Bugzilla 3.2.2 process_bug.cgi Message-ID: <451201.61049.qm@web43413.mail.sp1.yahoo.com> Hi, Thank you very much for the quick response. So under no condition, there is a way to bypass the check even though we are accessing it behind our own firewall internally. Thanks again for your help and time. ? ________________________________ From: Fr?d?ric Buclin To: developers at bugzilla.org Sent: Wednesday, April 22, 2009 3:46:38 PM Subject: Re: About Bugzilla 3.2.2 process_bug.cgi Le 23. 04. 09 00:42, Question Bugzilla a ?crit : > We need to configure Bugzilla 3.2.2 or higher such that using our super user account, we need to be able to update the record using the process_bug.cgi thru URL, but without passing the token. So we won't be getting the "Confirmation" page. Is this possible? If so, how do we configure it? The token is here on purpose. You cannot bypass the validation check. LpSolit - To view or change your list settings, click here: -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpsolit at gmail.com Wed Apr 22 23:04:13 2009 From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=) Date: Thu, 23 Apr 2009 01:04:13 +0200 Subject: About Bugzilla 3.2.2 process_bug.cgi In-Reply-To: <451201.61049.qm@web43413.mail.sp1.yahoo.com> References: <451201.61049.qm@web43413.mail.sp1.yahoo.com> Message-ID: <49EFA26D.4070100@gmail.com> Le 23. 04. 09 01:02, Question Bugzilla a ?crit : > Thank you very much for the quick response. So under no condition, there is a way to bypass the check even though we are accessing it behind our own firewall internally. It's very easy to get a valid token. Just look at the XML version of the bug, and extract the token which is there. Note that you need a new token every time the bug changes. LpSolit From bugzillaquestion at yahoo.com Wed Apr 22 23:14:15 2009 From: bugzillaquestion at yahoo.com (Question Bugzilla) Date: Wed, 22 Apr 2009 16:14:15 -0700 (PDT) Subject: About Bugzilla 3.2.2 process_bug.cgi In-Reply-To: <49EFA26D.4070100@gmail.com> References: <451201.61049.qm@web43413.mail.sp1.yahoo.com> <49EFA26D.4070100@gmail.com> Message-ID: <182786.52741.qm@web43405.mail.sp1.yahoo.com> Hi, Thanks for info. We actually already tried getting the token and passing it to the update and it worked, but we are curious about whether this can be bypassed at all since we do the update through a script. Anyway, if this is not configurable at all, I guess we will just do what is needed. Thanks again for your help in such a timely manner. ________________________________ From: Fr?d?ric Buclin To: developers at bugzilla.org Sent: Wednesday, April 22, 2009 4:04:13 PM Subject: Re: About Bugzilla 3.2.2 process_bug.cgi Le 23. 04. 09 01:02, Question Bugzilla a ?crit : > Thank you very much for the quick response. So under no condition, there is a way to bypass the check even though we are accessing it behind our own firewall internally. It's very easy to get a valid token. Just look at the XML version of the bug, and extract the token which is there. Note that you need a new token every time the bug changes. LpSolit - To view or change your list settings, click here: -------------- next part -------------- An HTML attachment was scrubbed... URL: From mbd at dbc.dk Mon Apr 27 11:43:19 2009 From: mbd at dbc.dk (Mads Bondo Dydensborg) Date: Mon, 27 Apr 2009 13:43:19 +0200 Subject: Bugzilla Web Services Client In-Reply-To: <49EF9493.6010301@redhat.com> References: <49EF9493.6010301@redhat.com> Message-ID: <200904271343.19880.mbd@dbc.dk> Torsdag 23 april 2009 skrev David Lawrence: > Jochen Wiedmann wrote: > FWIW, there is a python client library started by a guy here at Red Hat. FYI, FWIW, there is a C# library too (which, incidently, I wrote much of) at http://oss.dbc.dk/bugzproxy/ Regards. Mads -- Mads Bondo Dydensborg mads at dydensborg.dk http://www.madsdydensborg.dk/ There has never been a good war or a bad peace. - Benjamin Franklin From ijeevan at hotmail.com Mon Apr 27 12:58:06 2009 From: ijeevan at hotmail.com (Ignatius Jeevan) Date: Mon, 27 Apr 2009 18:28:06 +0530 Subject: Bugzilla Web Services Client In-Reply-To: References: <49EF9493.6010301@redhat.com> Message-ID: zddfdf "Mads Bondo Dydensborg" wrote in message news:mailman.464.1240832953.28721.dev-apps-bugzilla at lists.mozilla.org... > Torsdag 23 april 2009 skrev David Lawrence: >> Jochen Wiedmann wrote: > >> FWIW, there is a python client library started by a guy here at Red Hat. > > FYI, FWIW, there is a C# library too (which, incidently, I wrote much of) > at > http://oss.dbc.dk/bugzproxy/ > > Regards. > > Mads > > -- > Mads Bondo Dydensborg mads at dydensborg.dk http://www.madsdydensborg.dk/ > > There has never been a good war or a bad peace. > - Benjamin Franklin > > - > To view or change your list settings, click here: > _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From josesalgadosegovia at gmail.com Tue Apr 28 15:24:17 2009 From: josesalgadosegovia at gmail.com (Jose L. Sagado) Date: Tue, 28 Apr 2009 10:24:17 -0500 Subject: NEED MONEY FAST READ THIS ARTICLE 87470 Message-ID: NEED MONEY FAST? READ THIS ARTICLE SPEND 5 MINUTES OF YOUR TIME AND YOU?LL SEE THIS REALLY WORKS AND BESIDES? IT?S LEGAL!!! I was surfing by the groups (GOOGLE, YAHOO, ALTAVISTA, ETC.), when I saw an article saying something about earning money fast. ?Well -said to myself-, I have to see what kind of schematic can they show in internet?. These article described the way of sending BY MAIL, 1 EURO OR AMERICAN DOLLAR TO JUST 6 PERSONS AND EARNING THOUSANDS OF DOLLARS IN 4 WEEKS. Okay, the more I thought about this, the more excited I as getting. It seemed a scam, but I was curious, so I kept reading. After meditating it, I decided to give it a try. It is really worth just 6 euros, or 6 U.S. dollars and 6 postage stamps, I spent more buying lottery and I've never won. This is not a scam; is not indecent, is not illegal, and is 99% freerisk, it really works if you adhere to the instructions, you will receive extraordinary dividends. I must also tell you that this system has fulfilled its natural cycle, in other words, has proven its effectiveness and excellent results. Also, this system does not require physical contact with people, nor requires a heavy duty or difficult and the best: you do not have to leave home except to collect their mail. This is a program that uses the electronic medium Global Internet platform, which ensures its operation in perfect shape. 100% OF THE TIME. Thousands of people have used this way to get good capital and start their own business. Basically, it is possible through a chain that is lead to thousands of people and that will become a reality for you only with your cooperation. That's why I recommend you carefully follow EXACTLY THE INSTRUCTIONS OF THIS LETTER, saying once more that this is 100% safe and that you will not regret having read this article and putting it in practice ... SHARE AND RECEIVE MONEY FAST ... BY MAIL. THIS REALLY WORKS INSTRUCTIONS STEP 1. ? Get 6 sheets of white paper and write: "PLEASE ADD MY NAME TO YOUR LIST?. Then, write your own name, address and e-mail. And as a nice thing also write in what position was every name of people when you sent your DOLLAR OR EURO (eg "You were in slot 3?), so you can make it more complete.The goal is to make money and have a good time at the same time, all with good. will. ? Now bend the page where you have written the above around the 1 Euro coin or 1 U.S. dollar bill. Do not sent checks or other payments, only Euros or American Dollars. ? Put it all inside an envelope and send it to each one of the 6 persons listed, the idea of doubling the paper over the Euro is to ensure that it will arrive at its destination so that is an important thing. Otherwise the people who works in the mail could detect that there is money inside and they could get the thousands of incoming envelopes, so it is recommended to wrap everything, additionally, in a charcoal paper so noone could see through the envelope. ? What we're doing is creating a service and as such, it is COMPLETELY LEGAL. From now on, you are not sending a EURO or one dollar to any person without any grounds, you are paying An EURO or DOLLAR for a legitimate service. Then you must send the 6 envelopes to following addresses: 1) Mario Jose Cardozo Matute Sector OPS El Picacho Calle Venezuela, Urb. Trebol Country Edf. Altamira piso PB Apto C. Edo. Miranda Mpio. Los Salias, San Antonio de los Altos C.P. 1173, Venezuela. 2) Marcos Gonzalo Lopez San Luis 312 B 9 de Julio Palpala, Jujuy, Argentina C.P.4612 3) Jorge Luis Munoz Garcia Bernardo Alcedo 197 Dpto. 403 Santa Cruz Miraflores Lima, Peru C.P. Lima 18 4) Edgar Jorge Nava Arambula Carranza #500 zona centro Villa Union, Poanas Durango, Mexico C.P. 34803 5) Gildardo J. Villarreal 709 Concord St. Aurora, Il. 60505 USA 6) Jos? L. Salgado Av. De Las Palmeras N46-384 y Madro?os Provincia: Pichincha Quito - Ecuador STEP 2. Listen carefully, this is the way how are you going to receive money by mail. Look at the list of the six people, clear the name # 1 in the list above, and add yours at the end of it, so the # 2 becomes # 1 and the # 3 becomes # 2, the # 4 becomes # 3 and the # 5 becomes 4 and so on. So you are now the number 6, include your name, address, postal code, city, state and country. STEP 3. Change everything you think is useful on this article, but try to keep as close as possible to the original. Now put your article at least 200 newsgroups, forums, classified or free ads, and publicate it (To reach them, just put into any search engine these terms: newsgroups, discussion forums, classified ads or free guestbooks, and thousands of pages will appear). You only need 200, but the more numbers you get, the more you will be sent to you. Here are some Indications of how to break into Newsgroups: HOW TO MANAGE NEWSGROUPS: First, you don?t need to write again all this letter to make it yours. Just put the mouse or mouse cursor at the beginning of this letter and select downwards so all the text will be "shady". Then, press CTRL+C. This way it remains in the memory of your computer. Then open an application preferably NOTEPAD Wordpad or Word. Then, once opened any of these Applications place your cursor at the beginning of a blank sheet of paper and Pressing CTRL+V, so you'll have this letter and you can add your name and address in the # 6 by following the instructions above. At Last, save this letter with your changes into a new file in the application. THAT?S ALL. All you have to do now is get in different newsgroups, forums, classified or free ads, and so on. and publicate it. REMEMBER: DO NOT forget to publish the entire notice or letter with your name on the position 6, disappearing the one which has the number 1; when you acquire practice, it?ll only take you about 30 seconds per newsgroup It is further recommended that when publishing the description of this article to give it a "trapping name", like: "NEED MONEY FAST? READ THIS ARTICLE" or "NEED MONEY TO PAY YOUR DEBTS? "," DOWNLOAD THIS FILE? AND READ HOW YOU CAN RECEIVE MONEY BY MAIL "and so on. And do not name it: "WIN MILLION IN 1 WEEK",because nobody will take you seriously. READY! You're getting money from around the world, from places you don?t even know in a few days. MAKE SURE ALL ADDRESSES ARE CORRECT ** Now the WHY of all this: from 200 notices sent, let?s say you only get 5 replies (a very low example). If only 6 people respond, this makes: In the # 6: 6 Euros (U.S. $) In # 5: 36 Euros (U.S. $) In the # 4: 216 Euros (U.S. $) In # 3: 1296 Euros (U.S. $) In the # 2: 7776 Euros (U.S. $) In # 1: 46,656 Euros (U.S. $) LAST STEP. And this is the step I like JUST SIT DOWN and when you begin to fall short of money, reactivate it and file re-publish this file in the same places where you are going to do it now and new places you?ll know in the future. Always keep on hand a copy of this article, REACTIVATE IT every time you need money.. THIS IS AN UNBELIEVABLE TOOL THAT YOU CAN USE AGAIN EVERY TIME YOU NEED CASH, IT IS AN EXTRAORDINARY WAY OF SHARING AND IN WHICH WE ATTRACT WEALTH TO OUR LIVES. HONESTY IS WHAT MAKES THIS PROGRAM SUCCEEDS. DO NOT FORGET IT! GOOD LUCK! Just one more point, if you translate all this message to other languages, you can also paste it in various newsgroups of many countries,such as France, Germany, Russia (I say this as a tip to expand chances of seeing it by a lot more people). N<(?=BUMHddE_JbBravhsea)M -------------- next part -------------- _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mkanat at bugzilla.org Tue Apr 28 20:57:32 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 28 Apr 2009 13:57:32 -0700 Subject: Moving To Catalyst, Incrementally? Message-ID: <49F76DBC.3060209@bugzilla.org> Hey Folks. So, today, I was pointed at this blog post: https://www.opensourcery.com/blog/hans-dieter-pearcey/bugzilla-catalyst It describes how Bugzilla could be incrementally refactored to work with Catalyst with very little work. For those who don't know, Catalyst is a web development framework for Perl, much like Rails in Ruby or Django in Python: http://www.catalystframework.org/ It looks like we could at first support Catalyst along side normal mod_perl and mod_cgi (and Catalyst can actually run under both of those, as well). We'd just need a catalyst.pl (somewhat like our mod_perl.pl now) I believe. The advantages of running under Catalyst would be: * We could eventually start to use URLs like /bug/17 instead of show_bug.cgi?id=17 and process_bug.cgi?id=17. (The first would be a GET to /bug/17 and the second would be a POST to /bug/17.) This would be especially useful for extensions, as they could add new URLs to Bugzilla without having to put new .cgi files into the root of Bugzilla. * We could get FastCGI support for free (at least, as I understand things) which can be better than mod_perl in some circumstances (and works under other web servers than Apache). * We would eventually have all the advantages of the framework, including hundreds of CPAN modules that do things like authentication, webservices, etc. all without us having to write it ourselves. * Catalyst has its own built-in production-ready webserver, which could make initial setup of Bugzilla a LOT easier for people who aren't familiar with configuring webservers. * As I understand things, Catalyst would make it easier for us to start using DBIx::Class, the most popular Perl database layer, which would get us a lot of cross-database support for free, and we wouldn't have to write our own DB drivers anymore. Some of the disadvantages might be: * Catalyst has a LOT of dependencies. (However, install-module.pl should make this easier on *nix, and getting all the dependencies into the appropriate ActiveState repos would make this a lot easier on Windows.) * If we ever decided to move to Catalyst exclusively, bugs in Catalyst itself would heavily affect Bugzilla. (However, Catalyst has been in heavy production use for a long time now in a lot of places, and I think the maintainers would be happy to help us out, since we're a fairly visible, large Perl project.) So, what does everybody think? Is there anybody out there with both Catalyst experience who'd like to weigh in on this and tell us a bit about how well you think it would work for Bugzilla? -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From ghendricks at novell.com Tue Apr 28 21:05:07 2009 From: ghendricks at novell.com (Gregary Hendricks) Date: Tue, 28 Apr 2009 15:05:07 -0600 Subject: Moving To Catalyst, Incrementally? In-Reply-To: <49F76DBC.3060209@bugzilla.org> References: <49F76DBC.3060209@bugzilla.org> Message-ID: <49F71B23020000D2000470B0@lucius.provo.novell.com> >>> On 4/28/2009 at 02:57 PM, in message <49F76DBC.3060209 at bugzilla.org>, Max Kanat-Alexander wrote: > > So, what does everybody think? Is there anybody out there with both > Catalyst experience who'd like to weigh in on this and tell us a bit > about how well you think it would work for Bugzilla? > I remember looking into catalyst back at YAPC::NA 2005 and thinking "If only Bugzilla used this..." Then I promptly forgot about it and haven't really looked at it much since. It appears as though they have made it a much more sure foundation for building applications on. I'm all for it. Not only would we get all the benefits mentioned above, but making extensions (such as Testopia) would be simplified as well. Greg From m.roth2006 at rcn.com Tue Apr 28 21:18:58 2009 From: m.roth2006 at rcn.com (m.roth2006 at rcn.com) Date: Tue, 28 Apr 2009 17:18:58 -0400 (EDT) Subject: Moving To Catalyst, Incrementally? Message-ID: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> Hey, folks, Before you go rewriting the whole thing... last week I posted that I had a couple of enhancements, one of which required no code changes, that one being able to handle HTML email, and the other will allow attachments via email. I'd like to submit them, but have had a deafening silence as to where to take them. mark From mkanat at bugzilla.org Tue Apr 28 21:20:47 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 28 Apr 2009 14:20:47 -0700 Subject: Moving To Catalyst, Incrementally? In-Reply-To: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> References: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> Message-ID: <49F7732F.4020301@bugzilla.org> m.roth2006 at rcn.com wrote: > Before you go rewriting the whole thing... last week I posted that I had a couple of enhancements, one of which required no code changes, that one being able to handle HTML email, and the other will allow attachments via email. I'd like to submit them, but have had a deafening silence as to where to take them. Hey Mark. We won't be re-writing the whole thing. That's what "incrementally" means--not re-writing the whole thing. Also, this doesn't really have to do with this thread. However, just read our development process and post your patches on the appropriate bugs, which already exist. (Our development process is at http://wiki.mozilla.org/Bugzilla:Developers ) -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From guy.pyrzak at gmail.com Tue Apr 28 21:27:23 2009 From: guy.pyrzak at gmail.com (Guy Pyrzak) Date: Tue, 28 Apr 2009 14:27:23 -0700 Subject: Moving To Catalyst, Incrementally? In-Reply-To: <49F7732F.4020301@bugzilla.org> References: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> <49F7732F.4020301@bugzilla.org> Message-ID: I like frameworks they make me happy. However, one thing that I'd want to ensure is that the framework has little to no effect on performance. I think if we can ensure that, it would be great to have a framework. -Guy On Tue, Apr 28, 2009 at 2:20 PM, Max Kanat-Alexander wrote: > m.roth2006 at rcn.com wrote: > >> Before you go rewriting the whole thing... last week I posted that I had >> a couple of enhancements, one of which required no code changes, that one >> being able to handle HTML email, and the other will allow attachments via >> email. I'd like to submit them, but have had a deafening silence as to where >> to take them. >> > > Hey Mark. We won't be re-writing the whole thing. That's what > "incrementally" means--not re-writing the whole thing. Also, this doesn't > really have to do with this thread. However, just read our development > process and post your patches on the appropriate bugs, which already exist. > (Our development process is at http://wiki.mozilla.org/Bugzilla:Developers) > > -Max > -- > http://www.everythingsolved.com/ > Competent, Friendly Bugzilla and Perl Services. Everything Else, too. > - > To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From ghendricks at novell.com Tue Apr 28 21:33:38 2009 From: ghendricks at novell.com (Gregary Hendricks) Date: Tue, 28 Apr 2009 15:33:38 -0600 Subject: Moving To Catalyst, Incrementally? In-Reply-To: References: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> <49F7732F.4020301@bugzilla.org> Message-ID: <49F721D2020000D2000470C8@lucius.provo.novell.com> >>> On 4/28/2009 at 03:27 PM, in message , Guy Pyrzak wrote: > I like frameworks they make me happy. However, one thing that I'd want to > ensure is that the framework has little to no effect on performance. I think > if we can ensure that, it would be great to have a framework. > One of the things that they demonstrated at YAPC and OSCON was the benchmarks. Catalyst would likely speed things way up for any users still running mod_cgi, and would likely have speed benefits for hose running mod_perl. Probably the biggest speed benefit of the framework is that it consolodates all the database handling. My understanding of DBIx::Class is that it is really fast when compared to standard DBI. Max might have more to say on that though. Greg From eblack at higherone.com Tue Apr 28 21:38:31 2009 From: eblack at higherone.com (Eric Black) Date: Tue, 28 Apr 2009 17:38:31 -0400 Subject: Moving To Catalyst, Incrementally? In-Reply-To: <49F76DBC.3060209@bugzilla.org> References: <49F76DBC.3060209@bugzilla.org> Message-ID: <4F91EB003F5C784084736E717AB5AFCA43DDF8B5@mail02.higherone.com> I'll throw in my 2 cents even though I'm not a bugzilla or catalyst expert, but I have worked with catalyst a few times and when I first looked at Bugzilla, one of the first things that came to my mind was 'why haven't they moved this over to Catalyst yet' because Bugzilla seems to fit the structure of a Catalyst app well and probably wouldn't be such a great leap since the TT system is such an important aspect of Bugzilla. I'm sure the Catalyst team would be happy for the exposure of having Bugzilla as part of apps that run on it, so you're probably right that they'd be happy to help. When I first came across Catalyst, I thought it was the best thing to happen to Perl in a long time and would instantly revolutionize perl usage, but it's been slow to gain ground from what I've seen because of it's lack of exposure (I'm assumming). Teaming up with the Bugzilla team could only help that exposure. The one concern that I think you are right to mention is about getting all the Catalyst dependencies installed, as I had to install it on Solaris a few times and it was a real chore, so I can imagine that it would be for the Windows folks, although there is undoubtably a lot of windows users already. I get the feeling from the support list emails that many Bugzilla maintainers are not experienced perl programmers, and when Catalyst breaks, you sort of need to be to figure out the problems. I'm not really sure I understood whether you meant to take a refactoring approach that would allow Bugzilla to work with or without Catalyst, or only with the Catalyst framework. From the blog post, it looked like a few small changes was all it took to get Bugzilla integrated with Catalyst, so it would probably be relatively easy to start with that approach and look at where it could go from there. Eric ________________________________________ From: developers-owner at bugzilla.org [developers-owner at bugzilla.org] On Behalf Of Max Kanat-Alexander [mkanat at bugzilla.org] Sent: Tuesday, April 28, 2009 4:57 PM To: developers at bugzilla.org Subject: Moving To Catalyst, Incrementally? Hey Folks. So, today, I was pointed at this blog post: https://www.opensourcery.com/blog/hans-dieter-pearcey/bugzilla-catalyst It describes how Bugzilla could be incrementally refactored to work with Catalyst with very little work. For those who don't know, Catalyst is a web development framework for Perl, much like Rails in Ruby or Django in Python: http://www.catalystframework.org/ It looks like we could at first support Catalyst along side normal mod_perl and mod_cgi (and Catalyst can actually run under both of those, as well). We'd just need a catalyst.pl (somewhat like our mod_perl.pl now) I believe. The advantages of running under Catalyst would be: * We could eventually start to use URLs like /bug/17 instead of show_bug.cgi?id=17 and process_bug.cgi?id=17. (The first would be a GET to /bug/17 and the second would be a POST to /bug/17.) This would be especially useful for extensions, as they could add new URLs to Bugzilla without having to put new .cgi files into the root of Bugzilla. * We could get FastCGI support for free (at least, as I understand things) which can be better than mod_perl in some circumstances (and works under other web servers than Apache). * We would eventually have all the advantages of the framework, including hundreds of CPAN modules that do things like authentication, webservices, etc. all without us having to write it ourselves. * Catalyst has its own built-in production-ready webserver, which could make initial setup of Bugzilla a LOT easier for people who aren't familiar with configuring webservers. * As I understand things, Catalyst would make it easier for us to start using DBIx::Class, the most popular Perl database layer, which would get us a lot of cross-database support for free, and we wouldn't have to write our own DB drivers anymore. Some of the disadvantages might be: * Catalyst has a LOT of dependencies. (However, install-module.pl should make this easier on *nix, and getting all the dependencies into the appropriate ActiveState repos would make this a lot easier on Windows.) * If we ever decided to move to Catalyst exclusively, bugs in Catalyst itself would heavily affect Bugzilla. (However, Catalyst has been in heavy production use for a long time now in a lot of places, and I think the maintainers would be happy to help us out, since we're a fairly visible, large Perl project.) So, what does everybody think? Is there anybody out there with both Catalyst experience who'd like to weigh in on this and tell us a bit about how well you think it would work for Bugzilla? -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: From mkanat at bugzilla.org Tue Apr 28 21:59:13 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Tue, 28 Apr 2009 14:59:13 -0700 Subject: Moving To Catalyst, Incrementally? In-Reply-To: <4F91EB003F5C784084736E717AB5AFCA43DDF8B5@mail02.higherone.com> References: <49F76DBC.3060209@bugzilla.org> <4F91EB003F5C784084736E717AB5AFCA43DDF8B5@mail02.higherone.com> Message-ID: <49F77C31.5010007@bugzilla.org> Eric Black wrote: > From the blog post, it looked like a few small changes was all it took to get Bugzilla integrated with Catalyst, so it would probably be relatively easy to start with that approach and look at where it could go from there. Yeah, that was pretty much where I was going with the idea, at least for now. Refactor in a way that we could still use normal mod_perl and mod_cgi, and then maybe eventually consider going "whole hog" with Catalyst. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From mkanat at bugzilla.org Wed Apr 29 08:04:29 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 29 Apr 2009 01:04:29 -0700 Subject: Priorities Message-ID: <49F80A0D.9090609@bugzilla.org> There is currently far more work to be done on Bugzilla than we have developers, and even if we did it all, we wouldn't have enough reviewers to review it all. Even just the things assigned to me personally I probably couldn't do if I worked on them eight hours a day for the next 6 months. So, I came up with a way to prioritize my personal work, and I thought that others might be interested in it as a sort of a way of prioritizing work on Bugzilla in general. Basically, my priorities go like this: 1) Fix blockers for the next release. 2) Fix problems that would cause organizations to stop using Bugzilla. 3) Add features that, lacking, would cause current Bugzilla users to switch to some other bug-tracker than Bugzilla. 4) Add features that would cause people to start using Bugzilla, or to choose it over some other product. 5) Refactoring 6) Other major enhancements 7) Bug fixes and minor enhancements Now, if anybody would like to suggest items that fall into categories 2, 3, or 4, I would love to move them to the top of my list. In particular, if you know for a fact that certain issues caused your organization (or an organization that you know of) to stop using Bugzilla, please contact me directly by email and tell me. Even if your organization has *discussed* moving away from Bugzilla due to specific issues, I would really like to know. Also, if there are features of other bug-trackers that caused your organization (or another organization) to pick that bug-tracker over Bugzilla, please let me know by direct email. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From gerv at mozilla.org Wed Apr 29 14:57:38 2009 From: gerv at mozilla.org (Gervase Markham) Date: Wed, 29 Apr 2009 15:57:38 +0100 Subject: Moving To Catalyst, Incrementally? In-Reply-To: References: <49F76DBC.3060209@bugzilla.org> Message-ID: On 28/04/09 22:38, Eric Black wrote: > The one concern that I think you are right to mention is about > getting all the Catalyst dependencies installed I'm thinking that Bugzilla, in its current form, is never going to fall into the "easy to install" category like a PHP app might be. So a different variety of "complicated to install" wouldn't be much different :-) Gerv _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From dieter.pearcey at gmail.com Tue Apr 28 22:26:21 2009 From: dieter.pearcey at gmail.com (dieter.pearcey at gmail.com) Date: Tue, 28 Apr 2009 15:26:21 -0700 (PDT) Subject: Moving To Catalyst, Incrementally? References: Message-ID: On Apr 28, 1:57?pm, Max Kanat-Alexander wrote: > ? ? ? ? * We could get FastCGI support for free (at least, as I understand > things) which can be better than mod_perl in some circumstances (and > works under other web servers than Apache). In addition to supporting other webservers, FastCGI's other advantages over mod_perl include: * easy to run your app as non-webserver-user (good for shared hosting, I think) * not tied to/restricted by apache worker (some modules have problems with mpm-worker, since it is threaded) * 0-downtime restarts possible with unix sockets * easier to debug some problems since you aren't tied into the webserver's guts > ? ? ? ? * Catalyst has a LOT of dependencies. (However, install-module.pl > should make this easier on *nix, and getting all the dependencies into > the appropriate ActiveState repos would make this a lot easier on Windows.) Also, Strawberry Perl should be able to install everything using CPAN.pm out of the box. hdp. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mkanat at bugzilla.org Wed Apr 29 23:44:37 2009 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Wed, 29 Apr 2009 16:44:37 -0700 Subject: Moving To Catalyst, Incrementally? In-Reply-To: References: Message-ID: <49F8E665.2000504@bugzilla.org> dieter.pearcey at gmail.com wrote: > Also, Strawberry Perl should be able to install everything using > CPAN.pm out of the box. Unfortunately we can't use Strawberry because most Bugzilla users can't compile DBD::mysql on Windows (or any of our other DBDs). -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. From dieter.pearcey at gmail.com Tue Apr 28 22:33:23 2009 From: dieter.pearcey at gmail.com (dieter.pearcey at gmail.com) Date: Tue, 28 Apr 2009 15:33:23 -0700 (PDT) Subject: Moving To Catalyst, Incrementally? References: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> <49F7732F.4020301@bugzilla.org> Message-ID: <1173f046-f87d-44a2-8119-48567cf25e1b@d25g2000prn.googlegroups.com> On Apr 28, 2:33?pm, "Gregary Hendricks" wrote: > One of the things that they demonstrated at YAPC and OSCON was the benchmarks. Catalyst would likely speed things way up for any users still running mod_cgi, and would likely have speed benefits for hose running mod_perl. Probably the biggest speed benefit of the framework is that it consolodates all the database handling. My understanding of DBIx::Class is that it is really fast when compared to standard DBI. Max might have more to say on that though. I guess that's possible, but it would surprise me. In particular, I find it hard to imagine that DBIx::Class would be *faster* than DBI. All of this stuff is optimized for development time. You can always hand-optimize code to run faster than abstractions; it's just rarely worth the time it takes to do so. hdp. _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From after.fallout at gmail.com Thu Apr 30 03:21:13 2009 From: after.fallout at gmail.com (Bill Barry) Date: Wed, 29 Apr 2009 21:21:13 -0600 Subject: Moving To Catalyst, Incrementally? In-Reply-To: <1173f046-f87d-44a2-8119-48567cf25e1b@d25g2000prn.googlegroups.com> References: <20090428171858.CGF60977@ms17.lnh.mail.rcn.net> <49F7732F.4020301@bugzilla.org> <1173f046-f87d-44a2-8119-48567cf25e1b@d25g2000prn.googlegroups.com> Message-ID: <49F91929.4070702@gmail.com> dieter.pearcey at gmail.com wrote: > On Apr 28, 2:33 pm, "Gregary Hendricks" wrote: > >> One of the things that they demonstrated at YAPC and OSCON was the benchmarks. Catalyst would likely speed things way up for any users still running mod_cgi, and would likely have speed benefits for hose running mod_perl. Probably the biggest speed benefit of the framework is that it consolodates all the database handling. My understanding of DBIx::Class is that it is really fast when compared to standard DBI. Max might have more to say on that though. >> > > I guess that's possible, but it would surprise me. In particular, I > find it hard to imagine that DBIx::Class would be *faster* than DBI. > > All of this stuff is optimized for development time. You can always > hand-optimize code to run faster than abstractions; it's just rarely > worth the time it takes to do so. > In my experience with NHibernate, it is often faster than hand written query based apps. This is because it caches things heavily and batches writes to the database. Properly configured it also almost universally uses proper indexes too. I assume DBIx::Class would do the same thing (memcached support, flush buffers, ...). The point being that, sure you could optimize a single query to be be faster, but that isn't the proper optimization point most of the time (it is at the batches-of-queries-level to reduce db roundtrips). _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From alexsh at parallels.com Fri Apr 24 13:52:43 2009 From: alexsh at parallels.com (Alexander Shvetsov) Date: Fri, 24 Apr 2009 17:52:43 +0400 Subject: Modifications offering Message-ID: <7901A535B99ED848BAC76AE67185C5AF0113EF335752@msk-exch1.sw.swsoft.com> Hi All, I've just finished some Bugzilla customizations, and would like to offer them to community. So, step-by-step: 1. "bug-start_of_update" and "bug-start_of_create" hook entry points: That is just useful for limiting modification and creation of bugs; 2. Milestones obsoleting: I have completely implemented this feature, so it allows to: a. Hide obsolete milestones for bugs creation; b. Hide obsolete milestones (except current one) for bugs modification; c. Highlight with light gray obsolete milestones in Advanced Search. 3. Custom fields targeting: This modification allows to specify products for which custom fields are created, and perform product-based targeting of custom fields values. All modifications are fully integrated with admin panel. So if you are interested in such features, please let me know J. Regards, Alexander Shvetsov From christian at mozilla.com Wed Apr 29 06:03:11 2009 From: christian at mozilla.com (Christian Sejersen) Date: Tue, 28 Apr 2009 23:03:11 -0700 Subject: Bugzilla Web Services Client In-Reply-To: <200904271343.19880.mbd@dbc.dk> References: <49EF9493.6010301@redhat.com> <200904271343.19880.mbd@dbc.dk> Message-ID: <4B7AFD82-B823-4974-8C02-B8077551904F@mozilla.com> Has anyone successfully used xmlrpc.cgi on https://bugzilla.mozilla.org? I think I have tried every single implementation out there (Java, Python, PHP, C#, Perl) and they all work except against https://bugzilla.mozilla.org . /Christian On Apr 27, 2009, at 4:43 AM, Mads Bondo Dydensborg wrote: > Torsdag 23 april 2009 skrev David Lawrence: >> Jochen Wiedmann wrote: > >> FWIW, there is a python client library started by a guy here at Red >> Hat. > > FYI, FWIW, there is a C# library too (which, incidently, I wrote > much of) at > http://oss.dbc.dk/bugzproxy/ > > Regards. > > Mads > > -- > Mads Bondo Dydensborg mads at dydensborg.dk http://www.madsdydensborg.dk/ > > There has never been a good war or a bad peace. > - Benjamin Franklin > > - > To view or change your list settings, click here: > > > _______________________________________________ > dev-apps-bugzilla mailing list > dev-apps-bugzilla at lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-apps-bugzilla