WebmakerMoFo Marketing in 2015

We launch into our 2015 Mozilla Learning plan with lots of momentum. We have a strong, engaged base of contributors built on the ground through solid partnerships, strong and growing Hive learning networks, and our popular annual Maker Party. Our marketing objective in 2015: capitalize on this momentum and expand to reach a broader audience.

It’s worth noting that there are important elements of both marketing and sales in our approach. Marketing will be used to reach individuals through our broadcast channels – think Mozilla’s equivalent of a super bowl ad, the snippet – and have them engage with our Webmaker product. Sales will be used to take our program offerings to new and existing partners and demonstrate the value to them of incorporating the Mozilla Learning network approach into their work.

Our Goals

We’ll implement a two-pronged approach, building on what’s been working within our sales and partnership channels while reaching for a new, mass market of individual learners through marketing. The assumption is we can do two things at once and do them well: target an audience of learners and mentors in parallel, likely in different channels with slightly different messages. With this approach we aim to:

  • Have 250,000 people actively making and learning with the Webmaker desktop tool and mobile app through increased marketing activity.
  • Expand our the global footprint of our learning networks to 500 cities by running a Maker Party campaign, launching the club model, and adding more Hive Learning Network locations through successful sales and partnership engagements.

Branding: One Mozilla

Wrapped around this marketing and partnership outreach will be an ongoing branding and communications effort that seeks to align more closely with the larger Mozilla brand and establish our leadership in a global digital literacy movement.

With our on-the ground programs and online products, we’re taking the opportunity to evaluate our branding position across all of the Foundation’s initiatives. In practice, this means moving towards aligning products and programs in a way that is more similar to the Firefox-Mozilla architecture. The working version of this is Webmaker as our product tied to an individual’s desire to make and Mozilla Learning Network as the product tied to a community’s desire to change how digital literacy education works.

There are nuances of course — brand architecture questions to be worked through and naming and positioning to be established — but an efficient, thoughtful process that leads to a crisp, cohesive brand framework is the P1 this quarter.

Communications: Broadened awareness & thought leadership

With a working version of branding sorted out, another key umbrella for all product and programmatic activity is building and deploying a better communications plan. One that positions and establishes Mozilla as a leader in the global movement to keep the Web open, empowers users in emerging markets to become creators, not just consumers, and differentiates our literacy efforts as innovative, unrivaled and impactful. To get there, we’ll be focused on a few specific things over the next few months:

  • Improved long-term planning
  • Expanding our capacity by adding a Comms Manager
  • Better integration with Mozilla-wide opportunities
  • More earned media and public recognition
  • More strategic use of social media

Webmaker product marketing: Engagement, growth and impact

Our goal for the Webmaker product this year is to achieve real scale by reaching a mass market, defined as anyone who wants to make something on the web. That’s quite a “mass” when you consider the number of people already creating blogs, making .gifs, selling goods on Etsy, or editing and sharing photos on Instagram.

In our experience the best way to equip people with skills for this digital age is to empower them to become makers. Learning and skills development is something that happens as part of the experience. With this in mind, the Webmaker product team is building a free, simple-to-use and fun tool for creating on the web. It’s localized for their communities, relevant to their social, economic and cultural needs, allows for making on any type of device, and enables them to learn new skills.

As the new tool emerges over the next 3 months, we’ll engage in a variety of marketing activities to hone our go-to-market approach and kick-off a new era of learning with Webmaker. Here are some of the specific projects and initiatives taking shape over the next two quarters:

  • Honing a maker-focused value proposition
  • Testing and optimizing conversion and onboarding
  • Successfully launching beta at Mobile World Congress
  • Building buzz and attention around new Webmaker product
  • Testing new App acquisition channels
  • Better integration and prominence within Mozilla-wide campaigns
  • Localizing our marketing

Learning Network sales: quality growth

Foundationally, our learning network presence on the ground works. We continue to have a compelling offering that allows us to reach a global audience that includes professional educators teaching tech, educators interested in tech, individuals with passion for teaching others, and casual mentors who like to share skills with their personal networks.

Mozilla’s connected learning networks offer access to teaching resources, organizational support, recognition and rewards systems, and access to a global community of fellow teachers to have greater impact in the world. We want to continue to build upon what’s working and try some new ways to expand our reach and footprint along the way.

Working off two tiers of engagement — the developing “Webmaker clubs” model currently being piloted and the established Hive network model —  the Learning Networks team is already busy growing this area of our work. As those plans take shape, we can grow sales of our learning netwok offering to partners and support ongoing promotion and engagement through marketing by focusing on:

  • Building ongoing engagement campaigns for existing contributors
  • Creating buzz and attention around the launch of Webmaker Clubs inside the teaching community
  • Taking better advantage of existing and new partnerships by building out a robust sales pipeline
  • Using 2015’s Maker Party campaign as a way to attract new partners and re-engage existing mentors

Looking Forward

There are lots of moving pieces to wrangle, tough branding questions to be resolved, and new messages to be honed. In many ways, we are approaching Q1 as a test-bed to get these things right. With a methodical approach to testing, optimization and planning in the next few months, we’re optimistic we’ll be in a strong position to launch our new products and programs in a big way — bigger, better and more impactful than anything we’ve done before.

Mozilla ServicesMarketplace migration to Firefox Accounts

In the last year the Firefox Marketplace migrated from Persona to Firefox Accounts. This was done for a couple of reasons, perhaps the biggest being that Firefox OS was switching to Firefox Accounts. On a Firefox OS phone, you will log in once, to the phone and then be automatically logged into the Marketplace.

The migration for the Marketplace had a few unique challenges that some other projects do not have:

  • the Marketplace app supports Firefox OS all the way back to 1.1
  • the Marketplace site supports Android and Desktop clients
  • in the past unverified emails were allowed from Persona
  • Marketplace provides Payments which use the Trusted UI

Firefox Accounts has two different ways to login, a native flow in Firefox OS and an OAuth based flow for Desktop and Android clients. The number of dependencies to complete all that quickly grew out of control, so we focused on the first milestone of ensuring that an OAuth flow worked for all users on all devices.

Migration from a database point of view wasn’t too complicated at first. We store the users email from Persona, all we had to was look at the users email from Firefox Accounts … if a user already existed with that account then they logged in as that account. If not we created a new account.

The unverified emails were a problem to us, because it meant that a user or developer could have an email address that wasn’t routable, accessible or in any way usable. When they migrated to Firefox Accounts an email would be sent to that old email address and they were stuck. We really couldn’t see any around this other than manually verifying accounts as best as possible and moving them over as needed.

For users that already had a Firefox Account through sync and wanted to re-use that on the Marketplace, the Firefox Accounts team added the ability to use a pre-verified token. This allowed a user to start the registration flow as a user, but in the Firefox Accounts sign up use a different email address. At the end of the flow the Marketplace would then detect the difference in the email address, but know which account the flow came from and hook it up correctly.

This then gave birth to a flow chart and after lots of work, but we had a plan:

Screenshot 2015-01-27 11.52.36

Of course the road was not that smooth as the bug list will probably reveal. The biggest difference to any other Firefox Accounts implementors is that the OAuth flow is not the same as the Persona flow. An obvious statement, we thought we had covered until we hit elements like the Trusted UI – at that point it got complicated.

Screenshot 2015-01-30 13.53.23

Once deployed we sent out an email to everyone and waited for the users to come in. Sure enough they did and we saw a large number of transitions within 48 hours.

During this process we made sure emails came out with an email address that could be replied to, I was then able to follow up personally with anyone who had any issues. We also logged login attempts and when we found a bug, I was able to email those people while we fixed and deployed the bug – there were only two people who had a problem at that step, but it felt good to be able to help them.

Firefox Accounts has now been active for over 3 months and this week we turned off the special transition flow and deleted the transition flow as felt enough users and developers had migrated.

What’s next?

  • Getting the native flow deployed for Firefox OS 2.1
  • Moving to an iframe based flow and removing the popup based flow
  • Deeper integration with upcoming Firefox Accounts features, like avatars

Big thanks to the Marketplace team who implemented this and the Firefox Accounts team who did an awful lot of work helping us out.

Air MozillaWebmaker Demos January 30 2015

Webmaker Demos January 30 2015 Webmaker Demos January 30 2015

SUMO BlogWhat’s up with SUMO – 30th January

….aaaaaand there goes the first 1/12th of the year! That was quite fast, wasn’t it? Let’s roll out this week’s WUWS post!

You Keep Coming, We Keep Calling You Out!

If you’re not on the list and you joined us recently, remember to introduce yourself!

The latest SUMO Community meeting

You can find the agenda and notes here: https://etherpad.mozilla.org/sumo-2015-01-26.

The video recorder is apparently plotting against us, as we’ve had technical difficulties for the second week running. Worry not, a bug has been filed, and things are being looked into as you read this. We also ran out of running (heh…) hamsters.

So, in the spirit of getting serious for a while… Have you done something smart (and safe) with your data to celebrate the Data Privacy Day this year? You can take a quick look at our initiatives regarding privacy on the Official Mozilla Blog.

Reminder: the next SUMO Community meeting…

  • …is going to take place on Monday, 2nd of February. Join us live if you can! Details on how to do it and the agenda & notes can be found here.
  • If you want to add a discussion topic to the live meeting agenda:
    • Start a thread in the Community Forums, so that everyone in the community can see what will be discussed and voice their opinion here before Monday (this will make it easier to have an efficient meeting).
    • Please do so as soon as you can before the meeting, so that people have time to read, think, and reply (and also add it to the agenda).

Community shout-outs

Developer news

Forum news

Knowledge Base news

L10n news

Firefox (+ OS, + for Android) news

All right, time to wrap it up for this week and look forward to the next one. We hope to see you on Monday. Expect the unexpected!

Air MozillaJanuary Cantina Speaker - Nico Sell, CEO r00tz and Wickr

January Cantina Speaker - Nico Sell, CEO r00tz and Wickr Nico Sell is a professional artist, athlete and entrepreneur based in California. She is cofounder and CEO of r00tz and Wickr. r00tz is a...

SUMO BlogNew SUMO Day this Thursday, Jan 29th 2015

Two weeks have passed so it’s time for a new SUMO Day! We are answering questions in the support forum and helping each other in #sumo on IRC from 9am to 5pm PST (UTC -8) today.

We’re trying to answer each and every incoming question on the support forum today so please join us, create an account and then take some time today to help with unanswered questions. The more the merrier! Please check the etherpad for additional tips. Last time we have managed to go up to 90% answered in 24 hours so let’s try to reach at least 95% this time!

See you online and happy SUMO Day!

Air MozillaReps weekly

Reps weekly Weekly Mozilla Reps call

WebmakerA/B Testing New Designs for the Webmaker.org homepage

This is a quick post to share the results of an A/B test the Webmaker Product Team recently ran on the webmaker.org homepage.

The team designed and built four variations of a new homepage. The homepage was the same for all users except for the blue ‘Splash page’ area seen in the screenshots below where we tested different images and text.

First we’ll look at how these designed performed against each other…

Variation A

Variation A

Variation B

Variation B

Variation C

Variation C

Variation D

Variation D

 

Before you look at the results below, which design and messaging do you think will result in the most users joining Webmaker?

 

The results:

Variant Traffic Conversions Conversion Rate
Variation A 11,913 903 7.58%
Variation B 11,950 1,066 8.92% This is a statistically significant
winner against A or C
Variation C 11,714 748 6.39%
Variation D 11,896 1,034 8.69% This is a statistically significant
winner against A or C

Variation B & D are equal winners. Although B reports slightly higher in these results, the difference in performance between variation B and D is not statistically significant, so we can use either of these versions as our new default homepage.

One of the goals of this test was to explore the relative impact of how we talk about Webmaker to new users, and whether we focus on it’s place in relation to personal user benefit, of the Mozilla mission and these results give us a starting point in that research. But we should not jump to any conclusions from the results of a single test like this.

For example, we were testing a photo versus an illustration in this experiment. Variation A and D have the same text, but A has a photo background, and D has the illustration. Comparing the results of these two variations tells us that this illustration performs better than this photo. Not that all illustrations perform better than all photos, or even that the best option will always be an illustration. It could even be the positioning of the text that made the difference (left versus right on the screen).

What matters though is that we now have a combination of content for the homepage that we know is working well. We make this our new default (the ‘champion’ in testing terminology) and when we want to work further on this page we put up new designs as ‘challengers’ and test the page again. Given that this is our first round of testing, it is likely we can find many more gains over time.

What was the impact overall?

It’s interesting to compare these pages to each other, but what is even more dramatic is this impact this design had when compared to our previous homepage which was not included in the test variations. You can tell from the graph of Conversion Rate below which date this new homepage went live…

Homepage conversion rate

That’s it for now, but as we run more tests, we’ll share more results here too.

Meeting NotesMobile: 2015-01-28

Schedule

  • Next merge: 2015-02-23
    • This is an important merge for any Fx38 “Spring Moment” features, especially UI related

Tracking Review

Beta

  • Next Build:
ID Summary Status Assigned to
1010068 Disable OCSP in Firefox for Android NEW Brad Lassey [:blassey] (use needinfo?) (blassey.bugs)
1016555 Disable OCSP checking for certificates covered by OneCRL ASSIGNED David Keeler [:keeler] (use needinfo?) (dkeeler)
1084711 Graphic rendering problems on trunk, black boxes, nothing renderend, eventually crashes NEW Milan Sreckovic [:milan] (milan)
1089653 crash in java.lang.NullPointerException: at org.mozilla.search.SearchActivity.updateSettingsButtonVisibility(SearchActivity.java) NEW :Margaret Leibovic (margaret.leibovic)
1098227 Android crash in @0x0 | mozilla::layers::Layer::CalculateScissorRect NEW Nicolas Silva [:nical] (nical.bugzilla)
1113658 Unable to download while using second Android account ASSIGNED Wesley Johnston (:wesj) (wjohnston)
1114096 Wrong tab got mirrored NEW Mark Finkle (:mfinkle) (mark.finkle)
1120895 Interaction between TalkBack and Firefox beta/aurora/nightly broken with latest TalkBack 4.10 NEW Eitan Isaacson [:eeejay] (eitan)
1122643 Regression: Occasionally after a tab switch, images in the active tab turn black; corrects itself on reload NEW Seth Fowler [:seth] (seth)


9 Total;
9 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Aurora

  • Next Build:
ID Summary Status Assigned to
936041 Enable new malware download protection on Android NEW Gian-Carlo Pascutto [:gcp] (gpascutto)
1062758 crash in nsObserverService::RemoveObserver(nsIObserver*, char const*) REOPENED James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1065076 Update icons for video controls NEW Wesley Johnston (:wesj) (wjohnston)
1093815 Use AndroidPlatformDecoder for standalone MP3 on Android ASSIGNED Matthew Gregan [:kinetik] (kinetik)
1106935 Remove old tablet code and resources ASSIGNED Michael Comella (:mcomella) (michael.l.comella)
1120762 Test, solidify, and document Google Play distribution approach for split APKs NEW


6 Total;
6 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs. Make sure friends also get awarded a badge. New contributors are highlighted in bold.

  • James Dearing fixed bug 1124006 – Remove shrink comments in browser_toolbar.xml
  • Giovanny Gongora [:gioyik] fixed bug 1124479 – Remove unused plus-button styles from aboutReader.css and bug 1126426 – Rename reader-plus-icon-xhdpi.png on config.css
  • Dominique landed bug 663803 – Provide magnifying glass in areas of clustered links \o/
  • (iOS) Dusek landed bug 1123086 – Move VoiceOver cursor after loading webpage
  • (iOS) codestergit working on bug 1109666 – Customize behavior when long-pressing a link

Stand ups

Suggested format:

  • What did you do last week?
  • What are working on this week?
  • Anything blocking you?

Please keep your update to under 2 minutes!

James W. (snorp)

<Read Only>

  • Patches up for some video issues (bug 1100126, bug 1116469)
  • Ordered hardware to debug video crashes on Rockchip devices
  • Looking into what crash reports are still leaking to Google Play (filed and patch up for bug 1126454)

JChen

<Read Only> (on leave)

GCP

<Read Only>

  • Last week:
    • More SafeBrowsing discussion about alternate providers
    • Bugfixing on Video sandboxing (basically: it works)
    • Some investigation of NDK/ARM/AArch64 performance issues (summary: good thing we ditched ARMv6)
  • Next week:
    • More testing with video sandboxing
    • Think about sandboxing more stuffs

Randall Barker

<Read Only>

Last Week

  • Having (new) battles with try to get patches ready to land.
  • Have 5 of the 6 r+ needed to land (hope to get final one soon).
    • bug 1093934 Create a XPCOM library that can be used to support standalone WebRTC
    • bug 1097804 Create a library containing nsISocketTransportService and nsIDNS that can be used to support standalone WebRTC
    • bug 1101651 Enable WebRTC unit tests to be built using standalone WebRTC library

Next Week

  • Investigate bug 1121679 Enable receiving audio in standalone WebRTC

Eugen Sawin

<Read Only>

Finished

  • bug 1122623 – Implement update service as bound service

Working on

  • (landing) bug 792992 – Can’t override query URL for update service
  • bug 1093815 – Use AndroidPlatformDecoder for standalone MP3 on Android

Back from Berlin (office).

Brian Nicholson

<Read Only>

  • Getting the browser into a usable state
    • bug 1123501 – Dialog and window.open() support
    • bug 1126071 – Add stop/reload button to location bar
    • bug 1125996 – Location bar is too hard to tap
    • bug 1124310 – Crash when tapping the location view on on iPhone 6 Plus
  • bug 1126542 – Use mock server for SearchTests search suggestions

WesJ

liuche

<Read Only>

Highlights:

  • Passwords hack day – telemetry, process, goals
  • More onboarding with antlam: animations, fine-tuning
  • Reviews, mentoring

Present:

Past:

Margaret

<Read Only>

Highlights:

Past:

Present:

mcomella

Last of the new tablet uplifts to 36 (Beta). Test plz!

<Read Only>

Past
  • New tablet
    • Fix regression: bug 1117130 – URL bar border slightly covered by fading edge of title
    • bug 1110555 – LWT bitmap is incorrectly clamped to the right after starting the device in portrait mode and rotating to landscape
    • bug 1107386 – New tablet UI – Browser menu is clipped and unusable on the Kindle Fire
  • bug 1096958 – crash in java.lang.NullPointerException: at org.mozilla.gecko.home.TopSitesPanel.access$N(TopSitesPanel.java)
  • Mentor bug 663803 – Provide magnifying glass in areas of clustered links
Present
  • New tablet
    • bug 1125050 – Big space between thumbnail rows on Kindle Fire
  • bug 939350 – Create a python linter wrapper
Future
  • (Q1 goals) Toolbar cleanup & awesomescreen refresh

rnewman

<Read Only>

  • Distribution delaying. Waiting for beta approval.
  • Reading list stuff. Per-device datatypes for Sync… we hope.
  • Reviews and meetings, as usual.
Fixed
Working on

nalexander

Projects for this cycle:

  • Push migrate legacy Sync 1.1 devices across the finish line
    • Uplifted Telemetry and query parameter tracking
  • Make FxA provide OAuth implicit grants for Fennec consumers, tracked by bug 1117829
    • Rebased, tests still work \o/
  • Implement Firefox Accounts for iOS
    • Tracked by bug iosfxa
    • First version of embedded accounts.firefox.com up on github \o/
  • Make sure |mach bootstrap| for mobile/android works
    • Linux error has a patch, waiting for review: bug 1123824
  • Building with Gradle in automation
    • Green build, green try run with debug APK
Past
Present

