From lpsolit at gmail.com  Sun Feb  4 13:30:43 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Sun, 04 Feb 2007 14:30:43 +0100
Subject: Bugzilla meeting next Tuesday
Message-ID: <45C5E003.5000207@gmail.com>

Hi all,

We will meet again on Tuesday, February 6 at 19:00 GMT (11:00 PST) in 
the #bugzilla-meeting channel.

You probably noticed that our last meeting 2 weeks ago didn't happen due 
to an empty agenda.

If there is something specific you would like to discuss with us, feel 
free to add your suggestion to our agenda at 
http://wiki.mozilla.org/Bugzilla:Meetings


See you on Tuesday,

LpSolit


From gerv at mozilla.org  Tue Feb  6 15:23:08 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Tue, 06 Feb 2007 15:23:08 +0000
Subject: [Fwd: Bugzilla Installation List]
Message-ID: <45C89D5C.2020408@mozilla.org>

I thought I'd forward you the below message. Not because it's 
particularly unusual - I get between three and ten of these a week - but 
because I realised that most of you may not have noticed or realised 
quite how many companies are now on the installation list (587) and how 
many of them sent in profuse thanks with their applications.

People love our product :-)

Gerv

-------- Original Message --------
Subject: Bugzilla Installation List
Date: Fri, 2 Feb 2007 12:59:20 -0000
From: Patrick Koeberl <patrick.koeberl at dajeil.com>
To: <gerv at mozilla.org>

Hi Gerv,

We have been using Bugzilla for some years now for both our hardware and 
software development activities, so please put us on the installation list!

Thanks to you and the Bugzilla team for all your efforts!

Best regards,

Patrick

Patrick Koeberl
Head of Hardware Development
Dajeil Limited
Tel +353 1 2041428
patrick at dajeil.com
www.dajeil.com




Visit Dajeil's stand 446 at
RSA 2007 from 5th-9th Feb


From after.fallout at gmail.com  Tue Feb  6 15:53:50 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Tue, 06 Feb 2007 10:53:50 -0500
Subject: getting custom fields to display in the buglist css classes
Message-ID: <45C8A48E.20407@gmail.com>

I am trying to get custom fields to show up inside the class attribute 
of the table row in buglist.cgi (I'll file a bug when I get something 
working), but I am unable to get the values.
It appears that bug.${field.name} is always empty inside this template. 
Am I doing something wrong?


Index: template/en/default/list/table.html.tmpl
===================================================================
RCS file: 
/cvsroot/mozilla/webtools/bugzilla/template/en/default/list/table.html.tmpl,v
retrieving revision 1.32
diff -u -r1.32 table.html.tmpl
--- template/en/default/list/table.html.tmpl    20 Oct 2006 15:50:58 
-0000      1.32
+++ template/en/default/list/table.html.tmpl    6 Feb 2007 15:49:31 -0000
@@ -164,6 +164,13 @@
              bz_[% bug.bug_severity FILTER css_class_quote -%]
              bz_[% bug.priority FILTER css_class_quote -%]
              bz_[% bug.bug_status FILTER css_class_quote -%]
+             [% USE Bugzilla %]
+             [% fields = Bugzilla.get_fields({ obsolete => 0, custom => 
1 }) %]
+             [% IF fields %]
+               [% FOREACH field = fields %]
+                 bz_[% field.name FILTER css_class_quote %]_[% 
bug.${field.name} FILTER css_class_quote -%]
+               [% END %]
+             [% END %]
              [%+ "bz_$bug.resolution" FILTER css_class_quote IF 
bug.resolution -%]
              [%+ "bz_secure" IF bug.secure_mode -%]
              [%+ "bz_secure_mode_$bug.secure_mode" FILTER 
css_class_quote IF bug.secure_mode -%]



From justdave at bugzilla.org  Tue Feb  6 16:21:44 2007
From: justdave at bugzilla.org (David Miller)
Date: Tue, 06 Feb 2007 11:21:44 -0500
Subject: getting custom fields to display in the buglist css classes
In-Reply-To: <45C8A48E.20407@gmail.com>
References: <45C8A48E.20407@gmail.com>
Message-ID: <45C8AB18.5050107@bugzilla.org>

You've already got 'field' there in the loop, you don't need to
dereference Bug to get at it.  There

Bill Barry wrote on 2/6/07 10:53 AM:
> I am trying to get custom fields to show up inside the class attribute
> of the table row in buglist.cgi (I'll file a bug when I get something
> working), but I am unable to get the values.
> It appears that bug.${field.name} is always empty inside this template.
> Am I doing something wrong?
> 
> 
> Index: template/en/default/list/table.html.tmpl
> ===================================================================
> RCS file:
> /cvsroot/mozilla/webtools/bugzilla/template/en/default/list/table.html.tmpl,v
> 
> retrieving revision 1.32
> diff -u -r1.32 table.html.tmpl
> --- template/en/default/list/table.html.tmpl    20 Oct 2006 15:50:58
> -0000      1.32
> +++ template/en/default/list/table.html.tmpl    6 Feb 2007 15:49:31 -0000
> @@ -164,6 +164,13 @@
>              bz_[% bug.bug_severity FILTER css_class_quote -%]
>              bz_[% bug.priority FILTER css_class_quote -%]
>              bz_[% bug.bug_status FILTER css_class_quote -%]
> +             [% USE Bugzilla %]
> +             [% fields = Bugzilla.get_fields({ obsolete => 0, custom =>
> 1 }) %]
> +             [% IF fields %]
> +               [% FOREACH field = fields %]
> +                 bz_[% field.name FILTER css_class_quote %]_[%
> bug.${field.name} FILTER css_class_quote -%]
> +               [% END %]
> +             [% END %]
>              [%+ "bz_$bug.resolution" FILTER css_class_quote IF
> bug.resolution -%]
>              [%+ "bz_secure" IF bug.secure_mode -%]
>              [%+ "bz_secure_mode_$bug.secure_mode" FILTER
> css_class_quote IF bug.secure_mode -%]
> 
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=justdave at bugzilla.org>
> 


-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From justdave at bugzilla.org  Tue Feb  6 16:28:36 2007
From: justdave at bugzilla.org (David Miller)
Date: Tue, 06 Feb 2007 11:28:36 -0500
Subject: getting custom fields to display in the buglist css classes
In-Reply-To: <45C8AB18.5050107@bugzilla.org>
References: <45C8A48E.20407@gmail.com> <45C8AB18.5050107@bugzilla.org>
Message-ID: <45C8ACB4.8020705@bugzilla.org>

David Miller wrote on 2/6/07 11:21 AM:
> You've already got 'field' there in the loop, you don't need to
> dereference Bug to get at it.  There

oops, I sent that prematurely...  what I was trying to say was are you
trying to get at the value of the field rather than the name of it?
Looks like it's the same AUTOLOAD method to get at it so that ought to
work...  there may be some limit to the number of things you can stuff
in a class field and have the browser notice it, too.  Have you looked
at the generated source after running that?  I seem to recall that some
browsers only look at the first 8 things in a class attribute.

> Bill Barry wrote on 2/6/07 10:53 AM:
>> I am trying to get custom fields to show up inside the class attribute
>> of the table row in buglist.cgi (I'll file a bug when I get something
>> working), but I am unable to get the values.
>> It appears that bug.${field.name} is always empty inside this template.
>> Am I doing something wrong?
>>
>>
>> Index: template/en/default/list/table.html.tmpl
>> ===================================================================
>> RCS file:
>> /cvsroot/mozilla/webtools/bugzilla/template/en/default/list/table.html.tmpl,v
>>
>> retrieving revision 1.32
>> diff -u -r1.32 table.html.tmpl
>> --- template/en/default/list/table.html.tmpl    20 Oct 2006 15:50:58
>> -0000      1.32
>> +++ template/en/default/list/table.html.tmpl    6 Feb 2007 15:49:31 -0000
>> @@ -164,6 +164,13 @@
>>              bz_[% bug.bug_severity FILTER css_class_quote -%]
>>              bz_[% bug.priority FILTER css_class_quote -%]
>>              bz_[% bug.bug_status FILTER css_class_quote -%]
>> +             [% USE Bugzilla %]
>> +             [% fields = Bugzilla.get_fields({ obsolete => 0, custom =>
>> 1 }) %]
>> +             [% IF fields %]
>> +               [% FOREACH field = fields %]
>> +                 bz_[% field.name FILTER css_class_quote %]_[%
>> bug.${field.name} FILTER css_class_quote -%]
>> +               [% END %]
>> +             [% END %]
>>              [%+ "bz_$bug.resolution" FILTER css_class_quote IF
>> bug.resolution -%]
>>              [%+ "bz_secure" IF bug.secure_mode -%]
>>              [%+ "bz_secure_mode_$bug.secure_mode" FILTER
>> css_class_quote IF bug.secure_mode -%]
>>
>> -
>> To view or change your list settings, click here:
>> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=justdave at bugzilla.org>
>>
> 
> 


-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From after.fallout at gmail.com  Tue Feb  6 16:43:27 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Tue, 06 Feb 2007 11:43:27 -0500
Subject: getting custom fields to display in the buglist css classes
In-Reply-To: <45C8ACB4.8020705@bugzilla.org>
References: <45C8A48E.20407@gmail.com> <45C8AB18.5050107@bugzilla.org> <45C8ACB4.8020705@bugzilla.org>
Message-ID: <45C8B02F.10007@gmail.com>

David Miller wrote:
> David Miller wrote on 2/6/07 11:21 AM:
>   
>> You've already got 'field' there in the loop, you don't need to
>> dereference Bug to get at it.  There
>>     
>
> oops, I sent that prematurely...  what I was trying to say was are you
> trying to get at the value of the field rather than the name of it?
> Looks like it's the same AUTOLOAD method to get at it so that ought to
> work...  there may be some limit to the number of things you can stuff
> in a class field and have the browser notice it, too.  Have you looked
> at the generated source after running that?  I seem to recall that some
> browsers only look at the first 8 things in a class attribute.
I am trying to output "bz_" then the field name, then the field value, 
so for a custom type field with the value of "Feature" it would output:
bz_cf_type_Feature

that is what this line is supposed to do:
bz_[% field.name FILTER css_class_quote %]_[% bug.${field.name} FILTER css_class_quote -%]

However, what it is doing is outputting:
bz_cf_type_

When I look at the generated source I see the following:
class="bz_bugitem bz_normal bz_P3 bz_NEW bz_cf_type_ bz_row_odd"



