913075 - Change the Bugzilla Product Name of BootToGecko to Firefox OS

Status: RESOLVED FIXED

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

Description

[Jason Smith [:jsmith]]

We should change the bugzilla product name BootToGecko over to Firefox OS. This will help our contributors who know the brand name widely used outside of Bugzilla (Firefox OS) to align with the naming in our bug tracker.

Comment 1

[David Lawrence [:dkl]]

I would like to get sign-off from the Firefox OS module owners before we make this significant of a change in BMO. The people who may want to give feedback are Andreas Gal and Jonas Sicking according to https://wiki.mozilla.org/Modules/FirefoxOS. Adding them to the Cc of this bug.

Note: This will affect quite a large number of stored queries and other outside tools that do queries based on product=Boot2Gecko so we may need some time to announce the change before execution.

dkl

Comment 2

[Andreas Gal :gal]

I asked for feedback from marketing on this. If there are no brand concerns, if this helps Jason, I have no objections. Lets wait for marketing to comment.

Comment 3

[[e-mail]]

Thanks Andreas.  

I'd like more clarity around the actual code that will be developed under the proposed name — since there will need to be three releases of the code (based on licensing level).  The first release is for White Label implementation (and could be called b2g); the second is for Firefox OS partners who meet / fulfill the license requirements; and the third is a middle layer that allows for more flexibility by device manufacturers (this level will be named next week). 

The white label build will not include the Firefox Browser or Marketplace, and each build will have a different boot sequence that reflect the license level.  

Any details appreciated.

Pete

Comment 4

[Andreas Gal :gal]

Its always the same code, just different build settings.

Comment 5

[Andreas Gal :gal]

(Nightly and Firefox are the same code as well, just different build settings)

Comment 6

[[e-mail]]

thanks for the info.  I'm OK with changing the bugzilla product name to Firefox OS if it will be helpful

Comment 7

[Andreas Gal :gal]

a=me for the change. Do you have everything you need here?

Comment 8

[David Lawrence [:dkl]]

