show_bug.cgi should provide separate form for adding comments

Hi there, recently I was monitoring a bug that was quite active... In order to get = the=20 latest postings on this bug I refreshed the page regularly and added a = new=20 comment when appropriate. Then suddenly, a Mozilla member urged me not to always set the Component = field back to some other value... I was quite baffled, because I didn't update any of the fields. I just = added=20 comments to the bug. (#546930) Then I noticed that *all* the fields of a bug get updated whenever a = comment=20 is added to the bug. And although I had pressed <F5> to refresh the = pag

Loggerhead is all better, now

So, loggerhead (the web view of bzr.mozilla.org) was having some trouble, as you probably know if you ever tried to use it. justdave just now downgraded us to a stable release of loggerhead, and the annoying "KeyError" problems are all gone now. Basically, the site works reliably, now. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

3.6 Release Notes, Want to Help Review?

Hey folks. So, I've posted a Release Notes patch for 3.6rc1 (which is probably going to happen surprisingly soon), and I wanted to let everybody look over it in case you had any feedback: https://bugzilla.mozilla.org/show_bug.cgi?id=547466 -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Mozilla in the Google Summer of Code 2010

[Please respect the Followup-To header, although questions about the process should probably come straight to me.] The Google Summer of Code is running again this year[0]. :-) This is an opportunity for students to be paid by Google to work on open source software, mentored by community members. Selected free software projects are asked to provide a list of ideas that students can work on. Last year, Mozilla had ten slots, from all across the project. So, Mozilla people, please visit the Brainstorming page at: https://wiki.mozilla.org/Community:SummerOfCode10:Brainstorming and

Companies That Contributed To 3.6?

Hey folks. Were any of your contributions explicitly supported by a company that hired you to contribute to upstream Bugzilla? I ask because we like to credit those sorts of contributions (paying people to work on Bugzilla) in the release notes, and I'm working on the release notes now. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Wiki Updated With Bzr Instructions

I've updated the Wiki with Bzr instructions, for developers. The central point is: http://wiki.mozilla.org/Bugzilla:Developers Specifically, the updated/new pages are: https://wiki.mozilla.org/Bugzilla:Bzr https://wiki.mozilla.org/Bugzilla:Patches https://wiki.mozilla.org/Bugzilla:Committing_Patches They each contain a little more information than I originally posted to the list. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org

Free Bugzilla T-Shirts for Bugzilla Contributors!

Hey Bugzilla-ers. I don't know if you noticed, but the old Mozilla Store (where you could buy Bugzilla t-shirts) closed down a few months back, and it never re-opened. Well, I don't know if it's ever going to re-open, but Mozilla apparently got all the stock from it, and one of the things they did was they gave me all the Bugzilla t-shirts from the store. I happen to have been given all of the Bugzilla t-shirts that were in the Mozilla Store, to do whatever I want with. :-) As it turns out, what I want to do with them is to give them away to you! :-) According to the box, I hav

Voting is now an Extension, looking for a maintainer

So recently, I was looking over the highest-voted items in the Bugzilla product, and several of the top items were related to the voting system. Also, one of the "3.6 focus" items was "move voting into an extension". So, on trunk, I have now moved voting into an extension called Voting. For at least the next few releases of Bugzilla, this extension will ship with Bugzilla. However, it is now an entirely-self-contained piece of code that should be easier to hack on for anybody who wants to enhance or work on it. Eventually, I'd like to separate it from Bugzilla and find a maintainer

sample data

Hi all. Is there some kind of (small-ish) sample data set that I can use? Obviously, I can enter in a bunch of bogus bugs and then test, but that is a little tedious. If there is another solution I am all for it! (Keep in mind that my internet connection has been a little flaky since I moved to Europe. So, I would really prefer to load this onto my machine for the time being. But, that is not a "requirement"...) TIA! Craig - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Bugzilla cookies HTTP only

What exactly are the security benefits we get from having our cookies HTTPonly? I ask because I was hoping to allow Greasemonkey scripts/Jetpacks etc. which run in the context of Bugzilla pages to grab the auth cookie and pass it on to the API, which can then use it to access Bugzilla. This obviates the rather irritating and insecure step of having to configure every Jetpack or Greasemonkey script with your Bugzilla username and password. However, having refactored BzAPI for this to work, I now realise the cookies are HTTPonly and I can't get to them :-| The usual threat that HTTP