From pedro.lamarao at intersix.com.br  Tue Feb  6 20:19:43 2007
From: pedro.lamarao at intersix.com.br (=?ISO-8859-1?Q?Pedro_Lamar=E3o?=)
Date: Tue, 06 Feb 2007 18:19:43 -0200
Subject: unregister pedro.lamarao@intersix.com.br
Message-ID: <45C8E2DF.1040405@intersix.com.br>


-- 
Pedro Lamar?o
Desenvolvimento

Intersix Technologies S.A.
SP: (55 11 3803-9300)
RJ: (55 21 3852-3240)
www.intersix.com.br

Your Security is our Business



From lpsolit at gmail.com  Wed Feb  7 13:34:06 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Wed, 07 Feb 2007 14:34:06 +0100
Subject: Minutes of our last Bugzilla meeting
Message-ID: <45C9D54E.5050407@gmail.com>

For those who couldn't attend yesterday:

http://wiki.mozilla.org/Bugzilla:Meetings:2007-02-06

We plan to talk about the roadmap for 3.2 next time, so if you have 
special wishes, something you really want to see implemented, or 
something you plan to work on and which we should know about, add 
[roadmap: 3.2] to the status whiteboard of the corresponding bugs so 
that they will appear in our radar.

I will write a draft on wiki (http://wiki.mozilla.org/Bugzilla:Roadmap) 
probably this week-end so that everyone can add new suggestions before 
we meet on February 20. Note that this will be an initial discussion, so 
the roadmap can still be changed later next month if we think we missed 
something.

LpSolit


From after.fallout at gmail.com  Wed Feb  7 15:08:41 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Wed, 07 Feb 2007 10:08:41 -0500
Subject: getting custom fields to display in the buglist css classes
In-Reply-To: <45C8ACB4.8020705@bugzilla.org>
References: <45C8A48E.20407@gmail.com> <45C8AB18.5050107@bugzilla.org> <45C8ACB4.8020705@bugzilla.org>
Message-ID: <45C9EB79.4050705@gmail.com>

Bill Barry wrote on 2/6/07 10:53 AM:
>>> I am trying to get custom fields to show up inside the class attribute
>>> of the table row in buglist.cgi (I'll file a bug when I get something
>>> working), but I am unable to get the values.
>>> It appears that bug.${field.name} is always empty inside this template.
>>> Am I doing something wrong?
Nevermind any of this; I realized that the field wasn't being selected. 
Once I fixed that it worked. See bug 369612 if anyone is interested in 
the working initial version of the patch 
(https://bugzilla.mozilla.org/show_bug.cgi?id=369612)


From gerv at mozilla.org  Wed Feb  7 17:22:09 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 07 Feb 2007 17:22:09 +0000
Subject: Custom fields
Message-ID: <45CA0AC1.1070509@mozilla.org>

Chaps,

I've updated
http://www.gerv.net/hacking/custom-fields
to reflect the new reality. Comments welcome.

Gerv


From gerv at mozilla.org  Thu Feb  8 14:52:26 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Thu, 08 Feb 2007 14:52:26 +0000
Subject: Personas
Message-ID: <45CB392A.6060202@mozilla.org>

Guys,

I've been through and refreshed the Personas pages:
http://wiki.mozilla.org/Bugzilla:Personas

I assert that Mitch, Peter and Sarah together cover the user base that 
Bugzilla should be focussed on. I'm happy to call this 1.0 soon. Of 
course, they are only as useful as people want to make them. When you 
are designing a feature, think "which persona(s) am I designing this 
for?", and "how would they want to use it?".

Remember, that doesn't mean that everyone who ever uses Bugzilla is 
either "a Mitch", "a Peter" or "a Sarah". For example, in a free 
software project, many developers will be combinations of Mitch and Sarah.

If you really think we need more, read this first:
http://www.cooper.com/newsletters/2001_07/perfecting_your_personas.htm

Gerv


From djm at mindrot.org  Tue Feb 13 23:07:47 2007
From: djm at mindrot.org (Damien Miller)
Date: Wed, 14 Feb 2007 10:07:47 +1100 (EST)
Subject: Personas
In-Reply-To: <45CB392A.6060202@mozilla.org>
References: <45CB392A.6060202@mozilla.org>
Message-ID: <Pine.BSO.4.64.0702141004440.15387@fuyu.mindrot.org>

On Thu, 8 Feb 2007, Gervase Markham wrote:

> Guys,
> 
> I've been through and refreshed the Personas pages:
> http://wiki.mozilla.org/Bugzilla:Personas
> 
> I assert that Mitch, Peter and Sarah together cover the user base that
> Bugzilla should be focussed on. I'm happy to call this 1.0 soon. Of course,
> they are only as useful as people want to make them. When you are designing a
> feature, think "which persona(s) am I designing this for?", and "how would
> they want to use it?".

I disagree with labelling occasional bug reporters ("Fabio" persona) as
Unimportant. For our (OpenSSH's) bugzilla, these make a fair proportion
of bug reports, and some of our most important. I expect other Bugzilla-
using free software projects are similar in this regard.

-d


From gerv at mozilla.org  Thu Feb 15 18:47:05 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Thu, 15 Feb 2007 18:47:05 +0000
Subject: Personas
In-Reply-To: <Pine.BSO.4.64.0702141004440.15387@fuyu.mindrot.org>
References: <45CB392A.6060202@mozilla.org> <Pine.BSO.4.64.0702141004440.15387@fuyu.mindrot.org>
Message-ID: <45D4AAA9.3010502@mozilla.org>

Damien Miller wrote:
> I disagree with labelling occasional bug reporters ("Fabio" persona) as
> Unimportant. For our (OpenSSH's) bugzilla, these make a fair proportion
> of bug reports, and some of our most important. I expect other Bugzilla-
> using free software projects are similar in this regard.

We need to be very clear about the definition of "important" we are 
using. It is not "important to the software project using the Bugzilla", 
  it is "important in designing the software".

While Fabio-type people are undoubtedly important to OpenSSH or Mozilla, 
Fabio uses a very limited part of Bugzilla, and exactly what he sees can 
be customised through templates - as we do on b.m.o., as KDE do, and so 
on. Therefore, it doesn't make sense to design the rest of the software 
around his needs - because he never uses it. And it doesn't make much 
sense to design even the default bug entry screen around him, because 
the one he uses is unsuitable for our other core users, as it's too simple.

So what we do is we say "Fabio is of very limited importance in the 
design of the Bugzilla software, and we can meet his needs using the 
template system".

Do you see the distinction I am making? Is that reasonable?

Gerv


From ycombarnous at yahoo.fr  Wed Feb 14 21:38:29 2007
From: ycombarnous at yahoo.fr (Barns)
Date: Wed, 14 Feb 2007 13:38:29 -0800 (PST)
Subject: windows.bugzilla.org
In-Reply-To: <1165350533.2525.7.camel@es-lappy>
References: <1165350533.2525.7.camel@es-lappy>
Message-ID: <8974110.post@talk.nabble.com>


Just tried to go to query.cgi:

Software error:

DBD::mysql::db selectcol_arrayref failed: Unknown column 'id' in 'field
list' [for Statement "
            SELECT id FROM versions
            WHERE product_id = ?"] at Bugzilla/Product.pm line 109
	Bugzilla::Product::versions('Bugzilla::Product=HASH(0x25bf68c)') called at
C:/webroot/bugzilla-tip/query.cgi line 193




Max Kanat-Alexander wrote:
> 
> 	We now have a Windows Server 2003 testing machine for the Bugzilla
> Project!
> 
> 	You can see the first installation here:
> 
> 	http://windows.bugzilla.org/bugzilla-tip/
> 
> 	That's running on Apache. I'm also going to set up IIS later, on a
> different port.
> 
> 	Because this is a Windows machine (and thus a little more touchy about
> security and licensing), the reasons that we give out accounts on this
> machine will be much more limited than the reasons we give out landfill
> accounts.
> 
> 	If you are a Bugzilla developer with a good reason to need access to a
> Windows machine, contact me and I can set you up, and then I can tell
> you how the machine is configured.
> 
> 	Oh, and a big thanks to the Mozilla Community Giving Program, which set
> this all up for us and paid for everything.
> 
> 	-Max
> -- 
> http://www.everythingsolved.com/
> Everything Solved: Competent, Friendly Bugzilla and Linux Services
> 
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=lists at nabble.com>
> 
> 

-- 
View this message in context: http://www.nabble.com/windows.bugzilla.org-tf2764013.html#a8974110
Sent from the Bugzilla - Dev mailing list archive at Nabble.com.



From mkanat at bugzilla.org  Thu Feb 15 23:04:15 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Thu, 15 Feb 2007 15:04:15 -0800
Subject: windows.bugzilla.org
In-Reply-To: <8974110.post@talk.nabble.com>
References: <1165350533.2525.7.camel@es-lappy>
	<8974110.post@talk.nabble.com>
Message-ID: <20070215230427.3897518176@help.trusthosting.net>

On Wed, 14 Feb 2007 13:38:29 -0800 (PST) Barns <ycombarnous at yahoo.fr>
wrote:
> Just tried to go to query.cgi:
> 
> Software error: [snip]

	Ah, I had forgotten to run checksetup.pl on the server last
time I updated it. :-) It should be fixed now.

	-Max


From mkanat at bugzilla.org  Fri Feb 16 02:17:10 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Thu, 15 Feb 2007 18:17:10 -0800
Subject: supybot plugin for Bugzilla
Message-ID: <20070216021713.D85D718176@help.trusthosting.net>

	Hello out there in Bugzilla land.

	For those of you who use IRC, and who also use Bugzilla, and
who like IRC bots, I've written a Bugzilla plugin for supybot. 

	It can do searches against your Bugzilla, report changes to
the channel as they come in by email, and get the details of bugs and
attachments in your Bugzilla. It currently only works with the very
latest Bugzilla releases, 2.23 and above. If there's significant
interest in making it work with Bugzilla 2.22 or earlier, I can look
into that.

	I've submitted it to supybot.com, but they haven't made it
visible yet.

	Until then, you can get it using bzr:

	bzr checkout http://bzr.everythingsolved.com/supybot/Bugzilla

	And to update it (to any new version that I release, or to the
latest code), you just have to go to the Bugzilla directory and do:

	bzr update

	-Max


From justdave at bugzilla.org  Sat Feb 17 04:20:16 2007
From: justdave at bugzilla.org (David Miller)
Date: Fri, 16 Feb 2007 23:20:16 -0500
Subject: Open Source Press Relations
Message-ID: <45D68280.1060600@bugzilla.org>

Last year at OSCON I attended a session on "Open Source Press Relations"
that was led by Josh Berkus, who was the Postgres lead at Sun Microsystems.

With Bugzilla 3.0 being a major milestone, it's a good chance for us to
jump into the press game and get some good coverage for our new release.

The following are the notes I took at his presentation.  Hopefully
they're mostly coherent.  I don't know how much of it we can actually
do, but it'd probably be fun to try. :)

Open Source Press Relations
===========================

Josh Berkus
Postgres lead for Sun

Resources
- volunteers
- press contacts
- reference users
- press kit
- a little money

Volunteers Wanted!
- writers/designers
  - press releases
  - webdesign and graphics
  - handouts and articles
- translators
  - all of the above
- regional contacts
  - press/business experience
  - email & phone for work hours
  - one per country/region/language

care & feeding of volunteers
- PR contributions are as valuable as code, treat it that way
- OS-PR is participatory: ask, don't tell
- make sure each PR volunteer gets their 15 minutes of fame.

press contacts: your list
- collect a list
  - bloggers/reporters in your community
  - reporters who have covered your project
  - lists from conferences
  - business cards
- manage the list
  - keep in central secure location
  - separate into categories:
    - cold - only interested in releases, if anything
    - warm - covered in the past, seem to get it
    - intimate - go to events, etc.

reference users
- you need them
  - quotes
  - interviews
  - case studies
- get them through your community
  - mailing lists
  - consultant clients
  - conferences
- keep their contact info handy

press kit
- one-stop shopping for reporters
  - "what is" document
  - "latest news" document
  - case studies & reference users
  - contact information / regional contacts
  - logos/graphics
  - self-booting CD?
- have the same information everywhere
  - website (single web page with anchors for sections)
  - paper handouts (give them out at conferences)

handling the press

1. Reporters are people, too.  Treat them like another developer that
you respect, but they develop news rather than code.
   - Don't insult them when they get something wrong.
   - Do thank them when they get something right.

2. NOTHING is off the record.
   - Don't share it with a reporter if you don't want it shared with the
world.
   - Do plan everything you're going to say.
   - Don't expect to get a preview of the article

3. If you want to decide the news, you do the work
   - Do respond very quickly to requests
   - Do offer facts and quotes, and lists of contacts to reporters, And
numbers!
   - Do look for the "newsworthy" story.
   - Don't tell them what to report.

getting press for a release

8 weeks out: draft release

- Do it in an open source way
  - involve your advocacy group
  - use mailing lists and wikis/version control
  - "many eyes make bugs shallow" is true of press releases, too
  - allow 3 to 4 weeks for draft.
- Don't be afraid to do it in the open.  Most reporters don't have time
to follow along, so you shouldn't have to worry much about premature
announcements (usually).
- Use professional release format
  - top-down composition (so they can tell in the first paragraph if
they want to carry the story or not)
  - emphasize news value
  - have a theme (something to unify the story line in the press release)
  - one to 1.5 pages long
- professional release format has 8 parts
  1. contact information - include a phone number of someone who can
take phone calls during business hours
  2. dateline - mandatory: most services will auto-reject without
reading it if it doesn't have one.
  3. summary paragraph
  4. theme paragraph
  5a. first quote - full name and title of the person quoted, you'll get
calls asking for it if you don't include that
  6a. detailed information
  5b. second quote
  6b. Additional detail (keep it short)
  7. "about" paragraph - usually the same every time, may evolve over time.
  8. link to more information (press kit URL)

4 weeks out: create press kit

- press release, plus:
  - links to more advocacy information (case studies, etc)
  - full text of quotes
  - detail that didn't fit in the release
  - information about quoted companies
  - links to regional contacts

- get website ready to roll
  - use CMS so that you can activate content "all at once" (stage on a
branch?)
  - links to downloads
  - home page announcement
  - traffic monitors (statistics, etc)

- release to translators so you can send native-language press releases
to foreign press.

1 week out: "embargoed" releases

- contact press whom you "trust"
  - must agree to not release until the release date
  - must be willing to postpone/cancel release in case of problems
  - a good way to reward reporters you like
- additional advance content
  - Q&A about release
  - demo if appropriate
  - arrange interviews with developers/users
- be aware of press schedules
- file release with PRWire (especially if you don't have a lot of press
contacts yet)  This has to be done 2 days ahead of when you want the
release to be distributed.

12 hours out: stuff up on website

- last chance to postpone
  - check with lead developers (are we ready to go?)
- put up on web
  - press kit
  - home page news

0 hour: send out release

- contact embargo reporters and give the all-clear
- spam your whole press list
  - individual email to each press contact, not a mailing list or BCC
(use a script to send it if you want)
  - return address should be "press at ....."
- tell the translators to release to foreign press

1 to 5 days after: follow-up

- follow up with key reporters
- start collecting links to press coverage
  - send corrections, if necessary
- slashdot it!  digg it!
- update press list (weed out people who bounce, collect names of
reporters who ran the story? etc)
- thank volunteers, throw a party if local.


-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From justdave at bugzilla.org  Sat Feb 17 04:22:56 2007
From: justdave at bugzilla.org (David Miller)
Date: Fri, 16 Feb 2007 23:22:56 -0500
Subject: Personas
In-Reply-To: <45D4AAA9.3010502@mozilla.org>
References: <45CB392A.6060202@mozilla.org> <Pine.BSO.4.64.0702141004440.15387@fuyu.mindrot.org> <45D4AAA9.3010502@mozilla.org>
Message-ID: <45D68320.3060008@bugzilla.org>

Gervase Markham wrote on 2/15/07 1:47 PM:
> Damien Miller wrote:
>> I disagree with labelling occasional bug reporters ("Fabio" persona) as
>> Unimportant. For our (OpenSSH's) bugzilla, these make a fair proportion
>> of bug reports, and some of our most important. I expect other Bugzilla-
>> using free software projects are similar in this regard.
> 
> We need to be very clear about the definition of "important" we are
> using. It is not "important to the software project using the Bugzilla",
>  it is "important in designing the software".
> 
> While Fabio-type people are undoubtedly important to OpenSSH or Mozilla,
> Fabio uses a very limited part of Bugzilla, and exactly what he sees can
> be customised through templates - as we do on b.m.o., as KDE do, and so
> on. Therefore, it doesn't make sense to design the rest of the software
> around his needs - because he never uses it. And it doesn't make much
> sense to design even the default bug entry screen around him, because
> the one he uses is unsuitable for our other core users, as it's too simple.
> 
> So what we do is we say "Fabio is of very limited importance in the
> design of the Bugzilla software, and we can meet his needs using the
> template system".
> 
> Do you see the distinction I am making? Is that reasonable?

I think what Damien is pointing out is that Fabio should still be
considered an important customer of the Bugzilla design, and that the
one or two pages that he's ever going to see need to include his needs
in their design, even if it is only one or two pages.

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From mkanat at bugzilla.org  Sat Feb 17 07:09:15 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Fri, 16 Feb 2007 23:09:15 -0800
Subject: Open Source Press Relations
In-Reply-To: <45D68280.1060600@bugzilla.org>
References: <45D68280.1060600@bugzilla.org>
Message-ID: <20070217070915.EBB1518183@help.trusthosting.net>

On Fri, 16 Feb 2007 23:20:16 -0500 David Miller <justdave at bugzilla.org>
wrote:
> - [snip] throw a party if local.

	Okay, now see, I like that idea. :-D

	Also, did he have any slides for the stuff?

	We can write a press release, I suppose, and just make sure
that it's done long before we release. The notes are pretty good stuff.
I don't know how much news coverage we really need--I don't really want
to read *reviews* of Bugzilla, but just announcements being out there
would be cool. :-)

	(My thought on reviews is that many of the technical reviewers
I've ever known in previous jobs get things wrong, and we already
have good word-of-mouth and a major public installation so I don't see
the need for lots of reviews.)

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.


From justdave at bugzilla.org  Sat Feb 17 07:16:19 2007
From: justdave at bugzilla.org (David Miller)
Date: Sat, 17 Feb 2007 02:16:19 -0500
Subject: Open Source Press Relations
In-Reply-To: <20070217070915.EBB1518183@help.trusthosting.net>
References: <45D68280.1060600@bugzilla.org> <20070217070915.EBB1518183@help.trusthosting.net>
Message-ID: <45D6ABC3.2080906@bugzilla.org>

Max Kanat-Alexander wrote on 2/17/07 2:09 AM:
> On Fri, 16 Feb 2007 23:20:16 -0500 David Miller <justdave at bugzilla.org>
> wrote:
>> - [snip] throw a party if local.
> 
> 	Okay, now see, I like that idea. :-D
> 
> 	Also, did he have any slides for the stuff?

Yeah, he did, and they were supposed to get posted on the OSCON website,
but I looked earlier tonight (I was going to link to them if they were
there) and they never got posted.

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From lpsolit at gmail.com  Sat Feb 17 12:33:27 2007
From: lpsolit at gmail.com (=?UTF-8?B?RnLDqWTDqXJpYyBCdWNsaW4=?=)
Date: Sat, 17 Feb 2007 13:33:27 +0100
Subject: Open Source Press Relations
In-Reply-To: <45D68280.1060600@bugzilla.org>
References: <45D68280.1060600@bugzilla.org>
Message-ID: <45D6F617.80709@gmail.com>


> 8 weeks out: draft release

We are a bit late, no? :)


From lpsolit at gmail.com  Sat Feb 17 15:14:28 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Sat, 17 Feb 2007 16:14:28 +0100
Subject: Showstopper for Bugzilla 3.0 RC1
Message-ID: <45D71BD4.2030203@gmail.com>

Hi all,

Sorry to announce that two days before the expected release date, but as 
the QA lead, I put my veto on the current Bugzilla 3.0 RC1 release, see 
bug 370739 for details.

The reason is that the UI looks completely broken with Firefox 2 and I 
disagree to release Bugzilla 3.0 RC1 with such a major bug.

Help to fix this UI issue is welcome. Feel free to comment in the bug 
directly and to propose a patch so that we can release 3.0 RC1 asap.


LpSolit


From lpsolit at gmail.com  Sat Feb 17 17:59:56 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Sat, 17 Feb 2007 18:59:56 +0100
Subject: Showstopper for Bugzilla 3.0 RC1 - part 2
Message-ID: <45D7429C.4000602@gmail.com>

"The reason is that the UI looks completely broken with Firefox 2"

Some more information about this UI issue. You need to edit a bug to see 
this issue. If you look at it without editing the bug, it seems to 
display correctly.

ajschult in #qa said it may be related to my network connection speed. 
So this may involve a very minor part of Bugzilla users, in which case I 
would not block the release of Bugzilla 3.0 RC1 any longer. But I prefer 
to have some other users/developers looking at this problem first.

We still have some QA tests to run anyway, and release stuff to write 
before we are ready to release 3.0 RC1, so we have a few days left to 
investigate.


LpSolit


From mkanat at bugzilla.org  Sun Feb 18 04:06:04 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Sat, 17 Feb 2007 20:06:04 -0800
Subject: LinuxWorld Talk
Message-ID: <20070218040605.76B3418185@help.trusthosting.net>

	Hey! I was thinking of submitting an application to speak at
LinuxWorld San Francisco this year, about Bugzilla. Is there anybody
else who would like to speak with me, or can anybody think of any panel
ideas that we could do, perhaps? (Even with other projects or with
some Mozilla project, but probably not with other bug-tracking
projects.)

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.


From gbn at hqso.net  Sun Feb 18 05:18:52 2007
From: gbn at hqso.net (=?iso-8859-1?Q?Guzm=E1n_Bras=F3?=)
Date: Sun, 18 Feb 2007 02:18:52 -0300 (UYT)
Subject: Open Source Press Relations
In-Reply-To: <45D6F617.80709@gmail.com>
References: <45D68280.1060600@bugzilla.org> <45D6F617.80709@gmail.com>
Message-ID: <41860.201.217.156.22.1171775932.squirrel@www.hqso.com>

I vote yes for a press release JUST for media of opensource software
(slashdot, linuxjournal, etc).

I vote no for a press release for every one who have a webpage. Except we
have someone with the time to follow each one of the news, reply any
question the people who post it may have, etc. I think that some times
could  be extremely time consuming.

I can translate it into latin american spanish and resubmit it to latin
american spanish media of opensource software. I put "latin american"
because I believe the best would be to find someone from spain to
translate it to spain spanish. Latin american spanish and spain spanish
are not equal and sometimes there are words that means the opposite. E.g:
(L.A.  "cojer" is "fuck", Spain "cojer" is "take").

Regards,

valor



From lpsolit at gmail.com  Mon Feb 19 09:29:48 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Mon, 19 Feb 2007 10:29:48 +0100
Subject: Bugzilla meeting postponed
Message-ID: <45D96E0C.8060503@gmail.com>

FYI, the Bugzilla meeting which was initially planned for tomorrow is 
postponed until later this week (or eventually next week). The reason is 
that I cannot attend tomorrow (I have another meeting at the same time 
where I have to move physically). As we are very close to the release of 
Bugzilla 3.0 RC1, my presence as the QA lead is desirable by some other 
key developers.

I will let you know when we will meet (as soon as I have talked with 
other developers).


LpSolit


From gerv at mozilla.org  Mon Feb 19 15:29:22 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Mon, 19 Feb 2007 15:29:22 +0000
Subject: Personas
In-Reply-To: <45D68320.3060008@bugzilla.org>
References: <45CB392A.6060202@mozilla.org> <Pine.BSO.4.64.0702141004440.15387@fuyu.mindrot.org> <45D4AAA9.3010502@mozilla.org> <45D68320.3060008@bugzilla.org>
Message-ID: <45D9C252.8000601@mozilla.org>

David Miller wrote:
> Gervase Markham wrote on 2/15/07 1:47 PM:
>> Do you see the distinction I am making? Is that reasonable?
> 
> I think what Damien is pointing out is that Fabio should still be
> considered an important customer of the Bugzilla design, and that the
> one or two pages that he's ever going to see need to include his needs
> in their design, even if it is only one or two pages.

Well, if we include create-guided.html.tmpl as part of core Bugzilla. :-)

Two definitions from the web page are:
http://wiki.mozilla.org/Bugzilla:Personas

Focal: Focal users are primary users of the product who are its main 
focus. We will optimize the design for them.

I think we can agree that Fabio is not focal.

Unimportant: Unimportant users are low-priority users, including 
infrequent, unauthorized or unskilled users, as well as those who misuse 
the product.

Fabio is an infrequent user (himself; although there are a lot of him), 
and he's unskilled. Perhaps "Unimportant" is the wrong word in this 
particular case, but in terms of the amount of consideration we need to 
give him relative to our Focal personas, I think he's in the right category.

Gerv


From kevin.benton at amd.com  Mon Feb 19 16:16:46 2007
From: kevin.benton at amd.com (Benton, Kevin)
Date: Mon, 19 Feb 2007 08:16:46 -0800
Subject: Open Source Press Relations
References: <45D68280.1060600@bugzilla.org>
Message-ID: <D85E06673A2DFF44B221CF78D1CBB11BFE5FD4@SSVLEXMB1.amd.com>

"Wooing the press is an exercise roughly akin to picnicking with a
tiger. You might enjoy the meal, but the tiger always eats last."  --
Maureen Dowd.


Kevin Benton
Senior Software Developer
MSS Silicon Design Engineering
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.
 
-----Original Message-----
From: developers-owner at bugzilla.org
[mailto:developers-owner at bugzilla.org] On Behalf Of David Miller
Sent: Friday, February 16, 2007 9:20 PM
To: developers at bugzilla.org
Cc: Mary Colvig
Subject: Open Source Press Relations

Last year at OSCON I attended a session on "Open Source Press Relations"
that was led by Josh Berkus, who was the Postgres lead at Sun
Microsystems.

With Bugzilla 3.0 being a major milestone, it's a good chance for us to
jump into the press game and get some good coverage for our new release.

The following are the notes I took at his presentation.  Hopefully
they're mostly coherent.  I don't know how much of it we can actually
do, but it'd probably be fun to try. :)

Open Source Press Relations
===========================

Josh Berkus
Postgres lead for Sun

Resources
- volunteers
- press contacts
- reference users
- press kit
- a little money

Volunteers Wanted!
- writers/designers
  - press releases
  - webdesign and graphics
  - handouts and articles
- translators
  - all of the above
- regional contacts
  - press/business experience
  - email & phone for work hours
  - one per country/region/language

care & feeding of volunteers
- PR contributions are as valuable as code, treat it that way
- OS-PR is participatory: ask, don't tell
- make sure each PR volunteer gets their 15 minutes of fame.

press contacts: your list
- collect a list
  - bloggers/reporters in your community
  - reporters who have covered your project
  - lists from conferences
  - business cards
- manage the list
  - keep in central secure location
  - separate into categories:
    - cold - only interested in releases, if anything
    - warm - covered in the past, seem to get it
    - intimate - go to events, etc.

reference users
- you need them
  - quotes
  - interviews
  - case studies
- get them through your community
  - mailing lists
  - consultant clients
  - conferences
- keep their contact info handy

press kit
- one-stop shopping for reporters
  - "what is" document
  - "latest news" document
  - case studies & reference users
  - contact information / regional contacts
  - logos/graphics
  - self-booting CD?
- have the same information everywhere
  - website (single web page with anchors for sections)
  - paper handouts (give them out at conferences)

handling the press

1. Reporters are people, too.  Treat them like another developer that
you respect, but they develop news rather than code.
   - Don't insult them when they get something wrong.
   - Do thank them when they get something right.

2. NOTHING is off the record.
   - Don't share it with a reporter if you don't want it shared with the
world.
   - Do plan everything you're going to say.
   - Don't expect to get a preview of the article

3. If you want to decide the news, you do the work
   - Do respond very quickly to requests
   - Do offer facts and quotes, and lists of contacts to reporters, And
numbers!
   - Do look for the "newsworthy" story.
   - Don't tell them what to report.

getting press for a release

8 weeks out: draft release

- Do it in an open source way
  - involve your advocacy group
  - use mailing lists and wikis/version control
  - "many eyes make bugs shallow" is true of press releases, too
  - allow 3 to 4 weeks for draft.
- Don't be afraid to do it in the open.  Most reporters don't have time
to follow along, so you shouldn't have to worry much about premature
announcements (usually).
- Use professional release format
  - top-down composition (so they can tell in the first paragraph if
they want to carry the story or not)
  - emphasize news value
  - have a theme (something to unify the story line in the press
release)
  - one to 1.5 pages long
- professional release format has 8 parts
  1. contact information - include a phone number of someone who can
take phone calls during business hours
  2. dateline - mandatory: most services will auto-reject without
reading it if it doesn't have one.
  3. summary paragraph
  4. theme paragraph
  5a. first quote - full name and title of the person quoted, you'll get
calls asking for it if you don't include that
  6a. detailed information
  5b. second quote
  6b. Additional detail (keep it short)
  7. "about" paragraph - usually the same every time, may evolve over
time.
  8. link to more information (press kit URL)

4 weeks out: create press kit

- press release, plus:
  - links to more advocacy information (case studies, etc)
  - full text of quotes
  - detail that didn't fit in the release
  - information about quoted companies
  - links to regional contacts

- get website ready to roll
  - use CMS so that you can activate content "all at once" (stage on a
branch?)
  - links to downloads
  - home page announcement
  - traffic monitors (statistics, etc)

- release to translators so you can send native-language press releases
to foreign press.

1 week out: "embargoed" releases

- contact press whom you "trust"
  - must agree to not release until the release date
  - must be willing to postpone/cancel release in case of problems
  - a good way to reward reporters you like
- additional advance content
  - Q&A about release
  - demo if appropriate
  - arrange interviews with developers/users
- be aware of press schedules
- file release with PRWire (especially if you don't have a lot of press
contacts yet)  This has to be done 2 days ahead of when you want the
release to be distributed.

12 hours out: stuff up on website

- last chance to postpone
  - check with lead developers (are we ready to go?)
- put up on web
  - press kit
  - home page news

0 hour: send out release

- contact embargo reporters and give the all-clear
- spam your whole press list
  - individual email to each press contact, not a mailing list or BCC
(use a script to send it if you want)
  - return address should be "press at ....."
- tell the translators to release to foreign press

1 to 5 days after: follow-up

- follow up with key reporters
- start collecting links to press coverage
  - send corrections, if necessary
- slashdot it!  digg it!
- update press list (weed out people who bounce, collect names of
reporters who ran the story? etc)
- thank volunteers, throw a party if local.


-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/
-
To view or change your list settings, click here:
<http://bugzilla.org/cgi-bin/mj_wwwusr?user=kevin.benton at amd.com>






From dwilliss at microimages.com  Tue Feb 20 21:52:56 2007
From: dwilliss at microimages.com (Dave Williss)
Date: Tue, 20 Feb 2007 15:52:56 -0600
Subject: Email headers
Message-ID: <45DB6DB8.1000902@microimages.com>

I was wondering how one would go about adding extra X-Bugzilla headers 
to BugMail.pm
It seems that the headers themselves come from data/params, (editable 
via web interface) but it refers to things like %component%, 
%reasonsheader%, etc.  I want a %priority%, but it doesn't seem to be set.

I can see where in BugMail.pm it sets members of a $substs hash with 
those values.
What I can't figure out is how to get the bug priority in that module so 
I can add a Priority header.

This is Bugzilla 2.22, BTW.


From ghendricks at novell.com  Tue Feb 20 22:17:29 2007
From: ghendricks at novell.com (Gregary Hendricks)
Date: Tue, 20 Feb 2007 15:17:29 -0700
Subject: LinuxWorld Talk
Message-ID: <45DB1109020000D20000618A@sinclair.provo.novell.com>

On Sat, 2007-02-17 at 20:06 -0800, Max Kanat-Alexander wrote:
> 	Hey! I was thinking of submitting an application to speak at
> LinuxWorld San Francisco this year, about Bugzilla. Is there anybody
> else who would like to speak with me, or can anybody think of any panel
> ideas that we could do, perhaps? (Even with other projects or with
> some Mozilla project, but probably not with other bug-tracking
> projects.)
> 
> 	-Max

I have some slides and a presentation about using Bugzilla in the
enterprise. I am also not abashed about standing on a stage and
promoting open source. ;)

