1420561 - Make separate product under Components for Developer Tools

Status: RESOLVED FIXED

(bugzilla.mozilla.org :: Administration, task, P3)

Description

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Per discussion with :kohei, "Firefox Developer Tools could also be a standalone product that will be added to the New Bug and Browse pages for better discovery. I'm seeing a lot of bugs for the DevTools components filed under Firefox::Untriaged."

:harald, does this make sense for your team?

Comment 1

[Dylan Hardison [:dylan] (he/him)]

Emma, I think you're the natural assignee of this until Harald responds, at that time re-assign to me.

Comment 2

[:Harald Kirschner :digitarald]

It seems to solve the issue of too many devtools components in Firefox. Only risk I see that there are some tight dependencies between Firefox and Devtools, but they should not require the 2 of them to be stacked components.

Ni? Patrick to add his thoughts and maybe more devtools engineers to this discussion.

Comment 3

[Patrick Brosset <:pbro>]

I support this move. This will make our component names shorter, and I agree that it would be better for discoverability.
I'll run this by the team later today, so please don't do the change just yet.

Comment 4

[Patrick Brosset <:pbro>]

I've talked to the team and we ended up with 3 questions we'd like to answers to before we move on with this:

- Should we expect a massive bugmail storm when this happens? If so, will there be a keyword we can filter on?
- Would we lose some kind of history in the move?
- Will it touch old bugs we would like to keep "untouched"? Sometimes, it's useful to search for bugs by when they were last touched. Is this going to reset this date for all bugs?

Comment 5

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

(In reply to Patrick Brosset <:pbro> from comment #4)
> I've talked to the team and we ended up with 3 questions we'd like to
> answers to before we move on with this:
> 
> - Should we expect a massive bugmail storm when this happens? If so, will
> there be a keyword we can filter on?

No, we do this in a way that doesn't trigger bugmail.

> - Would we lose some kind of history in the move?

No.

> - Will it touch old bugs we would like to keep "untouched"? Sometimes, it's
> useful to search for bugs by when they were last touched. Is this going to
> reset this date for all bugs?

I don't believe it will, but asking :dylan to confirm.

Comment 6

[Patrick Brosset <:pbro>]

That sounds great Emma, thank you. Looking forward to a confirmation on the last question from :dylan.
During the move, we should drop the "Developer Tools:" prefix that appears in each of our component names right now. We won't need them since we'd already be inside a product named DevTools (or Developer Tools).
The only special case is our general component, currently named "Developer Tools". I think we should name this one "General", or something like that.

Comment 7

[Patrick Brosset <:pbro>]

Ah, another question, maybe for :dylan who is already needinfo'd here:

Will URLs like https://bugzilla.mozilla.org/enter_bug.cgi?product=Firefox&component=Developer%20Tools%3A%20Debugger be redirected to using the right product and component too?
These URLs are used in some places like mail archives, etc.

Comment 8

[Patrick Brosset <:pbro>]

One more thing: for the product name, just "DevTools" would be great. Shorter and more URL friendly than the longer "Developer Tools". And also more consistent with how we're communicating about DevTools.

Comment 9

[Patrick Brosset <:pbro>]

Hi Emma, circling back on this. No news from :dylan yet. Can you please help move this bug forward?

Comment 10

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Hi Patrick, Dylan and I need to make sure we have DevTools select-able as a product category from all the bug filing workflows. Will file the blocking bug for that.

Comment 11

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Seeing if we can get this un-wedged.

Comment 12

[Dylan Hardison [:dylan] (he/him)]

moving components using the scripts will not touch the last modified time of the bugs.

Does this bug have a concise list of which actions need to be taken?

Comment 13

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

I will add to user story.

Comment 14

[Julian Descottes [:jdescottes]]

Emma, should this be reassigned to :dylan now that you completed the user story?

Comment 15

[Emma Humphries ☕️🎸🧞‍♀️✨ (she/they) [:emceeaich] (Pacific Time) use needinfo]

Yes. Dylan's out until All-Hands. Seeing if dkl or glob can do this.

Comment 16

[David Lawrence [:dkl]]

Taking.

Comment 17

[David Lawrence [:dkl]]

(Commenting on User Story)
> Victory Conditions:
> 
> * DevTools is a new product under the Components category

What would the description be for the new component?
Do you want any suggested reviewers to be added for this new product?

> * All existing Toolkit: DevTools:* components are moved, with **all** bugs,
> under the new product

I do not see any DevTools:* components under the current Toolkit product. 
Did you mean Firefox :: Developer Tools:* components instead or am I missing 
something.

dkl

Comment 18

[Brian Grinstead [:bgrins]]

(In reply to David Lawrence [:dkl] from comment #17)
> > * All existing Toolkit: DevTools:* components are moved, with **all** bugs,
> > under the new product
> 
> I do not see any DevTools:* components under the current Toolkit product. 
> Did you mean Firefox :: Developer Tools:* components instead or am I missing 
> something.

That's correct - it should be the "Firefox :: Developer Tools:*" components.

Comment 19

[David Lawrence [:dkl]]

(In reply to David Lawrence [:dkl] from comment #17)
> (Commenting on User Story)
> > Victory Conditions:
> > 
> > * DevTools is a new product under the Components category
> 
> What would the description be for the new component?
> Do you want any suggested reviewers to be added for this new product?

Sorry. I meant to ask for the description for the new product, not component.

dkl

Comment 20

[Brian Grinstead [:bgrins]]

(In reply to David Lawrence [:dkl] from comment #19)
> (In reply to David Lawrence [:dkl] from comment #17)
> > (Commenting on User Story)
> > > Victory Conditions:
> > > 
> > > * DevTools is a new product under the Components category
> > 
> > What would the description be for the new component?
> > Do you want any suggested reviewers to be added for this new product?
> 
> Sorry. I meant to ask for the description for the new product, not component.
> 
> dkl

I'd ask Patrick for sign off but we could start with the current description of the Developer Tools component:

"For bugs relating to developer tools within the Firefox web browser (devtools). This includes developer-related APIs and front-end features."

If it's easy to update it'd be OK to start with that and then change it when we hear back from him.

Comment 21

[Patrick Brosset <:pbro>]

(In reply to Brian Grinstead [:bgrins] from comment #20)
> I'd ask Patrick for sign off but we could start with the current description
> of the Developer Tools component:
> 
> "For bugs relating to developer tools within the Firefox web browser
> (devtools). This includes developer-related APIs and front-end features."
Here's my take on it:

For bugs in Firefox DevTools, the developer tools within the Firefox web browser. This includes issues about the user interface of the toolbox, special pages such as about:debugging and about:devtools, and developer-related APIs.

Comment 22

[David Lawrence [:dkl]]

All done. You will need to make sure everyone updates their dashboards, saved queries, bookmarks, etc to reflect the new product structure.

dkl

Comment 23

[Tim Nguyen :ntim]

Please avoid changing the "Last changed" date of bugs when making mass changes like this one, it affects my workflow (I use a bug list of things I comment on, sorted by "Last changed" date).