Bzr Commit Message Format

Hey folks. So, bzr has a lot of features that CVS doesn't, one of which is that it supports a lot more information about commits. In particular it supports directly storing data about: 1) Which bug was fixed by this commit (--fixes 1234) 2) Who authored this commit, if it was different from the committer (--author awesome.contributor@example.com). So it seems like we should change the format of our commit messages. I'm not quite sure how we should do that, though. I was thinking maybe just a brief summary of the change and then the r= stuff on the same line? Or the r= stuff on

Bug Relationships

[I've had this idea kicking around in my head for a while, but I don't think I've ever written it up properly for discussion. So here it is. It's inspired by a feature on a proprietary bug tracking system I used to use. It was generally terrible, but this was good.] I think that we should replace dependencies, See Also, and perhaps duplicate marking too with a more generic system of Bug Relationships. It would work like this: an admin would define a number of relationships there could be between bugs. (Some common ones would ship by default.) E.g. A depends on B C caused regress

Ice Cream (Hard Freeze)

Hey folks. So, as of last week or so, we're hard frozen for 3.6. That means that we're going to branch for 3.6, and trunk will become 3.8. I'd like to take this opportunity to do the bzr switchover, though, so we will approve patches for trunk but not check them in until we've switched to bzr. I'm currently waiting on Mozilla to finish setting up the bzr server, at which time I'll send out more information about switching over. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list setting

80-character comments: does it matter?

So, right now we wrap comments server-side at exactly 80 characters before displaying them in the web interface (except for Chinese, Japanese, and Korean, which are always wrapped client-side). Does it actually matter that comments are wrapped at 80 characters? We do it because that's the exact width of the textarea, and so the comments will come out looking almost exactly like they do in the textarea. Does that actually matter? I'm asking because there is currently a bug that would be resolved if we did all comment-wrapping client side. (Though I'm actually not sure that all br

If You Used To Work On Bugzilla And No Longer Do...

Hey there. I'd like to hear from people who used to work on Bugzilla (in any way--as contributors, documentors, reviewers, anything) but no longer do, or people who stopped working on Bugzilla at any point in the past (even if they do work on it again now). I want to know what you feel caused you to stop working on Bugzilla, whether it was an indvidiual thing, a collection of things over time, the overwhelming demands of other parts of life, etc. To avoid starting a flame war, please email me directly instead of responding here on the list. If there was *anything* that discoura

Hard Freeze Extension

Due to LpSolit being unavailable for most of last week, and there being a LOT of patches that are awaiting review for 3.6, we're extending the hard freeze date to December 18. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

The new Bugzilla::Extension system

I spent the last several days re-writing Bugzilla's extensions system. The old system suffered from a few problems, many of which I encountered personally while writing several large extensions: * Template hooks went in a strange location that was partially inexplicable from looking at the code. (Did they go in template/en/hook, or template/en/default/hook, or template/en/extension, or what?) * Code was in individual .pl files that had to be compiled every time they were run, and couldn't really have subroutines in them (because Bugzilla would complain you were redefining the su

Freeze Reminder: November 24

We have our soft freeze for Bugzilla 3.6 on November 24. That means that, after that point, no enhancements will be accepted that do not already have a patch under review. Two weeks after that (December 8) will be the "hard freeze", when no new enhancements will be accepted at all (shortly after that we will branch for 3.6). -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Pre 3.4.3 upgrade question

I use a bookmarklet to copy bug data into bbs format for a forum. Just wondering if it will have to be modified for 3.4.3 Here's the code: javascript:(function()%20{%20var%20title%20=%20document.title;%20function%20htmlEscape(s){return%20s;};%20var%20OS=document.getElementById(%22op_sys%22).value.substring(0,3)%20;var%20PR=document.getElementById(%22product%22).value%20;var%20comp=document.getElementById(%22component%22).value;if(comp==%22XSLT%22||comp==%22MathML%22||%20comp==%22XForms%22||comp==%22SVG%22||comp==%22Layout:%20Canvas%22||comp==%22Editor%22||comp==%22Build%20Config%22)%20PR=PR

Mass influx of old emial

Not strictly on topic... but am I the only one to have suddenly received a load of CVS commit messages, review requests and a few messages from this list that have been stuck on Mozilla servers for more than a week or so? Colin - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Bugzilla::Comment, $bug->longdescs becomes $bug->comments

I just checked in a Bugzilla::Comment object--thanks to James Robson for the first nine revisions of the patch (which was most or much of work, really). Bugzilla::Bug::GetComments no longer exists. $bug->longdescs has become $bug->comments, and it can limit its return value by date, and sort its return value in various ways. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Self introduction: Krzysztof Drewniak

--=-B553SYhIioMjBoCBPJN1 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable Hi. My name is Krzysztof Drewniak. I don't currently have a nick on irc.mozilla.org. I live in (Dallas area), Texas, United States.=20 I know Perl to the point of getting by. I can probably pick up some intermediate SQL if I ever need to work with it. I know simple HTML (the template files' HTML seems understandable enough (for me)). I am bot familiar with Template, but the Template documentation will most likely be self-explanatory. I have not worked on any FOSS projects before, but t

self introduction - Kirubakaran

Name : Kirubakaran.S Chennai , India College of Engineering Guindy, Anna university I would like to help in developing patches and fixing bugs. I am a newcomer ( since I m pursuing my undergraduate studies), Amazingly this is my first open source initiative and I am sure I will definitely learn a lot and contribute towards Bugzilla. I am quite comfortable with PHP, java. I m in learning mode of CGI/ PERL Other skills can be like managing projects, fixing time line and interacting with developers.I am a quick learner. since I am a new comer, I am confus

Hello

Jag =E4r d=F6v ,, jag kan inte proffs sv=E5rt data nu ... jag tycker sv=E5r= t proffs inte mig ...

Ever-present fields

In the past, people have suggested that most fields in the Bug object returned by the HTTP API should be always present. The idea is that it's easier for an API user to just check for a value without having to check for existence first. That would mean adding the following fields with the following default values to every downloaded Bug object: "attachments" => [], "blocks" => [], "cc" => [], "depends_on" => [], "flags" => [], "groups" => [], "is_cc

Configuration object

Me again :-) I've done a design for the object that the /config call will return, which should tell you enough about Bugzilla's configuration to write a good client. https://wiki.mozilla.org/Bugzilla:REST_API:Objects:Configuration This is quite complicated, and I may have got some stuff wrong. So please let me know if you think the design is a good one. Gerv