I would love to get involved in something like this. Feel free to email
me directly.

Greg Hendricks
ghendricks at novell.com



From lpsolit at gmail.com  Wed Feb 21 13:33:23 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Wed, 21 Feb 2007 14:33:23 +0100
Subject: All QA tests done. a=qa_team for 3.0 RC1
Message-ID: <45DC4A23.6000702@gmail.com>

Except some minor bugs with dependency trees (bugs 309108 and 370883) 
and the UI issue some users are experiencing when viewing bugs (bug 
370739), Bugzilla 3.0 RC1 is ready for release. a=qa_team. :)

The bugs mentioned above won't block RC1 and it will be available for 
download as soon as the release stuff is complete, which could happen 
this week.

LpSolit


From gerv at mozilla.org  Thu Feb 22 12:05:02 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Thu, 22 Feb 2007 12:05:02 +0000
Subject: Email headers
In-Reply-To: <45DB6DB8.1000902@microimages.com>
References: <45DB6DB8.1000902@microimages.com>
Message-ID: <45DD86EE.1020605@mozilla.org>

Dave Williss wrote:
> I was wondering how one would go about adding extra X-Bugzilla headers 
> to BugMail.pm
> It seems that the headers themselves come from data/params, (editable 
> via web interface) but it refers to things like %component%, 
> %reasonsheader%, etc.  I want a %priority%, but it doesn't seem to be set.

