Https://wiki.mozilla.org/B2G/2016-07-05

B2G Weekly Meeting

• Date: 2016-07-05
• Host: Ben Francis
• Notes copied to the wiki each week B2G/Meeting
• Meeting time: Tuesday, 9am Pacific

Attendees

• CedC
• Enrico
• Jovan
• Lapineige
• Benjamin Francis
• Brian King

Announcements

Status Updates

Code Transition

Work on merge of pine into mozilla-central has started

• See blocking bugs https://bugzilla.mozilla.org/showdependencytree.cgi?id=1274295&hide_resolved=1
• Help needed
• First build of mozilla-central with tests green done this week :)

Good response for call for Adopt an app https://discourse.mozilla-community.org/t/updated-call-for-app-maintainers-adopt-an-app/9300

• 10 contributors, on: Dialer, Camera, Cost Control, SMS, Calendar, Clock, FM radio

Porting

• Nexus 5 build is available on B2G Installer
• Flame build updated a few days ago (Thx Jovan ;))
• Work on Fairphone 2 still on going

Infrastructure

Documentation

Italian Translation still affected by the bug bug 1279908 Anyone please fix it. Still need to convert the wiki to the "post-transition" phase

• https://github.com/mozilla-b2g/B2GOS-community/issues/17
• Need to update B2G to say we're no longer in transition phase

Governance

Communications

Call for contribution

• Spanish translation done
• Hindi,Swedish, Persian ongoing

Translations

• 16 translators referenced here: B2G/Transition_Project/Working_Groups
• 11 languages

Smartphone

Smart TV

Tablet

• Mihaela has published the tablet survey, please fill it out and share it with your friends! (especially tech pessimists) https://www.surveygizmo.com/s3/2873022/Tablet-1
• Alberto has a WIP patch for WiFi settings https://github.com/mozilla-b2g/gecko-tablet/pull/57
• Thomas created a working prototype of a WiFi daemon which provides WiFi configuration via a Node web service, an example of how to replace device APIs with system services
• Alex landed a basic battery indicator https://github.com/mozilla-b2g/gecko-tablet/pull/56

Round Table

It's a bit soon, but I think it's good to start thinking about it: how to manage feature request/proposals ? Who decide what to do ? The module owner ?

• In the absense of Product Manager, yes the module owner

"platform" to submit proposal/request ? Maybe investigate other tools (e.g. GetSatisfaction)

• Lapineige will take a look
• Include Discourse?

Votes ?

• Not the best way to make decisions but useful tool for getting feedback
• Shouldn't do a poll if we can't implement the feature

Some successful tests on Telegram-IRC bridge

• Have solution for flooding limit

Communications on transition

• Should consider sending something out soon

Note that 25th July is B2G's 5th Birthday!

• Let's take the opportunity for a celebration and some communications
• Have to be careful with our messaging
• Take into account status of Tablet and SmartTV projects
• Define clearly defined roles and responsibilities of where we need help (though with volunteer roles, we have to be careful they don't look like job descriptions!)
• A plan or timeline of what we're planning - roadmap to 3.0 alpha?
• List of features we need for an Alpha release?

Need a FoxFooding branch?

• Once pine merges do we need a stable branch we can keep in a good state for FoxFooding?