The timezone problem

So I'm looking at trying to solve (as best I can) the timezone problem for my API. I acquire time information from basically two places - the legacy XML interface, and the XML-RPC interface. Times that I get from the legacy XML interface come with timezone information already, of the +0100 form - although this isn't stored in the timestamp itself, but is external. So when I ship a database between timezones, all the times change :-/ Which is annoying for automated tests which check values of things. Still, for normal databases which aren't weird like mine, I could add or su

Whines to Mailing Lists

I have a client with a feature request for bugzilla. They want to be able to send whine mails to lists as well as just users and groups. I'm new to the bugzilla code base but at a glance it looks like I'll probably want to: 1) define database table(s) for the lists and possible permissioning rules 2) add handling for a MAILTO_LIST type everywhere MAILTO_* is used 3) add support in the front end code for defining and managing mail lists 4) add support to the whines page for mail lists as a type Does this seem a reasonable approach? Is there any other work in progress or completed

API Design Questions

Here are some things I've run into when designing the RESTful API. Perhaps people could tell me what they think the best option is. Attachments ----------- The current design uses URLs of the form: /bug/<bugid>/attachment/<attachid> However, attachids are globally unique, not per-bug unique. And this URL form means you need to know the bug number before you can access the attachment, which seems unnecessary (or it would mean the API just ignored the bug number, which seems somewhat dumb too). If all you have is e.g. a standard attachment URL, you don't have the bug number.

Re: Bug XML output questions

Wouldn't it help a lot if the interface also permitted retrieving an XSD output? The XSD could be generated with an awareness of flag types, custom fields, etc. Since the XSD itself is an xml format, it could either be treated by the client as an xsd or, more likely, parsed as an xml document that answers many of the questions Gerv points out. > > * It doesn't tell you if custom fields are single-valued, or are multiple-valued fields which happen to just contain a single value. You have to call the legal_values API for each field. > > * There's no way of finding out what possi