Martyn Haigh

Past:

Present:

  • Finishing up some tablet related stuff
  • Open in background

Stefan

  • Made lots of progress on Reader Mode (includes UI now)
  • Next: Include local web server for assets. (Been delaying that but it seems we have to because WKWebView cannot access fontsincluded in the app otherwise), Localization, Enterprise Deployments for Dogfooding

James Hugman

<Read Only>
Past


Patches in flight: [778588 – Support direct voice input from the location bar].

Also starting [602818 – Integrate QR code scanner into Fennec], and helping out with [1111615 – Error page viewport jumps around during loading].

Impediments: Fighting with workflow.

Ally

  • pto on tuesday(yesterday)
  • Bug 1124711 – Site identity popup overlaps the URL Bar on phone
    • in review
  • Bug 1025703 – Ignore autocomplete=”off” for filling login forms
    • in review
  • Bug 1123820 – Change the expiration of master password probes to never expire
    • landed
  • Bug 1091461 (Aurora bug) Tapping anywhere under the ‘Private Browsing’ tip in the History panel will open the Custom menu
    • landed
    • m-a? m-b? flags set
  • Bug 1118863 – Add telemetry to know whether password saving is disabled globally
    • landed
  • Bug 1101746 – Display message when no passwords are present
    • waiting on UX(antlam)
  • Bug 1107591 – Show site identity popup when clicking the favicon on phones
    • landed
  • Password Manager Project at Large
    • becoming more concrete
    • passwords hack day. very focused on getting data, triage, & bug filing
  • Data Collection Module
    • reviewing Desktop FHR/telemetry v4+AWS plan
    • reviewing Query Modes for FHR+Telemetry v4
  • Follow up with e10s addon js exceptions telemetry with addon authors & jimm
  • Canary In the Coal Mine
    • Bug 1125330 – Expose |mach| output when internal Gradle mach invocations fail
    • failure to do ./mach package before ./mach gradle-install results in a bevy of cryptic errors about missing symlinks
    • Error:Internal error: (java.io.FileNotFoundException) /obj-dir/mobile/android/gradle/.idea/misc.xml (No such file or directory) means that you need to reimport the objdir/…/gradle
  • Where do we keep these ‘bylaws’ anyway?

BLassey

Fixed
Working on

MFinkle

<Read Only>

  • Planning week for
    • Passwords
    • Firefox for iOS
    • Reading List and Send Tabs
Fixed
Working on

Antlam

<Read Only>

  • Past
    • bug 1122302: Expose devices in share menu
    • bug 1101746: about:passwords empty state
    • bug 1088220: Visual clean up of doorhangers (related to Passwords)
    • in SFO for Passwords UX sync up with rfeeley
  • Upcoming
    • bug 1126608: Design for better fall back/manual fill experience
    • Wrapping up Tablet V1 last bugs with mcomella
    • Wrapping up “Welcome screen” first run UI improvements with liuche
    • Passwords UX sync up cont’d with rfeeley

Robin

iOS

  • Finishing up Reader Mode/view — final touches on transitions/toolbar appearance. Finalizing font-faces.
  • Moving on to Profile/FxA flow. Webview vs. Native. Avatars!
  • Beginning UI! \o/

Darrin

<Read Only>

  • Planning week in SF for Passwords, Firefox for iOS
  • Next 2 weeks, hoping to pare down my calendar and get heads down on iOS

QA

Feature Focus


Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 99998
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 99998
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 99998
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 99998
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 99998
    • UK/London: +44 (0)207 855 3000, x92 Conf# 99998
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2015-01-28

Schedule & Progress onUpcoming Releases (Lukas/Sylvestre/Lawrence)

  • 36 Beta 4
    • Desktop shipped yesterday
    • Mobile ships today
  • Next Beta release
    • Desktop Beta 5 gtb Thu, ships Fri
    • Mobile Beta 6 gtb Mon, ships Tue/Wed
  • Looking at options for the release date for the spring Firefox release

Feedback Summary (Cheng/Tyler/Matt)

Desktop

35 Snippet Survey going live soon

Writing a report on e10s feedback in nightly

Looks like Youtube made some kind of change yesterday so that more people are on HTML5 video.

Marketing, Press & Public Reaction (Arcadio/Winston)

  • Android efforts ramping up
  • Yahoo
  • SEM

Planning Meeting Details

  • Wednesdays – 11:00am PT, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Finch Conference Room
  • irc.mozilla.org #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

Mozilla: View Source FundraisingYear-End Campaign in Review: What We Learned

Ending a campaign of this magnitude is like stepping off a roller coaster. I’m mildly disoriented, exhausted, but also ecstatic that we far exceeded the goals we set. In retrospect, we learned a lot. What we do next with what … Continue reading

Air MozillaPrivacy Lab - a meetup for privacy minded people in San Francisco

Privacy Lab - a meetup for privacy minded people in San Francisco Brings together privacy professionals and others interested in privacy at for-profits, non-profits, and NGOs in an effort to contribute to the state of the ecosystem...

Mozilla SecurityPhase 2: Phasing out Certificates with 1024-bit RSA Keys

In the previous post about certificates with 1024-bit RSA keys we said that the changes for the second phase of migrating off of 1024-bit root certificates were planned to be released in Firefox in early 2015. These changes have been made in Firefox 36, in which the following 1024-bit root certificates were either removed, or their SSL and Code Signing trust bits were turned off.

  • Verizon
    • CN = GTE CyberTrust Global Root
      • SHA1 Fingerprint: 97:81:79:50:D8:1C:96:70:CC:34:D8:09:CF:79:44:31:36:7E:F4:74
  • Symantec
    • CN = Thawte Server CA
      • SHA1 Fingerprint: 23:E5:94:94:51:95:F2:41:48:03:B4:D5:64:D2:A3:A3:F5:D8:8B:8C
    • CN = Thawte Premium Server CA
      • SHA1 Fingerprint: 62:7F:8D:78:27:65:63:99:D2:7D:7F:90:44:C9:FE:B3:F3:3E:FA:9A
    • OU = Class 3 Public Primary Certification Authority – G2
      • SHA1 Fingerprint: 85:37:1C:A6:E5:50:14:3D:CE:28:03:47:1B:DE:3A:09:E8:F8:77:0F
    • CN = Equifax Secure eBusiness CA-1
      • SHA1 Fingerprint: DA:40:18:8B:91:89:A3:ED:EE:AE:DA:97:FE:2F:9D:F5:B7:D1:8A:41

If you manage an SSL-enabled website, this change will not impact you if your certificates and the certificates above it have 2048-bit keys or more. If your SSL certificate has a 1024-bit key, or was issued by a certificate with a 1024-bit key, then you will need to get a new SSL certificate, and update the certificates in your Web server. If the intermediate certificate that you are using has a 1024-bit key, then you will need to download the 2048-bit intermediate certificate from the Certification Authority (CA), and update the certificate chain in your Web server. For your convenience, links to the impacted CAs are provided in the list above.

Please check your SSL certificates and replace any with 1024-bit RSA keys, and contact mozilla.dev.security.policy if you have comments or concerns.

Mozilla Security Engineering Team

Air MozillaProduct Coordination Meeting

Product Coordination Meeting Weekly coordination meeting for Firefox Desktop & Android product planning between Marketing/PR, Engineering, Release Scheduling, and Support.

Mozilla ITDeploying tor relays

On November 11, 2014 Mozilla announced the Polaris Privacy Initiative.  One key part of the initiative is us supporting the tor network by deploying tor middle relay nodes.  On January 15, 2015 our first proof of concept (POC) went live.

TL;DR; here are our tor relays: https://globe.torproject.org/#/search/query=mozilla

When we started this POC, the requirements we had were:

  • the tor nodes should run on dedicated hardware
  • the nodes should be logically and physically separated from our production infrastructure
  • use low cost and commoditized hardware
  • nodes should be operational within 3 weeks

Hardware and Infrastructure

  • We chose to make use of our spare and decommissioned hardware.  That included a pair of Juniper EX4200 switches and three HP SL170zG6 (48GB ram, 2*Xeon L5640, 2*1Gbps NIC)
  • We dedicated one of our existing IP Transit providers to the project (2 X 10Gbps).

Actual tor physical infrastucture diagram

The current design is fully redundant.  This allows us to complete maintenance or have node failure without impacting 100% of traffic.  The worst case scenario is a 50% loss of capacity.

The design also allows us to easily add more servers in the event we need more capacity, with no anticipated impact.

Building and Learning

There is a large body of knowledge available on building Tor nodes.  I read mailing lists archives, blog posts, and tutorials. I had exchanges with people already running large relays.  There are still data points Mozilla needs to understand before our experiment is complete.  This section is a “quick run down” on some of those data points.

  • A single organization shouldn’t be running more than 10Gbps of traffic for a middle relay (and 5Gbps for an exit node).

This seems to be more of gut feeling from existing operators than a proven value (let me know if I’m wrong), but it makes sense.  We do have available transit and capacity. Understanding throughput and resource utilization is a key criteria for us.

Important Note: An operator running relays must use the “MyFamily” option in torrc.  This ensures a user doesn’t bounce through several of your servers.

  • Slow ramp up

A new Tor instance (identified by its private/public key pair) will take time (up to 2 months) to use all its available bandwidth. This is explained in this blog post: The lifecycle of a new relay. We will be updating our blog posts and are curious how closely our nodes mirror the lifecycle.

  • A Tor process (instance) can only push about 400Mbps.

This is based on mailing list discussions, as we haven’t reached that bandwidth yet. We run several instances per physical server.

  • A single public IP can only be shared by 2 Tor instances

This is a security feature to prevent a single person to run a ton of fake different nodes as explained in this research paper. This feature is documented in the Tor protocol specification.

  • Listen on well known ports like 80 or 443

This helps people behind strict firewall to access Tor. Don’t worry about running the process as root (needed to listen on ports < 1024), as long as you have the “User” option in torrc, Tor will drop the privileges after binding to the ports.

Automation

We decided to use Ansible for configuration management.  A few things motivated us to make that choice.

  • There was an existing ansible-tor role very close to what we needed to accomplish (and here is our pull request with our fixes and additions).
  • Some of our teams are using Ansible in production and we (Network Engineering) are considering it.
  • Ansible does not require a heavy client/server infrastructure which should make it more accessible to other operators.

And look! Mozilla’s Ansible configuration is available on GitHub!

Security

The security team helped us a lot along this project. Together we have put together a list of requirements, such as

  • strict firewall filtering
  • hardening the operating system (disable unneeded services, good SSH configuration, automatic updates)
  • hardening the network devices management plane
  • implementing edge filtering to make sure only authorized systems can connect to the “network management plane”

The only place for the infrastructure administration is the jumphost. Systems don’t accept management connection from anywhere else.

It is important to note, that many of the security requirements align nicely with what’s considered a good practices in general system and network administration. Take enabling NTP or centralized syslog for example – equally important for some services to run smoothly, for troubleshooting and for Incident Response. Similar concepts apply with the principle “make sure the network devices security is at least as good as system’s one”.

We’ve also implemented a periodic security check to be run on these systems. All of them are scanned from inside for security updates and outside for opened ports.

Metrics

One of the points we’re wondering are: how do we figure out if we’re running an efficient relay (in terms of cost, participation in the Tor network, hardware efficiency, etc). Which metrics to use and how to use them?

Looking around it seems like there is no “good answer”. We’re graphing everything we can about bandwidth and servers utilization using Observium. The Tor network already has a project to collect relays statistics called Tor metrics. Thanks to it, tools like Globe and others can exists.

Future

Note that we have just started them and they are far from running at their maximal bandwidth (for the reasons listed above). We will share more information down the road about performances and scaling.

Depending on the results of the POC,  we may move the nodes to a managed part of our infrastructure. As long as their private keys stay the same, their reputation will follow them wherever they go, no more ramp up period.

On a technical side there are a lot of possible things to do like adding IPv6 connectivity.  We’re reviewing opportunities to more parts of the deployment (like iptables, logs, etc…).

Links

Here are a few links that you might find interesting:

[blog] IPredator – building a Tor server
[mailing list] [tor-dev] Scaling tor for a global population

[mailing list] How to Run High Capacity Tor Relays
[wiki] tor – archwiki
[blog] Run A Tor-Relay On Ubuntu Trusty
[mailing list] [tor-relays] Someone broke the tor-relay speed record?
[tor website] Configuring a Tor relay on Debian/Ubuntu
[wiki] tor exit full setup

Thanks

Of course, none of that would have been possible without the help of Van, Michal (who wrote the part about security) and Opsec, Javaun, James, Moritz and the people of #tor!

WebmakerPrivacy Matters, Today and Everyday

Today is Data Privacy Day and we think it’s a great opportunity to get smart about your online privacy. If you are anything like us, you probably spend a large part of your daily life online which means understanding and controlling our online privacy is one of the most important skills of our age. It’s critical to the future of the open Web.

We are celebrating Data Privacy Day with a few simple actions you can take – resources to help raise your privacy IQ, some simple activities so you can help others learn more about their privacy online and ways to participate with the Mozilla community as we explore the privacy issue. Learn more about each below:

  • Visit our Data Privacy Day website to learn more about privacy issues with four easy steps to help you get smart on privacy.
  • Gather a group of friends, family or students and complete the Webmaker “Private Eye” activity. It’s a quick lesson that can create a real “Wizard of Oz” moment by pulling back the curtain to see who’s watching you on the Web.
  • Join us for a real-time privacy conversation on Twitter. Our Executive Director, Mark Surman, will be answering questions during a Twitter chat today at 2:00 pm EST, along with thought leaders from Duck Duck Go, McAfee, iKeepSafe.org and the Center for Democracy and Progress. Just be sure to tweet @Mozilla or follow along at #PrivacyChat!
  • Participate in our monthly Teach the Web talk today at 3 pm EST. Stacy Martin, Senior Manager for Privacy and Engagement, will be joining us to talk about how to be smart with your Privacy online. Join the google hangout here.

Empowering people to be in control of their online lives is an important part of  our mission – it is core to our principles and it’s why we want everyone to be smart on privacy. If you feel like we’ve helped raise your privacy IQ, help your friends and family raise theirs. It’s as easy as starting a conversation.

Mozilla IndiaYou and your online Privacy : Data Privacy Day.

Today is Data Privacy Day – January 28, 2015

​Data Privacy Day (DPD) is an effort to empower people to protect their privacy, control their digital footprint and escalate the protection of privacy and data as everyone’s priority.  Held annually on January 28th, Data Privacy Day aims to increase awareness of privacy and data protection issues among consumers, organizations, and government officials. DPD helps industry, academia, and advocates to highlight consumer privacy efforts.​dpd

twitter: @DataPrivacyDay


What is Data Privacy?

Data privacy, also called information privacy, is the aspect of information technology (IT) that deals with the ability an organization or individual has to determine what data in a computer system can be shared with third parties.


 Why is data privacy important?

  • Everyone’s trying to track what you do on the Web, it’s no secret that there’s big money to be made in violating your privacy.

  • One of the most invisible things about the Internet is that there are hordes of robots constantly scrutinizing your aggregate online behavior and determining whether you fit a certain profile.. What determines whether you look like you have something to hide? The robot builders have it in their best interests to keep that secret: otherwise, the people with something to hide would simply start gaming the system. Yet this can also result in a chilling effect: innocent people self-censoring their online behavior based on what they think the robots might be looking for.

    ” says Atul Verma (@toolness) in his write up about why privacy matters.

  • Sometimes data privacy can be a juggling act in multinational organizations when it comes to fulfilling the needs of the organization and complying with local privacy laws.
  • Ultimately, data privacy boils down to protecting the rights of the individual to prevent others from stealing their identity, knowing their personal information and much more.

 Data Privacy Day: What I can do?

  • Use HTTPS and SSL Whenever Possible:
    • Always use a secure browser. Look for “https” at the beginning of the web address (the “s” stands for “secure”). Access your accounts from a secure location, using computers and networks that you know are safe and secure.
    • Avoid using public networks and always look for the padlock icon in the corner of the browser, signaling that the website is encrypted.
    • The major benefits of a HTTPS certificate are:
      • Customer information, like credit card numbers, is encrypted and cannot be intercepted.
      • Visitors can verify you are a registered business and that you own the domain.
      • Customers are more likely to trust and complete purchases from sites that use HTTPS
    • more..  SecureHttps
  • Create secure Passwords and keep them private:
    • Your passwords should be more than 6 characters and contain letters, numbers and special characters.
    • Mix upper and lower case letters.
    • Don’t use personal information or dictionary words.
    • Hackers use software to enter random dictionary words to help them determine your password.
    • more..
  • Use a Master Password to protect stored logins and passwords :
    • Firefox can save usernames and passwords that you use to access online services, such as banking and email websites.
    • If you share a computer with anyone, it is recommended that you use a master password.
    • more..
  • Don’t Overshare on Social Media:
    • Go through your privacy settings on each site and determine what is a good amount of privacy protection.
    • Consider keeping your profile limited to only certain groups or friends.
    • Never post your personal information such as Social Security number, date of birth or your full name in a public place. Social-Media-Icons
  • Use a search engine that does not track you:
    • A search engine that does not collect or share any of your personal information.
    • A search engine which has no search history, profile or anything else stored, sold, or given to third parties. Sounds like no search engine like that exists?
    • Yes, it does. Check out : DuckDuckGo
    • read more about this and why you should be concerned : https://duckduckgo.com/privacy
    • more.. duck
  • Beware of Scammers:
    • If you receive a suspicious email from a business and you’re not sure if it’s legitimate, close the email, open a new browser, type in their web address and contact them through their customer service.
    • You should know that scammers are real and they will try to steal your personal information if they come across it.
    • Never give out your personal information over the Internet, phone, mail or via text message, unless you know exactly who you are dealing with.
  • Keep yourself safe online. How?
    • Do not reveal personal information inadvertently.
    • Turn on cookie notices in your Web browser, and/or use cookie management software or infomediaries.
    • Don’t reveal personal details to strangers or just-met “friends”.
    • Keep a “clean” e-mail address.
    • Realize you may be monitored at work, avoid sending highly personal e-mail to mailing lists, and keep sensitive files on your home computer.
    • Beware sites that offer some sort of reward or prize in exchange for your data.
    • Do not reply to spammers, for any reason.
    • Be conscious of Web security.
    • Be conscious of home computer security.
    • Examine privacy policies and seals.
    • Remember that YOU decide what information about yourself to reveal, when, why, and to whom
    • Use encryption!
    • more.. online-security
  • Many of us use public wifi networks where ever we can access them. They are a boon enabling us to be online when we need. But are we protecting ourselves and our data on these networks? Below are some tips about the same:
    • Turn Off Sharing
    • Enable Your Firewall
    • Consider Using a Virtual Private Network
    • Turn Wi-Fi Off When You Aren’t Using It
    • Automate Your Public Wi-Fi Security Settings
    • more..
  • Shopping online and using e-commerce sites has become a frequent activity online. Most of us shop online for various reasons. While doing this do we think about our data privacy and security. Below are some basic tips to follow while shopping online next time.
    • Look for the Lock: Never ever, ever buy anything online using your credit card from a site that doesn’t have SSL (secure sockets layer) encryption installed—at the very least. https-browsers
    • See if the url of the shopping website begins with https:// While non secure sites and pages begin with http://, secure sites begin with https://
    • Don’t Tell All: No online shopping store needs your social security number or your birthday to do business.
    • Disregard any unsolicited or suspicious looking pop-ups that appear during your online banking/shopping session.
    • more..
  •  Learn, Teach and Share about data privacy:

What we are doing today, join us!


Tips:


Useful links to read through:

 

