If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

Create Components for Reporter tool (Other Applications, Webtools) default assignee: robert@accettura.com

RESOLVED FIXED

Status

()

bugzilla.mozilla.org
Administration
RESOLVED FIXED
13 years ago
4 years ago

People

(Reporter: raccettura, Assigned: timeless)

Tracking

Details

(Reporter)

Description

13 years ago
We need to have bugzilla components for the new reporter tool:

Proposal:
1.  Living in Core, since we plan to use it in both Firefox and SeaMonkey.  This
is for the XUL extension only.
2.  Living in webtool for the server side of things.  Server only.

Justification:  we have a client and a server.  We need to keep track of both.

Per discussion with Asa on IRC.

[this is the last time I use several tabs on bugzilla when I'm a little tired...
I'm messing up left and right].
(Assignee)

Comment 1

13 years ago
Typically when filing bugs like this, you're supposed to provide component
names, component descriptions, default assignees, and default qa contacts.

For example:
Component:  	Problem Reporter
Component Description: 	XUL Extension for reporting problems to mozilla.org
Initial owner: 	robert@accettura.com
Initial QA contact: 	
Component of Product: 	Core

(but it'd be nice if you specified a qa contact).
(Reporter)

Comment 2

13 years ago
Sorry Timeless, this is a first for me.  I've been lurking and patching tiny
things for a little while.  Now I'm prepairing to move towards something a bit
more substantial.

Component: Reporter
Component Description: 	XUL Extension for reporting problematic websites to
mozilla.org
Initial owner: 	robert@accettura.com
Initial QA contact: reporter@mozilla.bugs
Component of Product: 	Core

Component: Reporter Webtool
Component Description: 	Webtool for reporting problematic websites to mozilla.org 
Initial owner: 	robert@accettura.com
Initial QA contact: reporter-webtool@mozilla.bugs
Component of Product: 	Webtools

Leave to Asa to approve/revise.  He's got way more bugzilla hours than me.  And
that's not changing any time soon.

Comment 3

13 years ago
Yeah, this looks good, the webtool part needs a slightly better description,
though, because it is really about the app that receives and process reports, as
well as the query interfaces. 
(Reporter)

Comment 4

13 years ago
(In reply to comment #3)
> Yeah, this looks good, the webtool part needs a slightly better description,
> though, because it is really about the app that receives and process reports, as
> well as the query interfaces. 

How about:

--
webtool complement for reporter extension that recieves, processes and queries
reports (server issues only).
--
(Assignee)

Comment 5

13 years ago
how about:
Service that accepts, monitors and allows users to search for problems generated
by the Reporter XUL extension.

justdave would create the email accounts. i'm not particularly fond of
reporter-webtool@mozilla.bugs either, but it's way too late for me to figure
that one out.

i can create the components once we settle on the details and i ask justdave to
recycle the accounts.
(Reporter)

Comment 6

13 years ago
I personally couldn't really care on the email accounts.

Just differentiate between the service, and extension.  That's my primary concern.  

Comment 7

13 years ago
Timeless, can you make this happen? We can always adjust later. 
xul-client@reporter.bugs and web-service@reporter.bugs have been created, per
timeless' request on IRC this afternoon.
(Assignee)

Comment 9

13 years ago
Asa? I thought about this a bit more, Chatzilla, DOM Inspector and Venkman live
in Other Applications. And given this is a xul extension, I chose to put the
Reporter there too.

Component:  	Reporter
Component Description: 	XUL Extension for reporting problematic websites to
mozilla.org
Initial owner: 	robert@accettura.com
Initial QA contact: 	xul-client@reporter.bugs
Component of Product: 	Other Applications

We can move it if people really object, but I think people should agree that
this application is non core.

Component:  	Reporter
Component Description: 	Service that accepts, monitors and allows users to
search for problems generated by the Reporter XUL extension.
Initial owner: 	robert@accettura.com
Initial QA contact: 	web-service@reporter.bugs
Component of Product: 	Webtools
Assignee: asa → timeless
(Assignee)

Updated

13 years ago
Summary: Components for reporter tool → Create Components for Reporter tool (Other Applications, Webtools) default assignee: robert@accettura.com

Comment 10

13 years ago
OK. Seems fine to me. Where does the Talkback client live?
(Assignee)

Comment 11

13 years ago
in order to avoid spamming this bug, i filed bug 278053 to consider talkback
(Reporter)

Comment 12

13 years ago
Not quite sure if this is "other applications", simply because this would never
be standalone.  Nor is it even an "application".  It's more like a component
that lives in Firefox and SeaMonkey.

This (IMHO) is like calling Profile Manager an application.

Just my $0.02.
(Assignee)

Comment 13

13 years ago
javascript debugger is generally useless w/o a host, similarly for venkman.
Status: NEW → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED
(Assignee)

Comment 14

13 years ago
oops, s/venkman/dom inspector/
Component: Bugzilla: Keywords & Components → Administration
Product: mozilla.org → bugzilla.mozilla.org
You need to log in before you can comment on or make changes to this bug.