You might be better off asking in the support newsgroup, 
mozilla.support.bugzilla on news.mozilla.org.

Gerv


From mkanat at bugzilla.org  Fri Feb 23 05:03:29 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Thu, 22 Feb 2007 21:03:29 -0800
Subject: Making it Easier to Contribute to Bugzilla (2007 Edition)
Message-ID: <20070223050329.90B431821F@help.trusthosting.net>

	A long time ago, some of you may remember a thread called
"Making it easier to contribute to Bugzilla." I saved every email in
that thread and marked them all for getting back to, later. (This was
at the end of 2005.)

	Well, today I've gone over them all, and I'm excited to say
that I'm starting a project to make it easier to contribute.

	The major plan is tracked from here:

	https://bugzilla.mozilla.org/show_bug.cgi?id=371334

	As you can see, there's *lots* of documentation that could be
contributed. (Everything under step 5, there.) The best part is that
it can all go into the wiki, so it doesn't need to go through a review
process or anything!

	My goal is to have 10 active reviewers from a growing pool of
contributors, by the end of the year. By "active" I mean about as
active as myself, travis, LpSolit, and Wurblzap were back in 2005.

	The way that we get reviewers is to get contributors, and the
way that we get contributors is to make it *trivially easy* to
contribute to Bugzilla. And then once we have them, be nice to them!
Don't be mean to them, please. :-) Everybody's a little confused when
they first come into a new project--they just need some help.

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.