The Mozilla BlogGet Smart On International Data Privacy Day

Today is International Data Privacy Day. It is a day designed to raise awareness and promote best practices for privacy and data protection. It is a day that looks to the future and recognizes that we can and should do better as an industry. It reminds us that we need to focus on the importance of having the trust of our users. At Mozilla, we start from the baseline that privacy and security on the Web are fundamental and not optional. We are transparent with our users about our data practices and provide them options for choice and control. We seek to build trust so we can collectively create the Web our users want – the Web we all want. Still, we are working to do better.

The term “privacy” means different things to each of us. At Mozilla, we don’t pretend to know what it means to everyone or that we can determine the right course of action for each user. Rather, our goal is to provide options to our users so they can choose what is right for them. Our privacy principles help guide features specifically targeted at user privacy and security — such as Do Not Track and accountless communications through Hello. And, we have other initiatives that are aimed at changing the way industry interacts with users. For example, our Tiles initiative helps prove that advertising and other customized content can be displayed in a manner that respects users. Each of these features has been engineered with privacy in mind.

We are also experimenting with new privacy and security features. In November, we announced an experimental tool — a tracking protection feature — that allows a user to opt-out of cross-site tracking of their Web activities. This month, we’ve conducted user testing to iterate and improve the feature and will further simplify and optimize its operation. We also announced that we would support Tor’s efforts to provide users with a private and secure browsing experience. We’ve now launched Tor relays that allow Tor to expand its network and serve more users. Tor can now spend more time on innovation and less time on scalability. We’re learning through this experimentation and will continue to iterate until we can do better.

We continue to advocate for transparency in our industry with respect to the collection and use of user data, and are committed to proving — through our own actions — that there is a better way. We are excited to begin 2015 by being recognized for the second time as the Most Trusted Internet Company for Privacy by the Ponemon Institute. We want you to help us to create the Web you want. If you have ideas about other steps we can take, please get involved. In the mean time, let’s celebrate International Data Privacy Day! Here are a few quick tips to get smart on privacy. And please join our Twitter Chat on January 28 at 11am PST hosted by @Firefox with guests (including from DuckDuckGo, McAfee, iKeepSafe, Privacy International and the Center for Democracy and Technology, among others).

Meeting NotesMozilla Platform: 2015-01-27

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015 Next Release: February 24, 2015
Trains
Central: 38 Aurora: 37 Beta: 36 Release: 35
  • Beta 4
    • Desktop ships today
    • Mobile ships tomorrow
  • Next Beta release
    • Desktop Beta 5 gtb Thu, ships Fri
    • Mobile Beta 6 gtb Mon, ships Tue/Wed

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

  • Seth Fowler has resolved a series of image-related memory usage regressions that have been present on AWSY since early November.

Stability (kairo)

<Read Only>

  • Overall numbers are still bad for everything other than desktop release (see beta/devedition bugs above, nightly crash rates are even worse).

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Electrolysis (e10s) (blassey)

GFX (milan)

  • WebGL regression sadness on Windows related to ANGLE. Both in 32/33 (hardware/driver specific) and 35 (investigating.) Bugs 1122465 and 1123365.
  • Need to put tooling in place to see if it’s shared memory that is soft-leaking, accounting for OOM on Windows.
  • Unified crashes due to driver resets, seeing crashreports at #4 which was before a long tail. Should help with tracking down the solutions.

JS (naveed)

<Read Only>

  • Compiler (JIT)
    • bug 1124002: Fix a bad performance issue with closure-compiled code (by removing some code).
    • bug 1125505: Posted patches to fix mutable __proto__ to not reshape the proto chain in common cases. This should make Shumway (raytrace.swf) a lot faster.

Layout (jet/dbaron)

Media (mreavy)

<Read Only>

1. What has your team done since last week that might impact others?

  • bug 749703 from an external contributor broke WebRTC calls by exposing an existing bug/timing-hole (merged to m-c Saturday); a fix is about to land (bug 1126036)
    • Some end-to-end functional tests for Hello that are about to land would catch this; most in-single-browser tests as we have in mochitest suites can’t/don’t hit the timing issue introduced.

2. What will your team do this week that might impact others?

Performance (vladan)

No update this week

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting


Engineering Meeting Details

  • Tuesday 2015-01-2711:00 am Pacific Standard Time
  • Calendar links: iCal ics or Atom/XML feed
  • Engineering Vidyo Room / Air Mozilla / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
  • Join irc.mozilla.org #planning for back channel
  • Dial-in: conference# 98411
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 98411
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 98411
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 98411
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 98411
    • UK/London: +44 (0)207 855 3000, x92 Conf# 98411
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 98411

The Bugzilla UpdateRelease of Bugzilla 5.0rc2, 4.4.8, 4.2.13, and 4.0.17

Sorry for the new release so soon, but we found a regression in the release last week and felt it would be best to get the fix out now rather than wait.

Bugzilla 5.0rc2 is our second Release Candidate for Bugzilla 5.0. This release has receive QA testing, and should be considerably more stable than the development releases before it. It is still not considered fully stable, and so you should understand that if you use it, you use it at your own risk.

If feedback from this release candidate indicates that it is mostly stable, then Bugzilla 5.0 will be released in a few weeks. If feedback indicates that more extensive fixes are needed, there may be another release candidate after this one.

Bugzilla 4.4.8 is our latest stable release. It contains an important bug fix:

Bugzilla 4.2.13 is a bug fix update for the 4.2 branch:

Bugzilla 4.0.17 is a bug fix update for the 4.0 branch:


SUMO BlogBug management and prioritization FAQ

We spend a lot of time in SUMO filing and working on bugs and roadmap items. This is a quite complex process that can sometimes be confusing to a lot of people and raises questions around how things are being done.

This blog post intends to provide more information around bug management and prioritization that will hopefully clarify some of the questions and make the process a bit more transparent.

Ready? Here we go!

 

Developer time

bugzilla

Currently there are 2 developers working on Kitsune (with Ricky leaving, this will probably be reduced to 1 dev until a replacement will be found).

 25% of  development time is used for what we call “paper cuts”: small features and bug fixes, anything that can be done fairly quickly and doesn’t require a long time.

 75% of development time is used for roadmap items. Roadmap items are those features or bugs that require more planning and are large enough that will require several sprints to complete.

 Anything that can be done quickly will be done as a 25% time. Everything else needs to go on the roadmap.

 All bugs are going in sprints. If you want to see what are the bugs that are currently being worked on you can follow the sprints here: https://sumo-ernest.herokuapp.com/project/support-mozilla-org

 

How is prioritization being done?

 

There are two steps when doing prioritization.

First step: champion prioritization

It is the area champion  who does the initial prioritization. He or she will have to assess the bugs that are filed for his area and decide which are the top priority ones. He will then push those ones to development.

Currently there are around 700 bugs in the SUMO backlog so looking at all of them is a bit difficult but we’re getting there :)

Second step: project manager prioritization

After champions choose which bugs they want to push for development the project manager (Kadir) needs to do a second round of prioritization. That means that he needs to look at all bugs that are being pushed, get some estimations and decide what goes first, what needs more details etc. If in the first stage the prioritization was done at area level (for example comparing L10N bugs between each other) at this stage the prioritization is done across all SUMO areas. That means that all KB, Forum, L10N, AoA, Search, Mobile, Users and Groups etc. bugs are assessed against each other. There is no quota for each particular areas, whatever is most important goes first no matter what areas it belongs to.

 

How are top priorities being chosen?

 

Normally there are two main things that are being looked at:

  • how many people is this impacting
  • how strongly are  people being impacted

 Unfortunately when it comes to prioritization there is no hard and fast rule and no perfect process. There are many things to be taken into consideration like the amount of work that is needed, developer availability, UX needs etc so sometimes the Project Manager will need to make harsh judgement  calls.

However breaking issues will be tended to right away. Normally things break only when we change something in the code (like a new feature being implemented) so they are part of the roadmap items time.

To make things easier, SUMO Admins are now using a spreadsheet where they enter the bugs they want prioritized. This will make it easier for Kadir to decide which bug will go into which sprint. You can view the spreadsheet here: https://docs.google.com/a/mozilla.com/spreadsheets/d/1BGULIZZxFv54EcVoBo1IGPzsjlOsuUB-0CnaU_oJjjQ/edit#gid=0

Normally if a bug makes it to that spreadsheet it means it will be done, it’s just a matter of when (some will take longer then others depending on what the priorities are).

After bugs are being prioritized they go into sprints. What goes in each sprint is based on estimations (i.e. how much effort individual bugs would take) and how much dev time is available.

 

How to file bugs and feature requests?

 

Make sure that in your bug description you touch the following points:

  • What problem are we trying to solve? (why are we doing this)
  • Who are we trying to solve this problem for? (target persona/impact)
  • How will we know if we succeed? (what is the outcome we are hoping for)

Feature requests are generally better to be discussed in the community forums first to get a feeling on what is it exactly that we want. Bugs that contain feature requests that are a bit fuzzy and require discussions are more difficult to prioritize. It is also a good idea to try to estimate how big of a job this is, features or bugs that require a lot of development time but have a low impact are unlikely to get prioritized any time soon.

The more clear we are about the impact that our feature will have, the better. The more data we have the easier it will be the area champion to prioritize and push your bug to development.

 

I never know which changes are happening and I’m sometimes taken by surprise, where can I get more info?

 

All changes, features, sprints are being discussed in the Platform meeting, every Thursday at 9 am PDT in the SUMO Vidyo room. The meetings are recorded so if you cannot attend, you can always watch the meeting afterwards. If there are specific bugs are features that you want to discuss simply add them to the agenda. You can add them even if you cannot attend the meeting live, just make sure you provide enough information and context so the people present can address your questions. More details about the meetings can be found here: https://wiki.mozilla.org/Support/KB/Meetings

That’s all folks! I hope all this information was useful and helped making the whole process a bit more transparent. Should you have any questions or concerns feel free to leave a comment, drop an email or discuss in the community forums. And don’t forget to bookmark some of the useful links below!

Useful links

 The SUMO Roadmap is listing all the big items that are being worked on during the quarter:https://trello.com/b/lo2NBhas/sumo-roadmap

If you want to see the bugs that are currently being worked on check out the sprint page (it lists the current sprint and the previous ones): https://sumo-ernest.herokuapp.com/project/support-mozilla-org

If you want to see bugs that are being prioritized per SUMO area, you can check this doc (work in progress): https://docs.google.com/spreadsheets/d/1BGULIZZxFv54EcVoBo1IGPzsjlOsuUB-0CnaU_oJjjQ/edit?usp=sharing

SUMO Platform meeting: https://wiki.mozilla.org/Support/KB/Meetings

More info about sumodev and the sprint process: https://wiki.mozilla.org/Support:Sumodev

Air MozillaEngineering Meeting

Engineering Meeting The weekly Mozilla engineering meeting.

Meeting NotesMozilla Project: 2015-01-26

All-hands Status Meeting Agenda

Items in this section will be shared during the live all-hand status meeting.

Friends of Mozilla

  • Big thanks to Jlin and guillermo for helping with a Vidyo issue last Tuesday
  • Thanks to Rosana Ardila, Lonnen, Patrick Finch, Maire Reavy, Doug Turner, Emma Irwin, and Jason Weathersby for helping to vet potential VP of HR candidates last week

Upcoming Events

Wednesday, 28 January

Happy Data Privacy Day! Celebrate with us by joining our Twitter chat this Wed, Jan 28 at 11am PT!

  • Follow #PrivacyChat on Twitter this Wed, Jan 28 at 11am PT
  • You’re invited submit questions or answer any questions you see with #PrivacyChat
  • You can also RSVP here!

We’ll be covering the importance of online privacy and, we have some special participants joining us like: Mozilla, McAfee, Privacy International, iKeepSafe, DuckDuckGo, and Center for Democracy and Technology.

Privacy Lab – a meetup for privacy minded people in San Francisco – at the San Francisco Commons

Cooper Quintin from the EFF, will present “A State of the Union for Privacy and Consumer Protection and Wishlist for 2015″ (3.30pm PT).

Teach The Web Talks celebrates Data Privacy day with Stacy Martin, Senior Privacy Manager at Mozilla.

We will discuss how to be Smart with your Privacy and how to teach people who has access to their data, where it goes or could go, and that they have a choice in all of it.

  • Join us live via Google hangout at 12pm PT/ 3pm ET/ 8pm GMT. Post your questions on discourse or on Twitter using #Teachtheweb

If you cannnot join us live, find out how to get involved on our Teach the Web Talks Wiki

Homebrew Website Club Meetup Be independent with your web browser and your web site.

  • San Francisco (@MozSF 1st floor), Chicago, and Portland.
  • 17:30-18:30 Writing Hour
  • 18:30-19:30 IndieWeb meetup & hack night

    Create or update your personal web site — wherever you host it, shared, VPS, or at home; static, dynamic, WordPress, or other software.

    Join a community with like-minded interests. Bring friends that want a personal site!

    Any questions? See the wiki page for details
    or join IRC: http://indiewebcamp.com/irc/today?beta#bottom

Thursday, 29 January

January Cantina speaker event – Nico Sell, live in San Francisco Commons / streamed to MV, YVR, YYZ, PDX (cantina’s on Friday for EU spaces)

Friday, 30 January
 * All aspects of contributing, including getting set up with Guides and all the ways of contributing. Then, information about how to contribute via code.
Saturday, 31 January
  • FOSDEM!!!
    • FOSDEM (Free and Open Source Software Developers’ European Meeting) is a free event offering open source communities a place to meet, share ideas and collaborate. It is renowned for being highly developer-oriented and brings together 5000+ geeks from all over the world. No registration necessary.
    • Location: Brussels
    • Mozilla Devroom: Schedule
    • More Info: Wiki Page

Project Status Updates (voice updates)

Firefox

Speaker Location: toronto (johnath)

  • Hello!
  • Spring
  • Winston on Mobile Marketing
Firefox OS
Marketplace Update

Speaker Location: David Bialer, San Francisco

https://docs.google.com/presentation/d/1RZpdFAHyMptilSS4y-K37LCHtta9Z95B8fXU61JMkEc/edit?usp=sharing

  • Recent Highlights
  • Performance
  • What’s Ahead
Content Services

Speaker Location: Sean Bohan, NYC

  • The Content Services team is planning on running a Brown Bag session on “How Advertising Works” for any Mozillians interested. Depending on response, we may run this more than once or do a follow-up to answer questions. The Brown Bag will be scheduled for mid-Feb and we will have a final date/time for next Monday’s Project Call.

Feel free to check it out and let us know what you think on Yammer!

  • If you have any friends at companies around the world who might be interested in tiles, have them send a note to contentservices@mozilla.com
Webmaker

Speaker Location: Andrew Sliwinski, Portland

http://mzl.la/changelog

  • Webmaker.org – Improving the experience for new users
  • Webmaker App – Improving the core user experience
  • Research – Kenya Field Report
  • Build.webmaker.org
Google Summer of Code
  • Google is running Summer of Code again in 2015. Mozilla has had the pleasure of participating every year so far, and we are hoping to participate again this year. In the next few weeks, we need to prepare a list of suitable projects to support our application.
  • Would you like to mentor a student through a 3-month coding project next summer? If so, add your project ideas to our brainstorming wiki page.
Web VR

Speaker Location: Josh Carpenter, San Francisco

Speakers

Presenter Title Topic Location Share? Media More Details
Who Are You? What Do You Do? What are you going to talk about? Where are you presenting from? (Moz Space, your house, space) Will you be sharing your screen? (yes/no, other info) Links to slides or images you want displayed on screen Link to where audience can find out more information
Mary Ellen Muckerman and friends VP Brand Smart on Privacy / Privacy Day SF No (potch, please share yours with link below) https://docs.google.com/a/mozilla.com/presentation/d/1le55Q1qJJwxiOAGFshNVbEZOX1PbmPWipkKmJyyuso4/edit#slide=id.p11 https://wiki.mozilla.org/Community/DataPrivacyDay
Michelle Marovich Head of Recruiting Req Opening Process: Update MV Nope None mmarovich@mozilla.com
John Jensen Director, Metrics MetricsGraphics.js library Vancouver MozSpace Yes Slides http://metricsgraphicsjs.org
Mark Surman Executive Director, MoFo 2015 Participation Strategy Remote Yes No slides https://commonspace.wordpress.com/2015/01/26/participationplan/

Roundtable

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we’ll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

Who are you? Area of question Question
What’s your name? What do you work on? Is your question about policy, a product, a Foundation initiative, etc. What would you like to know?

Welcome!

Let’s say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

Introducing New Volunteers

New Volunteer(s) Introduced by Speaker location New Volunteer location Will be working on
Who is the new volunteer(s)? Who will be introducing that person? Where is the introducer? Where is the new person based? What will the new person be doing?

Introducing New Hires

New Hire Introduced by Speaker location New Hire location Will be working on
Ceci Chang Mike Tsai (Recorded) Taipei, Taiwan Firefox OS Visual Designer
Tori Chen Mike Tsai (Recorded) Taipei, Taiwan Firefox OS Software Engineer
Morpheus Chen Mike Tsai (Recorded) Taipei, Taiwan Firefox OS UX Designer
Sung Chiu Evelyn Hung (Recorded) Taipei, Taiwan Firefox OS Software Engineer
Daosheng Mu Shelly Lin (Recorded) Taipei, Taiwan Firefox OS Software Engineer
Maja Frydrychowicz Syd Polk Mountain View Office Canada Remote (QC) Platform QA
Ryan Gendreau Sylvie Brossard Mountain View Office San Francisco Office What will the new person be working on?
Melissa Romaine Dave Steer San Francisco Office San Francisco Office Program Manager, Mozilla Advocacy — Focus on Ford-Mozilla Open Web Fellows program

<meta>

Notes and non-voice status updates that aren’t part of the live meeting go here.

Status Updates By Team (*non-voice* updates)

Engagement

  • Dial-in: conference# 8600
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 8600
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 8600
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 8600
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 8600
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 8600
    • UK/London: +44 (0)207 855 3000, x92 Conf# 8600
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 8600

Air MozillaMozilla Weekly Project Meeting

Mozilla Weekly Project Meeting The Monday Project Meeting

Mozilla: View Source FundraisingShould we put payment provider options directly on the snippet?

While our End of Year (EOY) fundraising campaign is finished, we still have a few updates to share with you. This post documents one of the A/B tests we ran during the campaign. Should we put payment provider options directly … Continue reading

QMOFirefox 36 Beta 3 Testday Results

Hello everyone!

Friday, 23rd we held a Firefox 36.0 Beta 3 Testday. Thank you for helping us on doing some verification testing and updating some of the bugs.

More details about the work done can be found in the etherpad.

Many thanks to  Yunito, gaby2300, Rode Orm and to all our moderators! Your help is allways appreciated.

We look forward to seeing you at the next Testday. Keep an eye on QMO for details!

SUMO BlogWhat’s up with SUMO – 23rd January

Another week, another welcoming party!

There’s definitely more of your coming over, but not everyone’s saying “hi” – don’t be shy, we love good company such as yours – introduce yourself!

The latest SUMO Community meeting

You can find the agenda and notes here: https://etherpad.mozilla.org/sumo-2015-01-19.

