1195961 - Create a new B2GDroid product

Status: RESOLVED FIXED

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

Description

[[:fabrice] Fabrice Desré]

B2GDroid is a project that let us run b2g on android devices as a homescreen. It uses code from both android and b2g, along with additional custom code.

It doesn't make sense to create a component in either Firefox for Android or Firefox OS, so I'd like a new product.

Comment 1

[David Lawrence [:dkl]]

Ok. We will need quite a bit of information to finish the request listed here:

https://wiki.mozilla.org/BMO/Requesting_Changes#Products

dkl

Comment 2

[[:fabrice] Fabrice Desré]

Name: b2gdroid
Classification: Client Software
Description: b2gdroid is a project that let us run b2g on android devices as a homescreen. It uses code from both android and b2g, along with additional custom code.

Let's go with a single initial component:
Name: General
Description: b2gdroid issues related to Android integration, missing or broken apis and UX issues.
Suggested reviewer: me

I'm not sure what the "version" and "milestones" should be. Same as b2g? So the next is 2.5

Security group: same as b2g

Comment 3

[:glob ✱]

creating products with a single component causes an unnecessary overhead and it isn't something that we will generally do, especially for something that seems to mirror an existing product with regards to security, versions, and milestones.

is there any reason why this can't be a component under the existing 'firefox os' product?

Comment 4

[:glob ✱]

to clarify..  i did see

> It doesn't make sense to create a component in either Firefox for Android or Firefox OS, so I'd like a new product.

i'd like to hear why this doesn't make sense :)

Comment 5

[[:fabrice] Fabrice Desré]

(In reply to Byron Jones ‹:glob› from comment #3)
> creating products with a single component causes an unnecessary overhead and
> it isn't something that we will generally do, especially for something that
> seems to mirror an existing product with regards to security, versions, and
> milestones.

While I don't know yet exactly what the components will be, I'm confident that we will end up with more than one component. I just didn't want to make them up to prevent churn.

> is there any reason why this can't be a component under the existing
> 'firefox os' product?

Because the Firefox OS product deals with gecko code that is 99% of the time in b2g/, and with gaia code. For this product, changes will span gaia, b2g/ and mobile/android/b2gdroid. But it doesn't make much sense to file bugs on b2g/ code in `Firefox for Android`, and not much sense either to file bugs on mobile/ code in `Firefox OS`. It's a weird beast ;)

Comment 6

[:glob ✱]

great - thanks for the clarification, this all makes sense and your request for a new product sounds reasonable.

> I'm not sure what the "version" and "milestones" should be. Same as b2g? So the next is 2.5

the firefox-os product has a lot of milestones, however 2.5 isn't in their list currently.
could you please have a look at their milestones and indicate which ones are appropriate here (although looking at the dates on their sprints it looks like b2g aren't using those anymore).

note we can't synchronise versions or milestones automatically between products - you'll have to file admin bugs to get milestones added to b2gdroid when required.

Comment 7

[[:fabrice] Fabrice Desré]

Looking at the FxOS milestones, they indeed look useless for this product. Let's go with no milestones and no versions.

Comment 8

[David Lawrence [:dkl]]

(In reply to [:fabrice] Fabrice Desré from comment #7)
> Looking at the FxOS milestones, they indeed look useless for this product.
> Let's go with no milestones and no versions.

Then we should be good then. Let us know if you need anything more.

Comment 9

[[:fabrice] Fabrice Desré]

Thanks!

Comment 10

[[:fabrice] Fabrice Desré]

Hm, something needs to be turned on. Here's what I get when trying to create a new bug:

 Sorry, entering a bug into the product B2GDroid has been disabled.

Comment 11

[:glob ✱]

the product was created but wasn't enabled.  i've flipped that bit.