From justdave at bugzilla.org  Fri Feb 23 05:13:19 2007
From: justdave at bugzilla.org (David Miller)
Date: Fri, 23 Feb 2007 00:13:19 -0500
Subject: Making it Easier to Contribute to Bugzilla (2007 Edition)
In-Reply-To: <20070223050329.90B431821F@help.trusthosting.net>
References: <20070223050329.90B431821F@help.trusthosting.net>
Message-ID: <45DE77EF.9060000@bugzilla.org>

Max Kanat-Alexander wrote on 2/23/07 12:03 AM:

> 	Well, today I've gone over them all, and I'm excited to say
> that I'm starting a project to make it easier to contribute.

Lots of good ideas in there, thanks for picking this back up!

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From bugreport at peshkin.net  Fri Feb 23 08:48:45 2007
From: bugreport at peshkin.net (Joel Peshkin)
Date: Fri, 23 Feb 2007 00:48:45 -0800
Subject: Making it Easier to Contribute to Bugzilla (2007 Edition)
In-Reply-To: <20070223050329.90B431821F@help.trusthosting.net>
References: <20070223050329.90B431821F@help.trusthosting.net>
Message-ID: <45DEAA6D.8090807@peshkin.net>

     > -- Comment #1 from Max Kanat-Alexander <mkanat at bugzilla.org>
    2007-02-22 21:03:52 PST ---
     > I'm also going to contact Seth at community giving to see if I
    can get some
     > credit at the Mozilla Store for sending Bugzilla T-Shirts to new
    contributors.


I'm not sure if we want the standard Bugzilla shirt or one that says "I 
contributed code to Bugzilla and all I got was this lousy T-shirt"





From lpsolit at gmail.com  Fri Feb 23 16:28:36 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Fri, 23 Feb 2007 17:28:36 +0100
Subject: Making it Easier to Contribute to Bugzilla (2007 Edition)
In-Reply-To: <20070223050329.90B431821F@help.trusthosting.net>
References: <20070223050329.90B431821F@help.trusthosting.net>
Message-ID: <45DF1634.5040601@gmail.com>

> 	My goal is to have 10 active reviewers from a growing pool of
> contributors, by the end of the year.

Is "good luck" appropriate here?


From lpsolit at gmail.com  Fri Feb 23 22:07:38 2007
From: lpsolit at gmail.com (=?ISO-8859-1?Q?Fr=E9d=E9ric_Buclin?=)
Date: Fri, 23 Feb 2007 23:07:38 +0100
Subject: Bugzilla meeting next Tuesday
Message-ID: <45DF65AA.7070300@gmail.com>

The postponed Bugzilla meeting will finally take place next Tuesday, 
February 27 at 19:00 GMT (11:00 PST, 20:00 CET) in the #bugzilla-meeting 
channel on IRC.

The main topic will be about the roadmap for 3.2 and the release of 
Bugzilla 3.0 RC1 (which should be available before we meet).

Anyone interested can attend, as usual.


See you next week,

LpSolit


From chicks at chicks.net  Sun Feb 25 12:16:40 2007
From: chicks at chicks.net (Christopher Hicks)
Date: Sun, 25 Feb 2007 07:16:40 -0500
Subject: Making it Easier to Contribute to Bugzilla (2007 Edition)
In-Reply-To: <45DEAA6D.8090807@peshkin.net>
References: <20070223050329.90B431821F@help.trusthosting.net> <45DEAA6D.8090807@peshkin.net>
Message-ID: <20070225121640.GG9261@chicks.net>

On Fri, Feb 23, 2007 at 12:48:45AM -0800, Joel Peshkin wrote:
>     > -- Comment #1 from Max Kanat-Alexander <mkanat at bugzilla.org>
>    2007-02-22 21:03:52 PST ---
>     > I'm also going to contact Seth at community giving to see if I
>    can get some
>     > credit at the Mozilla Store for sending Bugzilla T-Shirts to new
>    contributors.
> 
> I'm not sure if we want the standard Bugzilla shirt or one that says "I 
> contributed code to Bugzilla and all I got was this lousy T-shirt"

I'd want the "I tried to contribute code to bugzilla, but I ended up forking a few files 3 years ago and I've been too lazy to upgrade since" t-shirt.  :)

Props to Max for restarting this "dev friendliness drive".  Wiki-ing is fun, so I'll see if I can't contribute some docs..... 

-- 
</chris>

The whole problem with the world is that fools and fanatics are always so
certain of themselves, and wiser people so full of doubts.
            - Bertrand Russell, philosopher, mathematician, author,
              Nobel laureate (1872-1970)


From mkanat at bugzilla.org  Mon Feb 26 09:30:49 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Mon, 26 Feb 2007 01:30:49 -0800
Subject: Trunk Open for 3.2!
Message-ID: <20070226093049.AC4241828E@help.trusthosting.net>

	With the release of Bugzilla 3.0rc1, the trunk is open for
development on 3.2! Have fun. :-)

	We're going to discuss our 3.2 roadmap in our meeting this
coming Tuesday. You can see the draft here:

	http://wiki.mozilla.org/Bugzilla:Roadmap

	And of course, info about the meetings is here:

	http://wiki.mozilla.org/Bugzilla:Meetings

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.


From mbd at dbc.dk  Mon Feb 26 13:00:27 2007
From: mbd at dbc.dk (Mads Bondo Dydensborg)
Date: Mon, 26 Feb 2007 14:00:27 +0100
Subject: Added reference to bugzproxy go Bugzilla plugin wiki page
Message-ID: <200702261400.27725.mbd@dbc.dk>

Hi there.

It says to mail the dev list if one adds something to the Bugzilla plugin 
page, so here goes:

[edit]
 Desktop Libraries 
Bugzproxy (website) - Bugzproxy is a C# based assembly that provides OO access 
to a Bugzilla server, using the WebService interface of Bugzilla 3.0RC1. It 
can be used to build commandline tools, VS 2005 integration, etc. Works with 
Linux/Mono.

Regards,

Mads

-- 
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34



From justdave at bugzilla.org  Mon Feb 26 15:13:43 2007
From: justdave at bugzilla.org (David Miller)
Date: Mon, 26 Feb 2007 10:13:43 -0500
Subject: Added reference to bugzproxy go Bugzilla plugin wiki page
In-Reply-To: <200702261400.27725.mbd@dbc.dk>
References: <200702261400.27725.mbd@dbc.dk>
Message-ID: <45E2F927.8050702@bugzilla.org>

Mads Bondo Dydensborg wrote on 2/26/07 8:00 AM:

> It says to mail the dev list if one adds something to the Bugzilla plugin 
> page, so here goes:

It does?  That's a surprise to me, and I don't see that when I look, but
thanks for the heads up anyway. :)

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From mbd at dbc.dk  Tue Feb 27 06:57:11 2007
From: mbd at dbc.dk (Mads Bondo Dydensborg)
Date: Tue, 27 Feb 2007 07:57:11 +0100
Subject: Added reference to bugzproxy go Bugzilla plugin wiki page
In-Reply-To: <45E2F927.8050702@bugzilla.org>
References: <200702261400.27725.mbd@dbc.dk> <45E2F927.8050702@bugzilla.org>
Message-ID: <200702270757.11325.mbd@dbc.dk>

mandag 26 februar 2007 16:13 skrev David Miller:
> Mads Bondo Dydensborg wrote on 2/26/07 8:00 AM:
> 
> > It says to mail the dev list if one adds something to the Bugzilla plugin 
> > page, so here goes:
> 
> It does?  That's a surprise to me, and I don't see that when I look, but
> thanks for the heads up anyway. :)

Well, I may be misreading it, but 
http://www.bugzilla.org/status/2007-02-26.html
says

----
Plugins!
One thing we'd really like to see for Bugzilla 3.0 is some plugins! Bugzilla 
3.0 has a lot of ways to write plugins, and if it doesn't support what you 
want to do with your plugin, we'd be happy to add hooks for you. Right now we 
don't have a standard place to store plugins, but if you make one, link it 
from the Bugzilla Addons page, and then tell us on the developers mailing 
list.
----

So... :-)

Hope its ok. I am not totally sure its really a plugin, but it does work with 
bugzilla, and as I have written earlier, one could write a visual studio 
plugin for it, or something like that. (Works with Linux/Mono, actually, so 
one could interface from that as well).

Regards,

Mads

-- 
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34



From mkanat at bugzilla.org  Tue Feb 27 08:36:03 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Tue, 27 Feb 2007 00:36:03 -0800
Subject: Summer of Code Projects
Message-ID: <20070227083629.157F61828E@help.trusthosting.net>

	Hey, I was thinking that we should submit some applications for
Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
projects that we could suggest that somebody work on?

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.


From mbd at dbc.dk  Tue Feb 27 08:42:18 2007
From: mbd at dbc.dk (Mads Bondo Dydensborg)
Date: Tue, 27 Feb 2007 09:42:18 +0100
Subject: Summer of Code Projects
In-Reply-To: <20070227083629.157F61828E@help.trusthosting.net>
References: <20070227083629.157F61828E@help.trusthosting.net>
Message-ID: <200702270942.19382.mbd@dbc.dk>

tirsdag 27 februar 2007 09:36 skrev Max Kanat-Alexander:
> 	Hey, I was thinking that we should submit some applications for
> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
> projects that we could suggest that somebody work on?
> 

- Extending the webservice framework! :-)
- Using it to build integration into VS .NET 2005. (No, I do not use it 
myself).

Regards,

Mads

-- 
Med venlig hilsen/Regards

Systemudvikler/Systemsdeveloper cand.scient.dat, Ph.d., Mads Bondo Dydensborg
Dansk BiblioteksCenter A/S, Tempovej 7-11, 2750 Ballerup, Tlf. +45 44 86 77 34



From after.fallout at gmail.com  Tue Feb 27 14:57:20 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Tue, 27 Feb 2007 09:57:20 -0500
Subject: Summer of Code Projects
In-Reply-To: <20070227083629.157F61828E@help.trusthosting.net>
References: <20070227083629.157F61828E@help.trusthosting.net>
Message-ID: <45E446D0.1030406@gmail.com>

Max Kanat-Alexander wrote:
> 	Hey, I was thinking that we should submit some applications for
> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
> projects that we could suggest that somebody work on?
>
> 	-Max
>   
I think it is a big project, but:
https://bugzilla.mozilla.org/show_bug.cgi?id=371333


From justdave at bugzilla.org  Tue Feb 27 16:57:10 2007
From: justdave at bugzilla.org (David Miller)
Date: Tue, 27 Feb 2007 11:57:10 -0500
Subject: Added reference to bugzproxy go Bugzilla plugin wiki page
In-Reply-To: <200702270757.11325.mbd@dbc.dk>
References: <200702261400.27725.mbd@dbc.dk> <45E2F927.8050702@bugzilla.org> <200702270757.11325.mbd@dbc.dk>
Message-ID: <45E462E6.9070607@bugzilla.org>

Mads Bondo Dydensborg wrote on 2/27/07 1:57 AM:
> mandag 26 februar 2007 16:13 skrev David Miller:
>> Mads Bondo Dydensborg wrote on 2/26/07 8:00 AM:
>>
>>> It says to mail the dev list if one adds something to the Bugzilla plugin 
>>> page, so here goes:
>> It does?  That's a surprise to me, and I don't see that when I look, but
>> thanks for the heads up anyway. :)
> 
> Well, I may be misreading it, but 
> http://www.bugzilla.org/status/2007-02-26.html

Oh, in the status update. :)  Cool :)  Carry on :)

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From justdave at bugzilla.org  Tue Feb 27 17:05:43 2007
From: justdave at bugzilla.org (David Miller)
Date: Tue, 27 Feb 2007 12:05:43 -0500
Subject: Summer of Code Projects
In-Reply-To: <45E446D0.1030406@gmail.com>
References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com>
Message-ID: <45E464E7.2080808@bugzilla.org>

Bill Barry wrote on 2/27/07 9:57 AM:
> Max Kanat-Alexander wrote:
>>     Hey, I was thinking that we should submit some applications for
>> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
>> projects that we could suggest that somebody work on?
>>
>>     -Max
>>   
> I think it is a big project, but:
> https://bugzilla.mozilla.org/show_bug.cgi?id=371333

I don't think that's too big for SoC.  Perfect for it, perhaps.  SoC is
supposed to last the entire summer, and it's the intention that they
work on it full time.  So this is probably a far better choice than some
of the more minor projects sitting around.

That said, we do have a few "minor" projects sitting around that would
probably take a week or two of someone's time, but most of the people
actively developing don't have a week to sit still on one specific thing
because we all have real jobs.  A collection of some of these
week-or-two-long projects might be a good SoC project, too.  One example
I'm thinking of here would be the queue runner daemon to offload the bug
change notification mails to a background process instead of making the
user wait while the mail is sent in the web UI.  It sounds big, but I
really don't think it would take long to do.

-- 
Dave Miller                                   http://www.justdave.net/
System Administrator, Mozilla Corporation      http://www.mozilla.com/
Project Leader, Bugzilla Bug Tracking System  http://www.bugzilla.org/


From kevin.benton at amd.com  Tue Feb 27 17:30:06 2007
From: kevin.benton at amd.com (Benton, Kevin)
Date: Tue, 27 Feb 2007 09:30:06 -0800
Subject: Summer of Code Projects
References: <20070227083629.157F61828E@help.trusthosting.net>
Message-ID: <D85E06673A2DFF44B221CF78D1CBB11BFE665E@SSVLEXMB1.amd.com>

Bugzilla plug-ins? :-)


Kevin Benton
Senior Software Developer
MSS Silicon Design Engineering
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.
 

> -----Original Message-----
> From: developers-owner at bugzilla.org
[mailto:developers-owner at bugzilla.org]
> On Behalf Of Max Kanat-Alexander
> Sent: Tuesday, February 27, 2007 1:36 AM
> To: developers at bugzilla.org
> Subject: Summer of Code Projects
> 
> 
> 	Hey, I was thinking that we should submit some applications for
> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
> projects that we could suggest that somebody work on?
> 
> 	-Max
> --
> http://www.everythingsolved.com/
> Competent, Friendly Bugzilla Services. And Everything Else, too.
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=kevin.benton at amd.com>
> 





From kristis.makris at asu.edu  Tue Feb 27 19:18:28 2007
From: kristis.makris at asu.edu (Kristis Makris)
Date: Tue, 27 Feb 2007 12:18:28 -0700
Subject: Summer of Code Projects
In-Reply-To: <20070227083629.157F61828E@help.trusthosting.net>
References: <20070227083629.157F61828E@help.trusthosting.net>
Message-ID: <1172603908.2732.9.camel@syd.mkgnu.net>

>From my end I get a lot of requests for this, but it's your call.

https://bugzilla.mozilla.org/show_bug.cgi?id=314097#c11

On Tue, 2007-02-27 at 00:36 -0800, Max Kanat-Alexander wrote:
> 	Hey, I was thinking that we should submit some applications for
> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
> projects that we could suggest that somebody work on?
> 
> 	-Max



From samf at collectivestudios.com  Tue Feb 27 19:33:33 2007
From: samf at collectivestudios.com (Sam Fu)
Date: Tue, 27 Feb 2007 11:33:33 -0800
Subject: Classifications
Message-ID: <DA6A6A6E5CD51D459A268BDC29CC45FC037E4A81@newman>

I'm hoping this is the correct forum to ask this question.  If not, I
apologize in advance, but I've been unable to find any detailed
information concerning classifications.  I was wondering if it was
intended that the relationship between classifications and products be 1
to 1 rather than 1 to many.  In my Bugzilla, we want to introduce bug
hierarchy for agile development and before I was doing it by modifying
the database and code until I noticed classification.  The only hurdle
that I've run into is the 1 to 1 relationship between classification and
products.  Thanks in advance for any help.

 

                        --Sam

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20070227/ce76e26f/attachment.html>

From fergus at yahoo-inc.com  Tue Feb 27 19:53:43 2007
From: fergus at yahoo-inc.com (Fergus Sullivan)
Date: Tue, 27 Feb 2007 11:53:43 -0800
Subject: Classifications
In-Reply-To: <DA6A6A6E5CD51D459A268BDC29CC45FC037E4A81@newman>
References: <DA6A6A6E5CD51D459A268BDC29CC45FC037E4A81@newman>
Message-ID: <EDA8062E-5F0B-4348-8F14-B867FA97BC8F@yahoo-inc.com>

Classifications have a 1-to-many relationship with products.  Each  
product can only belong to 1 one classification.  Each classification  
can contain many products.

I suspect you're looking for many-to-many, which is not supported by  
Classifications.

  /ferg

--
fergus sullivan | developer tools team | fergus at yahoo-inc.com | o.  
408.349.6807 | m. 408.203.FERG




On Tue 27-Feb-07, at 11a33 , Sam Fu wrote:

> I?m hoping this is the correct forum to ask this question.  If not,  
> I apologize in advance, but I?ve been unable to find any detailed  
> information concerning classifications.  I was wondering if it was  
> intended that the relationship between classifications and products  
> be 1 to 1 rather than 1 to many.  In my Bugzilla, we want to  
> introduce bug hierarchy for agile development and before I was  
> doing it by modifying the database and code until I noticed  
> classification.  The only hurdle that I?ve run into is the 1 to 1  
> relationship between classification and products.  Thanks in  
> advance for any help.
>
>
>
>                         --Sam
>
>



From samf at collectivestudios.com  Tue Feb 27 19:55:51 2007
From: samf at collectivestudios.com (Sam Fu)
Date: Tue, 27 Feb 2007 11:55:51 -0800
Subject: Classifications
References: <DA6A6A6E5CD51D459A268BDC29CC45FC037E4A81@newman> <EDA8062E-5F0B-4348-8F14-B867FA97BC8F@yahoo-inc.com>
Message-ID: <DA6A6A6E5CD51D459A268BDC29CC45FC037E4ADD@newman>

Thanks for the reply and confirmation Fergus, that's what I meant.

	--Sam

-----Original Message-----
From: Fergus Sullivan [mailto:fergus at yahoo-inc.com] 
Sent: Tuesday, February 27, 2007 11:54 AM
To: developers at bugzilla.org
Cc: Sam Fu
Subject: Re: Classifications

Classifications have a 1-to-many relationship with products.  Each  
product can only belong to 1 one classification.  Each classification  
can contain many products.

I suspect you're looking for many-to-many, which is not supported by  
Classifications.

  /ferg

--
fergus sullivan | developer tools team | fergus at yahoo-inc.com | o.  
408.349.6807 | m. 408.203.FERG




On Tue 27-Feb-07, at 11a33 , Sam Fu wrote:

> I'm hoping this is the correct forum to ask this question.  If not,  
> I apologize in advance, but I've been unable to find any detailed  
> information concerning classifications.  I was wondering if it was  
> intended that the relationship between classifications and products  
> be 1 to 1 rather than 1 to many.  In my Bugzilla, we want to  
> introduce bug hierarchy for agile development and before I was  
> doing it by modifying the database and code until I noticed  
> classification.  The only hurdle that I've run into is the 1 to 1  
> relationship between classification and products.  Thanks in  
> advance for any help.
>
>
>
>                         --Sam
>
>





From after.fallout at gmail.com  Tue Feb 27 21:42:37 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Tue, 27 Feb 2007 16:42:37 -0500
Subject: Summer of Code Projects
In-Reply-To: <1172603908.2732.9.camel@syd.mkgnu.net>
References: <20070227083629.157F61828E@help.trusthosting.net> <1172603908.2732.9.camel@syd.mkgnu.net>
Message-ID: <45E4A5CD.1010608@gmail.com>

Kristis Makris wrote:
> >From my end I get a lot of requests for this, but it's your call.
>
> https://bugzilla.mozilla.org/show_bug.cgi?id=314097#c11
>   
I think that would be a perfect plugin that would be done once 371333 
(easy plugin management) is done. It isn't really central to the purpose 
of bugzilla, but it is very useful for the installations where it would 
be used.


From mkanat at bugzilla.org  Tue Feb 27 21:47:59 2007
From: mkanat at bugzilla.org (Max Kanat-Alexander)
Date: Tue, 27 Feb 2007 13:47:59 -0800
Subject: Priority System for Enhancements
Message-ID: <20070227214800.5002518291@help.trusthosting.net>

	During our most recent meeting (you'll see minutes and so
forth, soon), justdave suggested that we come up with a long-term
roadmap.

	To assist this (or basically implement it), I'm going to be
prioritizing enhancements.

	P1 = We definitely want this. It's a major feature, and it's
obvious that it would be useful to everybody.

	P2 = We want this, but it's not totally clear or extremely
important.

	P3 = This isn't a bad idea, and maybe we'll want to implement
it at some point in the future, but it's not near-term roadmap
material. Some core Bugzilla developer may work on it.

	P4 = This isn't a terrible idea, but it's not important to our
long-term plans for Bugzilla. We would review a patch if somebody
posted it, but a core developer is unlikely to work on it.

	P5 = We basically never want this. If somebody implements it
and asks for review, we *might* look at it.

	Also, if you're a reviewer, feel free to prioritize
enhancements like this. Just remember that a P1 should be really
obviously needed, and we should basically all agree that it's needed.

	-Max
-- 
http://www.everythingsolved.com/
Competent, Friendly Bugzilla Services. And Everything Else, too.


From kevin.benton at amd.com  Tue Feb 27 22:35:03 2007
From: kevin.benton at amd.com (Benton, Kevin)
Date: Tue, 27 Feb 2007 14:35:03 -0800
Subject: Priority System for Enhancements
References: <20070227214800.5002518291@help.trusthosting.net>
Message-ID: <D85E06673A2DFF44B221CF78D1CBB11BFE66F8@SSVLEXMB1.amd.com>

Hi all :-)

> 	During our most recent meeting (you'll see minutes and so
> forth, soon), justdave suggested that we come up with a long-term
> roadmap.

Yeah!

> 	To assist this (or basically implement it), I'm going to be
> prioritizing enhancements.
> 
> 	P1 = We definitely want this. It's a major feature, and it's
> obvious that it would be useful to everybody.
> 
> 	P2 = We want this, but it's not totally clear or extremely
> important.
> 
> 	P3 = This isn't a bad idea, and maybe we'll want to implement
> it at some point in the future, but it's not near-term roadmap
> material. Some core Bugzilla developer may work on it.
> 
> 	P4 = This isn't a terrible idea, but it's not important to our
> long-term plans for Bugzilla. We would review a patch if somebody
> posted it, but a core developer is unlikely to work on it.
> 
> 	P5 = We basically never want this. If somebody implements it
> and asks for review, we *might* look at it.

I'm wondering - there are cases when it might be useful to use
Enhancement_Urgent, Enhancement_Needed, Enhancement_Wanted,
Enhancement_Not_Likely as the severity rather than changing the meaning
of Priority based on the status?  I'm saying this because I know of a
number of Bugzilla users that have service level agreements set up in
such a way so that the customer determines severity and the developer
determines priority.  I'm not suggesting that this override your
suggestion below, however, it is worth considering.  I have felt for a
very long time that "Enhancement" (in and of itself) is inadequate in
describing how badly the "customer" wants something though both sides
agree that it's not a part of the current design (correct or not).

One other possibility is to create Roadmap flags: Plan:ThisMajorRel,
Plan:ThisMinorRel, Plan:ThisFixRel, Plan:NextMajorRel,
Plan:NextMinorRel, Plan:NextBugFixRel, Plan:FutureRel.  It also wouldn't
be difficult to implement those as keywords.  If Plan: soundsl ik

> 	Also, if you're a reviewer, feel free to prioritize
> enhancements like this. Just remember that a P1 should be really
> obviously needed, and we should basically all agree that it's needed.

Could voting play a helpful role in this?

Kevin Benton
Senior Software Developer
MSS Silicon Design Engineering
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.




From bugzilla at glob.com.au  Tue Feb 27 12:54:23 2007
From: bugzilla at glob.com.au (byron)
Date: Tue, 27 Feb 2007 21:54:23 +0900
Subject: Summer of Code Projects
In-Reply-To: <20070227083629.157F61828E@help.trusthosting.net>
References: <20070227083629.157F61828E@help.trusthosting.net>
Message-ID: <20070227125422.GA23097@bur.st>

> 	Hey, I was thinking that we should submit some applications for
> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
> projects that we could suggest that somebody work on?

    ajax ui (esp. search page)
    automatic duplicate bug detection
    support for html/wikitext comments, emails, etc

begin-base64 644 signature.gif
R0lGODlhbQAHAIAAAABPo////ywAAAAAbQAHAAACfAxuGAnch+Bibkn7FL1p
XgVl4Ig1jjlZRoqybgun2Cur5uOunq7u/Ipq7WIyIc7XG9JquEgumPzdlhTf
h0O83kDJaXEm8mRHwXKJy5sac7qYOpT+gtv0n+0ujQOfdqh16caWt0foBViH
N1PRMXimiLUGt3ElVimlgbllWAAAOw==
====


From after.fallout at gmail.com  Tue Feb 27 23:46:08 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Tue, 27 Feb 2007 18:46:08 -0500
Subject: Priority System for Enhancements
In-Reply-To: <D85E06673A2DFF44B221CF78D1CBB11BFE66F8@SSVLEXMB1.amd.com>
References: <20070227214800.5002518291@help.trusthosting.net> <D85E06673A2DFF44B221CF78D1CBB11BFE66F8@SSVLEXMB1.amd.com>
Message-ID: <45E4C2C0.1050007@gmail.com>

Benton, Kevin wrote:
>
>> 	To assist this (or basically implement it), I'm going to be
>> prioritizing enhancements.
>>
>> 	P1 = We definitely want this. It's a major feature, and it's
>> obvious that it would be useful to everybody.
>>
>> 	P2 = We want this, but it's not totally clear or extremely
>> important.
>>
>> 	P3 = This isn't a bad idea, and maybe we'll want to implement
>> it at some point in the future, but it's not near-term roadmap
>> material. Some core Bugzilla developer may work on it.
>>
>> 	P4 = This isn't a terrible idea, but it's not important to our
>> long-term plans for Bugzilla. We would review a patch if somebody
>> posted it, but a core developer is unlikely to work on it.
>>
>> 	P5 = We basically never want this. If somebody implements it
>> and asks for review, we *might* look at it.
>>     
>
> I'm wondering - there are cases when it might be useful to use
> Enhancement_Urgent, Enhancement_Needed, Enhancement_Wanted,
> Enhancement_Not_Likely as the severity rather than changing the meaning
> of Priority based on the status?  I'm saying this because I know of a
> number of Bugzilla users that have service level agreements set up in
> such a way so that the customer determines severity and the developer
> determines priority.  
<snip>

This is exactly why bug 9412 needs to be done.


From kevin.benton at amd.com  Wed Feb 28 00:14:32 2007
From: kevin.benton at amd.com (Benton, Kevin)
Date: Tue, 27 Feb 2007 16:14:32 -0800
Subject: Priority System for Enhancements
References: <20070227214800.5002518291@help.trusthosting.net>
 <D85E06673A2DFF44B221CF78D1CBB11BFE66F8@SSVLEXMB1.amd.com>
 <45E4C2C0.1050007@gmail.com>
Message-ID: <D85E06673A2DFF44B221CF78D1CBB11BFE6724@SSVLEXMB1.amd.com>