[ANN] Security Advisory for Bugzilla 3.4.1, 3.2.4, and 3.0.8

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Summary ======= Bugzilla is a Web-based bug-tracking system, used by a large number of software projects. * Two SQL injection attacks have been discovered in Bugzilla. One only affects the 3.4 series, while the other affects the 3.0, 3.2, and 3.4 series. These are extremely serious vulnerabilities that must be patched immediately. * When a user would change his password, his new password would be exposed in the URL field of the browser if he logged in right after changing his password. All affected installations are

landfill test install cleanup

Hi there. If you have a test install on landfill.bugzilla.org and you aren't using it, please delete it: http://landfill.bugzilla.org/tools/installs.cgi I have currently cleared every installation listed on the front page from the "Patches" list except for the QA and L10N installations. (The installations still exist, just don't appear on the front page of landfill.bugzilla.org.) I'm trying to reduce the number of installations that I have to keep secure on landfill. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything El

HTTP RESTful API for Bugzilla

Hi everyone, To try and help Mozilla Project community members (in particular) innovate on top of Bugzilla, I'm going to be creating an HTTP RESTful API for it. As you know, the Mozilla Project has some rather diverse requirements for its bug-tracking tool; hopefully letting people more easily build new tools and task-specific UIs will ease their pain that the default web interface is not all they'd like it to be. Initially, I'm going to be implementing this as a proxy, which has the advantage that its development can be decoupled from the Bugzilla development cycle and b.m

What to do with ssl="authenticated sessions" + code freeze date for Bugzilla 3.6

Hi all, At the Bugzilla meeting today, there has been some discussion about what to do with the "authenticated sessions" value of the ssl parameter now that you can log in from every page. It seems that it doesn't make sense to keep this value anymore as all pages must be protected using SSL as you can potentially use any of them to log in. Does anyone see a valid reason to not kill this value? This means the ssl parameter would become a single yes/no to use ssl or not, see bug 329638. Now something unrelated to SSL, I just wanted to inform you that the code freeze for Bugzilla 3.

Mapping bugzilla bugs to RDF as EvoOnt BOM ontology : RFC

Hello. (I was not subscribed to the list, and started over to overcome moderation issues, sorry for potential duplicate, then.) FYI, as part of our work on the Helios project [0], we've devised a prototype of a small app based on triplify [1] to export data about Bugzilla bugs as RDF, using the EvoOnt BOM [2] ontology (and extensions). We now have a prototype which can take a Bugzilla's DB and output RDF, that will model relationships between people, bugs, comments, together with some bugs properties. We'd like to ask for review of interested people, and maybe try and attr

Announce: BZ::Client 1.0

Hi, I'd like to announce the availability of BZ::Client on CPAN. BZ::Client is a client library for the Bugzilla Webservices API. It provides an object oriented API, which is relatively close to the server side API, but hides the XML-RPC related details completely. Jochen -- Base64 decoding, 300% faster than sun.misc.BASE64Decoder: http://archive.netbsd.se/?ml=commons-dev&a=2008-05&t=7522166 - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Perlmonks website hacked. All passwords have been disclosed!

As Perl developers, you might also have an account on PerlMonks: http://www.perlmonks.org/ Unfortunately, the user database of this site has been compromised and it seems that they saved the passwords in clear text. According to the info on their web page: *all perlmonks users are advised to change their perlmonks.org passwords immediately.* Note: I received the information from PAUSE (Perl Authors Upload Server): > This email is being sent to inform you that all passwords on the popular > Perl Monks website were compromised. Many CPAN authors have accounts > there and in so

Bugzilla now requires Template-Toolkit 2.22

Hi all, I just checked in a patch which requires Template-Toolkit 2.22 on HEAD and on the 3.4 branch (and on the 3.2 branch on Windows only). This means that Bugzilla 3.5.1, 3.4 and 3.2.5 will all require TT 2.22. This also means that if you upgrade via CVS starting from a few minutes ago, TT 2.22 is also required. I checked, and TT 2.22 is available via PPM on Windows since a few hours ago. On Linux, http://www.cpan.org/modules/01modules.index.html didn't refresh since last Saturday for some unknown reason. I emailed them about this earlier today. All other CPAN mirrors I