Unfortunately, we had an issue with the video recorder and it’s impossible to recover recording for this week :-(. My sincere apologies for that. It would be weird to have a WUWS post without a video… So here’s something to make you (hopefully) smile:

Reminder: the next SUMO Community meeting…

  • …is going to take place on Monday, 26th of January. Join us live if you can! Details on how to do it and the agenda & notes can be found here.
  • If you want to add a discussion topic to the live meeting agenda:
    • Start a thread in the Community Forums, so that everyone in the community can see what will be discussed and voice their opinion here before Monday (this will make it easier to have an efficient meeting).
    • Please do so as soon as you can before the meeting, so that people have time to read, think, and reply (and also add it to the agenda).

Community shout-outs

  • Everyone who helped us rock the last SUMO Day up to 95% questions responded in 24 hours, and 98% in 72 hours. You are amazing and we bow to your awesomeness :-)

Developer news

Forum news

L10n news

Firefox (+ OS, + for Android) news

January is almost over – hard to believe how time flies by, hm? Almost as fast as on Twitter (are you following us already?). We are all looking forward to seeing you on Monday – have a relaxed weekend… Unless you prefer adventures, in which case may your compass never stop guiding you to all the right places ;-).

 

Mozilla Web DevelopmentBeer and Tell – January 2015

Once a month, web developers from across the Mozilla Project get together to trade and battle Pokémon. While we discover the power of friendship, we also find time to talk about our side projects and drink, an occurrence we like to call “Beer and Tell”.

There’s a wiki page available with a list of the presenters, as well as links to their presentation materials. There’s also a recording available courtesy of Air Mozilla.

Michael Kelly: gamegirl

Our first presenter, Osmose (that’s me!), shared a Gameboy emulator, written in Python, called gamegirl. The emulator itself is still very early in development and only has a few hundred CPU instructions implemented. It also includes a console-based debugger for inspecting the Gameboy state while executing instructions, powered by urwid.

Luke Crouch: Automatic Deployment to Heroku using TravisCI and Github

Next, groovecoder shared some wisdom about his new favorite continuous deployment setup. The setup involves hosting your code on Github, running continuous integration using Travis CI, and hosting the site on Heroku. Travis supports deploying your app to Heroku after a successful build, and groovecoder uses this to deploy his master branch to a staging server.

Once the code is ready to go to production, you can make a pull request to a production branch on the repo. Travis can be configured to deploy to a different app for each branch, so once that pull request is merged, the site is deployed to production. In addition, the pull request view gives a good overview of what’s being deployed. Neat!

This system is in use on codesy, and you can check out the codesy Github repo to see how they’ve configured their project to deploy using this pattern.

Peter Bengtsson: django-screencapper

Friend of the blog peterbe showed off django-screencapper, a microservice that generates screencaps from video files using ffmpeg. Developed as a test to see if generating AirMozilla icons via an external service was viable, it queues incoming requests using Alligator and POSTs the screencaps to a callback URL once they’ve been generated.

A live example of the app is available at http://screencapper.peterbe.com/receiver/.

tofumatt: i-dont-like-open-source AKA GitHub Contribution Hider

Motorcycle enthusiast tofumatt hates the Github contributor streak graph. To be specific, he hates the one on his own profile; it’s distracting and leads to bad behavior and imposter syndrome. To save himself and others from this terror, he created a Firefox add-on called the GitHub Contribution Hider that hides only the contribution graph on your own profile. You can install the addon by visiting it’s addons.mozilla.org page. Versions of the add-on for other browsers are in the works.


Fun fact: The power of friendship cannot, in fact, overcome type weaknesses.

If you’re interested in attending the next Beer and Tell, sign up for the dev-webdev@lists.mozilla.org mailing list. An email is sent out a week beforehand with connection details. You could even add yourself to the wiki and show off your side-project!

See you next month!

Air MozillaWebmaker Demos January 23 2015

Webmaker Demos January 23 2015 Webmaker Demos January 23 2015

Mozilla Add-ons BlogRecent AMO Milestones

Screenshot 2015-01-28 11.14.23

4 Billion Add-ons Downloaded

AMO recently surpassed 4 billion add-on downloads (4,068,542,664 as of this writing), a huge milestone and a big win for customization.

There are 18,000 add-ons available, the most popular of which has over 20 million users. To give your Firefox a fresh look, you can choose from a library of over 369,000 themes. MaDonna, the most prolific theme designer, has created over 11,000 themes!

10 Years of the AMO Reviewer Community

The AMO reviewers community turned 10 years old a couple of months ago, and we haven’t had a chance to show you the special-edition t-shirts we’re making to celebrate the milestone.

FFx10th_AMO_Tshirt_1

Current AMO reviewers were invited to reserve one for themselves, and we expect them to be ready for shipping in a week or two. If you’re an add-on developer interested in joining this community of volunteers, please visit https://wiki.mozilla.org/Marketplace/Reviewers/Addons

Whether you’re a developer, designer, reviewer, or user, thank you for keeping Firefox the most extensible browser available!

WebmakerMozilla Learning in 2015: our vision and plan

Air MozillaCommunity Building Forum

Community Building Forum The Grow Mozilla Community Building Forum

Air MozillaReps weekly

Reps weekly Weekly Mozilla Reps call

Meeting NotesMobile: 2015-01-21

Schedule

  • Next merge: 2015-02-23

Topics for This Week

Crash Tracking
Soccorro is not correctly tracking Fx38.0a1 and Fx37.0a2 so we are not able to see Top Crashers for Nightly and Aurora. For details, see bug 1122145.
Meetups
There is a meetup on Jan 22nd in SF for Passwords Dev group. There is a meetup (Jan 26th) in SF to discuss progress and planning for Passwords, Task Continuity and iOS Q1 projects. There is a meetup (Feb 16th) in SF to critique and tweak Fx on iOS.

Tracking Review

Beta

  • Next Build:
ID Summary Status Assigned to
987223 No visible H.264 video playback on MPEG-4 AVC (part 10) (avc1) (Planar 4:2:0 YUV) on Android 4.0 devices NEW Edwin Flores [:eflores] [:edwin] (edwin)
1058160 Specify main activity org.mozilla.fennec.App with a default intent over org.mozilla.search.MainActivity ASSIGNED Nick Alexander :nalexander (nalexander)
1071690 WebGL content disappears NEW Robert O’Callahan (:roc) (offline Jan 17-22) (Mozilla Corporation) (roc)
1083271 Big regression in taskjs benchmark 2014-10-08 NEW Matt Woodrow (:mattwoodrow) (matt.woodrow)
1089417 fail to restyle for media query feature changes between adding/removing an empty stylesheet and next event that forces style computation (breaks golem.de on mobile) REOPENED David Baron [:dbaron] (UTC-8) (needinfo? for questions) (dbaron)
1090300 crash in mozilla::MediaCodecDataDecoder::DecoderLoop() REOPENED James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1096090 Android Aurora 35 fails to play videos on Asus Memopad NEW James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1096958 crash in java.lang.NullPointerException: at org.mozilla.gecko.home.TopSitesPanel.access$N(TopSitesPanel.java) NEW Michael Comella (:mcomella) (michael.l.comella)
1098390 Graphic buffer garbage shown and persists when entering full-screen (video/regular content) in Android 5.0 (Nexus 5) NEW
1100126 Flickering green/pink screen while playback video in different devices ASSIGNED James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1113658 Unable to download while using second Android account ASSIGNED Wesley Johnston (:wesj) (wjohnston)


11 Total;
11 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Aurora

  • Next Build:
ID Summary Status Assigned to
1010068 Disable OCSP in Firefox for Android NEW Brad Lassey [:blassey] (use needinfo?) (blassey.bugs)
1016555 Disable OCSP checking for certificates covered by OneCRL ASSIGNED David Keeler [:keeler] (use needinfo?) (dkeeler)
1059984 Remove CSS hacks from search activity results page NEW
1074635 don’t rerender the page for every frame in a GuM tab video stream NEW
1084711 Graphic rendering problems on trunk, black boxes, nothing renderend, eventually crashes NEW Milan Sreckovic [:milan] (milan)
1089653 crash in java.lang.NullPointerException: at org.mozilla.search.SearchActivity.updateSettingsButtonVisibility(SearchActivity.java) NEW Mark Finkle (:mfinkle) (mark.finkle)
1091461 Tapping anywhere under the ‘Private Browsing’ tip in the History panel will open the Custom menu NEW Allison Naaktgeboren please NEEDINFO? :ally (ally)
1091677 crash in @0x0 | mozilla::layers::ImageHost::GenEffect(mozilla::gfx::Filter const&) ASSIGNED Jonathan Watt [:jwatt] (jwatt)
1094214 fuzzy text NEW
1098227 Android crash in @0x0 | mozilla::layers::Layer::CalculateScissorRect NEW Nicolas Silva [:nical] (nical.bugzilla)
1107386 New tablet UI – Browser menu is clipped and unusable on the Kindle Fire ASSIGNED Michael Comella (:mcomella) (michael.l.comella)
1107930 crash in @0x0 | mozilla::layers::ContentHostIncremental::Composite(mozilla::layers::EffectChain&, float, mozilla::gfx::Matrix4x4 const&, mozilla::gfx::Filter const&, mozilla::gfx::RectTyped<mozilla::gfx::UnknownUnits> const&, nsIntRegion const*) NEW
1112232 Find in page search: It is not obvious that the case insensitivity button enables insensitivity NEW Robin Andersen [:tecgirl] (randersen)
1112939 Roku Tab mirroring falls behind NEW
1114096 Wrong tab got mirrored NEW Mark Finkle (:mfinkle) (mark.finkle)
1120895 Interaction between TalkBack and Firefox beta/aurora/nightly broken with latest TalkBack 4.10 NEW Eitan Isaacson [:eeejay] (eitan)


