Add the `Fenix` product in BMO's "choose from the following selections" list
Categories
(bugzilla.mozilla.org :: General, task)
Tracking
()
People
(Reporter: cpeterson, Unassigned)
References
Details
Please add the Fenix product in the "choose from the following selections" list on Bugzilla's https://bugzilla.mozilla.org/enter_bug.cgi and https://bugzilla.mozilla.org/describecomponents.cgi pages. I'm the EPM for the Firefox Android (Fenix and GeckoView) team.
Fenix's product description from https://bugzilla.mozilla.org/describecomponents.cgi?product=Fenix:
Fenix (Firefox for Android) is a new Android browser built using Android Components that re-imagines how a mobile browser would look if it was built from scratch to demonstrate better design for typical mobile use cases.
This BMO request is not urgent.
CORRECTION: I originally suggested replacing the GeckoView product with Fenix, but the Android engineers would like to keep GeckoView on this list (and add Fenix).
|
Reporter | |
Updated•3 years ago
|
|
||
Comment 1•3 years ago
|
||
On the guided bug entry page that new users see, we currently send Firefox for Android uses to GitHub automatically. I assume we also want to stop doing that as well?
See: https://bugzilla.mozilla.org/enter_bug.cgi?format=guided
For that page, we should remove the redirect and rename Firefox for Android to Fenix with the updated description. Correct?
|
|
Reporter | |
Comment 2•3 years ago
|
||
(In reply to David Lawrence [:dkl] from comment #1)
On the guided bug entry page that new users see, we currently send Firefox for Android uses to GitHub automatically. I assume we also want to stop doing that as well?
Good catch. We'll want to update that page, too.
For that page, we should remove the redirect and rename Firefox for Android to Fenix with the updated description. Correct?
Good question. "Fenix" is the Bugzilla product name (because it was an internal nickname that stuck), but "Firefox for Android" is the app's user-facing name. In these descriptions, we should probably write out both like "Firefox for Android (Fenix)" but still link to the "Fenix" Bugzilla product.
Summarizing this bug's updated change requests:
-
Add the Fenix product in the "choose from the following selections" list on Bugzilla's https://bugzilla.mozilla.org/enter_bug.cgi and https://bugzilla.mozilla.org/describecomponents.cgi and https://bugzilla.mozilla.org/enter_bug.cgi?format=guided pages.
-
Looks like the "If you are reporting a security issue that puts users at risk, use this form." links on the guided page for Firefox Android and iOS are broken. They point to a Bugzilla form that looks correct, but then are quickly redirected to a public GitHub issue tracker, which is exactly where we DON'T want users to file security bugs (because we can't make GitHub issues private).
How do you recommend we fix that redirect problem for the security bug form? Do we still need that security bug form for Fenix if we are directing users to file Fenix bugs in Bugzilla? I see that neither the Firefox desktop nor Thunderbird link to security bug forms.
- For the Bugzilla product description, please use:
Fenix (Firefox for Android) is a new Android browser built using Android Components that re-imagines how a mobile browser would look if it was built from scratch to demonstrate better design for typical mobile use cases.
- Can you please also update the "Fenix" product description on https://bugzilla.mozilla.org/describecomponents.cgi?product=Fenix to use that same description with "Fenix (Firefox for Android)"?
|
|
||
Comment 3•3 years ago
|
||
(In reply to Chris Peterson [:cpeterson] from comment #2)
(In reply to David Lawrence [:dkl] from comment #1)
On the guided bug entry page that new users see, we currently send Firefox for Android uses to GitHub automatically. I assume we also want to stop doing that as well?
Good catch. We'll want to update that page, too.
For that page, we should remove the redirect and rename Firefox for Android to Fenix with the updated description. Correct?
Good question. "Fenix" is the Bugzilla product name (because it was an internal nickname that stuck), but "Firefox for Android" is the app's user-facing name. In these descriptions, we should probably write out both like "Firefox for Android (Fenix)" but still link to the "Fenix" Bugzilla product.
Summarizing this bug's updated change requests:
Add the Fenix product in the "choose from the following selections" list on Bugzilla's https://bugzilla.mozilla.org/enter_bug.cgi and https://bugzilla.mozilla.org/describecomponents.cgi and https://bugzilla.mozilla.org/enter_bug.cgi?format=guided pages.
Looks like the "If you are reporting a security issue that puts users at risk, use this form." links on the guided page for Firefox Android and iOS are broken. They point to a Bugzilla form that looks correct, but then are quickly redirected to a public GitHub issue tracker, which is exactly where we DON'T want users to file security bugs (because we can't make GitHub issues private).
How do you recommend we fix that redirect problem for the security bug form? Do we still need that security bug form for Fenix if we are directing users to file Fenix bugs in Bugzilla? I see that neither the Firefox desktop nor Thunderbird link to security bug forms.
It certainly looks like a bug in that the whole box redirects to GitHub but the link was added inside the box to go to a Bugzilla bug entry form for security issues. When clicking on the inside link, it goes to the bug form but the outside link for the whole product box is still executing so it then redirects right after to GitHub anyway.
If we don't need to redirect to GitHub anymore, then the fix is easy as we just have it go to the normal Bugzilla entry form for all bugs and not just for security issues. So the box would just work like any other normal Bugzilla product. Is that what we want here?
- For the Bugzilla product description, please use:
Fenix (Firefox for Android) is a new Android browser built using Android Components that re-imagines how a mobile browser would look if it was built from scratch to demonstrate better design for typical mobile use cases.
- Can you please also update the "Fenix" product description on https://bugzilla.mozilla.org/describecomponents.cgi?product=Fenix to use that same description with "Fenix (Firefox for Android)"?
I have updated the description now so request 3 and 4 should be done.
|
|
Reporter | |
Comment 4•3 years ago
|
||
If we don't need to redirect to GitHub anymore, then the fix is easy as we just have it go to the normal Bugzilla entry form for all bugs and not just for security issues. So the box would just work like any other normal Bugzilla product. Is that what we want here?
For Firefox for Android, let's remove the security form link and just link to the normal Bugzilla entry form for all bugs.
Let's not change anything about Firefox for iOS in this bug. They use GitHub for their public bugs and Bugzilla for their security bugs, but they also have an ancient (but not graveyard) Firefox for iOS Bugzilla product. I'll notify that team about these iOS Bugzilla issues and let them decide how to address them.
If you need a logo icon for the Firefox for Android (Fenix) product, you can reuse this png from the https://bugzilla.mozilla.org/enter_bug.cgi?format=guided page:
https://bugzilla.mozilla.org/extensions/BMO/web/producticons/firefox_android.png
|
|
||
Comment 5•3 years ago
|
||
Merged.
https://github.com/mozilla-bteam/bmo/commit/3fd1e6ce3ddc489bd51e910a6080c950db937315
Will be in the next deployment.
Description
•