From duret.tanguy at gmail.com Fri Nov 2 11:13:15 2012 From: duret.tanguy at gmail.com (Tengy Td) Date: Fri, 2 Nov 2012 12:13:15 +0100 Subject: Coordination between developers in the Mozilla projects Message-ID: Hello, I am a French student and I am currently realizing my final thesis in the field of Free/libre open source software. It would be a great help for me if you could answer a short online survey (it should take approximately 5 minutes). This survey is designed to reach a better understanding of the cooperation and coordination between developers in Free/libre open source projects. There is no right or wrong answers, therefore, feel free to answer spontaneously and to skip the questions you feel you do not want to answer. The link to the survey is: http://bit.ly/SwMIYq I would like to remind you that the participation is absolutely anonymous and voluntary, and you can quit it at any time. Your answers will be strictly confidential and will be used only for research purpose (no commercial use of any information you provided). If you find this survey interesting, you are welcome to share it with other developers! If you want to add something, or if you need further information about this survey, feel free to contact me at: tanguy.duret at gmx.fr Thank you in advance for your cooperation and your enthusiasm! :) Tanguy Duret _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From sgreen at redhat.com Fri Nov 9 12:13:13 2012 From: sgreen at redhat.com (Simon Green) Date: Fri, 09 Nov 2012 22:13:13 +1000 Subject: Rules Engine in Bugzilla Message-ID: <509CF359.8070504@redhat.com> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi all, For those that do not know me, I'm one of the developers for Red Hat Bugzilla, and live and work in Brisbane. I hang out in #bugzilla with the nick simon, and have submitted a couple of patches upstream. As the second largest known Bugzilla installation, we have plenty of customisations. One thing I am considering is some sort of 'rules engine' that runs after bugs are created or updated. Examples of rules would be: If the bug has flagA+ and flagB+, set flagC to +, and make a comment If product is I or J, and component is K or L, add group M If bug is in group X, add user Y to the CC: list Up until now, we have been writing extension code using the bug_end_of_update and bug_end_of_create hooks, and this is becoming a bit unmaintainable. The rules don't need to be run instantly, so I'm thinking about using the job queue. I would store the bug id, whether it was a create or update, user making the change or reporting the bug, and the timestamp (so we wouldn't get hit by the issue of rows being added in the job queue before the bug update is committed to the database). I'm wondering if other Bugzilla installations have looked at some sort of rules engine that takes a series of criteria and performs an action if the bug matches the criteria? Alternatively, does anyone know of a CPAN module that can be used to define a set of rules. I'm sure something exists, but my Internet searching isn't returning anything useful. Ideally it would work with objects, so I can use any part of the Bugzilla::Bug object, and by extension the Bugzilla::User of the reporter or the person making the change. Any thoughts or wisdom shared is appreciated. Thanks in advance. -- simon -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iQEcBAEBCAAGBQJQnPNYAAoJEGFoF1bezwI/+98H/1TYCsgL3P+B20/5GgqQmPPF xpLHfGGgVUlIg+LZnn7clNyM44VS/piRf3624l1XqEGOTBKWN5txNTR4X0FnRLef YHR3FpEIYkfmueZGJHVzbyZZlXLudWtrAbZl96fVNPp7hagLXReScKxTnCK//Hc6 VbPALEPYBkic/mzF3DmMvN/EHtTCnR+5drS5aVtwfi3dsknAiQ4zq6YnA10Q8hTG 74Qa1H2FR0sT7oBiwP9blZCa9/43mSpVLd1wItOOsOsCQ2V/IdjVWc+QBWk+p4Dk 0NPBA+gC5ZcetLXPJSOBjUeWlge/S54EX8AENoPh/OaOVoV+Xn1+xwAR7F25Atg= =eaTn -----END PGP SIGNATURE----- From mkanat at bugzilla.org Thu Nov 15 08:42:30 2012 From: mkanat at bugzilla.org (Max Kanat-Alexander) Date: Thu, 15 Nov 2012 00:42:30 -0800 Subject: Transitioning Message-ID: <50A4AAF6.4090901@bugzilla.org> Hey Bugzilla Developers. I love working on Bugzilla, and I'm totally thrilled at the unbelievable changes we've made it it. I'm pretty sure that in 2004, most people thought that this project was going to die and be crushed by all the major commercial competitors that suddenly arose. And yet, here we are, still one of the most widely-respected and used bug-tracking systems in the world, all based on volunteer efforts and open-source principles. This isn't to say that the project is totally out of danger--it's very likely that some significant changes have to happen in order to keep the project alive (myself and other reviewers discussed this a few months back), and the Pretty project needs to be completed in order for us to retain a broad userbase. But the sort of things we've accomplished (particularly the degree of improvement in code quality without a full re-write) with this codebase have possibly never before been achieved by any software organization in the world, let alone one populated across nearly every timezone by people working in their spare time. So I think we deserve a little pat on the back from ourselves. I personally had a major goal of bringing Bugzilla's code up to a high level of quality and learning enough from that process to develop a series of broad principles for software development as a whole. With the completion of my book, I believe that I have accomplished this, and now it's time for me to start focusing on bringing that message to the world, as well as time for me to start focusing on my career at Google where I may also be able to have a significant and important impact on the world of software development. In reality, LpSolit and others have actually been managing the project entirely without me for the last several months (in fact, for pretty much the entire 4.4 release cycle) so I think there's excellent evidence that the project can both survive and flourish without me. I will definitely miss the Bugzilla community and the great work that we've done together, but I think the best thing to do at this point is to transition away all of my duties to others so that I can focus on what I need to focus on, and so that the project can have somebody holding all of the positions that need to be held. If I had to supply only three pieces of advice to the Bugzilla community that should live on and be kept in force always, they would be: (1) Make sure you keep intact all of the principles of an effective open-source community. It's most important that we gain and retain developers faster than we lose them. I wrote up the results of my research into this at: http://www.codesimplicity.com/post/open-source-community-simplified/ (2) The most important thing to focus on when prioritizing features is "how much does this help people track bugs?" I wrote this up as "The Feature Acceptance Test" once, and I think it helped us have one of the most successful releases we ever had. I would suggest keeping this in operation for every release: https://groups.google.com/forum/#!topic/mozilla.dev.apps.bugzilla/hHoJ3IqN0ns (3) Remember that code quality is king. Without code quality, we can't deliver features in time that actually end up helping our users. Losing code quality almost killed the project once; letting that standard slip could end us up there again. With that said, it's time to give away all of my duties! As near as I can tell, here's a list of all the things I'm currently in charge of, with who they should go to: * Infrastructure (Sysadmin) This is already being handled by wicked. * CVS-to-bzr sync wicked, could you please take this over? It runs on landfill from my personal crontab. * webmaster at bugzilla.org Also being handled by wicked. * Twitter justdave has volunteered to take this over. Note that I routinely search for the word "Bugzilla" on Twitter and reply to people who have genuine questions or problems. I don't feed the trolls who have pure complaints that aren't useful, but sometimes I do offer to help them or ask them for specifics so that I can be helpful to them. Doing this search is also a good way to get an idea of how people feel about Bugzilla. Generally, the longer it's been since we released anything, the more negative they feel. Anybody can help in this fashion, as long as they actually know enough about Bugzilla and are willing to be polite and positive to every single person they Tweet at. * The Bugzilla Update (blog) I believe I have transitioned this to LpSolit. * Extensions module owner I think timello should take on my work on this with oversight from the other reviewers, if he's willing. I don't think there should continue to be a module owner. * DB module owner I think LpSolit should take over maintaining the DB layers. I don't think there should presently be a module owner. * Release Manager dkl, as has been happening anyway. * Authentication module owner Nobody. Should be maintained by the community for now. Perhaps wicked could look into this, though, as I recall he had some patches and interest. * WebServices dkl. Note that API reviews should remain very strict. The API should retain TOTAL consistency and reviewers should always think about forward-compatibility so that we have a stable API where we (ideally) never have to break backwards-compatibility. Also, all WebService methods must be fully unit-tested before a Bugzilla release can be called stable. Every single release, we have discovered problems during unit testing that would have prevented backwards-compatibility if not fixed before the release. * Installation and Upgrading LpSolit should probably take over generally directing this work. There should probably be no module owner for now. * Chief Architect I suspect that this title should simply disappear until it's clear that somebody else is doing this specific job. Essentially this role is implicitly held by the project's leaders. * Community Lead This is essentially the job of making sure that the community stays healthy and that each member of the community is enjoying working on the Bugzilla Project. I think justdave is probably best positioned for this, or he can assign that job away to somebody else who really wants to do it and seems well-suited for it. * Maintaining the Developers Guide. In general, this probably won't change much, particularly the guidelines for new contributors that are on the Wiki. However, I suspect things will need to change over time, and I'm guessing that LpSolit would be the best person in general to maintain this. It's probably going to partially be a community effort, too, I imagine. But particularly anything having to do with coding style should generally have a single maintainer who makes the important decisions about consistency for the whole app. * UI coordination Perhaps glob or dkl would like to do this? Essentially I have always coordinated with our UX people and given them my input and guidance based on experience with lots of Bugzilla users. I helped Jonathan revise the mocks for Pretty, as an example. * The xt/ search test. I would suggest dkl or glob. Please maintain this test; it took tremendous effort and it's the *only* way to know that the Custom Search system is behaving as it was intended. We spent 10 years with a continuously buggy system because this test didn't exist. Don't let it fade away and let us go back to that parade of endless bugs. * Reviewer There exist many other reviewers, they can still do reviews. I will unfortunately not be available for reviews. * My bugs Should mostly go back to their default assignees. Some should be taken over by individuals, particularly the P1 enhancements. If there's anything else that I've missed, please let me know! Once again, I've loved working with you, it's been an incredible adventure, and I will miss you all. -Max -- Max Kanat-Alexander Chief Architect, Community Lead, and Release Manager Bugzilla Project http://www.bugzilla.org/ From jochen.wiedmann at gmail.com Thu Nov 15 09:52:20 2012 From: jochen.wiedmann at gmail.com (Jochen Wiedmann) Date: Thu, 15 Nov 2012 10:52:20 +0100 Subject: Transitioning In-Reply-To: <50A4AAF6.4090901@bugzilla.org> References: <50A4AAF6.4090901@bugzilla.org> Message-ID: I'd volunteer for Authentication Module Owner. On Thu, Nov 15, 2012 at 9:42 AM, Max Kanat-Alexander wrote: > Hey Bugzilla Developers. > > I love working on Bugzilla, and I'm totally thrilled at the > unbelievable changes we've made it it. I'm pretty sure that in 2004, most > people thought that this project was going to die and be crushed by all the > major commercial competitors that suddenly arose. And yet, here we are, > still one of the most widely-respected and used bug-tracking systems in > the world, all based on volunteer efforts and open-source principles. > > This isn't to say that the project is totally out of danger--it's > very likely that some significant changes have to happen in order to keep > the project alive (myself and other reviewers discussed this a few months > back), and the Pretty project needs to be completed in order for us to > retain a broad userbase. But the sort of things we've accomplished > (particularly the degree of improvement in code quality without a full > re-write) with this codebase have possibly never before been achieved by > any software organization in the world, let alone one populated across > nearly every timezone by people working in their spare time. So I think we > deserve a little pat on the back from ourselves. > > I personally had a major goal of bringing Bugzilla's code up to a > high level of quality and learning enough from that process to develop a > series of broad principles for software development as a whole. With the > completion of my book, I believe that I have accomplished this, and now > it's time for me to start focusing on bringing that message to the world, > as well as time for me to start focusing on my career at Google where I may > also be able to have a significant and important impact on the world of > software development. > > In reality, LpSolit and others have actually been managing the > project entirely without me for the last several months (in fact, for > pretty much the entire 4.4 release cycle) so I think there's excellent > evidence that the project can both survive and flourish without me. I will > definitely miss the Bugzilla community and the great work that we've done > together, but I think the best thing to do at this point is to transition > away all of my duties to others so that I can focus on what I need to focus > on, and so that the project can have somebody holding all of the positions > that need to be held. > > If I had to supply only three pieces of advice to the Bugzilla > community that should live on and be kept in force always, they would be: > > (1) Make sure you keep intact all of the principles of an > effective open-source community. It's most important that we gain and > retain developers faster than we lose them. I wrote up the results of my > research into this at: http://www.codesimplicity.com/** > post/open-source-community-**simplified/ > > (2) The most important thing to focus on when prioritizing > features is "how much does this help people track bugs?" I wrote this up as > "The Feature Acceptance Test" once, and I think it helped us have one of > the most successful releases we ever had. I would suggest keeping this in > operation for every release: https://groups.google.com/** > forum/#!topic/mozilla.dev.**apps.bugzilla/hHoJ3IqN0ns > > (3) Remember that code quality is king. Without code quality, we > can't deliver features in time that actually end up helping our users. > Losing code quality almost killed the project once; letting that standard > slip could end us up there again. > > With that said, it's time to give away all of my duties! As near > as I can tell, here's a list of all the things I'm currently in charge of, > with who they should go to: > > * Infrastructure (Sysadmin) > > This is already being handled by wicked. > > * CVS-to-bzr sync > > wicked, could you please take this over? It runs on landfill from > my personal crontab. > > * webmaster at bugzilla.org > > Also being handled by wicked. > > * Twitter > > justdave has volunteered to take this over. > > Note that I routinely search for the word "Bugzilla" on Twitter > and reply to people who have genuine questions or problems. I don't feed > the trolls who have pure complaints that aren't useful, but sometimes I do > offer to help them or ask them for specifics so that I can be helpful to > them. Doing this search is also a good way to get an idea of how people > feel about Bugzilla. Generally, the longer it's been since we released > anything, the more negative they feel. Anybody can help in this fashion, as > long as they actually know enough about Bugzilla and are willing to be > polite and positive to every single person they Tweet at. > > * The Bugzilla Update (blog) > > I believe I have transitioned this to LpSolit. > > * Extensions module owner > > I think timello should take on my work on this with oversight from > the other reviewers, if he's willing. I don't think there should continue > to be a module owner. > > * DB module owner > > I think LpSolit should take over maintaining the DB layers. I > don't think there should presently be a module owner. > > * Release Manager > > dkl, as has been happening anyway. > > * Authentication module owner > > Nobody. Should be maintained by the community for now. Perhaps > wicked could look into this, though, as I recall he had some patches and > interest. > > * WebServices > > dkl. Note that API reviews should remain very strict. The API > should retain TOTAL consistency and reviewers should always think about > forward-compatibility so that we have a stable API where we (ideally) > never have to break backwards-compatibility. Also, all WebService methods > must be fully unit-tested before a Bugzilla release can be called stable. > Every single release, we have discovered problems during unit testing that > would have prevented backwards-compatibility if not fixed before the > release. > > * Installation and Upgrading > > LpSolit should probably take over generally directing this work. > There should probably be no module owner for now. > > * Chief Architect > > I suspect that this title should simply disappear until it's clear > that somebody else is doing this specific job. Essentially this role is > implicitly held by the project's leaders. > > * Community Lead > > This is essentially the job of making sure that the community > stays healthy and that each member of the community is enjoying working on > the Bugzilla Project. I think justdave is probably best positioned for > this, or he can assign that job away to somebody else who really wants to > do it and seems well-suited for it. > > * Maintaining the Developers Guide. > > In general, this probably won't change much, particularly the > guidelines for new contributors that are on the Wiki. However, I suspect > things will need to change over time, and I'm guessing that LpSolit > would be the best person in general to maintain this. It's probably > going to partially be a community effort, too, I imagine. But > particularly anything having to do with coding style should generally > have a single maintainer who makes the important decisions about > consistency for the whole app. > > * UI coordination > > Perhaps glob or dkl would like to do this? Essentially I have > always coordinated with our UX people and given them my input and guidance > based on experience with lots of Bugzilla users. I helped Jonathan revise > the mocks for Pretty, as an example. > > * The xt/ search test. > > I would suggest dkl or glob. Please maintain this test; it took > tremendous effort and it's the *only* way to know that the Custom Search > system is behaving as it was intended. We spent 10 years with a > continuously buggy system because this test didn't exist. Don't let it fade > away and let us go back to that parade of endless bugs. > > * Reviewer > > There exist many other reviewers, they can still do reviews. I > will unfortunately not be available for reviews. > > * My bugs > > Should mostly go back to their default assignees. Some should be > taken over by individuals, particularly the P1 enhancements. > > If there's anything else that I've missed, please let me know! > > Once again, I've loved working with you, it's been an incredible > adventure, and I will miss you all. > > -Max > -- > Max Kanat-Alexander > Chief Architect, Community Lead, and Release Manager > Bugzilla Project > http://www.bugzilla.org/ > - > To view or change your list settings, click here: > > > > -- The best argument for celibacy is that the clergy will sooner or later become extinct. -------------- next part -------------- An HTML attachment was scrubbed... URL: From lpsolit at gmail.com Thu Nov 15 16:11:48 2012 From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=) Date: Thu, 15 Nov 2012 17:11:48 +0100 Subject: Transitioning In-Reply-To: References: <50A4AAF6.4090901@bugzilla.org> Message-ID: <50A51444.10708@gmail.com> Le 15. 11. 12 10:52, Jochen Wiedmann a ?crit : > I'd volunteer for Authentication Module Owner. Hi Jochen, I'm sure you understand that in order to become a module owner, you must first be a core developer and reviewer. And you match none of these two conditions. There won't be any new module owner for authentication anyway. LpSolit From justdave at bugzilla.org Thu Nov 15 16:56:50 2012 From: justdave at bugzilla.org (Dave Miller) Date: Thu, 15 Nov 2012 11:56:50 -0500 Subject: Transitioning In-Reply-To: <50A4AAF6.4090901@bugzilla.org> References: <50A4AAF6.4090901@bugzilla.org> Message-ID: <50A51ED2.1070903@bugzilla.org> Max Kanat-Alexander wrote on 11/15/12 3:42 AM: > * The Bugzilla Update (blog) > > I believe I have transitioned this to LpSolit. I've been doing it, actually. > Once again, I've loved working with you, it's been an incredible > adventure, and I will miss you all. Thanks for all your help over the years! You've had a pretty large influence on the project. -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From justdave at bugzilla.org Thu Nov 15 17:22:00 2012 From: justdave at bugzilla.org (Dave Miller) Date: Thu, 15 Nov 2012 12:22:00 -0500 Subject: Transitioning In-Reply-To: <50A51444.10708@gmail.com> References: <50A4AAF6.4090901@bugzilla.org> <50A51444.10708@gmail.com> Message-ID: <50A524B8.4090201@bugzilla.org> Fr?d?ric Buclin wrote on 11/15/12 11:11 AM: > Le 15. 11. 12 10:52, Jochen Wiedmann a ?crit : >> I'd volunteer for Authentication Module Owner. > > Hi Jochen, > > I'm sure you understand that in order to become a module owner, you must > first be a core developer and reviewer. And you match none of these two > conditions. There won't be any new module owner for authentication anyway. Which doesn't mean he can't give it a shot. If you're actively contributing to it and getting good reviews, the reviewers might sign off on letting you do that eventually. For now just make sure you're contributing. :) -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ From shimono at bug-ja.org Mon Nov 19 22:05:58 2012 From: shimono at bug-ja.org (Atsushi Shimono) Date: Tue, 20 Nov 2012 07:05:58 +0900 Subject: ja 3.6.12, 4.0.9, 4.2.4 template archive out Message-ID: <50AAAD46.5020001@bug-ja.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Dear all, Sorry for really late from release of bugzilla.org (and also more than one day later from tagging in -ja repository), I've just uploaded archives into our release site. best, - -- Atsushi Shimono - shimono at bug-ja.org - skype shimono_univ Tel +81-50-5539-5179, +1-626-720-4274 / http://blog.himor.in/ Mozilla Evangelist; Mozilla Japanese Translation Group / Bugzilla UG in Japan HTML5-WEST.jp - Co-Founder of HTML5 Evangelism Group in west/Japan -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.10 (MingW32) iQIcBAEBCgAGBQJQqq1GAAoJEHI5evwJBSZdOioP/R3FIEJ9cSsWiqHP6h1uFoIL fRwhln4IT1vNdnbZMv0mZz++gbxdT3Alebadt0wNjNVk5rwUEUTxQGlsh39F2n0A u4t1ng4tx8zwycrfkvPpN7KNl5Htq3Y+5SZaIPQY+FCnVgWQNmrlvqUHDqk3+8ot nsU7E/WL9bEgsDpPEUElBAQSE6NNePmJcZ2ZDdMmbPQfURAqS6tkjRHiiW85WCE5 QNA9hewOBDxd9FOdWoQIpE71xLQ100axF2AG/OILKUTjmekq37tpTVtCLiRAJVq+ KS3qSslDbhI3YYBNHO3qWeBbUL4yXNQlmLGEwddpTjRDQRfVonFXZ4PXNgqy5nJW 2fTE/9uACAa1Il6WrAi38h60mFRV+ITUTuQzutUMGpYv/2cKla7JTwInf+rRZinT wUrI7Npa7T+mNiOeUP+scBQuCwecXhPh0uMMFyntgaobq6wZn2ZEgP8QHPREjovj 8F/7NO8tV3O/2eEEwooIB+pRoYQvir4CwmnmszRrePs827pG5zQysGx8FSWPbSaQ 6SklsdTauoxjJ0Ts/FPj85LHf+uqm7OxfA8SuXG1Di9M8lSq3C6u1SIiiIv6KBqw aOemdIavU8QOEQordIWm7aeZQtwfG4UvxvUSBxf/7BqEMJNSE/4eYNJqLuNegTZF ce5CeLaNxjl/OZS+BoP8 =LAdm -----END PGP SIGNATURE----- From oscarcillero at gmail.com Fri Nov 23 00:58:28 2012 From: oscarcillero at gmail.com (oscarcillero at gmail.com) Date: Thu, 22 Nov 2012 16:58:28 -0800 (PST) Subject: Coordination between developers in the Mozilla projects In-Reply-To: References: Message-ID: _______________________________________________ dev-apps-bugzilla mailing list dev-apps-bugzilla at lists.mozilla.org https://lists.mozilla.org/listinfo/dev-apps-bugzilla From mail at smogura.eu Mon Nov 26 18:01:49 2012 From: mail at smogura.eu (=?UTF-8?Q?Rados=C5=82aw_Smogura?=) Date: Mon, 26 Nov 2012 19:01:49 +0100 Subject: New UI functionality and registration Message-ID: Hello, As to introduce myself my name is Rados?aw Smogura. I would like to send patch, I created mainly for my (almost) personal Bugzilla. The changes adds following functionality: 1. Add some icons to status, severity and priority (actually new style classes may be used). 2. Add possibility to redirect user to external registration page (which may be used in large sites, with single-sing on like features). For 1. I add style class with constant prefix and postfix generated form e.g. bug status, so to add e.g new icons to new statuses administrator need just to code new style class. I send patch, without icons, but with sample .css. The patch was created with bzr diff against 4.2 version. The patch was taken from my customization. Regards, -------------- next part -------------- A non-text attachment was scrubbed... Name: bugzilla_style_registration.diff Type: application/octet-stream Size: 6904 bytes Desc: not available URL: From justdave at bugzilla.org Mon Nov 26 18:44:12 2012 From: justdave at bugzilla.org (Dave Miller) Date: Mon, 26 Nov 2012 13:44:12 -0500 Subject: New UI functionality and registration In-Reply-To: References: Message-ID: Thanks for your contribution! For best results and to make sure it doesn't get lost, the best place to put a patch is to file a bug in our Bugzilla (https://bugzilla.mozilla.org/) if there isn't already a similar bug filed there (in which case, use the existing bug) and attach the patch to the bug. The added icons sounds kind of cool... I suspect this part would be best implemented as an extension. Some people like things simple and wouldn't want the extra flashiness. :) It sounds like something that might be doable with a stylesheet supplied by the extension, although the css classes themselves probably need to be added in the core templates as you've done to make it work. These are two distinct features... not sure how feasible it would be to separate them into separate patches when they get posted on Bugzilla? Usually works better that way. "Rados?aw Smogura" wrote: >I would like to send patch, I created mainly for my (almost) personal >Bugzilla. The changes adds following functionality: > >1. Add some icons to status, severity and priority (actually new style >classes may be used). >2. Add possibility to redirect user to external registration page >(which may be used in large sites, with single-sing on like features). > >For 1. I add style class with constant prefix and postfix generated >form e.g. bug status, so to add e.g new icons to new statuses >administrator need just to code new style class. > >I send patch, without icons, but with sample .css. The patch was >created with bzr diff against 4.2 version. The patch was taken from my >customization. -- Dave Miller http://www.justdave.net/ IT Infrastructure Engineer, Mozilla http://www.mozilla.org/ Project Leader, Bugzilla Bug Tracking System http://www.bugzilla.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: From steven_tierney at yahoo.co.uk Mon Nov 26 19:21:18 2012 From: steven_tierney at yahoo.co.uk (Steven Tierney) Date: Mon, 26 Nov 2012 19:21:18 +0000 (GMT) Subject: Customisable Custom Field Autocomplete Message-ID: <1353957678.31537.YahooMailNeo@web29706.mail.ird.yahoo.com> Hi, Thanks Dave and Jochen. ?I've gone with Dave's plan and added a link to the Wiki page. Regards, --- Steven On 16 October 2012 10:23, Jochen Wiedmann??wrote: Or, much better, contribute it to the core by opening a bug with the >necessary patch. > > > >On Tue, Oct 16, 2012 at 6:35 AM, Dave Miller wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> Steven Tierney wrote on 10/2/12 2:42 PM: >>> Hi, >>> >>> Just to announce a feature I have developed: ?A customisable >>> autocompletion feature for Bugzilla Custom Fields. >>> >>> The source is available at >>>?https://sourceforge.net/projects/cfautocomplete/ >>> >>> I'm no Perl or Bugzilla guru but it has worked for me in the light >>> testing I have done. ?Feel free to give it a whirl! >> >> Cool! ?You should add this to?https://wiki.mozilla.org/Bugzilla:Addons >> >> - -- >> Dave Miller ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ??http://www.justdave.net/ >> IT Infrastructure Engineer, Mozilla ? ? ? ? ??http://www.mozilla.org/ >> Project Leader, Bugzilla Bug Tracking System ?http://www.bugzilla.org/ >> -----BEGIN PGP SIGNATURE----- >> Version: GnuPG v1.4.5 (Darwin) >> Comment: Using GnuPG with Mozilla -?http://www.enigmail.net/ >> >> iD8DBQFQfOQl0YeDAOcbS44RAmV+AJ9Q/WZ44gVzkk16qX76JiLq3YrDPwCeJDGx >> GiJD53qKp5LDPz4KoplHZgU= >> =dZny >> -----END PGP SIGNATURE----- >> - >> To view or change your list settings, click here: >> > > > >-- >The best argument for celibacy is that the clergy will sooner or later >become extinct. > >- >To view or change your list settings, click here: > > -------------- next part -------------- An HTML attachment was scrubbed... URL: