797934 - Create a new bugzilla product for Metro Firefox

Status: RESOLVED FIXED

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

Description

[Jim Mathies [:jimm]]

- Name of the product:

Firefox for Metro

- The classification (group) you would like the product in

Client Software

- Longer description, usually including a web link for more info on the product:

string: Firefox for Metro is Mozilla's immersive version of Firefox for Windows.
link: https://wiki.mozilla.org/Firefox/Windows_8_Integration

- The initial list of versions, with their info:

The product will track Firefox versioning on mc.

- The initial list of target milestones, with their info

The product will track Firefox milestones.

- The security group(s) bugs should be classified under when a user checks the security flag:

Same behavior as Firefox or Firefox for Android.

- The number of votes needed to confirm a bug (UNCO --> NEW)

Whatever value we use for Firefox.

- The initial list of components, with their info:

Will post in a follow up.

Comment 1

[Bill Gianopoulos [:WG9s]]

We should not be using the word "Metro" in this product.  I thought there were trademark issues with that word and Microsoft has asked developers to NOT use that word in their product.  Or has that changed?

Comment 2

[Jim Mathies [:jimm]]

Here are some suggested starter components I've come up with. Feedback welcome.

Browser – Issues with the navigation bar, start and awesome screens, tab dock, tab behavior, command line handling, and page zoom and display.

Build Config - Issues with build and configuration setup.

Components – Issues with self contained components and add-ons, including pdfjs, popup blocker, downloads, and private browsing.

File Handling - Issues with downloaded file handling and helper applications.

General - Bugs to be triaged or bugs that do not fit into existing product components.

Input – Issues with mouse and touch interaction in chrome and content including text selection, form input, soft keyboard, links, context menus, and focus related issues.

Shell – Issues with operating system integration including charms menu features, app bar, and snap view.

Theme - Issues and requests for enhancements to the default theme that ships with Firefox for Metro.

Comment 3

[Jim Mathies [:jimm]]

(In reply to Bill Gianopoulos [:WG9s] from comment #1)
> We should not be using the word "Metro" in this product.  I thought there
> were trademark issues with that word and Microsoft has asked developers to
> NOT use that word in their product.  Or has that changed?

Well we aren't using Metro in any official naming, just internally. Outwardly metrofx is just regular old Firefox. It'll be distributed such that it will be indiscernible from the desktop product. But internally we need something unique in bugzilla, and since everyone knows what Metro is, it seemed to be the best fit.

Feel free to post alternative suggestions.

Comment 4

[Brian R. Bondy [:bbondy]]

(In reply to Bill Gianopoulos [:WG9s] from comment #1)
> We should not be using the word "Metro" in this product.  I thought there
> were trademark issues with that word and Microsoft has asked developers to
> NOT use that word in their product.  Or has that changed?

I think we should be using Metro internally for now. MSDN itself still refers to everything as Metro so why shouldn't our developer sites?  http://msdn.microsoft.com/en-us/library/windows/apps/hh465413.aspx

Special note to the whitepaper: Developing a Metro style enabled Desktop Browser
...which is what we're talking about here.

Comment 5

[Frank Yan (:fryn)]

(In reply to Brian R. Bondy [:bbondy] from comment #4)
> I think we should be using Metro internally for now. MSDN itself still
> refers to everything as Metro so why shouldn't our developer sites? 
> http://msdn.microsoft.com/en-us/library/windows/apps/hh465413.aspx

Actually, if you visit that page now, you'll see they just renamed everything to "Windows Store apps"...

"Store Firefox" doesn't have the same ring to it sadly.

Comment 6

[Brian R. Bondy [:bbondy]]

I just loaded that page and it still shows me: Developing a Metro style enabled Desktop Browser

Also we're not eligible to be on the Windows Store as far as I've read.

Comment 7

[Brian R. Bondy [:bbondy]]

My bad, apparently MS announced in June that Desktop apps can appear in the Windows store.  But the MSDN link still does say Metro style enabled Desktop Browser :)

Comment 8

[Bill Gianopoulos [:WG9s]]

This is fine but Bugzilla usage is NOT internally only.  Kind of why I brought this up.

(In reply to Brian R. Bondy [:bbondy] from comment #4)
> (In reply to Bill Gianopoulos [:WG9s] from comment #1)
> > We should not be using the word "Metro" in this product.  I thought there
> > were trademark issues with that word and Microsoft has asked developers to
> > NOT use that word in their product.  Or has that changed?
> 
> I think we should be using Metro internally for now. MSDN itself still
> refers to everything as Metro so why shouldn't our developer sites? 
> http://msdn.microsoft.com/en-us/library/windows/apps/hh465413.aspx
> 
> Special note to the whitepaper: Developing a Metro style enabled Desktop
> Browser
> ...which is what we're talking about here.

Comment 9

[Mark Finkle (:mfinkle) (use needinfo?)]

"Firefox for Metro" seems like the best choice

Comment 10

[:Gavin Sharp [email: [e-mail]]]

I concur; we can change it later if that's really needed.

Comment 11

[David Lawrence [:dkl]]

Product has been created but is currently disabled. We need small code change to also be pushed out to support the new product which will happen middle of this week. So it will remain invisible til then. 

Committing to: bzr+ssh://[e-mail]/bmo/4.0
modified extensions/BMO/lib/Data.pm
Committed revision 8348. 

Note to self:
When production is updated later this week have the IT person run the following script to sync up the versions and milestones.

# perl contrib/reorg-tools/syncmsandversions.pl "Firefox" "Firefox for Metro"

dkl

Comment 12

[:glob ✱]

(In reply to David Lawrence [:dkl] from comment #11)
> When production is updated later this week have the IT person run the
> following script to sync up the versions and milestones.
> 
> # perl contrib/reorg-tools/syncmsandversions.pl "Firefox" "Firefox for Metro"

this script has been executed, and i've added this product the new-version wiki.

Comment 13

[David Lawrence [:dkl]]

(In reply to Byron Jones ‹:glob› from comment #12)
> (In reply to David Lawrence [:dkl] from comment #11)
> > When production is updated later this week have the IT person run the
> > following script to sync up the versions and milestones.
> > 
> > # perl contrib/reorg-tools/syncmsandversions.pl "Firefox" "Firefox for Metro"
> 
> this script has been executed, and i've added this product the new-version
> wiki.

Thanks glob. New product open for business.