1960423 - Change Triage Owner for Firefox for iOS

Status: NEW

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

Description

[mreagan]

Change Component Info
Please change the Triage Owner for Firefox-iOS.

Change Triage Owner

• Product: Firefox for iOS
• Component: Security (*or General, see follow-up Comment 1)
• Old Owner: [e-mail]
• New Owner: [e-mail]

Request to change triage owner for Firefox iOS. This is to improve triage response and visibility for Firefox iOS tickets. If there is any other information needed from me please let me know! Thank you

Comment 1

[mreagan]

Note: I referenced this previous Bugzilla as a template: https://bugzilla.mozilla.org/show_bug.cgi?id=1761295

There was a previous discussion there about which components to change, let me know if that is still a concern. I believe we typically use the General component for security related tickets. +cc @dveditz

Comment 2

[David Lawrence [:dkl]]

I do not see a Security component. Does one need to be added or is it something else?

https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox%20for%20iOS

Comment 3

[mreagan]

(In reply to David Lawrence [:dkl] from comment #2)

I do not see a Security component. Does one need to be added or is it something else?

https://bugzilla.mozilla.org/describecomponents.cgi?product=Firefox%20for%20iOS

Hi David, this same question came up previously in https://bugzilla.mozilla.org/show_bug.cgi?id=1761295. I believe it would be fine to just change for General component. Changing all of the components seems excessive but it might make sense also since I currently am most active in Bugzilla for the Firefox iOS team.

I'd like to double-check this with Daniel if possible since he has more background on how the components are typically used.

Comment 4

[David Lawrence [:dkl]]

(In reply to mreagan from comment #3)

Hi David, this same question came up previously in https://bugzilla.mozilla.org/show_bug.cgi?id=1761295. I believe it would be fine to just change for General component. Changing all of the components seems excessive but it might make sense also since I currently am most active in Bugzilla for the Firefox iOS team.

I'd like to double-check this with Daniel if possible since he has more background on how the components are typically used.

Right. Thanks for the clarification. I will hold off until dveditz has a chance to respond.

Comment 5

[Daniel Veditz [:dveditz]]

I'd like to double-check this with Daniel if possible since he has more background on how the components are typically used.

Thanks for the vote of confidence, but I'm a bit out of my depth on why the iOS bugzilla components are the way they are. It's going to take some effort on the team's part to straighten that out and should go into some other bug. It appears work originally happened in bugzilla and there are a broad array of components to reflect that. Then the team switched to use https://github.com/mozilla-mobile/firefox-ios/issues (and JIRA) with Bugzilla only monitored for security bugs as far as I can tell. As with many MoCo things, the discontinuity was August 2020.

Most of the world seems to have figured out filing non-security bugs in github, but unlike Focus, there's no notice of that on the site. Just last week Overholt filed bug 1958397, and if we can't figure it out ourselves imagine how confused other Firefox users could be.

There are currently 930 open bugs and >90% are non-security.; 785 of those were filed before Aug 2020

Most of the current security bugs ARE in the "General" component. About a dozen are in "Browser" (which might as well be "General"), and a couple more in the Reader View component. But there are over 400 non-security bugs in the "General" component so we can't just rename that one to "Security". Nor do I want to create a new "Security" component to clean things up when we already have more components than we need.

OPTION 1: just make Matt the triage owner of all the components currently owned by jeevans, and leave the component clean-up/move to a later time.

OPTION 2: make Matt the triage owner of

• General (this is the default place to file)
• Browser (this is always going to be a common guess by people)
• Third Party Security Issues (this is a useful category for bugs we depend on Apple to fix)

For the handful of security bugs in other components we'll make sure Matt is CC'd. Leave the bigger component clean-up / move for the team to deal with at a later time.

ALSO (with either option above):

• make Matt the triage owner for Security: iOS in the Focus product
• add a note to the top of the Firefox for iOS component description page directing people to the correct github repository, like the one at the top of the Focus page
• correct the link in the Focus "Security: iOS" component description to point to the same github repo as the note at the top of the page (we've archived focus-ios and merged it into firefox-ios)

Comment 6

[Daniel Veditz [:dveditz]]

Can I change my mind slightly? We do need to have a component named "Security", because as long as it's called "General" people will mistakenly file non-security bugs there. I don't know if it's better to create a new component and move the security bugs, or just rename "General" and deal with all the non-security bugs that will be in it. The old non-security General bugs aren't getting in our way now so it probably would be fine either way.

Later on, after the team has done some triage and decided how they want to deal with the old non-security bugs, we could then graveyard the components other than "Security" and "Third Party Security Issues" (this future weighs in favor of a new security component rather than renaming General, I think)