Bill - I don't disagree, however, that requires code changes in order to
implement.  My suggestion requires no code changes and can be
implemented today (assuming that BMO product/component owners agree).  I
have been shifting toward features by bug_type in my own installations.
I'm also implementing default bug types per classification, but that
code is still very early in the coding stages.

Kevin Benton
Senior Software Developer
MSS Silicon Design Engineering
Advanced Micro Devices
 
The opinions stated in this communication do not necessarily reflect the
view of Advanced Micro Devices and have not been reviewed by management.
This communication may contain sensitive and/or confidential and/or
proprietary information.  Distribution of such information is strictly
prohibited without prior consent of Advanced Micro Devices.  This
communication is for the intended recipient(s) only.  If you have
received this communication in error, please notify the sender, then
destroy any remaining copies of this communication.
 

> -----Original Message-----
> From: developers-owner at bugzilla.org
[mailto:developers-owner at bugzilla.org]
> On Behalf Of Bill Barry
> Sent: Tuesday, February 27, 2007 4:46 PM
> To: developers at bugzilla.org
> Subject: Re: Priority System for Enhancements
> 
> Benton, Kevin wrote:
> >
> >> 	To assist this (or basically implement it), I'm going to be
> >> prioritizing enhancements.
> >>
> >> 	P1 = We definitely want this. It's a major feature, and it's
> >> obvious that it would be useful to everybody.
> >>
> >> 	P2 = We want this, but it's not totally clear or extremely
> >> important.
> >>
> >> 	P3 = This isn't a bad idea, and maybe we'll want to implement
> >> it at some point in the future, but it's not near-term roadmap
> >> material. Some core Bugzilla developer may work on it.
> >>
> >> 	P4 = This isn't a terrible idea, but it's not important to our
> >> long-term plans for Bugzilla. We would review a patch if somebody
> >> posted it, but a core developer is unlikely to work on it.
> >>
> >> 	P5 = We basically never want this. If somebody implements it
> >> and asks for review, we *might* look at it.
> >>
> >
> > I'm wondering - there are cases when it might be useful to use
> > Enhancement_Urgent, Enhancement_Needed, Enhancement_Wanted,
> > Enhancement_Not_Likely as the severity rather than changing the
meaning
> > of Priority based on the status?  I'm saying this because I know of
a
> > number of Bugzilla users that have service level agreements set up
in
> > such a way so that the customer determines severity and the
developer
> > determines priority.
> <snip>
> 
> This is exactly why bug 9412 needs to be done.
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=kevin.benton at amd.com>
> 





From gerv at mozilla.org  Wed Feb 28 09:44:35 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 28 Feb 2007 09:44:35 +0000
Subject: Priority System for Enhancements
In-Reply-To: <D85E06673A2DFF44B221CF78D1CBB11BFE66F8@SSVLEXMB1.amd.com>
References: <20070227214800.5002518291@help.trusthosting.net> <D85E06673A2DFF44B221CF78D1CBB11BFE66F8@SSVLEXMB1.amd.com>
Message-ID: <45E54F03.70800@mozilla.org>

Benton, Kevin wrote:
> I'm wondering - there are cases when it might be useful to use
> Enhancement_Urgent, Enhancement_Needed, Enhancement_Wanted,
> Enhancement_Not_Likely as the severity rather than changing the meaning
> of Priority based on the status?  

What does this gain us? I don't think that using Priority in this way is 
a semantic stretch. It's just that priorities are now "priorities for 
the project" rather than "priorities for the individual, assigned 
developer".

> One other possibility is to create Roadmap flags: Plan:ThisMajorRel,
> Plan:ThisMinorRel, Plan:ThisFixRel, Plan:NextMajorRel,
> Plan:NextMinorRel, Plan:NextBugFixRel, Plan:FutureRel.  

This is what Target Milestone is for, isn't it? If you think we need 
non-numeric target milestones (like "Future" is) then we should set them up.

>> 	Also, if you're a reviewer, feel free to prioritize
>> enhancements like this. Just remember that a P1 should be really
>> obviously needed, and we should basically all agree that it's needed.
> 
> Could voting play a helpful role in this?

Probably not, as it's hard to give the correct amount of weight to 
votes. (Votes from a core developer should weigh more than votes from a 
random individual IMO.)

The voting system was originally implemented to deal with a time in 
Mozilla's life where we were trying to manage vociferous yet unhelpful 
community elements. I now consider it to be a bit of a wart. Does any 
project use it seriously any more?

Gerv


From gerv at mozilla.org  Wed Feb 28 17:25:11 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 28 Feb 2007 17:25:11 +0000
Subject: Downloading plugins (Was: Summer of Code Projects)
In-Reply-To: <45E446D0.1030406@gmail.com>
References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com>
Message-ID: <45E5BAF7.6000102@mozilla.org>

Bill Barry wrote:
> I think it is a big project, but:
> https://bugzilla.mozilla.org/show_bug.cgi?id=371333

Do we really want to encourage administrators to download and install 
code on their servers without examining it first? Servers and client 
machines (running Firefox) are fundamentally different here.

I might give some non-malicious admin privileges on Bugzilla, but that 
doesn't mean I want them entering URLs to automatically download and 
install new code. They might do that even if they never considered using 
the admin privileges to find a hole in the Bugzilla code, get a shell etc.

Gerv


From gerv at mozilla.org  Wed Feb 28 17:27:15 2007
From: gerv at mozilla.org (Gervase Markham)
Date: Wed, 28 Feb 2007 17:27:15 +0000
Subject: Summer of Code Projects
In-Reply-To: <20070227083629.157F61828E@help.trusthosting.net>
References: <20070227083629.157F61828E@help.trusthosting.net>
Message-ID: <45E5BB73.8030307@mozilla.org>

Max Kanat-Alexander wrote:
> 	Hey, I was thinking that we should submit some applications for
> Google's Summer of Code, for Bugzilla. Anybody have any ideas of some
> projects that we could suggest that somebody work on?

Are you suggesting that we do within the boundaries of the Mozilla 
project's participation in the SoC, or do you think the Bugzilla project 
should apply for itself?

The latter, if accepted by Google, would give us more leeway in how we 
handled contributors, and give us a fixed number of slots. If you 
piggy-backed on the Mozilla relationship, it may end up that a bunch of 
Firefox and Thunderbird projects ended up getting judged as more 
important, and you get no funding at all.

Last year, the Mozilla Foundation did independently fund one idea which 
didn't make the cut. But I wouldn't rely on that and anyway, that rather 
makes it pointless to have gone via Google anyway.

Gerv


From after.fallout at gmail.com  Wed Feb 28 18:51:31 2007
From: after.fallout at gmail.com (Bill Barry)
Date: Wed, 28 Feb 2007 13:51:31 -0500
Subject: Downloading plugins (Was: Summer of Code Projects)
In-Reply-To: <45E5BAF7.6000102@mozilla.org>
References: <20070227083629.157F61828E@help.trusthosting.net> <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org>
Message-ID: <45E5CF33.60908@gmail.com>

Gervase Markham wrote:
> Bill Barry wrote:
>> I think it is a big project, but:
>> https://bugzilla.mozilla.org/show_bug.cgi?id=371333
>
> Do we really want to encourage administrators to download and install 
> code on their servers without examining it first? Servers and client 
> machines (running Firefox) are fundamentally different here.
>
> I might give some non-malicious admin privileges on Bugzilla, but that 
> doesn't mean I want them entering URLs to automatically download and 
> install new code. They might do that even if they never considered 
> using the admin privileges to find a hole in the Bugzilla code, get a 
> shell etc. 
I don't think anyone wants that. The plugin system for bugzilla would 
need to be different than the systems for any of the MoCo software.

I would suggest each plugin passes a whole bunch of "safety" tests (to 
be determined some time in the future) and would then need to be signed 
by official reviewers (note). The system would only allow plugins to be 
installed that are in the official repository or which are installed 
from a command line via some perl script that accepts a URL. That way 
admins can install official plugins through the interface and plugin 
developers can install theirs through the command line. The command line 
interface would only be documented in the developers guide and there 
would be some sort of advisory that this is not the recommended way to 
install plugins.


note:

We don't want plugin developers to be too far off base with the core 
developers of bugzilla anyways; good communication between them is a 
must. So having official code review and security testing would be a 
good thing no matter how much it slows everything down.


From goobix at gmail.com  Wed Feb 28 19:09:13 2007
From: goobix at gmail.com (Vlad Dascalu)
Date: Wed, 28 Feb 2007 21:09:13 +0200
Subject: Downloading plugins (Was: Summer of Code Projects)
In-Reply-To: <45E5CF33.60908@gmail.com>
References: <20070227083629.157F61828E@help.trusthosting.net>
	 <45E446D0.1030406@gmail.com> <45E5BAF7.6000102@mozilla.org>
	 <45E5CF33.60908@gmail.com>
Message-ID: <a16d8c9b0702281109o797f929dmb23412510dc3a5fd@mail.gmail.com>

Either that, or create some kind of super "adminshell" priv that's required
for web-based plugin installation.

On 2/28/07, Bill Barry <after.fallout at gmail.com> wrote:
>
> Gervase Markham wrote:
> > Bill Barry wrote:
> >> I think it is a big project, but:
> >> https://bugzilla.mozilla.org/show_bug.cgi?id=371333
> >
> > Do we really want to encourage administrators to download and install
> > code on their servers without examining it first? Servers and client
> > machines (running Firefox) are fundamentally different here.
> >
> > I might give some non-malicious admin privileges on Bugzilla, but that
> > doesn't mean I want them entering URLs to automatically download and
> > install new code. They might do that even if they never considered
> > using the admin privileges to find a hole in the Bugzilla code, get a
> > shell etc.
> I don't think anyone wants that. The plugin system for bugzilla would
> need to be different than the systems for any of the MoCo software.
>
> I would suggest each plugin passes a whole bunch of "safety" tests (to
> be determined some time in the future) and would then need to be signed
> by official reviewers (note). The system would only allow plugins to be
> installed that are in the official repository or which are installed
> from a command line via some perl script that accepts a URL. That way
> admins can install official plugins through the interface and plugin
> developers can install theirs through the command line. The command line
> interface would only be documented in the developers guide and there
> would be some sort of advisory that this is not the recommended way to
> install plugins.
>
>
> note:
>
> We don't want plugin developers to be too far off base with the core
> developers of bugzilla anyways; good communication between them is a
> must. So having official code review and security testing would be a
> good thing no matter how much it slows everything down.
> -
> To view or change your list settings, click here:
> <http://bugzilla.org/cgi-bin/mj_wwwusr?user=vladd at bugzilla.org>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bugzilla.org/pipermail/developers/attachments/20070228/db4d7d3c/attachment.html>