testopia for bugzilla3.4rc1

hi, i have a problem iam using bugzilla3.4rc1 new one. when i serch for tesopia it is given for 3.0.x and 3.2.x so for my version which one matches. iam in confution to use. thanks in advonce.

Self-Introduction: Eric Olson

Hello everyone. Per the wiki, I'm introducing myself as someone who'd like to contribute to the Bugzilla project. I'm located in Champaign, Illinios, USA, birthplace of both Mosaic and HAL 9000. At my work, we've switched away from an older commercial product to Bugzilla and I was the one that got to convert our database over. I figure working in some small way on the project is a good way to get to know Bugzilla a bit better and hone my Perl skills. I figure I may start working on some of the intro bugs, catching the low-hanging fruit. - To view or change your list setting

default users may use bugzilla by giving access permission

Hi, If my linux box have x,y with some passwords. Know i want to use these users with same passwords as in linux and give access permissions to bugzilla. please help me out from this problem. thanks in advonce.

Reminder: Bugzilla meeting today!

For those who forgot, we meet today at 11:00 PDT (18:00 GMT, 20:00 CEST) on IRC in the #bugzilla-meeting channel. Everyone is welcome. LpSolit - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Draft Release Notes for Bugzilla 3.4

I've posted a patch for release notes for Bugzilla 3.4 on this bug: https://bugzilla.mozilla.org/show_bug.cgi?id=494037 Please review and comment (in the bug) if you would like to. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

Self-Introduction: Sun Xin

Hi all, Thank you for your time to read my self-Introduction. I am the new guy to this community. * Full legal name Sun Nicholas Xin * Your IRC nick on irc.mozilla.org: nicho * City, Country: Beijing, China * Profession * Company: Redhat * What do you want to help out with? I am interesting in bugzilla, maybe I can try to provide patch for some bugs or develop the test case. * Historical qualifications o What other technical projects have you worked on in the past? http://hardware.redhat.com which is based

Bugzilla Webservice Client in Perl

Hi, I have ready what might serve as a first version of a complete Perl client for the Bugzilla Webservice API. See http://people.apache.org/~jochen/scripts/BZ-Client-1.0.tar.gz It is in the standard format of a Perl module, meaning there is a Makefile.PL and a test suite, which includes a fair couple of integration tests. Question is how to proceed. I can imagine two things: a) Add it to the Bugzilla code base. This might very well be used to test the webservices API. b) Publish it on CPAN. My preferred solution would be a), as I had a good share of mails from

bugzilla.mozilla.org improvements

Over the next few months, I will be working on improving bugzilla.mozilla.org to better meet the needs of the Mozilla development community.[0] I am therefore gathering 'requirements' - that is to say, asking people's opinion about which possible improvements would be most useful. This newsgroup post and an associated blogpost pointing here are a start; please let me know if there are other forums I could usefully ask in. (I apologise if the reasonably wide crossposting irritates anyone. It seems that mozilla.announce has morphed into something which non-community-members su

Bugzilla Plugin for Supybot Has a Home

I just created a Google Code page for the Supybot Bugzilla plugin (what bugbot is using to report changes): http://code.google.com/p/supybot-bugzilla/ You can use that to get the code and to report issues about it. -Max -- http://www.everythingsolved.com/ Competent, Friendly Bugzilla and Perl Services. Everything Else, too. - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>

herbavigor

party pills, legal highs www.herbavigor.com

Bugzilla 3.6: Consistency, Completeness, and Usability

Okay, so I have a somewhat-radical proposal to make for Bugzilla 3.6, that I've talked to LpSolit and a few of the other reviewers about already, and it's this: No new features for Bugzilla 3.6. Instead, we focus on fixing the features we already have. This means that we fix all the major HCI (usability) issues in Bugzilla. We finish any incomplete features that we have (so adding enhancements that actually just complete existing features is fine), and we make Bugzilla behave in a universally consistent fashion. There is work for everybody in this scheme! Refactoring t

Re: Moving To Catalyst, Incrementally?

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 - To view or change your list settings, click here: <http://bugzilla.org/cgi-bin/mj_wwwusr?user=dev-apps-bugzilla@lists.mozilla.org>