Update on B2G OS for smartphones transition

Dear Mozillians,

Upfront, my apology that this update is coming later than promised.

The purpose of this note is to give you an update on the transition of B2G OS for smartphones (which we’ve known as Firefox OS for smartphones) to a volunteer/contributor community owned, open source project.

Let me start with the action:
Please fill out this Doodle with your availability for the transition project kickoff meeting.

As you know, we are ending the development of Firefox OS for smartphones, which includes staff involvement in this project. However, we know that ending staff involvement abruptly would hurt Boot to Gecko (B2G) as an open source project.

I’ve watched from the sidelines as some of you have organized efforts to keep B2G for smartphones evolving as an open source project in the years ahead – this is inspiring. Mozilla will invest some resources now that will support a transition process that sets your volunteer efforts up for success.

We are still working out the details – and want non-staff input – but we are planning for this investment to be approximately 5-10 staff members (exact details are still being worked out) for the next 4-5 months (again details to be worked through, with your input). Most of this effort would go toward reducing the complexity and ongoing maintenance costs of the B2G code base (more details below).

Volunteer community ownership:
The Connected Devices leadership team’s priority for this effort is ensuring non-staff ownership coming out of the transition period. As you all know, this means volunteer involvement right now!

I have taken on accountability for ensuring this “ownership” transition is done as well as possible within the resource and time constraints. For my own role, this means serving and facilitating a bigger team of staff and volunteers who can come together to make this happen.

From a brief analysis by staff, there are a number of important topics to be discussed and decisions to be made:

  1. Determining the relationship between the B2G OS for smartphones project and Mozilla moving forward
  2. Code transition specifics
  3. Governance
  4. Mentoring/get information to volunteer leaders/contributors
  5. Build and test infrastructure

This is a big set of topics already, and there may be more. Identifying these and making decisions will require staff and volunteers working together in the months ahead.

To get this started, I’m organizing an open B2G OS for smartphones transition kick-off meeting. If you’re interested in guiding this project in the months ahead, please fill out this Doodle with your availability for this meeting.

This meeting is open to anyone, and specifically designed for volunteer or staff community members who want to be involved in this transition period.

I will take on “chairing” this first meeting, and have the following topics in mind as agenda items:
a) State of the code + code transition plan as it stands (staff leading conversation: Gregor Wagner or Fabrice Desré)
b) Goals/areas of decision for the transition period
c) Overall roadmap for transition, including specific timing
d) Forming Working Group(s)

Let’s aim to keep this first meeting to ideally 60min and maximum 90min.

Please add any other topics to this email/Discourse thread, or ping me on IRC or Telegram at geroter.

Naming the project
Aside from the above, there is the issue of the name of the project. You’ll notice that I have been using B2G OS instead of Firefox OS in this note.

The current thinking by our brand team is to reserve the “Firefox” label for products that are actively being brought to market with users. This might include any new Connected Devices products – they would only get the Firefox or Fox name once they were being marketed to potential users.

I’d like your feedback on this, but my recommendation would be to start calling this project B2G OS for smartphones right away (instead of Firefox OS), with the volunteer community leadership of the project figuring out later if there’s another more appropriate name.

Basic technical outline of the code transition work:
The goal of this plan is to reduce the gap between B2G and other Mozilla products (Firefox Desktop and Android) to limit the potential for breakage coming from platform changes, and to overall improve the webiness of B2G by removing apis that won’t become web standards.

This effort spans several areas of the codebase:

  • deprecating packaged apps and security model
  • process model
  • low-level APIs
  • making Service Workers actually work

We’ll give more details of this on the kickoff call, and will publish a draft overall plan to the project wiki over the coming few days.

To finish, I look forward to working together on making B2G OS for smartphones a first class open source project owned by the community, built for the community and still very much advancing Mozilla’s values.



Oh, soo much of this! :clap: :clap:
Thank you, this is awesome! :sunglasses:


Hey George,

That’s generally great news! Need to digest this a bit more still.

Any update on Foxfooding? What are the plans?

1 Like

The Firefox OS is dead, long live The B2G OS!

1 Like

You might want to follow the foxfooding issues in the Participation github repo.

Hi Elio,

The next update on foxfooding will be published tomorrow.

Really great news, hope to be with you at the kick-off meeting! :sunglasses:

Glad to hear this! =D I hope I’ll be with you too for the meeting next week

Good news. Thanks for the communication.

Dear all,

The date that seems best given availability and not overlapping with the weekly project call (as someone pointed out to me that Monday does) is…

Thursday March 10th @ 18h30 UTC.

The location is Vidyo here:

(George Roter’s Vidyo room if you want to search)

For those of you who aren’t there, it will be recorded and you can watch later.



Reminder, this meeting is tomorrow at 18h30 UTC --> join by going to the Vidyo room at this link:


Hello george,
How can we connect with this software (I don’t know how it works).
It need a VidyoPortal, and a registration ?

edit: Ok I find it: just install it and click on the link.

Hi, I wonder what issues you refer to here. Could you please elaborate?

Is following issue already part of the picture?


The recording from the kickoff meeting is now live on Air Mozilla:

You can access the Etherpad from the meeting here:

The next steps from this, including gathering the working groups will happen starting next week. In the meantime you can:

  1. Follow this on the Wiki - https://wiki.mozilla.org/B2G/Transition_Project
  2. Attend the B2G weekly meeting to talk through code transition specifically - https://wiki.mozilla.org/B2G/Meeting
  3. Plan to attend the next overall transition meeting on Thurs April 14 @ 18h30 UTC

uh ? So basically the plan is to use only API available on standard desktop browser ?
No BluetoothLE for example …

WebBluetooth is not mobile specific. That being said, we are lacking resources to actively work on that api right now.