(In reply to Andreas Gal :gal from comment #7)
> a=me for the change. Do you have everything you need here?

We need to also determine if this needs an announcement with a week or so rest period before we make the change. If not we can go ahead and get this changed this week, otherwise it will be next Thursday as this will require code change
to production as well.

Comment 9

[Jason Smith [:jsmith]]

(In reply to David Lawrence [:dkl] from comment #8)
> (In reply to Andreas Gal :gal from comment #7)
> > a=me for the change. Do you have everything you need here?
> 
> We need to also determine if this needs an announcement with a week or so
> rest period before we make the change. If not we can go ahead and get this
> changed this week, otherwise it will be next Thursday as this will require
> code change
> to production as well.

It's probably better to announce first to give a heads up for a week, then make the change after. There's bug queries dependent on searching for B2G, so we need to give some lead time to resolve that.

Comment 10

[David Lawrence [:dkl]]

(In reply to Jason Smith [:jsmith] from comment #9)
> It's probably better to announce first to give a heads up for a week, then
> make the change after. There's bug queries dependent on searching for B2G,
> so we need to give some lead time to resolve that.

Cool. So I leave it to you guys to make sure the proper audience is aware of the change and we will plan on doing our part in this by next Thursday's code push. Unless you feel more than a week is needed. Let me know.

dkl

Comment 11

[Jason Smith [:jsmith]]

(In reply to David Lawrence [:dkl] from comment #10)
> (In reply to Jason Smith [:jsmith] from comment #9)
> > It's probably better to announce first to give a heads up for a week, then
> > make the change after. There's bug queries dependent on searching for B2G,
> > so we need to give some lead time to resolve that.
> 
> Cool. So I leave it to you guys to make sure the proper audience is aware of
> the change and we will plan on doing our part in this by next Thursday's
> code push. Unless you feel more than a week is needed. Let me know.
> 
> dkl

Sounds good. I just emailed the relevant b2g email aliases with a notice that this product name change is happening this Thursday.

Comment 12

[:glob ✱]

(In reply to Jason Smith [:jsmith] from comment #11)
> > Cool. So I leave it to you guys to make sure the proper audience is aware of
> > the change and we will plan on doing our part in this by next Thursday's
> > code push. Unless you feel more than a week is needed. Let me know.
> > 
> > dkl
> 
> Sounds good. I just emailed the relevant b2g email aliases with a notice
> that this product name change is happening this Thursday.

* next thursday - 19th

Comment 13

[:glob ✱]

to clarify - this week's push will most likely happen in about 12 hours time, rather than the usual late wednesday/early thursday time slot.

Comment 14

[David Lawrence [:dkl]]

(In reply to Jason Smith [:jsmith] from comment #11)
> 
> Sounds good. I just emailed the relevant b2g email aliases with a notice
> that this product name change is happening this Thursday.

glob is right and I do apologize that I was not more specific when I said next Thursday. I mean to say
the following Thursday as we will not be doing a code push this week after today. You may need to update
your email you sent to let people know they have a little bit more time and no need to panic :)

dkl

Comment 15

[David Lawrence [:dkl]]

Attachment: 913075_1.patch

Need you to just back me up and make sure I didnt miss any other places that grep couldn't find.

Thanks
dkl

Comment 16

[:glob ✱]

Comment on attachment 819148 [details] [diff] [review]
913075_1.patch

r=glob look right to me :)

Comment 17

[David Lawrence [:dkl]]

Code changes committed. Will leave this open until we push live and I can change the name using the admin UI.

Committing to: bzr+ssh://[e-mail]/bmo/4.2
modified .htaccess
modified extensions/BMO/lib/Data.pm
modified extensions/BMO/template/en/default/bug/create/create-fxos-betaprogram.html.tmpl
renamed extensions/BMO/template/en/default/bug/create/create-bootgecko-partner.html.tmpl => extensions/BMO/template/en/default/bug/create/create-fxos-partner.html.tmpl
modified extensions/BMO/template/en/default/global/choose-product.html.tmpl
modified extensions/GuidedBugEntry/template/en/default/guided/products.html.tmpl
Committed revision 9090

dkl

Comment 18

[:glob ✱]

Updated product name from 'Boot2Gecko' to 'Firefox OS'.

Comment 19

[Anthony Ricaud (:rik)]

Gentle Post Mortem: Given that this change was done a month later, a new heads up to the B2G teams would have been appreciated. I sent a notice to dev.gaia and dev.b2g, maybe other lists need to be warned.

Comment 20

[Dietrich Ayala (:dietrich)]

This breaks a bazillion URLs spread throughout the history of this project with little tangible upside.

The space in the name is unfortunate (cannot quicksearch easily).

There should be a way to *alias* products, instead of break all current search URLs and historical documents, dashboards, emails, wiki pages, etc.

Glob, can we do some kind of aliasing so we don't break the world?

Also unfortunate is the lack of warning (I missed the first one somehow, but saw Rik's post to dev-gaia today).

Comment 21

[:glob ✱]

(In reply to Dietrich Ayala (:dietrich) from comment #20)
> Glob, can we do some kind of aliasing so we don't break the world?

sorry, but that isn't possible with bugzilla, and the effort required to implement that isn't trivial unfortunately.

Comment 22

[Jason Smith [:jsmith]]

Ack. I didn't realize that there wasn't going to be aliasing implemented here. I'm seeing the effects immediately as well. Do we need backout?

Comment 23

[:glob ✱]

(In reply to Jason Smith [:jsmith] from comment #22)
>  I'm seeing the effects immediately as well. Do we need backout?

we could, but the earliest we'll be able to back this out is sunday night pacific (which is the earliest we can get a bmo code push).

of course that would then cause problems for people who have updated their stuff to use the new product name :(

Comment 24

[Preeti Raghunath(:Preeti)]

Yes, this is causing a lot of chaos. We are neck deep in trouble already with the release.

Second the back out.

Can you please send out a note to the aliases not to make changes to the new product name?

Comment 25

[Jason Smith [:jsmith]]

(In reply to Preeti Raghunath(:Preeti) from comment #24)
> Yes, this is causing a lot of chaos. We are neck deep in trouble already
> with the release.
> 
> Second the back out.
> 
> Can you please send out a note to the aliases not to make changes to the new
> product name?

Hold up. People are already flipping things around, so I don't know if we should back out yet. We're in limbo right now. Let me followup offline on this.

Comment 26

[Dietrich Ayala (:dietrich)]

The amount of things changed in the last day cannot compare to the amount of things broken by this.

Comment 27

[Dietrich Ayala (:dietrich)]

This is crazy. It breaks awesomebars too.

If you file a lot of bugs, all enter_bug.cgi URLs in your history now get a "permission denied" page.

http://cl.ly/image/3U0w2f2X0n1n

If you start with the bug entry form, it puts the product in the URL.

Comment 28

[:glob ✱]

bug 931192 has been pushed into production, so all searches (including via an API) will rewrite the product name from "Boot2Gecko" to "Firefox OS".

(In reply to Dietrich Ayala (:dietrich) from comment #27)
> This is crazy. It breaks awesomebars too.

you can use shift+delete to remove those invalid entries.