16 Total;
16 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs. Make sure friends also get awarded a badge. New contributors are highlighted in bold.

  • Surabhi Anand fixed bug 1115542 – Add software usage license to tests/*.java comments (except StringHelper)
  • psd fixed bug 852247 – Expose pref to force page zoomability via settings
  • capella fixed a ton of text selection bugs, including improving our test coverage and fixing a tricky intermittent orange (bug 851861)
  • (iOS) dusek fixed bug 1123055 – Respect “Darken colors” accessibility setting

Stand ups

Suggested format:

  • What did you do last week?
  • What are working on this week?
  • Anything blocking you?

Please keep your update to under 2 minutes!

James W. (snorp)

<Read Only>

  • Working On
    • Code reviews (bug 1106958, bug 663803)
    • DMCA exception stuff
    • Fixing inverted video and blocklisted decoder on PVR

JChen

<Read Only> (on leave)

GCP

<Read Only>

  • WebRTC sandboxing: everything works…one way only
  • SafeBrowsing work
    • Tracking Protection performance on pageload bug 1122691
    • Working with new partners for SafeBrowsing data

Randall Barker

<Read Only>

Last Week

Next Week

  • Same as last week.

Eugen Sawin

<Read Only>

Working on

  • Update service rewrite/refactoring
    • (in review) bug 1122623 – Implement update service as bound service
    • (depends on above) bug 792992 – Can’t override query URL for update service

Next week in Berlin (office).

Brian Nicholson

<Read Only>

WesJ

  • Landed a new run at a sqlite backend
  • Storing history now on iOS
  • Made the history pane work

Working on:

  • Storing individual history visits
  • filtering and sorting (frecency)

liuche

<Read Only>

Highlights:

  • Onboarding v1.5 in review
  • Discussions about Onboarding v2 (additional content, user studies, active customization)
  • Passwords (so many meetings…!) + Hack Day: Telemetry

Present:

Margaret

<Read Only>

Highlights:

  • Landed reader mode toolbar button for desktop (disabled) – bug 795981
  • Continuing work on desktop reader mode
  • Reading list discussions
  • Passwords discussions

Past:

Present:

mcomella

<Read Only>

Past
  • New tablet refresh
    • bug 1105472 – Domain highlighting fails when the URL is longer than the Awesomebar
    • bug 1116910 – Share button is larger than other buttons in ActionBar action mode on new tablet
    • bug 1116912 – [Tablet] Toolbar is hidden when opening a new tab with action mode open while scrolled down
Present
  • New tablet refresh
    • bug 1106935 – Remove old tablet code and resources
    • bug 1107386 – New tablet UI – Browser menu is clipped and unusable on the Kindle Fire
    • bug 1110555 – Graphical glitches when rotating with LWT enabled
Future
  • JSLint
  • Browser toolbar cleanup
  • Edit screen changes

rnewman

<Read Only>

Fixed
Working on

nalexander

<Read Only>

Projects for this cycle:

  • Push migrate legacy Sync 1.1 devices across the finish line
    • Migration bits all landed, tracked by bug migratesyncandroid
    • Landed Telemetry and query parameter tracking; need to request uplift
  • Make FxA provide OAuth implicit grants for Fennec consumers, tracked by bug 1117829
    • Rebased, tests still work \o/
  • Implement Firefox Accounts for iOS
    • Tracked by bug iosfxa
    • Pushing on jelly doughnut approach
      • Got screwed because accounts.firefox.com sets X-Frame-Options=DENY (and I was trying to iframe). WKWebView is not a full-fledged browser; we can’t ignore aspects of the web that we don’t like when using it. Work-around is easy.
  • Make sure |mach bootstrap| for mobile/android works
    • Looks like we’re on OS X now
    • Possible errors on Linux
Past
Present

Martyn Haigh

Past:

Present:

  • Open in background work
  • Mentoring

Stefan

<Read Only>

TL;DR Reader Mode landed. Currently finishing some more Reader Mode bugs. Then probably moving on to things important for our first round of dogfooding?

Ally

<Read Only>

  • landed first bug
  • finding bugs in gradle plugins… :/
  • telemetry probes for passwords project

BLassey

Fixed
Working on

MFinkle

Fixed
Working on

Antlam

<Read Only>

  • Past
    • bug 1063844: Improvements to current Onboarding
    • bug 1122302: Expose devices in share menu
    • Doorhangers UI
    • Passwords meetings
    • First run sync up
    • Reading list/mode sync up
    • iOS mocks
    • General Android bugs
  • Upcoming
    • Passwords UX sync up with Desktop
    • SFO!
    • NI-mail

Robin

iOS

  • Compiling designs, navigation variations.
  • Laying out landscape and iPad views.
  • Menu views.
  • Tab view variations.

Darrin

<Read Only>

  • iOS work (tab switch concept: http://cl.ly/image/3j0n3F3w0z3k, tab ideas: http://cl.ly/image/2K1k0u3o3k20)
  • working towards committing to some of the high level architecture/UX → next comes breaking down teh rest of the UI and starting to wireframe that
  • reading list work week in toronto (desktop + mobile)
  • password manager meetings

QA

Feature Focus

  • 38 list for Nightly – updated on Tuesday. Any problems with status? Please call out.
  • Short funnel review this morning. No changes impacting nightly work.
  • Also in SFO next week

Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 99998
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 99998
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 99998
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 99998
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 99998
    • UK/London: +44 (0)207 855 3000, x92 Conf# 99998
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2015-01-21

Feedback Summary (Cheng/Tyler/Matt)

Desktop

  • Input traffic is up as a result of the release but nothing stands out. Doing a deep dive (with MATH) today.

Planning Meeting Details

  • Wednesdays – 11:00am PT, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Finch Conference Room
  • irc.mozilla.org #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

The Bugzilla UpdateRelease of Bugzilla 4.4.7, 4.2.12, 4.0.16, and 5.0rc1

Today we have several new releases for you!

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 5.0rc1 is our first Release Candidate for Bugzilla 5.0. This release has received QA testing, and should be considerably more stable than the development releases before it. It is still not considered fully stable, and so you should understand that if you use it, you use it at your own risk.

If feedback from this release candidate indicates that it is mostly stable, then Bugzilla 5.0 will be released in a few weeks. If feedback indicates that more extensive fixes are needed, there may be another release candidate after this one.

Bugzilla 4.4.7 is our latest stable release. It contains various useful bug fixes and security improvements:

Bugzilla 4.2.12 is a security and bugfix update for the 4.2 branch:

Bugzilla 4.0.16 is a security and bugfix update for the 4.0 branch:


Air MozillaPassages: Leveraging Machine Virtualization and VPNs to Isolate the Browser from the Local Desktop

Passages: Leveraging Machine Virtualization and VPNs to Isolate the Browser from the Local Desktop Lance Cottrell, chief scientist for Ntrepid, presents Passages, a secure browsing platform for business which leverages machine virtualization and VPNs to completely isolate the browser...

Mozilla: View Source FundraisingShould we use the Mozilla or Firefox logo on our donation form?

Our end of year fundraising campaign has finished now, but while it’s fresh in our minds we still want to write up and share the results of some of the A/B tests we ran during the campaign that might be … Continue reading

Mozilla SecurityTighter Control Over Your Referrers

The purpose of the HTTP Referer (sic) header is to help sites figure out where their traffic comes from. However, as the Web got more complex, the amount of information in the Referer header ballooned, leading to bigger privacy problems. Firefox Beta supports a new feature to help sites protect their users’ privacy by changing the Referer header.

HTTP Referer provides a wealth of information about where you came from to the sites you visit, but this context isn’t always necessary (or desired). In addition, it is an unreliable tool for authenticating the origin of an HTTP request unless it’s always present, which it’s not due to privacy concerns (HTTPS sessions should not leak URLs to HTTP). When it is transmitted, there are still privacy concerns (“is that my username in the URL?”) because it’s all (whole URI) or nothing. To get what they want privacy-wise, sites often had to hack around direct loads with redirects and frames to change the referrer to something safer. What’s needed is a better way for referring sites to reduce the amount of data transmitted and thus providing a more uniform referrer that’s less privacy invasive.

This HTTP header has become quite problematic and not very useful, so we’re working to make it better.

Step one was to make gecko more flexible: we laid the groundwork so that it is easier for a user or browser extension to configure when Referer headers are sent and what they contain.

Step two is to help sites protect their users. Firefox 36 Beta now supports a feature called “meta referrer.” (Yes, this time “referrer” is spelled correctly.) Now your HTML documents can include a meta tag that specifies one of many referrer policies for the document to change what Firefox sends in the Referer header, and when it is sent. If your page contains the tag:

<meta name="referrer" content="origin">

all Referer headers in loads from your document will be without a path, query string or fragment, origin only. There are other policies you can specify to suppress referrers entirely, send a stripped-down referrer string cross-origin, and more.

We are proud to add this tool to the suite of features in Firefox that Web developers can use to protect their visitors’ privacy. Try it out! Let us know what you think!

Many thanks to Owen Chu for getting the gecko implementation started.

Sid Stamm
Security and Privacy Engineer

WebmakerBuilding version 1.5 of Mozilla’s Web Literacy Map

Alvar Maciel's thinking around representations of the Web Literacy Map at MozFest 2014

Mozilla’s Web Literacy Map constitutes the skills and competencies required to read, write and participate on the web. It currently stands at version 1.1 and a more graphical overview of the competency layer can be found in the Webmaker resources section.

Context

Starting last week we began working with the community on updating the Web Literacy Map to version 1.5. This is the result of a consultation process that initially aimed at a v2.0 but was re-scoped following community input. Find out more about the interviews, survey and calls that were part of that arc on the Mozilla wiki or in this tumblr post. The feeling was that we should double-down on what makes v1.x useful before moving to a v2.0 later in the year.

Some of what we’ll be discussing and working on in the community calls has already been scoped out, while some will be emergent. We’ll definitely be dealing with the following:

  • Deciding whether we want to include ‘levels’ in the map (e.g. Beginner / Intermediate / Advanced)
  • Reviewing the existing skills and competencies (i.e. names/descriptors)
  • Linking to the Mozilla manifesto (where appropriate)
  • Exploring ways to iterate on the visual design of the competency layer

On the first call we focused on the top item in this list – namely whether we should include ‘levels’ in the map. You can listen to the recording and read an overview of the decision we came to here. The consensus was that what might be ‘beginner’ in one context might be ‘advanced’ in another. So we’re not going to be including skills levels in v1.5 of the Web Literacy Map.

Get involved!

Please do join us every Thursday at 4pm UTC for the Web Literacy Map community calls (what time is that for me?). These will run to the end of March, by which time we should have created v1.5. Details of the calls are posted to the Webmaker list, or you can bookmark this wiki page.

In addition to these calls, we’ll almost certainly have ‘half-hour hack’ sessions at the same time on a Monday. These may include re-writing skills/competencies and work on other things that need doing – rather than discussing. Pay attention to the Webmaker list for more details on these!

Can’t make the calls? Please do add your feedback and ideas to the relevant section of the #TeachTheWeb discussion forum!

Image of Alvar Maciel’s notebook at MozFest 2014 CC BY Doug Belshaw

Meeting NotesSeaMonkey: 2015-01-20

Agenda

  • Who’s taking minutes? -> TBD
  • Nominees for Friends of the Fish Tank:
    • TBD

Action Items

(who needs to do what that hasn’t been recorded in a bug)
We should assign people to the open items.

NEW

  • Callek needs to talk to sheeri someone about public SeaMonkey dataviz pages not working.

OPEN

  • bug 1081726 Donation link on website needs to be change to point to SeaMonkey Paypal donation page. Blocked on mcsmurf getting a new CVS website account, looks like his old one has expired.
  • (bug 956561); move blog to https://blog.seamonkey-project.org. [DONE]
    • Now live with new design and branding.
    • Some progress with the SSL certificate issue. With the certificate, things would work easier as mcsmurf wants to sync the blog with Facebook entries.
  • Callek has been in discussions with MoCo on whether we (SM) can make use of Firefox Accounts.
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager
      • mcsmurf says he has a short term workaround for this.
  • bug 1057920 SeaMonkey’s CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website).
    • This has been spun off into a separate bugs for the website and the rest. For the website it looks like we’ll be going mercurial rather than svn (as that is the way the mozilla people would prefer it too).

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

  • Windows nightly trunk builds arewere running again briefly (thanks to Callek and Ewong) but are down again due to bug 1108970. Migrating our Windows builders to VS2013 would likely solve this and other bustages.
  • VS2010 support was removed from mozilla-central on 15th December (bug 1092468). Our Windows slaves are in the process of being upgraded to Win2008 and VS2013 (bug 1114876). There are also some upcoming changes to L10n build system in Q1 2015 (bug 1107635).
  • Buildmaster is up and running, and produces en-US builds, see 9/16 meeting’s Friends of the Fish Tank. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla.
  • bug 1083689 Langpacks aren’t updated when auto-updating SeaMonkey. The langpacks need strict versioning e.g. min 2.30 max 2.30.* which makes sense since you don’t want 2.29 strings with 2.30. This is possibly a build config problem so we should check with Callek, ewong, or KaiRo.
    • The de and en-GB langpacks for 2.30 have:
      <em:minVersion>2.30</em:minVersion><em:maxVersion>2.*</em:maxVersion>
      2.22 had:
      <em:minVersion>2.22</em:minVersion><em:maxVersion>2.22.*</em:maxVersion>
    • [IanN and RSX11M] There was a change in one of the scripts that generates the language pack files (the underlying issue was truncated version numbers introduced by Firefox) so it needs to be adjusted to take SeaMonkey into account.
  • Due to the master having some mysql issues, Callek has put a halt on the mysql updates, which affects the tbpl. So nothing is showing in TBPL atm.
  • [20th January 2015]
  • See RelEng page for the RelEng status history.
  • In Bug 902876 Comment 12 Mcsmurf is waiting for feedback from the build team on how to proceed.

Release Train

  • SeaMonkey 2.32b1 was released on December 16, 2014.
  • SeaMonkey 2.32b2 was released on December 21, 2014.
  • SeaMonkey 2.32b3 was released on January 4, 2015.
  • SeaMonkey 2.32 final was released on January 13, 2015.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • AMO and addon-signing. All addons will have to be signed, uploaded to AMO then reviewed by AMO editors including extensions not hosted on AMO. Otherwise they’ll be disabled. Discussion in mozilla.addons.user-experience
  • Firefox & Thunderbird Add-on Converter for SeaMonkey http://addonconverter.fotokraina.com/
    This tool goes a little further beyond simply modifying install.rdf – it also identifies a few more other things in the code that are Firefox or Thunderbird specific and attempts to change them. Of course, not all extensions can be ported so easily to SeaMonkey since there’s only so much an automated tool like that can do.
    •  !This item should be moved to somewhere more permanent and discoverable!
  • New versions of Flashblock for Firefox and SeaMonkey have been released to address a regression caused by bug 1050049.
  • Current Lightning 3.6b1 builds offered on AMO don’t work with the 2.31 release (bug 1081534, bug 1106034, bug 1107865)
    • Workaround is to install the version from 3.6b1-candidates/build3/
    • Lightning 3.7b1 builds for SM 2.32 release are expected may be released this week [1].
  • The Thunderbird team is planning to ship Lightning with Thunderbird. IanN thinks we will want to ship lightning too. We should coordinate with Thunderbird.
  • Proposed replacement for Venkman for shipping with SeaMonkey: Tiny JavaScript Debugger. TinyJSD is a JavaScript debugger for privileged code running Mozilla products like Firefox, Thunderbird, SeaMonkey. It serves to debug the application as well as extensions written in JavaScript.
    • Consensus is that we should ship TJSD as a replacement for Venkman. The next step is to contact the author.
  • bug 957149 DOM Inspector 2.0.15 released on 12th December. Ratty took over from IanN and finished preparing DOMi 2.0.15 for release [2].
  • Our build team needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. bug 763506

2.x (Last, Current, Next)

  • SeaMonkey Statistics can be viewed at https://dataviz.mozilla.org Across all channels we have an approximate ADU of 120k.
    • Callek needs to talk to sheeri about public SeaMonkey dataviz pages not working.
  • See Basics page for the usual reminders.
2.32

open tracking (0)
tracking requests (1)
targeted (2)
fixed (18)

2.Next
  • Stalled. Needs a kick.
    • bug 815954 Click-to-Play: Port bug 812562 (click-to-play blocklisted plugins: reshow urlbar notification as with normal click-to-play).
    • bug 476108 GetShortPathNameW fails under some NTFS junctions [patchlove].
  • Current breakages:
    • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager needs an owner
    • bug 995737 adapt seamonkey for the address book remote content policy change; use permission manager instead of address book property.
  • Mozilla-central bugs that affect us:
    • Our front end Sync UI needs to be updated as the old backend is going away in Gecko/Firefox 31. See: New Firefox Sync has landed in Firefox Nightly. Tracked in:
      • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager.
      • bug 1003434 Add support for about:sync-progress.
    • A lot of these bugs are due to mozilla-central switching from synchronous APIs to Asynchronous APIs.
    • bug 566746 (asyncFormHistory) Form history should use asynchronous storage API. Tracked in:
      • bug 912031 Use Asynchronous FormHistory.jsm in place of nsIFormHistory2 in Suite.
    • bug 769764 move proxy resolution to separate thread and remove sync api. Tracked in:
      • MailNews bug 791645 Rewrite calls to synchronous nsIProtocolProxyService::DeprecatedBlockingResolve with Async code before DeprecatedBlockingResolve disappears as well.
    • The C++ downloads manager backend nsIDownloadManager is being decommissioned. Firefox has migrated to jsdownloads. Thunderbird is in the process of migrating. We need to decide how we are going to handle this sooner rather than later.
    • bug 825588 Asynchronous JavaScript API for downloads and bug 851471 Decommission nsIDownloadManager. Tracked in:
      • bug 888915 Move SeaMonkey to the new JavaScript API for downloads when nsIDownloadManager is decommissioned.

Feature List, Planning

Bug statistics for the last two (full) weeks: 29 new, 9 fixed, 6 triaged.

  • Low triaging effort, average number of new bugs filed.
  • IanN thinks it would be useful to remind people on the newsgroups / forums that they can contribute by triaging. Tonymec will post a reminder to newsgroups / forums. See bug 1092632 (Sm_tri_HowTo) Document how to triage SeaMonkey bugs.

Open reviews/flags:
32 review
5 super-review
4 ui-review
8 feedback

  • See Feature List page for major wanted/needed features.
  • TODO: We will need to update our Sync UI code due to the new Sync API. Also we need to check if we are allowed to create FX accounts from our UI Since the new Sync accounts are FX accounts.[IanN] I’m sure I saw a question about FX accounts and branding. Callek was going to ask about being able to use Firefox accounts.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

ewong
  • review:
    • bug 1120067 — RSS (2.0?) feeds not updating and not being added.
    • bug 1106536 — Replace remaining use of obsolete dialogOverlay.xul, in SeaMonkey (/suite/browser/metadata.xul)
IanN
  • Usual testing, reviewing and commenting.
  • Fixed:
  • Fixed for c-c:
  • Fixed for m-c:
  • Fixed for m-i:
  • Pending check in:
  • Checked in pending review:
  • Waiting for feedback/review/information:
  • Fixing review comments before checkin:
    • bug 757230 When using add button for permissions in Data Manager set a displayHost
    • bug 798147 Switch to correct pref pane if pref window already open
  • Working on:
    • bug 1051642 Allow for flat chrome format when packaging extensions
    • bug 943335 [TB] Update icons used in searchplugins (Yahoo, eBay, Wikipedia, Amazon, Bing, Twitter)
    • Various SM Council documents.
    • bug 606683 Allow customization of toolbar in Composer and MailNews Composition
    • bug 639690 [META] Re-arrange code between editor and editorOverlay
    • bug 773979 [META] Switch to new drag and drop api in SeaMonkey
    • bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
    • File/Folder selection in windows.
  • To Do:
    • bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
    • Prefs-in-a-tab.
    • Create FAQ for Friends of the Fish Tank.
    • Help get composer standalone builds working with –enable-tests.
Neil

Checked in to comm-central, uplifted to comm-aurora:

  • bug 870556 Try to improve performance of the IMAP download queue.
  • bug 1101978 Deal with removal of the plugin finder service (string tweaks).
  • bug 558659 Support IMAP Special-Use folders.
  • bug 11039 Filter Sent messages.

Checked in to comm-central, uplifted to comm-aurora, checked in to comm-beta:

Working on:

  • bug 1121678 Add a menuitem to open a bookmark in a private window.

Still waiting for review:

Ratty
2014-12-09 to 2014-12-23

Working on:

  • bug 640420 Add draggable splitter between urlbar and searchbar.
  • bug 917725 Consolidate utils.js and PlacesUIUtils.jsm.
  • bug 1040910 Support XHTML in feed titles.

Waiting for review:

  • bug 1097818 Add search suggestions to the DuckDuckGo search engine.

Fixed:

  • bug 1098639 Arrow panels in SeaMonkey should not animate when opening.
  • bug 1110036 “Save As” stops working from “Page Info” > “Media” pane. Progress of downloading is 0% forever [Firefox].
  • bug 1106274 Go history menu items end up at the bottom of the menu and not between the startHistorySeparator and endHistorySeparator.
  • bug 1112690 Make the dialog for “Edit/New Attribute” Resizable.
  • bug 1114070 After bug 783829 PlacesUtils.nodeAncestors is now a new generator.
2014-12-23 to 2015-01-06

Working on:

  • bug 640420 Add draggable splitter between urlbar and searchbar.
  • bug 1040910 Support XHTML in feed titles.
  • bug 1117577 Bookmarks Manager, Tools, Restore, Choose file… does not recognize .json4lz.
  • bug 1115036 Update el (Greek) locale for DOM Inspector.

Fixed:

  • bug 917725 Consolidate utils.js and PlacesUIUtils.jsm.
  • bug 1097818 Add search suggestions to the DuckDuckGo search engine.
  • bug 1112196 In TopLevelImageDocument.css use img.transparent instead of img.decoded.
  • bug 1112205 SidebarTogglePanel() should ignore nodes that aren’t panel headers and aren’t panel menuitems.
  • bug 1115023 After bug 1066383 the navigator context menu is huge.
  • bug 1115572 Add newChannel2 (that takes loadinfo as an argument) to suite protocol handlers.
  • bug 1115575 Error: formatURLPref: Couldn’t get pref: browser.search.geoip.url.
2015-01-06 to 2015-01-20

Working on:

Fixed:

  • bug 1115036 Update el (Greek) locale for DOM Inspector.
  • Backed out bug 1115575 Prefs have been moved to core/toolkit.
  • bug 1116097 Selected profile not remembered in profiles.ini (regression)
  • bug 1117577 Bookmarks Manager, Tools, Restore, Choose file… does not recognize .json4lz.
  • bug 1118194 Clicking Validate link on Feed Subscriptions dialog does nothing.
  • bug 1122702 JavaScript Error: “invalid value for aNodeOrItemId” from PlacesUIUtils.jsm.
  • bug 1122934 Followup to bug 1074021 Tidy up and sync with Firefox nsBrowserApp.

Other stuff:

  • Did some reviews.
  • Bug triage and Bug discussions.
  • Usual end user support and PR in newsgroups and Mozillazine.
rsx11m

Fixed on trunk, merged into aurora:

  • bug 1102576 Extend help for tracking protection by descriptions for new notification bar and its preference.
  • bug 1108189 Color preference pane needs to be adjusted after bug 639134 changed boolean “browser.display.use_document_colors” to tristate “browser.display.document_color_use”. (strings only)

Fixed on trunk, waiting to be pushed to comm-aurora:

  • bug 1108189 Color preference pane needs to be adjusted after bug 639134 changed boolean “browser.display.use_document_colors” to tristate “browser.display.document_color_use”. (code and help)

Waiting for review:

  • bug 912216 Temporarily disable CONDSTORE support for GMail. (MailNews)

Stalled:

  • bug 1032302 8BITMIME keyword ignored in EHLO greeting, BODY=8BITMIME absent in MAIL request for 8-bit transfers. (MailNews)

Other:

  • Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
  • End-user information and discussion on MozillaZine.

Any other business?

  • The December 23, 2014 and January 6, 2015 meetings got cancelled due to holidays
  • New review policy for packaging fixes (package-manifest.in). Due to the general unavailability of the team members who usually review these changes (mcsmurf, Callek), Ratty will be available for reviewing packaging fixes or do them himself with a rs=packaging fix..

SeaMonkey Meeting Details

Meeting NotesMozilla Platform: 2015-01-20

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015 Next Release: February 24, 2015
Trains
Central: 38 Aurora: 37 Beta: 36 Release: 35
  • Firefox 35.0.1 candidates:
    • bug 1117873 – Firefox crash with “Enhanced Steam” extension since Fx35b1
    • bug 1113121 – Godaddy webmail crash [EXCEPTION_ACCESS_VIOLATION_READ]
    • bug 1121857 – document.baseURI does not get updated to document.location after base tag is removed from DOM for site with a CSP
    • bug 1122445 – CSP change in behavior regards case sensitivity loading resources
  • Firefox 36 beta2 gtb Tue, ships Wed (day late due to MLK day in the US)
  • Firefox 37 Aurora/Dev Edition updates have been re-enabled
  • lsblakk and lmandel both off the rest of this week. Sylvestre is handling all things relman.

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

  • Tree Closing Window (TCW) Saturday, January 24. Est 0700PT-1500 “Soft Close” (devs must follow up on their own jobs, intermittent outages possible.) Final details TBD. Tracking bug.

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

No update.

Stability (kairo)

  • Crash rates currently do not look good anywhere else than desktop release. If you have any topcrash or tracked bugs filed against your team, please help getting them fixed.

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Electrolysis (e10s) (blassey)

GFX (milan)

  • No update

JS (naveed)

<Read Only>

  • Compiler (JIT)
  • Garbage Collection
    • bug 650161: Compacting GC
      • Fixed an issue with uncollected shapes that are never touched except by compacting GC
      • Fixed several test failures and build errors
      • Attempted to land and got backed out

Media (mreavy)

<Read Only>

1. What has your team done since last week that might impact others?

  • Landed (thanks to Andreas Pehrson) bug 879717 (MediaStream->video_element->canvas works again)

2. What will your team do this week that might impact others?

  • Multistream support in WebRTC will reland once one problem is resolved
  • Once Multistream lands and sticks, Webrtc upstream update to branch 40 will land
  • Hello throttling (limits users who have the Hello button in the toolbar by default, as opposed to in Customize palette) will likely be turned to 100% within the next 1-2 weeks (everyone sees Hello in the toolbar)
  • Major rewrite of WebRTC mochitests (bug 1119593)

Performance (vladan)

1. What has your team done since last week that might impact others?

  • bug 1120126: Profiling Win64 nightlies should now be possible (thanks njn and dmajor)
  • Reminder: 3 business days to respond to Talos regressions, 2 weeks to make decision on the regression
  • If you get frequent or reproducible out-of-memory crashes (especially when Firefox is not actually out of physical memory), please ping me or David Major
  • Help us test bug 998863: Asynchronous initialization of plugins
    • It’s currently preffed *OFF* by default, please help us test it: set dom.ipc.plugins.asyncInit to true
      • e10s crash issues have been fixed
    • Mark any bug reports as blockers of bug 1116806

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting


Engineering Meeting Details

  • Tuesday 2015-01-2011:00 am Pacific Standard Time
  • Calendar links: iCal ics or Atom/XML feed
  • Engineering Vidyo Room / Air Mozilla / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
  • Join irc.mozilla.org #planning for back channel
  • Dial-in: conference# 98411
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 98411
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 98411
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 98411
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 98411
    • UK/London: +44 (0)207 855 3000, x92 Conf# 98411
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 98411

Air MozillaBay Area useR Group Official Meetup

Bay Area useR Group Official Meetup The Bay Area R Users Group hosts Ryan Hafen, Hadley Wikham and Nick Elprin. Ryan Hafen - Tessera is a statistical computing environment that enables...

Air MozillaEngineering Meeting

Engineering Meeting The weekly Mozilla engineering meeting.

WebmakerWhat we’re working on this Heartbeat

Transparency. Agililty. Radical participation. That’s how we want to work on Webmaker this year. We’ve got a long way to go, but we’re building concrete improvements and momentum — every two weeks.

We work mostly in two-week sprints or “Heartbeats.” Here’s the priorities we’ve set together for the current Heartbeat ending January 30.

Questions? Want to get involved? Ask questions in any of the tickets linked below, say hello in #webmaker IRC, or get in touch with @OpenMatt.

What we’re working on now

See it all (always up to date): http://build.webmaker.org/now

Or access the work broken down by:

Learning Networks

  • Design & test new teach.webmaker.org wireframes
  • Get the first Webmaker Club curriculum module ready for testing
  • Finalize our documentation for Badges / Credentialing
  • Document our Q1 / Q2 plan for Training

Learning Products

Desktop / Tablet:

  • Improve user on-boarding (Phase II)
  • Improve our email communications after users sign up
  • Create better moderation functionality for webmaker.org/explore (formerly known as “the gallery”)
  • Build a unified tool prototype (Phase II)

Mobile

  • Draft demo script and plan our marketing activities for Mobile World Congress
  • Make localization improvements to the Webmaker App
  • Build and ship device integrations and a screenshot service for Webmaker App
  • Distribute the first draft of our Kenya Field Report

Engagement

  • Prep and execute Data Privacy Day campaign (Jan 28)
  • Prep for Net Neutrality Campaign (Feb 5)
  • Draft a branding plan for Learning Products and Learning Networks
  • Design a splash page for Mobile World Congress

Planning & Process

  • Design and execute a communications plan on our overall 2015 plan
  • Document all our Q1 goals and KPIs in one spot
  • Add those quarterly goals to our dashboard
  • Ship updated documentation to build.webmaker.org (including: “How we do Heartbeats” & “How to use Git Hub Issues”)

 

 

Air MozillaMartes mozilleros

Martes mozilleros Reunión bi-semanal para hablar sobre el estado de Mozilla, la comunidad y sus proyectos.

Meeting NotesMozilla Project: 2015-01-19

All-hands Status Meeting Agenda

Items in this section will be shared during the live all-hand status meeting.

Speakers

Presenter Title Topic Location Share? Media More Details
Who Are You? What Do You Do? What are you going to talk about? Where are you presenting from? (Moz Space, your house, space) Will you be sharing your screen? (yes/no, other info) Links to slides or images you want displayed on screen Link to where audience can find out more information

Roundtable

Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we’ll do our best to get you an answer.

Please note that we may not always be able to get to every item on this list, but we will try!

Who are you? Area of question Question
What’s your name? What do you work on? Is your question about policy, a product, a Foundation initiative, etc. What would you like to know?

Welcome!

Let’s say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

Introducing New Volunteers

New Volunteer(s) Introduced by Speaker location New Volunteer location Will be working on
Who is the new volunteer(s)? Who will be introducing that person? Where is the introducer? Where is the new person based? What will the new person be doing?

<meta>

Notes and non-voice status updates that aren’t part of the live meeting go here.

Status Updates By Team (*non-voice* updates)

Automation & Tools
bugzilla.mozilla.org

Notable changes to bugzilla.mozilla.org during the last week:

  • bug 1077510 Check a Vagrant/Docker project file (excl DB content) into the Bugzilla repo

All changes.

Engagement

The DenFirefox Add-ons Hit 4 Billion Downloads

Thanks to an impressive suite of add-ons, the ability to customize Firefox is one of the reasons it’s the independent browser of choice for so many people. The proof is in numbers:

  • 18,000 add-ons available
  • 369,000 browser themes in the library
  • $634,000 donated to developers since 2009, when we started record-keeping
  • 4,000,000,000 add-ons downloaded!

That’s a lot of personalization! Three cheers to all of the developers who have contributed their time and talent to the amazing Firefox Add-ons resource and to all of you who are actively using it. Check out the latest add-ons, and add some fresh features to your Firefox today.


 

RELATED: Firefox Add-ons Cross More Than 3 Billion Downloads

SUMO BlogWhat’s up with… SUMO Buddies

Hello, SUMO Nation!

You may have heard of SUMO Buddies and noticed that recently we have not been particularly active in that area. Time to update everyone on what’s up with Buddies and where we want this idea to go this year.

We can not start talking into the future without a brief look into the past, of course. Soon after I had the honour of joining SUMO, Madalina asked me to take a closer look at Buddies and lead the charge in organizing the way SuMozillians support one another and help new members of our community get started.

The idea behind SUMO Buddies is a very simple one, but also one tied directly to how Mozillians as a community operate and succeed: “no new contributor left behind”. This means that whenever there is a new person joining SUMO and wanting to help as a member of the Support Forum Army of Awesome, the KB Editors, or the L10ns (rawr), there would be someone to show them around, answer their questions, and make sure they feel confident, comfortable, and happy to contribute to SUMO’s and Mozilla’s mission.

To achieve this, we tried to organize through different ways of communication (including IRC meetings on #sumomeet and #buddies, as well as forum threads on Discourse) and documentation (which you can find on the Mozilla Wiki, where it migrated from SUMO KB and was significantly expanded).

With time, it slowly became obvious that we were facing a few factors that made the Buddy format obsolete:

  • We were too spread globally to meet at regular times. We tried supplanting that with asynchronous communication (also known as “forums”).
  • Forum communication was not working, because being a Buddy was an extra activity for the majority of Mozillians willing to “buddy up”, already busy with the many aspects of supporting Mozilla’s mission in their free time.
  • Too much structure felt restrictive and “mechanical”; not enough structure felt loose and disorganised. At its core, the need and will to help others comes from within, and putting too many rules and regulations around it destroys that.

Having learned all this through trial and error, we discussed the state and future plans for Buddies last year in December, and now it is time to share our ideas for the next iteration of the idea with you:

  • We will keep encouraging all new SUMO contributors to introduce themselves in the forums.
  • As much as possible, we (Madalina and Michał) will take care of the new contributors and guide them to the SUMO experts – you :-)
  • Everyone (and we do mean everyone!) is welcome to jump in and be friendly and informative – the new SuMozillians count on you!
  • We will encourage new contributors to nominate the most helpful among you as “SUMO Buddies”. Yes, there will be badges…

The “SUMO Buddy” title will therefore be more of a badge (heh ;-)) of recognition for your friendly community presence and general awesomeness, rather than another role to fill in.

Confused? Concerned? Got questions or comments? Let us know in the forums!

SUMO BlogWhat’s up with SUMO – 16th January

Welcome to the second update of the year. We hope your 2015 is shaping up nicely and you’re ready for another set of news and reminders from the world of SUMO and Mozilla.

For Those About To Support Others… We Salute You!

Apologies if I missed you – let me know below, in the comments section.

The latest SUMO Community meeting

You can find the agenda and notes here: https://etherpad.mozilla.org/sumo-2015-01-12. The video should be below – if it’s not showing, check your browser settings ;-)

Reminder: the next SUMO Community meeting…

  • …is going to take place on Monday, 19th of January. Join us live if you can! Details on how to do it and the agenda & notes can be found here.
  • If you want to add a discussion topic to the live meeting agenda:
    • Start a thread in the Community Forums, so that everyone in the community can see what will be discussed and voice their opinion here before Monday (this will make it easier to have an efficient meeting).
    • Please do so as soon as you can before the meeting, so that people have time to read, think, and reply (and also add it to the agenda).

Community shout-outs

  • Safwan gets a million high fives for fixing a bunch of KB bugs in 1 day – thank you, good sir!

Developer news

Forum news

L10n news

Firefox (+ OS, + for Android) news

. Before you ask “where is the summary post for 2014, hmm?”, I’ll say “it will be here when it’s ready”, Duke Nukem 3D style ;-).

Whew, that’s it… Yes, we are still on Twitter, and we are looking for events around the world where you think SUMO and Mozilla should be present, talking about our mission and increasing Mozillian ranks. Have a great weekend and see you on Monday.

 

WebmakerAhead of the game on Obama’s call for broadband

On Wednesday POTUS broke out his iPad and spoke about the critical need to ensure internet access for all in the U.S. As a preview to his State of the Union address, he wants to “clear away the red tape,” and “help communities succeed in our digital economy.”

The President highlighted two cities as models of progress: Kansas City and Chattanooga. Two places that are at the center of Mozilla’s Gigabit Community Fund effort . Through generous support by the National Science Foundation, this fund provides grants and resources for local innovators exploring the use of next-generation gigabit technologies in Kansas City and Chattanooga and are emerging as active communities of practice.

In 2014, Mozilla’s Gigabit Community Fund invested in 17 educational projects that were piloted in more than 40 learning spaces. On the ground, these projects leverage the network for learning in classrooms and other spaces across communities, put next-generation technology into the hands of learners and push innovation forward while also building critical web literacy capacity among our teachers, informal educators and students. All of this leads to improved connected learning experiences, in and out of the classroom, by providing young people and adults with skills to explore, build and collaborate on the web in meaningful ways.

Access Isn’t Enough
The President is absolutely on target with pushing broadband access for all. However, it’s only one part of the success equation that needs to ensure that all people have access to digital literacy. Through our work with the Gigabit Community Fund, our Hive Learning Networks and Webmaker, we are committed to combining access to technology with skills that are integral to modern society: the ability to read, write and participate in the digital world.

One of the goals of Mozilla’s literacy efforts is to grow the scope and scale of our education and empowerment efforts. To reach more people. We also want to increase the diversity of how people learn with Mozilla: building opportunities for people to get together to learn, hack, invent and innovate in cities on every corner of the planet. We need to take the seeds of what is being started in places like Chattanooga and Kansas City and bring it to more people in more places.

Join Us
It’s up to us to take the next step. To make sure all the citizens of the web have the skills they need to help shape the future of the web. To learn more about our work in education on next-gen networks, visit the Mozilla Gigabit Community Fund blog or join the conversation on twitter @MozillaGigabit

Air MozillaWebdev Beer and Tell: January 2015

Webdev Beer and Tell: January 2015 Web developers across the Mozilla community get together (in person and virtually) to share what side projects or cool stuff we've been working on.

Air MozillaWebmaker Demos January 16 2015

Webmaker Demos January 16 2015 Webmaker Demos January 16 2015

QMOFirefox 36 Beta 3 Testday, January 23rd

Greetings mozillians!

 

Long time no Testday! So, the great news is that the following Friday, January 23rd, we’ll be hosting Firefox 36.0 beta 3 Testday. The main focus is going to be on  Youtube testing. All the detailed instructions are available in this etherpad.

No previous testing experience is required so feel free to join via #qa IRC channel and our moderators will give you assistance.

Join us next Friday and let’s make Firefox better together!

Air MozillaThinkFWD – What's the Hold Up? Accelerating Opportunity for Women in Tech

ThinkFWD – What's the Hold Up? Accelerating Opportunity for Women in Tech ThinkFWD is a quarterly speaker series focusing on important issues at the intersection of tech and politics. The tech community is great at solving problems....

WebmakerYour Stories from MozFest 2014’s Community Building track

This is a guest post from Beatrice Martini (of http://beatricemartini.it/) and Bekka Kahn (of The Open Coalition), Community Building track wranglers from MozFest 2014.

Screen Shot 2015-01-15 at 10.40.33 AMThis year, MozFest hosted the first-ever Community Building track for participants. Wrangled by Beatrice Martini and Bekka Kahn, and rocked by a phenomenal team of facilitators, this track explored a wide variety of aspects of how to build communities, from what defines a community, to how to gather your crowd, finding funding, understanding how to include open working practices in your community’s day-to-day activity.  We were blown away by how many people joined our sessions, bringing a wealth of perspectives, experience, insights and opinions. We’ve collected a couple of their stories here – we hope they make you feel as inspired as we are to continue building powerful communities on the Web.

Screen Shot 2015-01-15 at 10.41.50 AMName: Alifiyah Ganijee

Session: Join! Types of diversity and inclusion

Twitter or Website: @alifyaganijee | @mozillamombasa | @MombasaTech | www.mombasatech.org

What did you learn: I learnt that cultural diversity is a common and global challenge and that it is the simple perspective towards certain issues that can help us collectively overcome the challenge.  On the other hand, what might work in one country may not work in another it’s very important to study one’s community and identify what may work best and then give it a shot! It is equally crucial to appreciate people’s thoughts. The overall objective is to be able to fix the puzzle :)

What would you like to do next: I look forward to actualize some of the ideas shared within the groups on how to adopt a vibrant and culturally diverse community. I would also like to stay connected with the entire MozFestCB team to share my learning outcomes and experiences as time goes by and thus build a better, more connected, more diverse and stronger community.

Screen Shot 2015-01-15 at 10.42.38 AMSession: Join! Types of diversity and inclusion

Name: Cynthia “Arty” Ng

Twitter or Website: @TheRealArty

What is your project about: Accessibility (as part of the Diversity and Inclusion session)

What did you learn or make : We had a great discussion during the session about the different aspects to consider including online vs. offline, different types of disabilities, and variety of technology (both software and hardware). One of the major points that came up was that inclusion has such a large scope that it seems almost impossible to take everything into account, but that one method might be to attempt to design at a broader level to consider all types of diversity by thinking about universal design or universal usability.

What would you like to do next: I would love to create or contribute to a list of resources, especially around web based or online development.

Screen Shot 2015-01-15 at 10.44.03 AMName: Faye Tandog

Session: Student Involvement in Mozilla Communities

Twitter or Website: @fayetandog,  http://fayetandog.com

What is your project about: Student Involvement in Mozilla Communities

What did you learn or make (include details):

We have gathered feedback on how we can improve the FSA program and make Mozilla communities more interesting for students.

What would you like to do next:

I would like to focus on raising awareness first on the existence of Mozilla communities (as apparently, people still perceive Mozilla as simply another for-profit tech company), develop recruitment programs to spread the word to students and create programs to keep student contributors empowered in the community.

Name: Galaxy Kadiyala

Session: Student Involvement in Mozilla Communities

Twitter: @GalaxyK

Website: http://galaxyk.github.io

What did you learn? Ilearnt about different community practices from the participants. Each of them had a different perspective regarding involvement of students in communities in general. An interesting find is that most of them won’t get involved because they think that they do not have much knowledge about the project/community.

What would you like to do next: We’ll be making use of the feedback in the Firefox Student Ambassador program. This program has vast number of students from different countries and think we can improve the program in a much more *easy to get involved* way.

Screen Shot 2015-01-15 at 10.44.48 AMName: Carl Ruppin

Session: Walking the talk – How to work open

Twitter or Website: @p2pu

What did you learn? ‘Open’ means quite different things when applied to governance or work-practices .  Working ‘openly’ tends to mean either working transparently or making decisions collaboratively which are two different things. Both are hard to implement and apply consistently across an organization, particularly one with many different sub-communities, like tech vs non-tech, managers vs staffers, open literati vs newcomers to the world of open etc. Making it work requires  discussion and building processes in advance, which can be hard to do.

Screen Shot 2015-01-15 at 10.45.37 AM

Name: Jessica Kaminsky

Session: Using a Spectrogram for Stakeholder Mapping and Power Analysis

Twitter or Website: @jesskaminsky and @hear_me_project

What is your project about:  An initiative of the CREATE Lab at Carnegie Mellon University, Hear Me asks students to contribute their voices to meaningful conversations through media-making projects. Hear Me’s platform connects student voices to audiences to inform policies and practices and raise awareness around youth issues.

What did you learn or make? I worked with Mikva Challenge (http://www.mikvachallenge.org/) to create a stakeholder map on a project about implementing restorative justice practices in Chicago Public Schools.  The workshop helped us identify stakeholders and other interested parties, and discuss the power relationships between these groups.  We created a spectrogram that visualized these relationships. The session also covered the different engagement tactics that we should use for each stakeholder based on where they were within the spectrogram.

What would you like to do next:  I’d like to continue to work with Mikva Challenge to figure out how to get more schools to implement restorative justice practices, in Chicago and beyond!  I would also like to unify efforts with groups like Mikva to challenge policies, like restorative justice practices, at the local and national level.

 

Want to know more about the Community Building track? Check out the track’s documentation here!

Also, the Open Coalition is happy to host our upcoming conversations – join the mailing list to stay in touch!

SUMO BlogThursday, January 15th 2015, is SUMO Day!

Hey, hey, hey, it’s Thursday, it’s 2015 and it’s SUMO Day! We are answering questions in the support forum and helping each other in #sumo on IRC from 9am to 5pm PST (UTC -8) today.

Join us, create an account and then take some time today to help with unanswered questions. Please check the etherpad for additional tips. We have been experiencing quite a high number of questions in the last few days. Our goal this Thursday is to respond to each and ever one of them, so please try to answer as many questions as you can throughout the day.

Happy SUMO Day!

Air MozillaReps weekly

Reps weekly Weekly Mozilla Reps call

Rumbling Edge - Thunderbird2015-01-14 Calendar builds

Common (excluding Website bugs)-specific: (16)

  • Fixed: 432675 – Revise layout of Alarms option pane in preference dialog
  • Fixed: 639284 – Metadata of “Provider for Google Calendar” extension are not translated at AMO
  • Fixed: 909183 – calIDateTime.compare returns incorrect result with floating timezone
  • Fixed: 941425 – Yearly rule “Last day of a month” can’t be set with the UI and is wrongly displayed in the views.
  • Fixed: 958978 – Yearly recurrences with BYMONTH and more BYDAY are displayed wrongly if the last day of the month is not displayed in the view
  • Fixed: 985114 – Make use of CSS variables
  • Fixed: 1072815 – Multiple locales were missing in Lightning 3.3.1 release
  • Fixed: 1080659 – Converting email into task/event fails when localization uses regular expression special characters
  • Fixed: 1082286 – [icaljs] Date/Time Picker seems to have a timezone error
  • Fixed: 1107388 – No auth prompt is shown when subscribing to CalDAV calendars [domWin.document is null]
  • Fixed: 1112502 – Right clicking on a recurring event, and bringing up the attendance sub-menu gives unreadable titles
  • Fixed: 1114504 – Extra localization notes for bug 493389 – Provider for Google Calendar cannot sync tasks
  • Fixed: 1115965 – Provide filename and line number in cal.WARN and cal.ERROR
  • Fixed: 1117324 – Improve stack trace for calListenerBag
  • Fixed: 1117456 – Run unit tests on ical.js as well as libical
  • Fixed: 1118489 – promisifyCalendar mis-invokes Proxy constructor

Sunbird will no longer be actively developed by the Calendar team.

Windows builds Official Windows

Linux builds Official Linux (i686), Official Linux (x86_64)

Mac builds Official Mac

Rumbling Edge - Thunderbird2015-01-14 Thunderbird comm-central builds

Thunderbird-specific: (30)

  • Fixed: 486501 – edit an address after autocomplete and autocomplete reselects the first choice, even reverts to a different address (involving quoted “Display Name”)
  • Fixed: 505721 – Thunderbird theme on Linux feels cluttered (inappropriate spacing, etc.)
  • Fixed: 532067 – (Windows 7 theme) Icon for Sent folder to match qute and gnomestripe metaphor
  • Fixed: 733856 – [meta] Australis OSX tracker bug
  • Fixed: 735318 – Chatting notification only show the selected conversation not the one notifying me.
  • Fixed: 925746 – Option to Open the Preferences in a Tab
  • Fixed: 947656 – [meta] Shared Themes
  • Fixed: 1025684 – With mail.identity.default.autocompleteToMyDomain=true, edit an address after autocomplete and autocomplete reselects the first choice, even reverts to a different address (only for speedy corrections!)
  • Fixed: 1094706 – Thunderbird changes needed due to the web installer interfaces now using browsers instead of DOM windows
  • Fixed: 1095893 – opened attachments (using “Open with”) are no longer set read only
  • Fixed: 1099068 – Switch to new event constructors in Thunderbird
  • Fixed: 1105841 – Lightweight themes don’t change styling properly on OS X 10.10.
  • Fixed: 1106796 – reference to undefined property this.lastMessage.sourceFolder in resource:///modules/activity/moveCopy.js
  • Fixed: 1107844 – Recipient autocomplete: For multiple matches, select dropdown result other than first using mouse click, confirm with Tab or Enter, and TB uses 1st result instead (i.e. private msg gets easily addressed and sent to random recipients)
  • Fixed: 1110095 – Messages -> Create filter from message broken by bug 1085205
  • Fixed: 1110389 – Allow “create filter from message” also for other fields in message header
  • Fixed: 1113035 – Adapt Debugger Server startup code for changes in bug 1059001. error DebuggerServer.openListener is not a function
  • Fixed: 1113298 – Recipient autocomplete: From results dropdown, select any but 1st entry via mouse click, then Ctrl+Enter to send message immediately: sudden change to another recipient (1st result)
  • Fixed: 1113610 – New version of other actions button breaks CompactHeader addon
  • Fixed: 1115018 – On startup, error “Windows cannot find … uninstall\helper.exe”
  • Fixed: 1115034 – Recipient type selectors (To, CC, etc.) design nits on WinXP theme: showing two dropdown arrows, inconsistent background color and hover behaviour
  • Fixed: 1115189 – TEST-UNEXPECTED-FAIL | /builds/slave/test/build/mozmill/content-tabs/test-content-tab.js | test-content-tab.js::test_content_tab_context_menu
  • Fixed: 1115990 – Add an option to Prefs/Advanced to enable/disable the hardware acceleration
  • Fixed: 1116958 – Win7+: treelines on selected treechildren should have the text color
  • Fixed: 1117089 – preference.value is null opening the font settings.
  • Fixed: 1118703 – TEST-UNEXPECTED-FAIL | toolkit/forgetaboutsite/test/unit/test_removeDataFromDomain.js | xpcshell return code: 0
  • Fixed: 1119468 – Port Bug 1118032 to TB [the word “Automatic” does not convey any information on what the choice actually does]
  • Fixed: 1119512 – mozilla/mach fails to configure without python in path
  • Fixed: 1119911 – autosync.js, line 75: ReferenceError: reference to undefined property this.autoSyncManager
  • Fixed: 1119959 – TEST-UNEXPECTED-FAIL | toolkit/components/telemetry/tests/unit/test_TelemetryPing.js | xpcshell return code: 0

MailNews Core-specific: (14)

  • Fixed: 11039 – Filter outgoing/Sent messages (perhaps to use a different Sent/FCC folder)
  • Fixed: 570711 – When going online, send outbox first
  • Fixed: 695671 – Filtering stops — Only 1 filter executes for “Run Filters on Folder” (after execution of action=”Delete”, further/different actions on other mails is not executed and filter log is not written to filterlog.html).
  • Fixed: 741340 – Port |Bug 739188 – Allow crosscompiling for Windows without NSIS| to comm-central
  • Fixed: 872357 – Perma-orange on Windows: TEST-UNEXPECTED-FAIL | ../../../resources/mailTestUtils.js:444 | Error: CreateFile failed for c:\users\cltbld\appdata\local\temp\tmpmddsgp\mailtest\Mail\Local Folders\Inbox, error 32
  • Fixed: 998191 – Introduce the structured header concept to nsIMsgCompFields
  • Fixed: 1070525 – applying the ‘delete’ operator to an unqualified name is deprecated in Feed reader
  • Fixed: 1114328 – Remove some useless variables
  • Fixed: 1115113 – fix signed/unsigned comparison warnings in mailnews/local/src/nsLocalUndoTxn.cpp
  • Fixed: 1115145 – Convert some occurences of ns*Array.IndexOf(elem) != kNotFound to ns*Array.Contains(elem)
  • Fixed: 1116561 – filter after the fact should return an error if any filter failed
  • Fixed: 1116959 – Removing search terms blanks out results list in address book quick search and contacts side bar search
  • Fixed: 1116982 – TEST-UNEXPECTED-FAIL | mailnews/compose/test/unit/test_messageHeaders.js | xpcshell return code: -11
  • Fixed: 1120093 – mailnews/imap/test/unit/test_imapSearch.js, line 260: SyntaxError: test for equality (==) mistyped

Windows builds Official Windows, Official Windows installer

Linux builds Official Linux (i686), Official Linux (x86_64)

Mac builds Official Mac

Meeting NotesMobile: 2015-01-14

Schedule

  • Firefox 35 has shipped!
  • Next merge: 2015-02-23

Topics for This Week

Firefox 35
Shipped a jam-packed release: Search activity & widget, Share overlay, Sync Tabs homepanel, Better error pages (Wifi and Search), Stumbler (perms bump), System DM integration (perms bump), Better network switching and lots of other stuff!
Passwords
The group driving the Password project has been meeting weekly, and has also started triaging bugs. Q1 goals include: Telemetry/Metrics; Changes to save/fill heuristics; and UX changes for saving, filling (including fallback) and password manager.
Task Continuity
The group working on Reader/Reading List have started meeting weekly and planning Q1 goals. Reader view for Android, iOS and Desktop seems to be moving ahead. UX is working on designs for Reading List on Desktop. The Reading Service is also moving ahead and work should be starting soon on client-side integration. The “Send Tabs to Devices” project has not been explicitly addressed yet, but should be soon. Work has been accumulating on that project, but it needs a bit of management/process.

Tracking Review

Beta

  • Next Build:
ID Summary Status Assigned to
987223 No visible H.264 video playback on MPEG-4 AVC (part 10) (avc1) (Planar 4:2:0 YUV) on Android 4.0 devices NEW Edwin Flores [:eflores] [:edwin] (edwin)
1058160 Specify main activity org.mozilla.fennec.App with a default intent over org.mozilla.search.MainActivity ASSIGNED Nick Alexander :nalexander (nalexander)
1071690 WebGL content disappears NEW Robert O’Callahan (:roc) (Mozilla Corporation) (roc)
1083271 Big regression in taskjs benchmark 2014-10-08 NEW Matt Woodrow (:mattwoodrow) (matt.woodrow)
1089417 fail to restyle for media query feature changes between adding/removing an empty stylesheet and next event that forces style computation (breaks golem.de on mobile) REOPENED David Baron [:dbaron] (UTC-8) (needinfo? for questions) (dbaron)
1090300 crash in mozilla::MediaCodecDataDecoder::DecoderLoop() REOPENED James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1096090 Android Aurora 35 fails to play videos on Asus Memopad NEW James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1096958 crash in java.lang.NullPointerException: at org.mozilla.gecko.home.TopSitesPanel.access$N(TopSitesPanel.java) NEW Michael Comella (:mcomella) (michael.l.comella)
1098390 Graphic buffer garbage shown and persists when entering full-screen (video/regular content) in Android 5.0 (Nexus 5) NEW
1100126 Flickering green/pink screen while playback video in different devices ASSIGNED James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1113658 Unable to download while using second Android account NEW Wesley Johnston (:wesj) (wjohnston)


11 Total;
11 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Aurora

  • Next Build:
ID Summary Status Assigned to
710802 we need updater tests NEW James Willcox (:snorp) (jwillcox@mozilla.com) (snorp)
1010068 Disable OCSP in Firefox for Android NEW Brad Lassey [:blassey] (use needinfo?) (blassey.bugs)
1016555 Disable OCSP checking for certificates covered by OneCRL ASSIGNED David Keeler [:keeler] (use needinfo?) (dkeeler)
1061268 Wrong photo gets used in some BBC articles NEW
1074635 don’t rerender the page for every frame in a GuM tab video stream NEW
1076966 Use “immersive” fullscreen mode REOPENED
1084711 Graphic rendering problems on trunk, black boxes, nothing renderend, eventually crashes NEW Milan Sreckovic [:milan] (milan)
1089653 crash in java.lang.NullPointerException: at org.mozilla.search.SearchActivity.updateSettingsButtonVisibility(SearchActivity.java) NEW Mark Finkle (:mfinkle) (mark.finkle)
1090884 Back button doesn’t do anything NEW
1091461 Tapping anywhere under the ‘Private Browsing’ tip in the History panel will open the Custom menu NEW please NEEDINFO? :ally Allison Naaktgeboren (ally)
1091677 crash in @0x0 | mozilla::layers::ImageHost::GenEffect(mozilla::gfx::Filter const&) ASSIGNED Jonathan Watt [:jwatt] (jwatt)
1094214 fuzzy text NEW
1098227 Android crash in @0x0 | mozilla::layers::Layer::CalculateScissorRect NEW Nicolas Silva [:nical] (nical.bugzilla)
1107386 New tablet UI – Browser menu is clipped and unusable on the Kindle Fire ASSIGNED Michael Comella (:mcomella) (michael.l.comella)
1112232 Find in page search: It is not obvious that the case insensitivity button enables insensitivity NEW Robin Andersen [:tecgirl] (randersen)
1112939 Roku Tab mirroring falls behind NEW
1114096 Wrong tab got mirrored NEW Mark Finkle (:mfinkle) (mark.finkle)
1116856 dynamically resize tab mirror video stream based on window size NEW Brad Lassey [:blassey] (use needinfo?) (blassey.bugs)
1117130 URL bar border slightly covered by fading edge of title ASSIGNED Martyn Haigh (:mhaigh) (mhaigh)


19 Total;
19 Open (100%);
0 Resolved (0%);
0 Verified (0%);

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs. Make sure friends also get awarded a badge. New contributors are highlighted in bold.

  • Surabhi fixed bug 1116633, another instance of BufferedReader cleanup, and bug 1115542, adding license blocks.
  • Skandan fixed bug 1118977, extracting a magic constant in LocalBrowserDB.
  • (iOS) apbendi fixed bug 1109641 – Disable the back/forward buttons when there is nothing to do
  • (iOS) kylenoble fixed bug 1117847 – Hide the keyboard when navigating between tab bar button items
  • (iOS) aaronraimist fixed bug 1109641 – Use standard format for Mozilla Public License comments
  • (iOS) palewar fixed bug 1109653 – Long press on back or forward should present previous visits

Stand ups

Suggested format:

  • What did you do last week?
  • What are working on this week?
  • Anything blocking you?

Please keep your update to under 2 minutes!

James W. (snorp)

<Read Only>

  • Tried to review/understand jchen’s JNI bindings rewrite. Awesome stuff.
  • Working on a smattering of video bugs (inverted video, performance issues, removing powervr blacklist)

JChen

<Read Only> (on leave)

GCP

Past:

  • bug 1119852 Camera width/height constraints ignored on Windows
  • SafeBrowsing & Tracking Protection races
    • bug 1120145 Crash in nsUrlClassifierPrefixSet::Contains()
    • bug 1120499 Run ClassifyLocal on the worker thread
  • WebRTC “40” uplift, Android parts
  • WebRTC sandboxing: implemented first complete remoted parts

Present:

  • Test WebRTC sandboxing, watch explosions
  • Watch out for WebRTC uplift fallout

Randall Barker

<Read Only>

Last Week:

  • Continued to work on landing:
    • bug 1093934 Create a XPCOM library that can be used to support standalone WebRTC
    • bug 1097804 Create a library containing nsISocketTransportService and nsIDNS that can be used to support standalone WebRTC
    • bug 1101651 Enable WebRTC unit tests to be built using standalone WebRTC library

Next Week:

  • Same as last week.
  • Start investigating receiving audio in standalone WebRTC.

Eugen Sawin

Fixed

  • bug 1115377 – Fennec updater often doesn’t work
  • bug 1117095 – Update downloader should use a wifi lock

Working on

  • bug 792992 – Can’t override query URL for update service

Brian Nicholson

<Read Only>

WesJ

  • bug 1118532 – Write a history sqlite provider
  • bug 1116537 – Make the history panel work
  • Landed FMDB as a backend, replacing with a custom one now though

liuche

<Read Only>

  • All refreshed from PTO :D
  • Picking up onboarding, passwords again

Present:

Margaret

<Read Only>

Highlights:

Past:

Present:

mcomella

<Read Only>

Past
  • Back from PTO (재미있었다!)
Present
  • Catching up on new tablet
  • Bugmail D:
Future
  • JSLint
  • Browser toolbar cleanup
  • Edit screen changes

rnewman

<Read Only>

Highlights
  • BrowserDB is gone. Access via the profile instead. Thanks to Wes for the initial patch and for slogging through the reviews.
  • Fixed a bunch of oranges and miscellany.
  • Lots of Sync, FHR, etc. questions and reviews.
  • Pushing on reading list service.
  • All the reviews.
Fixed
Working on

nalexander

<Read Only>

Projects for this cycle:

  • Push migrate legacy Sync 1.1 devices across the finish line
  • Make FxA provide OAuth implicit grants for Fennec consumers, tracked by bug 1117829
    • Minimal progress
  • Implement Firefox Accounts for iOS
    • Tracked by bug iosfxa
    • Met with fxa-content-server team (ckarlof, stomlinson, vladikoff, zaach) to discuss jelly doughnut approach
    • dveditz raised security concerns of hosted content; working those in to my evaluation
  • Make sure |mach bootstrap| for mobile/android works
Past
Present

Martyn Haigh

Past:

Present:

  • Broken build :(

Stefan

<Read Only>

  • Full focus on Reader Mode – first iteration in PR
  • Working on setting up that Xcode Server (blocks on SSL and DNS things IT needs to do)
  • Misc UI fixes/tweaks

BLassey

Fixed
Working on

MFinkle

Fixed
Working on

Antlam

Robin

iOS

  • Sketches → Sketch for flow. Laying out all screens, menus, options.

Will add to my 105 process page (http://people.mozilla.org/~randersen/105/) after today’s meeting with UX.

  • Hoping to get to iPad this week.

Darrin

<Read Only>

iOS:

  • continuing to refine the macro view of iOS app (http://invis.io/2F1Z97APH) ← please give me feedback in #mobile or directly if you have any :)
  • starting to look at pieces of the UI in more detail
  • sanity check on v1 features and making sure we have a ‘home’ for everything before we go into high fidelity (as well as considering v2+ features so we aren’t rebuilding things unnecessarily)

Coordination:

  • lots of password manager and reading list meetings this week as well

QA

Feature Focus

  • 38 list for Nightly – will be tracking status on these items as of next weeks meetings.
  • Did a review yesterday on what’s merging – anything look wrong to you? Last minute items held back not shown here?

Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 99998
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 99998
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 99998
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 99998
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 99998
    • UK/London: +44 (0)207 855 3000, x92 Conf# 99998
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2015-01-14

Schedule & Progress onUpcoming Releases (Lawrence)

  • Firefox 35.0 shipped yesterday, updates enabled at 25%
  • Firefox 36 beta1 ships Thursday
  • Firefox 37 Aurora updates scheduled to be re-enabled on Friday
  • Note: 38 (currently Nightly) will be the next ESR.
  • Want all merge and release days included in your calendar? Add this Google calendar.

Firefox Desktop & Platform (Javaun/Chad/Martin)

38.1 started yesterday. Recap from last week on priorities

- Hello:

 - wrapping up Firefox 36/37 work, getting started on 38 (with a focus on sharing)

- Task Continuity:

 - finishing UX design work for Reading List/Synced Tabs
 - research work support those features
 - investigating sync back-end changes needed to support them

- Search:

 - continue to address important regressions from the Firefox 34 work
 - UX design/research for next steps in search UI improvements

- Password Management:

 - focus on telemetry to begin improving filling/saving reliability

- Sync Migration:

 - finishing the migration work needed to start migrating "old sync" users to "new sync" in Firefox 37

- Places:

 - continue the refactorings needed to avoid main-thread IO

- E10S:

 - continue supporting the e10s team in pushing through the e10s milestones

Also:
Privacy:
Some UI exploration for privacy and some work on research/telemetry experiments on Tracking Protection

Some EME bugs

Feedback Summary (Cheng/Tyler/Matt)

Desktop

Release going smoothly, nothing to report yet

Contributor Engagement

Mike Hoye announcing the revamp of a community-engagement onramp, to ship end of Q1


Planning Meeting Details

  • Wednesdays – 11:00am PT, 18:00 UTC
  • Mountain View Offices: Warp Core Conference Room
  • Toronto Offices: Finch Conference Room
  • irc.mozilla.org #planning for backchannel
  • (the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

Mozilla Add-ons BlogAdd-ons Update – Week of 2014/01/14

I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.

The Review Queues

  • Most nominations for full review are taking less than 9 weeks to review.
  • 34 nominations in the queue awaiting review.
  • Most updates are being reviewed within 6 weeks.
  • 18 updates in the queue awaiting review.
  • Most preliminary reviews are being reviewed within 6 weeks.
  • 24 preliminary review submissions in the queue awaiting review.

Thanks to our volunteer reviewers, most new submissions are being handled within a day or so (the measurements above are based on the state of the queue and not the actual waiting times). We still have a large backlog of complex add-ons that require admin review, but we’re making progress in decreasing it.

If you’re an add-on developer and would like to see add-ons reviewed faster, please consider joining us. Add-on reviewers get invited to Mozilla events and earn cool gear with their work. Visit our wiki page for more information.

Firefox 36 Compatibility

The Firefox 35 compatibility blog post is up. The automatic AMO validation will be run in the coming weeks.

As always, we recommend that you test your add-ons on Beta and Firefox Developer Edition (formerly known as Aurora) to make sure that they continue to work correctly. End users can install the Add-on Compatibility Reporter to identify and report any add-ons that aren’t working anymore.

Electrolysis

Electrolysis, also known as e10s, is the next major compatibility change coming to Firefox. In a nutshell, Firefox will run on multiple processes now, running each content tab in a different one. This should improve responsiveness and overall stability, but it also means many add-ons will need to be updated to support this.

We will be talking more about these changes in this blog in the near future. For now we recommend you start looking at the available documentation.

Air MozillaProduct Coordination Meeting

Product Coordination Meeting Weekly coordination meeting for Firefox Desktop & Android product planning between Marketing/PR, Engineering, Release Scheduling, and Support.

Mozilla ServicesHeka Log Parsing Perfomance

I’ve been experimenting with Heka throughput recently, and have discovered a few log parsing tips and tricks that I thought were worth sharing.

I ran tests on my Lenovo Thinkpad W530 laptop, which has four 2.8GHz cores, showing up as 8 cores to my Linux OS thanks to hyperthreading. From our ops team I got a couple of Nginx log files, each with over 6 million entries. I made three copies of each log file, and put each copy in a separate directory, emulating the common use case of having to parse output from multiple hosts and/or domains. I configured Heka with a single LogstreamerInput set up to concurrently load all six files, using our Nginx access log decoder, which ultimately uses Lua’s LPEG engine to handle the actual parsing. Not a scientifically rigorous test, but I’m just trying to get some ballpark throughput numbers.

For my first run I set Go’s maxprocs value to 1, which makes only one core available for Heka to use. With that setting, I was processing in the neighborhood of 31K events per second (eps); so far so good. Then I cranked maxprocs up to 4. I ran the tests again and my throughput jumped all the way up to about 33K eps. Wait… what!?! I know that sometimes lock contention and other issues can cause poor performance across multiple cores, but we’re processing six distinct streams here; this should parallelize fairly well. I was seeing almost no improvement. What the heck was going on?

Nothing to do but roll up my sleeves and dig in. I busted out the Go profiling tools, but nothing obvious jumped out at me. So I took a look at the source code, and was temporarily stunned by the force of my palm slamming into my forehead at high velocity. While the LogstreamerInput was correctly spinning up a separate goroutine for each unique log stream, it was only spinning up a single decoder to be shared by all of them. That meant that no matter how many cores were available to Heka as a whole, all of the parsing was happening in a single goroutine, which would only be running on a single core.

Luckily this was an easy fix. In about 30 minutes, I had a working Heka that would spin up a separate decoder instance for each log stream; these changes have since landed in the v0.8.3 release. Running this with maxprocs of 1 ran slightly slower than before, about 30K eps. This wasn’t surprising, since now the single core was context switching through six different decoder goroutines whereas before there was just one. But cranking maxprocs up to 4 and trying again gave me around 85K eps. Now we’re talking! Not linear improvement, but still a much better number. I got my best results with maxprocs set to 7, where I was consistently processing approximately 118K log lines per second.

I was actually able to do even better than that. In prior experimentation with log parsing performance, we’ve realized that parsing timestamps is a very processor intensive part of the job. We can lighten this load by configuring our Nginx servers to log timestamps using `$msec` instead of `$time_local` or `$time_iso8601` in the `log_format` setting. This means our log files contain Unix timestamps (seconds-since-epoch format) rather than more complicated date strings. The difference is significant. When I tested versions of the log files using the `$msec` timestamp format, my single core throughput jumped to around 36K eps. Four cores gave me 105K eps, and using 7 cores had me consistently parsing about 143K lines per second. Not too shabby!

It’s worth noting that there is still a lot of room for improvement. For instance, due to details of the runtime layers, pushing text from Go through C and into Lua (and then back again) involves more memory copies than it probably should. The Lua sandbox that Heka uses is implemented as a separate project, in pure C. It would be possible for us to get much higher parsing throughput by writing a thinner wrapper around the sandbox using a language that doesn’t require copies to talk to C, such as C++, Rust, or C itself. This removes us from the rest of the Heka pipeline, of course, but since a considerable amount of the data processing that we do in Heka is also happening in a sandbox, we’d still be able to do a lot of crunching, we’d just have to set up a bespoke pipeline with Lua code instead of using Heka’s routing infrastructure.

Even so, the full Heka stack is fast enough for most use cases, and is ready to be used today. I hope you’ll try it out, and come find us in the #heka channel on irc.mozilla.org, or on the Heka mailing list to ask questions and/or tell us about your experience.

Meeting NotesMozilla Platform: 2015-01-13

Need To Know

(Release and system issues that may impact engineering this week.)

Notices/Schedule (lmandel)

Next Merge: February 23, 2015 Next Release: February 24, 2015
Trains
Central: 38 Aurora: 37 Beta: 36 Release: 35
  • Today is release day! Congratulations on releasing Firefox 35 and Firefox ESR 31.4!
  • 36 Beta1 ships Thursday
    • MSE is enabled in beta1. Please test YouTube playback on Windows and file bugs.
  • 37 Aurora updates are scheduled to be re-enabled on Friday
  • 38 Nightly will be the next ESR. Get your refactorings or other major changes in while 38 is on m-c.

A note on branching:

  • FXOS v2.2 update : Please note that has diverged from mainline gecko and is on its own b2g37 branch. mozilla-aurora (gecko 37) will continuously be merged to mozilla-b2g37_v2_2 . So, if you have a gecko bug that you are fixing on aurora and impacts b2g as well, you do not have to worry about requesting approval twice as the sheriff’s will auto-merge it for you.
  • Want all merge and release days included in your calendar? Add this Google calendar.

Build Changes (gps)

(Build changes of which engineers should be aware.)

RelEng (catlee)

(Repo, test, and other information for engineers from the release engineering team.)

Upcoming Outages/Upgrades

(System outages/upgrades and tree closures that impact engineering.)

  • The next Tree Closing Window (TCW) is scheduled for Saturday, January 24. The list of work is not yet finalized, more detail on time impact next week.

Quality Programs

(An opportunity to hear about status with the various quality programs that do not have a formal team structure.)

MemShrink (njn)

<Read Only>

Stability (kairo)

<Read Only>

  • Waiting for data on new versions, a lot of 36 beta focus will be on MSE crashes.

Team Stand-ups

(In <2 mins, what did your team accomplish last week, on what is your team working on this week, and on what, if anything, is your team blocked? No questions during the stand-ups. All questions should be asked during the roundtable.)

Desktop Platform (bsmedberg)

  • We will be disabling Flash protected mode for FF36beta1 (Desktop) and evaluating stability metrics and looking for regressions. We have not yet made a decision about whether this will ship to release.
    • There appears to be a bug where our hook is ineffective on Windows 8.1.

Electrolysis (e10s) (blassey)

GFX (milan)

  • Random:
    • Looking at some MSE related issues.
    • Chasing a few intermittent problems.
  • Coming soon:
    • APZ 2.2 improvements (ok)
    • Silk on 2.2 (exciting)
    • WebGL2 (interesting)
  • Coming later:
    • Desktop APZ (interesting)

Layout (jet/dbaron)

<Read Only>

  • bug 1045929 JPEG downscale-during-decode landed and bounced. Will re-land and uplift this week as this feature is important for B2G 2.2.
  • bug 1055658 Major components of CSS Ruby are landing
  • bug 1115691 New Perf Metrics API to count layout frames constructed and reflowed

Media (mreavy)

1. What has your team done since last week that might impact others?

  • Hello/Loop Rooms going to release this week
  • MSE is enabled in Beta1; Please test Youtube without Flash on Windows (Vista+)

2. What will your team do this week that might impact others?

  • Landing bug 879717 (fix mediastream->video_element->canvas path) – thanks to Andreas Pehrson of Telenor!
    • Landed last night and bounced due to unrelated bug in EME it triggered
  • Initial Multistream support in webrtc
    • Becomes more useful later once we get renegotiation & bundle
  • Landing of WebRTC.org stable branch 40 (also being used by Chrome 40) – bug 1109428.
    • Green on all platforms other than OpenH264 not working yet (packetization changes).

Necko (dougt/jduell)

  • The Network Predictor (aka “Seer”) is about to land again
    • This time it’s written over the HTTP cache instead of SQLite

Performance (vladan)

<Read Only>

  • Help us test bug 998863: Asynchronous initialization of plugins
    • It’s currently preffed *OFF* by default, please help us test it: set dom.ipc.plugins.asyncInit to true
    • There are stability problems with e10s at the moment, Aaron is working on fixing these issues
    • Mark any bug reports as blockers of bug 1116806

Roundtable

(Comments and questions that arise during the course of the meeting or otherwise do not have a section.)

Links

Mailing List Threads

(Threads that are likely to be of interest to engineering from various mailing lists.)

Good Reads

(Links to blog posts, books, videos, etc. that you think will be of interest to others.)

irc #planning Log From This Meeting


Engineering Meeting Details

  • Tuesday 2015-01-1311:00 am Pacific Standard Time
  • Calendar links: iCal ics or Atom/XML feed
  • Engineering Vidyo Room / Air Mozilla / MTV Alien Nation / TOR Finch / SFO Warfield / PDX Hair of the Dog
  • Join irc.mozilla.org #planning for back channel
  • Dial-in: conference# 98411
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
    • US/California/Mountain View: +1 650 903 0800, x92 Conf# 98411
    • US/California/San Francisco: +1 415 762 5700, x92 Conf# 98411
    • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 98411
    • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 98411
    • UK/London: +44 (0)207 855 3000, x92 Conf# 98411
    • FR/Paris: +33 1 44 79 34 80, x92 Conf# 98411

Mozilla Add-ons BlogAdd-on Compatibility for Firefox 36

Firefox 36 will be released on February 24th. Here’s the list of changes that went into this version that can affect add-on compatibility. There is more information available in Firefox 36 for Developers, so you should also give it a look.

General

XPCOM

 Wrappers

There are a number of wrappers that are applied whenever chrome JS objects interact with content JS objects. They are meant to protect privileged code from malicious or otherwise misbehaving content code. The following bugs removed some features in wrappers that could lead to unexpected problems in your chrome/content code. However, you should keep in mind that Multiprocess Firefox is coming, and that means you should be changing your code anyway (some wrappers are still involved, but they should be rare).

Please let me know in the comments if there’s anything missing or incorrect on these lists. If your add-on breaks on Firefox 36, I’d like to know.

The automatic compatibility validation and upgrade for add-ons on AMO will happen within a week or two, so keep an eye on your email if you have an add-on listed on our site with its compatibility set to Firefox 35.

Air MozillaEngineering Meeting

Engineering Meeting The weekly Mozilla engineering meeting.

The Mozilla BlogFirefox Enables You to Experience and Share More on the Web

Firefox puts you in control of your online life and puts everything you need in a personal and customized Web experience. Now, we’re making it easier to experience and share everything you enjoy on the Web with video calling, social sharing and Web apps integrated directly into Firefox.

Firefox integrates three new features directly in the Firefox toolbar or in Customize Mode: Firefox Hello (the first global communications system built directly into a browser), social integration to easily share content with your friends and family through your favorite social sites in one place, and Firefox Marketplace Beta to test Web apps.

Firefox Hello – A simpler way to communicate

Recently, we introduced Firefox Hello, the first global communications system built directly into a browser to make it easier and more privacy friendly for you to have voice and video calls online.

Firefox Hello
Conversation window in Firefox Hello

Firefox Hello is free to use, doesn’t require you to sign up for an account and allows Firefox users to connect to anyone, anywhere in the world so long as they have a WebRTC-enabled browser such as Firefox, Chrome or Opera. Before Firefox Hello, making a video call meant giving up your email address and possibly more personal information as well as downloading software before you could start the conversation.

Now we’re making it even easier to say ‘hello’ by eliminating some of the call steps and allowing you to save and name your favorite conversations, so you can drop into them as soon as you click a link. Find out more about Firefox Hello here.

Firefox Share – Share the Web through all your favorite social networks

We’re integrating all your favorite social networks in Firefox and giving you a single site to activate your social networks and make it even easier to share Web content without having to leave the website you’re visiting.

Share window in Firefox

Share window in Firefox

To add “Share” functionality in Firefox: visit the Share Activation page and click on the Activate Now link for any social network you wish. Some of the social sites that you can connect with include Facebook, Twitter, Tumblr, LinkedIn and Google+.

Firefox Marketplace Beta – Help Test Apps

Firefox Marketplace Beta is now open for testing on the desktop on Windows, Mac and Linux. Firefox Marketplace Beta is built on open Web technologies to give developers and users the flexibility of creating and consuming consistent and connected app experiences across platforms. Visit our support page for details on how to use Firefox Marketplace Beta.

For More Information:

  • Firefox for Windows, Mac and Linux release notes
  • Download Firefox
  • Firefox for Android release notes
  • Download Firefox for Android
  • The Mozilla BlogFirefox Hello Makes Connecting By Video As Simple As In Person

    Conversations should begin by video as simply as they do in person. The fact is they don’t. You have to give up your email address, set up an account and share personal information as well as download software before starting to talk.

    Recently, we introduced Firefox Hello, the first global communications system built directly into a browser to help make things easier.

    Today we’re simplifying the call process by eliminating some steps. After locating the Hello icon in the menu bar or customization panel, simply click the ‘Start a conversation’ button to create your first conversation. Now when you start a conversation, a window opens showing a self-view until the person you have invited clicks on the link and joins you. While you’re waiting for them to join, you can navigate away from this call window to a website. Hello will then notify you when another party joins the room. The Hello icon will turn blue and you’ll get an audio alert.


    Demonstration of Firefox Hello

    Each conversation uses a unique URL for two people to communicate more easily over video or audio. You can create multiple conversations and name them for different occasions, making it easier to go back to the people you speak to regularly without having to create a new link each time. This can all be done without the need for setting up an account or giving up any of your personal information. You might label one conversation ‘121’ for your weekly check-in with a co-worker and another ‘Family time’ for your regular family catch-up. Your saved conversations will always be there when you need them.
    Firefox Hello
    Conversation window in Firefox Hello

    For those of you who want to contact someone directly, you just need to make sure both parties have Firefox Accounts. If your contacts have a Firefox Account and are online, then you can call these contacts directly from Firefox. You can sign into your Firefox Account on every computer you use, so you can be reached at home or at work. If you have a Google account, you can easily import your contacts to your Hello address book. Simply select ‘Import Contacts’ from the address book and then sign into your Google account to give permission.

    Experiencing the Web Together

    We’ve been developing Firefox Hello with our long-term partner Telefónica, and leveraging TokBox technology to help power the service, but this is just the beginning. As we look to expand Firefox Hello into a comprehensive tool for communicating over the Web, we’ll be testing new features like screen sharing and online collaboration so people can be more productive and get the most out of their video calls. This could include things like planning a vacation, shopping online or playing a game while on a video call together. The possibilities are endless.

    So what are you waiting for? Why not say ‘hello’ to someone today! Here’s how to get started.
    We hope you enjoy using Hello and look forward to sharing more updates with you soon.

    Meeting NotesMozilla Project: 2015-01-12

    All-hands Status Meeting Agenda

    Items in this section will be shared during the live all-hand status meeting.

    Friends of Mozilla

    • Big thanks to Niccolò Cantù, Marketplace contributor of the month for December. Niccolò began contributing in March 2014, and has since published seven apps on Marketplace, written a chapter for the FirefoxOS Quick Guide in Italian, and reported many bugs.
    • Rachel Hathaway landed her first patch on Marketplace after braving a mountain of feedback (68 review comments). Thanks Rachel!

    Upcoming Events

    Monday, 12 January
    • Mozilla Contributor Meetup
      • this event will be in #contributors on IRC
      • An event were we’ll discuss about contributing to Mozilla. The intention is to make it bi-monthly
      • From 14:00 PST to 15:00 PST
      • from 10:00 PM to 11:00 PM Uk time
    Tuesday, 13 January
    Wednesday, 14 January
    • Homebrew Website Club Meetup
      • San Francisco (@MozSF 1st floor), Chicago, and Portland.
      • 17:30-18:30 Writing Hour
      • 18:30-19:30 IndieWeb meetup & hack night

        Be independent with your web browser and your web site.

        Create or update your personal web site — wherever you host it, shared, VPS, or at home; static, dynamic, WordPress, or other software.

        Join a community with like-minded interests. Bring friends that want a personal site!

        Any questions? See the wiki page for details
        or join IRC: http://indiewebcamp.com/irc/today?beta#bottom

    Thursday, 15 January
    • SuMo Day *
      • A day for all contributors to help on SuMo to respond to questions **
    Friday, 16 January
    • Browser-Based Virtual Reality in HTML5 from 5pm-9pm at Google, San Francisco
      • Josh Carpenter speaking
      • It’s VR time! Let’s kick off 2015 with a super exciting event featuring 5 expert talks about browser-based virtual reality at SFHTML5. After that, head over to the VR world tour kick-off event at The Metreon!
    • Webdev Beer and Tell at 2PM Pacific in the Webdev Vidyo room (and streaming on AirMo)
      • Open to the public!
      • Monthly get-together where webdevs across the community show off their side projects.
    Saturday, 17 January
    • Mozilla Hispano Work Day in Madrid
      • Mozilla Hispano contributors living in Spain will meet in Madrid for a get together, discuss and advance on the plans for the community in Spain
    Next Week

    Project Status Updates (voice updates)

    Firefox

    Speaker Location: toronto (johnath)

    Firefox OS

    Speaker Location: Rick Fant

    CTO Update

    Speaker Location: San Francisco (mbx)

    Shumway Update: Flash video continues to cause problems in Firefox. Over the next few weeks we’ll start enabling Shumway in the Beta channel for some popular video players.

    Recorded Demo: http://areweflashyet.com/tmp/oop/shumway.mp4

    Live Demo:

    1. https://www.facebook.com/video.php?v=141192919273962&set=vb.22893372268
    2. http://jwsolution.net/index.php/demo

    Please help us test and provide feedback at https://github.com/mozilla/shumway

    Webmaker

    Speaker: Andrew Sliwinski
    Location: PDX

    http://mzl.la/changelog

    • Major updates launched last week to Webmaker.org focused on improving the visitor to user registration conversion rate.
      • Splash
      • Navigation
      • Login
    • Next up:
      • On-boarding – Get new users making & learning right away
      • Marketing – Privacy day campaign
      • Mobile – Field testing in India
    Web Compatibility

    Speaker Location: Vidyo (miketaylr)

    RSVP and Call for Speakers form for Web Compatibility Summit now available. If talking about making broken things less broken is your thing, come join us on February 17th in Mountain View.

    Speakers

    Presenter Title Topic Location Share? Media More Details
    Who Are You? What Do You Do? What are you going to talk about? Where are you presenting from? (Moz Space, your house, space) Will you be sharing your screen? (yes/no, other info) Links to slides or images you want displayed on screen Link to where audience can find out more information
    Peter B, Richard M Air Mozilla Help out edit past Air Mozilla events MV Moz Office Live demo on Potch’s screen https://air.mozilla.org/unpicked-pictures/ https://air.mozilla.org/contributors

    Roundtable

    Do you have a question about a Mozilla Project or initiative? Let us know by Friday- we’ll do our best to get you an answer.

    Please note that we may not always be able to get to every item on this list, but we will try!

    Who are you? Area of question Question
    What’s your name? What do you work on? Is your question about policy, a product, a Foundation initiative, etc. What would you like to know?
    David Weir (satdav) contributor Service Desk or IRC Hello can you update us contributors on the IRCCLoud beta what Mozilla is doing and how we can get involved to help with this?

    Welcome!

    Let’s say hello to some new Mozillians! If you are not able to join the meeting live, you can add a link to a short video introducing yourself.

    Introducing New Volunteers

    New Volunteer(s) Introduced by Speaker location New Volunteer location Will be working on
    Who is the new volunteer(s)? Who will be introducing that person? Where is the introducer? Where is the new person based? What will the new person be doing?

    Introducing New Hires

    New Hire Introduced by Speaker location New Hire location Will be working on
    Michelle Liu Bellu Su Recorded Taipei Office Administrative Assistant
    Tommy Kuo ShihChiang Chien Recorded Taipei Office Software Engineer
    Will Wang Ben Tian Recorded Taipei Office Software Engineer
    Alexandra Costello Mary Ellen Muckerman San Francisco San Francisco
    Rachel Berenbaum Michelle Marovich Mountain View San Francisco
    Bryan Bell Bill Maggs San Francisco US Remote
    Stuart Philp Bill Maggs San Francisco Toronto
    Ashish Vijayaram Linda Ypulong San Francisco San Francisco Mozilla Operations Center (MOC)

    <meta>

    Notes and non-voice status updates that aren’t part of the live meeting go here.

    Status Updates By Team (*non-voice* updates)

    Automation & Tools
    bugzilla.mozilla.org

    Notable changes to bugzilla.mozilla.org during the last week:

    • bug 1050232 The first of a batch of changes improving the guided bug entry form landed. This improves the bug filing experience for the majority of our users.

    All changes.

    Engagement

    • Dial-in: conference# 8600
      • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600
      • US/California/Mountain View: +1 650 903 0800, x92 Conf# 8600
      • US/California/San Francisco: +1 415 762 5700, x92 Conf# 8600
      • US/Oregon/Portland: +1 971 544 8000, x92 Conf# 8600
      • CA/British Columbia/Vancouver: +1 778 785 1540, x92 Conf# 8600
      • CA/Ontario/Toronto: +1 416 848 3114, x92 Conf# 8600
      • UK/London: +44 (0)207 855 3000, x92 Conf# 8600
      • FR/Paris: +33 1 44 79 34 80, x92 Conf# 8600

    Air MozillaMozilla Weekly Project Meeting

    Mozilla Weekly Project Meeting The Monday Project Meeting

    The Mozilla BlogAnnouncing the Mozilla Science Lab Fellowship Program

    With generous support from the Leona M. and Harry B. Helmsley Charitable Trust, we are excited to announce the Mozilla Science Lab’s first Open Science fellowship program. The grant is one of the first  investments by the Trust’s new funding program dedicated to  collaboration, reproducibility, and infrastructure in biomedical  sciences.

    Our two-year, $1.7 million dollar grant builds on our existing educational work supporting skills training and capacity building for the biomedical and physical sciences. It features a fellowship program for early-career researchers focused on promoting more efficient, collaborative research and building leadership within  the community. The ten-month fellowships will include computational and data training and mentorship needed to serve as open science trainers. In addition to training, fellows will  develop new materials, tools, and projects to further science on the  web.

    The grant also supports curriculum design, a data training program and train-the-trainers activities for researchers, extending the Lab’s existing work to provide learning pathways for researchers around open practice.

    The Mozilla Science Lab, an initiative of the  Mozilla Foundation, works with partners around the world to bring principles and values of the open web to advance scientific discovery. Launched in 2013, the Lab serves as a hub for the research community, providing open science skills training, mentorship and community support to build and scale a community of practitioners working  in the open.

    The first call for fellows goes live this spring, with an initial focus on the biomedical and physical/natural sciences. Join our mailing list for more information or visit us at mozillascience.org. You can also read more about today’s announcement on the Science Lab’s blog.