Meeting NotesMobile: 2014-10-01

Schedule

  • Next merge: 2014-10-13

Topics for This Week

  • Tablet refresh update from Anthony and Yuan [10mins]

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.

  • Vikneshwar fixed bug 1053994 – Paste & Go attempts a Google search instead of recognizing a bookmark keyword

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>

  • Actually made progress on MediaCodec patch[es].
    • Output going through SurfaceTexture, which avoids all of the YUV conversion insanity. This should be highly reliable and performant once finished up.
    • Now working on stability fixes, learned a lot about how to use MediaCodec from Grafika, a collection of samples made available by Google (or a googler): https://github.com/google/grafika/
  • Landed the Android support for the network change notifications. We should do a lot better now when you switch wifi -> 3g, etc.

Alan K. (ack)

This week

  • WebRTC refactoring to break DOM deps
  • Finished with feedback for cloudsync aurora uplift, should land soon

JChen

Fixed
Working on
  • Working on an add-on to make logcat/JS errors more visible

GCP

<Read Only>

Fixed
Working on
  • WebRTC standboxing investigation

Randall Barker

<Read Only>

Last Week:

  • Investigate new method for implementing standalone WebRTC.

Next Week(s):

  • Investigate new method for implementing standalone WebRTC.
  • Investigate sending H.264 instead of VP8 video to standalone WebRTC.

Eugen Sawin

Last week

  • Landed bug 1034114 – WebApp startup slowed significantly by debug server
  • Landed bug 1072639 – Notification event handlers not triggered for web apps webapp notification context
  • Fixed & landed bug 1051654 – APKs for previous versions of Nightly and Aurora stick around in Downloads
  • Fixed & landed bug 896735 – App update fails if Download folder doesn’t exist
  • Janus Proxy (https://wiki.mozilla.org/Mobile/Janus)
    • Applied workaround for image compression issue (low quality images may increase in size temporarily)

Next week

  • Land bug 1071831 – HTML5 video playback is not paused in the browser after opening in external player
  • Fix bug 1022669 – Display does not turn off while playing audio
  • Look into bug 942736 – Page-position when going back a page is not always remembered when conducting a scroll on prior page and then hitting back
  • Janus Proxy fixes and improvements

Brian Nicholson

<Read Only>

WesJ

<Read Only>

  • bug 1074189 – crash in java.lang.NullPointerException: at org.mozilla.gecko.GeckoApplication.onActivityResume$642b2292(GeckoApplication.java)
  • bug 1054035 – Block about urls in guest mode
  • bug 1071116 – crash in java.lang.IllegalArgumentException: invalid value for param: totalBytes at android.app.DownloadManager.addCompletedDownload(DownloadManager.java)
  • bug 1070797 – crash in java.lang.IllegalArgumentException: mimeType cant be null at android.app.DownloadManager.validateArgumentIsNonEmpty(DownloadManager.java)
  • bug 1072332 – crash in java.lang.NullPointerException: at org.mozilla.gecko.db.PerProfileDatabases.getDatabaseHelperForProfile(PerProfileDatabases.java)
  • bug 1071091 – System download manager needs a build time pref
  • bug 1072376 – Regression: Open/Close animation of the tabs tray and menu is sluggish
  • bug 1063541 crash in java.lang.IllegalArgumentException: Wifi:Enable was not registered at org.mozilla.gecko.EventDispatcher.unregisterListener(EventDispatcher.java)
  • bug 1071076 – Search button on keyboard doesn’t work with the search widget in error pages

LucasR

<Read Only>

Last week

Next week

  • Fix fallout from status bar tinting or backout feature
  • Wrap-up tab strip bits for the current engineering milestone

liuche

<Read Only>

Margaret

<Read Only>

Highlights:

Past:

Present:

mcomella

<Read Only>

Past
  • Browser toolbar refresh
    • bug 1058909 – Implement new tablet toolbar display mode
    • bug 1071878 – Sites without favicons should show an empty rectangle rather than a globe
    • bug 1071226 – Refine private browsing new tablet browser toolbar
    • bug 1073449 – Regression: the default favicon icon looks too big on phones
    • bug 1072466 – Update new tablet assets
Present
  • Browser toolbar refresh
    • bug 1071267 – Revise door hanger behavior in new tablet toolbar
    • bug 1019127 – Remove updateChildrenEnabledStateForEditing
    • bug 960746 – Back/forward button state can get out of sync on tablets
    • bug 1070087 – Discuss new tablet menu bar button size
    • bug 1072464 – Discuss new tablet forward button size
    • bug 1072469 – Discuss new tablet browser toolbar height
    • bug 1075531 – Robocop failures in larch due to changes in toolbar
  • bug 1020534 – Tablet toolbar icons hard to read on dark lightweight themes
Future
  • Herding bug 941155 (fix talos on mobile to have pageloader tests working in regular mode and nochrome mode) along
  • bug 939350 – Create Python linter wrapper
  • bug 983437 – Delay FHR pruning until the screen is off
  • bug 989441 – Centralized documentation for writing tests
  • bug 1058902 – Implement new tablet browser toolbar editing mode

rnewman

<Read Only>

  • Project Vancouver. Writeup to follow this week, along with more work.
  • ~1 day PTO.
  • FxA metrics investigation for board stuff.
  • Lots of Sync and FHR randomization — reviews (e.g., bug 675397, questions (e.g., pagination), Dispensing Hard-won Experience®.
  • Mobile reviews. Backlog built up last week, which I’m burning through now.
  • bug 1045053 is awaiting bnicholson review.

nalexander

<Read Only>

  • Code: Remote Tabs home panel UI polish tickets landing this week. Split pane tablet view still outstanding.
  • Code: Re-landing bug 1065306 because Python and Unicode is a match made in heaven.
  • Testing: working on first pass at test runner for instrumentation tests in automation (meta bug is bug 1064004).
  • IDEs: meeting with mhaigh to discuss Android best practices and Android Studio integration tomorrow morning.
Past
Present

Martyn Haigh

Done

Doing

To Do

BLassey

Fixed
Working on

Antlam

  • Past
    • Tablet V1 wrap up
    • Firefox Search V1 wrap up
    • Toolbar improvements V1 wrap up
    • bug 1071730: Working on ideas to improve search on Fennec
    • General UI clean up bugs
  • Upcoming
    • bug 1075219: About: pages UI clean up
    • bug 1058663: Toolbar improvements cont’d!
    • PTO (but will remain addicted to emails), back on the 15th.

Yuan

  • Worked on search/edit mode on tablet. Get to v1 and v2 scope this week.
  • Synced up with FxOS UX Taiwan about copy + paste interactions
  • Continue to follow up with the UX for search engine update
  • Discussions about lightweight onboarding. Get to a few concepts for full “Get started” this week.

Robin

  • Project 105 concepts

WebRT

  • Myk still distracted by another project
  • making progress on hiring for open position
  • needinfo Myk for urgent issues

QA

Feature Focus

[Roadmap]


Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2014-10-01

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

  • 33 beta 9 desktop gtb tomorrow (last desktop beta)
  • 33 beta 10 mobile gtb Monday (last mobile beta)
  • 33 release candidates build Mon/Tue next week
  • Upcoming Aurora uplifts
    • Loop changes
    • OSX Gatekeeping v2 signature changes landing on Nightly this week. Still targeting 34 for this change (uplift coming shortly)
    • CloudSync uplift landing this week (bug 993584)

Firefox Desktop & Platform (Javaun/Chad/Martin)

Summary of Work In Progress
  • You can see the status of the current iteration (35.3) in progress here
Summary of Recent Landings
  • Team landed 80 bugs over the last week, to complete the 35.2 iteration.
  • Details of landings from the past week can be seen here
Priorities for the upcoming iteration
  • e10s on Nightly
  • Loop:
    • finalize accounts/contacts work
    • UX: design spike looking into “collaboration” use cases
  • “Panic button”: better-exposed “Clear Recent History” functionality
  • “Reset button on the web”: a mechanism to prompt users to reset Firefox when they try to download Firefox when already running the latest version
  • OS X Yosemite themeing work
  • New tab page performance investigations
  • Places performance work (main thread IO removal)
  • Translation trial followup

Firefox Mobile (Mark/Brad/Jenn)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Uplifts from the past week
Beta (33)
  • crash in mozilla::gfx::AlphaBoxBlur::Blur(unsigned char*) ( Bug 1028802 )
  • crash in mozilla::gfx::SourceSurfaceAlignedRawData::InitWithStride(mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gfx::SurfaceFormat, int, bool) ( Bug 1067018 )
  • crash in android.content.res.Resources$NotFoundException: Resource is not a Drawable (color or path): TypedValue{t=0x1/d=$ a=3 r=$} at android.content.res.Resources.loadDrawable(Resources.java) ( Bug 1067429 )
  • [roku] add a ‘beta’ label to the Roku channel until client code hits ‘release’ ( Bug 1068573 )
Aurora (34)
  • Add telemetry for Settings usage ( Bug 996753 )
  • Visible seams on the page (maybe at tile borders?) ( Bug 1009306 )
  • Disable downloads and extension installs in guest mode ( Bug 1046941 )
  • crash in webrtc::ViEInputManager::NumberOfCaptureDevices() ( Bug 1063547 )
Landings from the past week
Nightly (35)
  • Send NS_NETWORK_LINK_DATA_CHANGED events on Android ( Bug 1024614 )
  • WebApp startup slowed significantly by debug server ( Bug 1034114 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange(PinSiteDialog.java) ( Bug 1041448 )
  • APKs for previous versions of Nightly and Aurora stick around in Downloads ( Bug 1051654 )
  • Performing searches with Wikipedia search engine immediately launches Fennec ( Bug 1063193 )
  • crash in java.lang.IllegalArgumentException: Wifi:Enable was not registered at org.mozilla.gecko.EventDispatcher.unregisterListener(EventDispatcher.java) ( Bug 1063541 )
  • The URL displayed under tab titles in the Synced Tabs panel disappears for a while after choosing “Open in New Tab”/”Open in Private Tab” ( Bug 1064162 )
  • Synced Tabs panel shouldn’t be present in Guest Mode ( Bug 1064177 )
  • Firefox: User doesn’t go back to the channel after watching video till the end ( Bug 1068633 )
  • Android crash in mozilla::image::RasterImage::DecodeSomeData ( Bug 1069369 )
  • Selecting “No video” and “No audio” options from the permission prompt still shows the content of the device camera and the audio active ( Bug 1070989 )
  • System download manager needs a build time pref ( Bug 1071091 )
  • Form autocomplete dialog can take up the entire screen and make it really hard to use fennec ( Bug 1071738 )
  • Tapping sometimes triggers two clicks ( Bug 1071758 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.db.PerProfileDatabases.getDatabaseHelperForProfile(PerProfileDatabases.java) ( Bug 1072332 )
  • Regression: Open/Close animation of the tabs tray and menu is sluggish ( Bug 1072376 )
  • Issues with hidden/unhidden devices on Synced Tabs ( Bug 1072954 )

Feedback Summary (Cheng/Tyler/Matt)

Desktop

  • OMTC removal caused a spike in “blackouts” but now that it’s back, it seems to be going down.

Market Insights from the Market Strategy Team (Kev)

Read-only notes this week. Apologies, folks. – kev

Notes


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-on Compatibility for Firefox 33

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

General

XPCOM

New!

  • Add a field to install.rdf for add-ons that are compatible with electrolysis. The multiprocessCompatible flag was added to install.rdf so that you can declare that your add-on works with the new Electrolysis (e10s) multiprocess mode without any compatibility shims. So, even if you activate e10s on Nightly builds, you can’t be sure that your add-on works well with e10s until you run it with that flag set to true. The compatibility shims are temporary and bad for performance, so please make sure to test your add-on and set that flag as soon as possible! You can read more about e10s compatibility here. Note that, while the flag was introduced in Firefox 33, e10s is still being worked on and disabled by default, and we’re not sure yet when it will make it to release. We will keep you up to date on this blog.

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

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

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

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 7 weeks to review.
  • 124 nominations in the queue awaiting review.
  • Most updates are being reviewed within 6 weeks.
  • 88 updates in the queue awaiting review.
  • Most preliminary reviews are being reviewed within 6 weeks.
  • 147 preliminary review submissions in the queue awaiting review.

The Add-ons Team met last week to discuss various issues related to the add-ons world, including the time it takes to perform a review and what we can do to improve it. I’ll be posting a summary about everything we discussed shortly.

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 32 Compatibility

The Firefox 32 compatibility blog post is up. The automatic compatibility validation was run shortly thereafter.

Firefox 33 Compatibility

The Firefox 33 compatibility blog post is coming up, probably tomorrow. Expect the automatic compatibility validation to be run sometime next week.

As always, we recommend that you test your add-ons on Beta and 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. We will also begin contacting developers about add-ons malfunctioning with e10s very soon. 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.

about:communityGrow Mozilla discussion this Thursday

If you’re interested in helping new people get involved with Mozilla, join us Thursday for an open community building forum.

hacks.mozilla.orgThe Missing SDK For Hybrid App Development

Hybrid vs. native: The debate has gone on, and will go on, for ages. Each form of app development has its pros and cons, and an examination of the key differences between the two methods reveals that a flat correlation is like comparing apples to oranges. Many hybrid app developers understand that they’re not starting on a level playing field with native developers, but it’s important for them to understand exactly how that field fails to be level. We should analyze the differences at the app development framework level, instead of simply comparing hybrid to native.

Native App Development

Native software development kits (SDKs) come prepackaged with the required tools to compile and sign apps–all that boring stuff that “just works.” Their canned templates and the common code they provide determines “how” an app works, which are hugely beneficial features hiding in plain sight.

For example, Apple’s own development environment, Xcode, is a suite of tools that make it easier to develop software for Apple platforms. As soon as you launch Xcode, it provides a list of templates for a new project. Let’s create an iOS tabbed application and see just how many tools native app developers have available to them from the start.

After plugging in a few settings, I quickly have a working tabbed app that can be run within a minute of Xcode’s launch. Awesome! The easy part is done, and now it’s time to sport the hoodie and headphones and focus on my goal of creating a best-selling iOS app.

Let’s drill into this a little further and take a look at what Xcode built for me, without me even having to give it a second thought. The app fills 100% of the device’s display; the tabs are aligned to the base with a gray background; one tab is highlighted blue, the other one gray, with icons on top of the tab’s title. Event listeners are added to the tab buttons, and when I click the second tab, it then turns blue, and the other one turns gray, along with switching out the content for the second view.

After a little more development, my app will have a separate navigation stack for each tab; the back button will show when needed; the title of each view will switch out in the header; and smooth transitions will happen as I navigate between different views. Fonts, colors, gradients, and styles will all follow what an app should look like on that platform. By expanding folders in Xcode’s project navigator, I notice the ridiculous amount of files that were placed there for me. I have no clue what they do and honestly don’t really care, but they’re actually extremely important: They’re the files that made the development of my app so seamless.

Hybrid App Development

Honestly, though, I’m a web developer. My organization isn’t filled with Objective-C and Java developers ready to build multiple apps with the ultimate goal of just trying to be the same app (but built entirely differently, from the ground up). I have existing HTML/CSS/JS skills, and I want my app to hit not only Apple’s App Store, but Google’s Play Store and all the others. Instead of locking myself into each platform and having to learn and maintain multiple proprietary languages, hybrid app development makes more sense, given my skill set and my time constraints.

Don’t let hybrid app development scare you. In its simplest form, a hybrid app is still just a web browser, but without the URL bar and back button. This means you can build a full-fledged app using HTML/CSS/JS but still have it work like a native app, with all the same superpowers, like accessing bluetooth, GPS, camera, files, device motion, etc. Hybrid apps offers the best of both worlds.

Let’s Build A Hybrid App

For my use-case, I’ve decide a hybrid app is perfect, so let’s fire up….wait, there is no Xcode for hybrid apps! Where do I get all those files that makes my app do app things? Where’s the built-in UI, cool animations, and smooth transitions? The disadvantage to hybrid app development is that those starting with the web platform have to start from scratch. It’s the Wild West, and each developer is on his or her own.

I absolutely love the web platform. It provides a core set of tools to not only share information but consume it. However, the web platform offers only the basic building blocks for structuring content; styling and interacting with that content; and navigating between documents. The core of the web platform does not provide pre-packaged libraries like those in iOS and Android. At the lowest level, a web browser represents one “view” and one navigation/history stack. This is another area in which native apps have an advantage, and hybrid devs burn up time generating code to give browsers the ability to handle multiple views with multiple stacks.

Hybrid app developers quickly find themselves dealing with countless issues just to get their heads above water: figuring out the CSS to fill 100% of the viewport, sticking the tabs on the bottom and hovering content, adding event listeners, switching active states for icons and views, keeping track of navigation stacks of each tab, implementing touch gestures, generating a common way to navigate and transition between view, using hardware accelerated animations for the transitions, removing 300ms delays, knowing when to show or hide the back button, updating and animating the header title, interacting with Android’s back button, smooth scrolling through thousands of items, etc. All of these things come with native SDKs. And as an app grows, it’ll seem as though recreating natural, native interactions is a constant uphill battle–all of which native developers rarely think about, because for them it was baked in from the start.

I believe the solution is to use a framework/library that levels the playing field, giving hybrid developers a toolkit similar to that of native developers. Most developers have a sense of pride in writing everything themselves, and there are certainly plenty of use-cases in which frameworks and/or libraries are not required. But when it comes to hybrid app development, there is a whole world of common code being recreated by each developer, for each app, and that’s a lot of work and time to invest in something that native developers already get.

Cordova (the guts to Phonegap) is the predominant open-source software to morph the web platform into a native app. But just like the web platform, it only offers the basic building blocks, rather than a built-in framework to start with.

Frameworks and libraries amplify app development and allow devs to focus on how their apps work, not the logic of how apps work.

Hybrid Development Frameworks: Hybrid’s Missing SDK

I define frameworks and libraries as any software package that increases productivity. In my experience, hybrid developers’ main frustration lies not in creating their app, but rather in getting their app to work like an app, which is a subtle, yet significant difference.

With the advent of development frameworks focused on hybrid app development, developers finally have that missing SDK that levels the playing field with native. Cross-platform frameworks that embrace HTML/CSS/JS allow web developers to take their skills to app development. To increase productivity, hybrid app development frameworks should not only stick to the standards with pretty CSS and markup; they should also provide a MVC for serious, large-scale app development by a team.

Sworkit, a hybrid app built using the Ionic Framework, featured in the iOS App Store.

Sworkit, a hybrid app built using the Ionic Framework, featured in the iOS App Store.

Frameworks like the Ionic Framework provide a common set of logic used to create apps, which isn’t already baked into the web platform (full disclosure: I am a co-creator of Ionic and a core contributor to AngularJS Material Design). Rather than inventing yet another MVC, Ionic chose to build on top of AngularJS, which has proven itself to be a leader among popular front-end frameworks in the last few years. Ionic is backed by a large and active community, solid documentation, and its own command-line tool to increase productivity (the CLI isn’t required but is highly recommended).

Ionic’s use of AngularJS directives to create the user-interface allows for fast development, but most importantly, it’s highly customizable, through its use of Sass and simple markup. If you’re unfamiliar with AngularJS, Ionic offers a great way to learn it quickly, via numerous examples and templates.

Google’s Polymer project and Mozilla Brick are built on top of the cutting-edge Web Components specification. As with AngularJS directives, Web Components offer a great way to abstract away complex code with simple HTML tags.

Other proven hybrid development frameworks that have been around longer and offer their own powerful MVC/MVVM include Sencha Touch and Kendo UI. Both frameworks come with a large list of built-in components and widgets that enable developers to build powerful apps that work on iOS, Android, BlackBerry, Windows Phone, and more.

I do not consider front-end frameworks, such as AngularJS, Ember, and Backbone to be hybrid app development frameworks. While I highly recommend front-end frameworks for large-scale app development, they’re focused on the logic, rather than the user interface.

Frameworks like Twitter Bootstrap and Foundation offer a great user interface and responsive design capabilities. However, CSS frameworks focus on the UI and a responsive design pattern; but a UI alone still requires each developer to recreate the way a native app “works.”

App frameworks abstract away the complexity of building an app and offer developers both the core logic and the UI, similar to what iOS and Android provide. I believe it is important to embrace the web standards and the web platform at the core, so it can be easily run from Cordova and built for multiple platforms (including a standard web browser).

Software Engineering: Still Required

Hybrid app development frameworks have come a long way in the last few years, and they have a bright future ahead of them. However, Developing Hybrid Apps Still Requires Actual Software Engineering, just as developing native apps does. As in any form of web development, if only a few hours are put into a project, the result is rarely a highly polished and production-ready piece of work.

Hybrid fans sometimes offer the impression that frameworks create a unicorn and rainbow filled wonderland during development, which may mislead new developers. Just because you can write once and deploy everywhere doesn’t mean you’re exempt from the rules of software development. Hybrid offers many benefits, but as with so many things in life, cutting corners does not produce quality results, so please don’t claim all is lost after minimal effort.

Making An Accurate Comparison

The comparison of a hybrid app without a framework to a native app isn’t a fair one. To accurately examine hybrid vs. native development, we need to analyze each method at the framework level (hybrid with a framework vs. native, like Ionic Framework vs. iOS or Polymer vs. Android). As for hybrid vs. native: It’s a matter of studying your use-case first, rather than a choosing a definitive level of abstraction over everything else. It all ends up as 1s and 0s anyway, so jumping up another level of abstraction (HTML/CSS/JS) may be the right fit for your use-case and organization.

I often feel that opinions regarding hybrid app development were formed well before hybrid was ready for prime time. The world has quickly been transitioning to faster devices and browsers, as well as improved web standards, and there’s no signs of either one slowing down. There is no better time than now to leverage your existing web development skills and build quality apps by standing on the shoulders of hybrid SDKs.

@adamdbradley

WebmakerMozFest 2014: Spotlight on “Open Badges Lab”

This is the sixth post in a series featuring interviews with the 2014 Mozilla Festival “Space Wranglers,” the curators of the many exciting programmatic tracks slated for this year’s Festival.

For this edition, we chatted with Laurie Garrison, one of the Space Wranglers for the Open Badges Lab track. Participants in this track will challenge the conventional system of recognizing skills and learning, while celebrating achievements from Open Badge creators and issuers.

What excites you most about your track?
Last year our space was full of opportunities to create and design badges. This year we’re expanding on that by making sure that there will be lots of opportunities to earn badges throughout the weekend. We want to see badges escape from the Open Badge Lab and start interacting in the MozFest ecosystem, ideally providing inspiration for new connections amongst different disciplines, tracks and experts. There will be opportunities to earn a badge for connecting any device to the web on the Open the Web with Things floor, an Open Web Protector badge on the Policy and Advocacy floor, as well as a number of others.

Who are you working with to make this track happen?

We’ll have some impressive facilitators at work on our floor. The iDEA team (a new award for young entrepreneurs supported by the Duke of York and Nominet Trust) will offer the opportunity to create the badge that will be given to those who win the iDEA award. There will also be badge design with University College London staff, a workshop with the Think Big team, an opportunity to design a robot in Minecraft, Sci-Art storytelling with UNSA, mobile game design, wearable computing badges as well as sessions on the latest research and learning projects. We have something for all ages and every interest group!

How can someone who isn’t able to attend MozFest learn more or get involved in this topic?
Badges can be earned remotely before, during, and after the Festival. We’ll share challenges that will be recognized with badges in the lead up to MozFest. So badges will not only serve as documentation and mementos of participants’ experiences of MozFest, but will also help continue the momentum of MozFest after the event. In addition, we’ll be bringing a new, improved Badge the World website with us. We’ll be looking for more pledges to help us badge the world!

 

Inspired?

Head on over to the MozFest site to register!

CalendarCalconnect XXXI Interop Testing

Thanks to the wonderful folks at Linagora, I was able to spend the last three days at the Calconnect XXXI meeting in Bedford, England. The goal of this meeting is to get server and client vendors together in a room both for ad-hoc testing and discussions on calendaring standards.

Before arriving, I’ve set myself the goal to go through a big list of bugs that have been sitting around in our CalDAV component to see if they can be resolved. It turns out that I was able to close 48 of the 76 bugs I had picked out:

report-2014-10-01

A good amount of the bugs I’ve resolved were sitting and waiting for any one of our contributors to reproduce with a specific server. This is often a problem because the time it takes to set up and configure the servers is time consuming. The great thing about being here at Calconnect is having a testing instance most of the reported servers readily set up. Not only that, but engineers from the respective servers are sitting together at a table and can answer any questions that may arise, or comment on potential bugs that have been fixed in later versions.

The other category of bugs are support issues, duplicates and bugs that haven’t received an answer from the reporter. These could have been found outside of Calconnect, but its still a good opportunity to take the time to handle these.

Eight of the remaining bugs already have a patch attached, four of them were created while I was here. There is also a new feature coming up that makes it easy to share calendars with other users directly from Lightning. This requires the server to support caldav-sharing, for example the Apple Calendar and Contacts Server and fruux.com.

Screenshot 2014-10-01 11.02.11
Note: The ugly add button will be replaced by an icon. The email addresses are editable.

 

In the next few days we will be going on to the standards discussions. I am actively involved as the chair to TC-API, a technical committee dedicated to producing an abstract calendaring model that ensures that vendors integrating calendaring into their products are aware of the implications of calendaring and scheduling, hopefully resulting in better interoperability in the future. Another goal we have is to find a common understanding for a REST API that is geared towards webpages, which may become a standards document some day.

Meeting NotesSeaMonkey: 2014-09-30

Agenda

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

Action Items

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

NEW

OPEN

  • http://weblogs.mozillazine.org/seamonkey/ has not been updated since November 2012, the last version listed is 2.14 (bug 956561); move blog to blog.mozilla.org if possible Assigned: mcsmurf.
    • blog account has been created in bug 973886
    • Callek has imported old blogs from mozillazine
    • some sprucing / branding needs to happen next
  • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager
    • mcsmurf will look into this
  • bug 1057920 SeaMonkey’s CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website).
    • IanN will create a separate bug for the releng automation stuff and will find out what is required to get the work done.

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

  • 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, see also FOFT above.
    • 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.
  • comm-* will be building out of mozilla-* (bug 648979 etc.). Jcrammer has completed the coding. The decision to merge c-c into m-c has been kicked down the road into the next quarter or two.
    • Recent work on this:
    • bug 1040009 .mozconfig configure options are ignored if objdir path is absolute
    • bug 1035599 Pseudo-merge m-c and c-c’s objdir
  • [30th September 2014]
    • Infrastructure issues
      • linux64 systems are plagued by bug 1058385. Regular AWOLing. Currently 8 slaves are down.
      • WinNT systems were plagued by bug 1069119 and bug 1069117; but they seem to be ok now.
      • NB: Currently the miscellaneous patches to fix the RelEng infra (tooltool et.al) are all applied to the master directly. Once reviewed, the patches will be pushed to their corresponding repositories and the master will be updated properly.
    • [comm-central]
      • All platforms busted : bug 1071497 Patch checked in. Builds now back to “normal”.
      • l10n nightly/dep builds busted : bug 1073327 Fix waiting review.
      • blocklist update bustage : bug 1074572 Fix waiting review.
    • [comm-aurora]
      • blocklist update bustage : bug 1074572 Fix waiting review.
      • OSX64 l10n nightly/dep bustage : related to bug 902876
      • WinNT (build/debug) bustage : bug 1053652 Waiting for potential upstream fix.
    • [comm-beta]
    • [comm-release]
      • OSX64 bustage : bug 1023644 Patches waiting for review.
  • 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.29.1 was released on 24th September 2014.
  • There shall be a 2.30 beta soon. Schedule TBA.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • Firefox & Thunderbird Add-on Converter for SeaMonkey
  • 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.

    Add-on Converter for SeaMonkey: http://addonconverter.fotokraina.com/

    • Lemon Juice has been regularly updating his converter code, adding new fixes whenever an extension doesn’t convert properly.
  • bug 1060858 Ghostery 5.3.1 dropped support for SeaMonkey. Ghostery depends on the Addon-SDK. Since the SDK has been rewritten to support Firefox Australis, Ghostery no longer works for SeaMonkey. See discussion thread on mozillazine
    • [Ratty] I’ve contacted the Ghostery people (bmcdermott) and the addon-SDK people. The Addon-SDK has been updated (bug 1071048 so now Ghostery works on SeaMonkey trunk builds. The Addon-SDK is uplifted to mozilla-central every few weeks. Once this is done I’ll try to get the Ghostery patch uplifted to -aurora and -beta. Lemon Juice has been investigating other SDK based addons and so far the news is encouraging. QrCodeR can work in SeaMonkey by setting a SeaMonkey compatibility flag on three modules context-menu.js, selection.js and panel.js. Investigation continues!
  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Ratty filed bug 957149 to push an updated version of DOMi to addons.mozilla.org to pick up the latest fixes. Depends on:
  • 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)

  • [From a previous meeting:] There is a problem with the metrics server, so no current data is available
  • See Basics page for the usual reminders.
2.29

open tracking (0)
tracking requests (0)
targeted (0)
fixed (8)

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.
    • bug 793634 Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
      • bug 795354 Migrate SeaMonkey Linux builders to CentOS 6.
    • bug 846635 Use asynchronous getCharsetForURI in getShortcutOrURI. bug 834543 Add asynchronous version of setCharsetForURI and getCharsetForURI. Tracked in:
      • bug 896947 Use asynchronous version of setCharsetForURI and getCharsetForURI in getShortcutOrURI and other places.
    • 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.
  • Soon to land changes on OSX, tracked by:
    • bug 1074019 Modify file structure of SeaMonkey.app to allow for OSX v2 signing
    • bug 1074021 Get SeaMonkey to launch with the new .app bundle structure
    • bug 1074025 SeaMonkey’s preprocessed channel-prefs.js file needs to be the same for each build

Feature List, Planning

Bug statistics for the last two (full) weeks: 57 new, 12 fixed, 18 triaged.

  • Medium triaging effort, well above average in new bugs filed during the last three weeks.
  • 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

Open reviews/flags:
31 review
6 super-review
3 ui-review
4 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.

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
  • Haven’t done regular code fixing as I’ve been concentrating on the infra code changes.
    • bug 1072713 somewhat tracks the miscellaneous releng bugs.
IanN
  • Usual testing, reviewing and commenting.
  • Fixed:
  • Fixed for c-c:
    • bug 1060848 Static-link the CRT into SeaMonkey executable (/suite/app/moz.build). Port bug 1023941 Part 1
    • bug 1061011 Do not package .mkdir.done in XPIs
    • bug 1061029 Port |bug 815219 – Default to building with all available cores| to SeaMonkey
    • bug 1061336 Do not source mozconfig.common multiple times in linux in-tree mozconfigs
    • bug 1061341 Port |bug 895248 – Move –enable-stdcxx-compat in build/unix/mozconfig.linux| to SeaMonkey
  • Fixed for m-c:
  • Fixed for m-i:
  • Pending check in:
    • bug 1039003 Port |bug 633773 Use Google’s HTTPS search by default|, |bug 958883 Use HTTPS for Yahoo searches| and search plugin parts of |bug 959576 Create a component to get the list of priority domains| to Thunderbird
    • bug 1062559 Port |bug 1055627 Pass MOZ_GLUE_PROGRAM_LDFLAGS after STATIC_LIBS to linker| to c-c
  • Checked in pending review:
  • Waiting for feedback/review:
  • 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 1060897 Static-link the CRT into Instantbird executable (/im/app/moz.build). Port bug 1023941 Part 1
    • 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:

  • bug 986935 Restore from crash page is blank if default client dialog is open.

Needs checkin:

  • bug 870556 Try to improve performance of the IMAP download queue.

Still waiting for review:

Ratty

Fixed. Needs checkin (waiting for greener tree):

Fixed in Addon-SDK. Waiting for uplift to mozilla-central.

  • bug 1071048 update sdk/tabs metadata to work in SeaMonkey (for Ghostery and other SDK based addons).

Fixed:

  • bug 1035171 Switching tabs triggers onLocationChange with LOCATION_CHANGE_SAME_DOCUMENT flag.
  • bug 1039933 While composing mail, there exists an empty line in attachment context menu when right clicked on the attachment area.

Working on:

  • bug 640420 Add draggable splitter between urlbar and searchbar.
  • bug 698310 Spell Check Dialog to small for long words. Make it resizable.
  • bug 752331 Define TopLevelImageDocument.css and TopLevelVideoDocument.css for SeaMonkey themes.
  • bug 1040910 Support XHTML in feed titles.
  • bug 1068846 Enable generational GC for SeaMonkey.

Investigating:

Other stuff:

  • Coordinate efforts to get SeaMonkey support into the Addon SDK, needed by Ghostery, QrCodeR, and other SDK based addons.
  • Did some reviews.
  • Bug triage and Bug discussions.
  • Usual end user support and PR in newsgroups and Mozillazine.
rsx11m

Working on:

  • bug 1060852 Expose privacy.trackingprotection.enabled in Privacy preferences and account for removal of Do-Not-Track options.
    • Quasi-blocking bug 1031033 has only checked in FF string changes thus far;
    • bug 1042135 has patch for DNT-pref removal approved but won’t check in until patches for all FF-products are approved.

Needs testing:

  • 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.
stefanh

Did one review.

Waiting for review:

  • bug 333910 nsITheme for menu/scrollbox arrows (Widget: Cocoa).
  • bug 973644 Port bug 967970 – Set NSDisablePersistence to prevent disk leaks.
  • bug 1068997 Implement keyboard shortcut for composition’s “Find and Replace” on MAC.

Any other business?


SeaMonkey Meeting Details

Meeting NotesMozilla Platform: 2014-09-30

Need To Know

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

Notices/Schedule (lmandel)

Next Merge: October 13, 2014 Next Release: October 14, 2014
Trains
Central: 35 Aurora: 34 Beta: 33 Release: 32
  • You might have heard that we chemspilled last week
  • 33 beta 8 ships today
  • Final betas coming up
    • 33 beta 9 (last desktop beta) goes to build Thursday
    • 33 beta 10 (last mobile beta) goes to build Monday
    • still 22 tracked bugs for 33, please help drive down this list
  • Notable Aurora uplifts coming this week
    • OSX Gatekeeper v2 signing support via package layout changes
    • Loop changes

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.)

OrangeFactor (ryanvm)

<Read Only>

  • Past week’s OrangeFactor: 4.52 (last week: 4.17).
  • No progress on frequent Android and B2G timeouts raised in the prior weeks.
  • 14 intermittent failures fixed in the last week – List – Thanks!.

MemShrink (njn)

Stability (kairo)

  • Thanks to the GFX team for a lot of work and cooperation around OMTC on Windows.
    • We will very probably ship 33 with it back on and some good crash fixes added, turning it off for almost a week gave us good data though.

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.)

A*Team (RyanVM)

<Read Only>

Desktop Platform (bsmedberg)

  • New mac bundle structure and v2 signing landed
    • Planned to uplift to 34
    • Please file regressions or addon-incompatibility issues!

DOM (jst/overholt)

  • watch out for regressions in IndexedDB and related areas (bug 994190 relanded and looks good so far)

Electrolysis (e10s) (blassey)

<Read Only>

  • Please help dogfood e10s in Nightly!
  • Many e10s bugs fixed this week. Some highlights:

Firefox Desktop (gavin)

Summary of Work In Progress
  • You can see the status of the current iteration (35.2) in progress here
Summary of Recent Landings
  • Team landed 80 bugs over the last week, to complete the 35.2 iteration.
  • Details of landings from the past week can be seen here
Priorities for the upcoming iteration
  • e10s on Nightly
  • Loop:
    • finalize accounts/contacts work
    • UX: design spike looking into “collaboration” use cases
  • “Panic button”: better-exposed “Clear Recent History” functionality
  • “Reset button on the web”: a mechanism to prompt users to reset Firefox when they try to download Firefox when already running the latest version
  • OS X Yosemite themeing work
  • New tab page performance investigations
  • Places performance work (main thread IO removal)
  • Translation trial followup

Firefox Mobile (snorp/blassey/mfinkle)

You can find more on upcoming feature plans in the[roadmap]

Landings from the past week
Nightly (35)
  • Visible seams on the page (maybe at tile borders?) ( Bug 1009306 )
  • Send NS_NETWORK_LINK_DATA_CHANGED events on Android ( Bug 1024614 )
  • crash in mozilla::gfx::AlphaBoxBlur::Blur(unsigned char*) ( Bug 1028802 )
  • WebApp startup slowed significantly by debug server ( Bug 1034114 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange(PinSiteDialog.java) ( Bug 1041448 )
  • APKs for previous versions of Nightly and Aurora stick around in Downloads ( Bug 1051654 )
  • Performing searches with Wikipedia search engine immediately launches Fennec ( Bug 1063193 )
  • crash in java.lang.IllegalArgumentException: Wifi:Enable was not registered at org.mozilla.gecko.EventDispatcher.unregisterListener(EventDispatcher.java) ( Bug 1063541 )
  • The URL displayed under tab titles in the Synced Tabs panel disappears for a while after choosing “Open in New Tab”/”Open in Private Tab” ( Bug 1064162 )
  • Synced Tabs panel shouldn’t be present in Guest Mode ( Bug 1064177 )
  • crash in mozilla::gfx::SourceSurfaceAlignedRawData::InitWithStride(mozilla::gfx::IntSizeTyped<mozilla::gfx::UnknownUnits> const&, mozilla::gfx::SurfaceFormat, int, bool) ( Bug 1067018 )
  • Firefox: User doesn’t go back to the channel after watching video till the end ( Bug 1068633 )
  • Android crash in mozilla::image::RasterImage::DecodeSomeData ( Bug 1069369 )
  • Selecting “No video” and “No audio” options from the permission prompt still shows the content of the device camera and the audio active ( Bug 1070989 )
  • System download manager needs a build time pref ( Bug 1071091 )
  • Form autocomplete dialog can take up the entire screen and make it really hard to use fennec ( Bug 1071738 )
  • Tapping sometimes triggers two clicks ( Bug 1071758 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.db.PerProfileDatabases.getDatabaseHelperForProfile(PerProfileDatabases.java) ( Bug 1072332 )
  • Regression: Open/Close animation of the tabs tray and menu is sluggish ( Bug 1072376 )
  • Issues with hidden/unhidden devices on Synced Tabs ( Bug 1072954 )

Firefox OS Connectivity (vchang)

<Read Only>

  1. https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2014-09-30

Firefox OS Peripherals / Device Porting (ericchou)

<Read Only>

  • Bluetooth (members: Shawn Huang, Ben Tian, Jamin Liu, Jocelyn Liu)
    • BLE API discussion on dev-webapi
    • bug 1063066 – [Flame][KK] Bluetooth transfer does not work in Gallery App – landed (2.1+, smoketest blocker)
    • bug 1062697 – [MADAI][Bluetooth] avrcp metadata doesn’t update on carkit. – landed (2.0+)
    • bug 1072142 – [woodduck] Read the 2nd socket message info directly – landed (2.0M+)
  • Media Playback (members: Bruce Sun, Blake Wu, Star Cheng)
    • bug 1069857 – [FFOS] OMXCodec’s seek could be triggered again in DecodeVideoFrame() when seeking – landed (2.0+)
    • bug 1053031 – [FFOS V2.0] When operate I-frame seek, Video player position was not changed. – patch ready (2.0+)
  • Device Storage & Stability (members: Alphan Chen, Eden Chuang)
    • No update this week

GFX (milan)

  • Bumpy ride for the Windows OMTC; is/was there a better way given the hardware variety?
  • Work week covered topics like APZ & tiling on desktop, Project Silk, E10S, etc. See here and here for notes.

Layout (jet/dbaron)

  • Xidorn Quan joins the Platform rendering team. He’ll start working on our Asian Text projects, completing the CSS Ruby layout feature.
  • Q3 Goals updated with current status. Will share Q4 Goals next week.

Media (mreavy)

<Read Only>

  • Fixed a number of race conditions resulting from the MediaStreamGraph refactor (bug 848954)
    • Added thread-safety assertions (caught a bug we’d already been tracking a fix for)
  • Found that in overloaded conditions the output buffering code would drop audio and run unnecessary processing (bug 1074420)
  • Landed a wallpaper patch for a top-crasher in beta – bug 1033066 (allocation size going negative; may be related to bug 1074420).
  • Found eager-allocation of 8MB when webrtc/gum is started that was supposed to be disabled on beta and release bug 1074548 – thanks khuey!
  • e10s getUserMedia/etc UI fixes – should work now
  • preparing to work on multi-stream support for PeerConnections (and call setup improvements like BUNDLE (less ports) and renegotiation (no having to start a new connection and drop the old one when adding/removing video, for example)
  • Lots and lots of Loop work. Better every day! File bugs!
    • Use it for 1-1’s in place of Vidyo!
  • More 2.0 fixes
    • Support for HW Audio AEC/noise-suppression on Flame landed (build option in 2.0)
    • working to make sure “right” device-specific prefs/files are installed on next base build (H.264 enable, better H.264 codec, HW AEC, etc)

Necko (dougt/jduell)

  • Network change detection (Windows-only for now, Android coming soon, other platforms Q4) finally landed and is sticking so far (bug 939318)
  • We’re implementing an OpenVPN API for Firefox OS: talk to me if you’re interested in what webAPI should look like (bug 1033580)
  • Resource Timing will probably be landing today (finally!) (bug 1002855)
    • e10 support isn’t there yet but should happen within a week or two.

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.)

<Read only beyond this point>

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

11:04 lmandel: sydpolk: https://wiki.mozilla.org/Platform/2014-09-30
11:05 sydpolk: thx!
11:05 KaiRo: cpeterson: I guess you didn't reload, otherwise I would have done a very brief stability update
11:06 cpeterson: KaiRo: OK, we can jump back to you
11:06 KaiRo: cpeterson: ok, thanks
11:12 ctalbert: snorp: yay for that network link fix \o/
11:12 snorp: ctalbert: yeah seriously
11:12 snorp: ctalbert: bagder had a hell of a time landing it
11:13 KaiRo: milan_: other than getting more people to test Aurora, I don't know too much of what we could do better
11:14 lizzard: kaiRo: yeah, i think people with older computers may not be rushing to run Nightly
11:14 milan_: KaiRo: yeah, that's what I'm afraid of
11:14 milan_: we have webgl performance work coming up, and XP is a fairly large target, so it'll get interesting trying to do it without completely messing them up :)
11:15 KaiRo: milan_: of course, the amount of crashes that have been reported as OOM|small but weren't really OOM has not helped, but we finally should have fixed the largest issue with that
11:16 RyanVM|sheriffduty: snorp: I try ;)
11:16 snorp: RyanVM|sheriffduty: it found actual bugs!
11:16 snorp: testing works yay!
11:16 RyanVM|sheriffduty: our tests work! \m/
11:18 KaiRo: milan_: FWIW, you probably heard that we had reftests failing with OMTC off, I asked User Advocacy and it looks like they can confirm that users have been reporting more rendering issues last week as well, so that matches as well :)

Engineering Meeting Details

  • Tuesday 2014-09-3011:00 am Pacific Standard Time
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
  • 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

Air MozillaFxos Engineering Weekly "Late" Meeting

Fxos Engineering Weekly The weekly FirefoxOS engineering meeting.

Firefox AppsSeptember Contributor of the Month: Daniele Scasciafratte

Congratulations to Daniele Scasciafratte, our first-ever Marketplace Contributor of the Month! Daniele is a developer, mentor, and evangelist who first discovered Firefox in 2009, and became an active contributor after a Firefox OS App Day in Rome last year. In September, Daniele contributed translations and apps, gave a talk about developing on FirefoxOS, and blogged about the experience. He has this to say about the Mozilla community:

“Thanks to Mozilla for supporting the volunteers, its openness to ideas and suggestions that allow you to feel a true global community. New initiatives such as the online Marketplace Day and the support material for the events are things that amaze people, then after evangelization, become volunteers for these little details that make the difference. Not all communities have these opportunities to enhance their knowledge and to learn to work internationally. Go Mozilla Italia go!”

We’d also like to congratulate Rabimba Karanjai for being awarded a Loft Video Game Innovation Fellowship from the Entertainment Software Association, for his Firefox OS game Math Racer. Best wishes to him for his trip to Washington DC on October 1-3 to present his game to White House and Congressional representatives interested in games in STEM education.

Here are all the accomplishments from September—thank you to everyone who made a difference last month. All of your efforts count.

There is a new wiki to kick off October, with some new featured projects and a few carried over from last month. There should be new ones added in the next week or two, and of course suggestions are always appreciated. Lastly, please be sure to report any accomplishments in the Get Recognized section.

We look forward to collaborating with you!

Air MozillaEngineering Meeting

Engineering Meeting The weekly Mozilla engineering meeting.

Air MozillaParis Scala User Group meeting

Paris Scala User Group meeting La soirée sera en 2 parties avec une introduction de 30 minutes sur le language Rust par Felix Klock, suivi par une présentation de FlamSpark...

hacks.mozilla.orgMatchstick Brings Firefox OS to Your HDTV: Be the First to get a Developer Stick

The first HDMI streaming stick powered by Firefox OS has arrived. It’s called Matchstick and we’re looking for your help to create apps for this new device.

Background

Matchstick stems from a group of coders that spent way too much time mired in the guts of platforms such as Boot to Gecko, XBMC, and Boxee. When Google introduced Chromecast we were excited about the possibilities but ultimately were disappointed when they pulled back on the device’s ultimate promise – any content on any HD screen, anywhere, anytime.

We decided to make something better and more open, and to accomplish this we had to choose an operating system that would become the bedrock for the adaptable and open-sourced platform that is Matchstick. That platform is Firefox OS, which allows us to build the first streaming stick free of any walled garden ecosystem.

Matchstick and Firefox OS combined offers a totally open platform (both software and hardware), that lets developers explore content and applications from video to games, and bring it right into the living room. That’s right Developers! An open SDK means you can build out your own personalized streaming and interactive experiences without the need for approval or review.

Apps for Matchsticks

We have opened up a full developer site with access to everything you need to begin working with Matchstick. Support for Firefox OS will be available at launch, and we look forward to adding TV applications to the Firefox OS Marketplace. For now, we have included a full API library, of sender apps with support for Android and iOS, as well as receiver apps that are compatible with the Matchstick Receiver.

When we say Apps for Matchsticks, we mean both sender and receiver apps. You can use the sender APIs to enable your Firefox OS, Android or iOS device to discover a Matchstick device, then communicate with your receiver app. It’s not difficult to embed sender APIs into existing apps or create new sender apps, please refer to the sample code we have included with the SDK.

Matchstick sender apps typically follow this execution flow:

  1. Scan for Matchstick
    The sender app searches for Matchstick devices residing in the same Wi-Fi network as the sender device. The scanning reveals a friendly display name, model and manufacturer, icon, and the device’s IP address. Presented with a list, a user may then select a target device from all those discovered.
  2. Connect to Matchstick
    We support both TLS and NON-TLS communication between sender and receiver.
  3. Launch Receiver App
    The sender initiates a negotiation with the target device, launching a receiver app either with the URL of a HTML5 receiver app, or even a Chromecast App ID.
  4. Establish Message Channels
    With the receiver app now launched, Matchstick establishes message channels between the sender and receiver. In addition to a media control channel common to all Matchstick and Chromecast apps, you may establish any number of application-specific channels to convey whatever customized data that your app might require.

The receiver app is a combination of HTML5, CSS and Javascript, loaded into a “receiver container” which is a certified app of Firefox OS. To use the Matchstick receiver APIs, you need only include fling_receiver.js in your app.

Here is an example of a simple video receiver app:

<!DOCTYPE html>
<html>
    <head>
     <title>Example simplest receiver</title>
     <meta charset="UTF-8">
     <!--(need) include matchstick receiver sdk-->
     <script src="//fling.matchstick.tv/sdk/libs/receiver/2.0.0/fling_receiver.js"></script>
    </head>
    <body>
     <!--(need) Give a video tag-->
     <video id="media"></video>
     <script>
         // (need) Get video element
         window.mediaElement = document.getElementById("media");
         // (need) For media applications, override/provide any event listeners on the MediaManager.
         window.mediaManager = new fling.receiver.MediaManager(window.mediaElement);
 
         // (need) Get and hold the provided instance of the FlingReceiverManager.
         // Override/provide any event listeners on the FlingReceiverManager.
         window.flingReceiverManager = fling.receiver.FlingReceiverManager.getInstance();
 
         // (need) Call start on the FlingReceiverManager to indicate the receiver application is ready to receive messages.
         window.flingReceiverManager.start();
     </script>
    </body>
</html>

Matchsticks for Apps

Rather than relying on emulators, we want to be sure developers can get their hands on Matchstick prototypes and start coding without delay. As a result, we are inviting app developers who will commit to building and porting apps for Firefox OS on Matchstick to apply for a free developer-preview device through our Matchsticks for Apps program.

Similar to the phones-for-apps program launched by Mozilla, our Matchsticks for Apps program is aimed at developers who have built apps for Firefox OS, Chrome, Android, iOS …. Even for Chromecast! Let’s bring those visions to the big screen.

image

Developer (pre-production) version of Matchstick (pic by Christian Heilmann)

We are now looking for good ideas, video content, new channels, as well as games, tools, utilities, pictures, even skins for the UI. If you have a plan to build apps or do something for Matchstick, please share your plan and we’ll send you a stick so you can start coding ASAP.

Who Should Apply:

  • Those interested in building apps on a big screen TV
  • Those with existing Web or mobile apps, who would like to expand to the big screen
  • HDMI dongle developers, who want to build their own Matchstick
  • Chromecast developers, who want to port their apps to an open platform
  • You!

Matchstick workshop in November

On Tuesday, November 18th, we plan to host an invitation-only Firefox OS App Workshop for Matchstick in the Mozilla office in San Francisco. The enrollment form is open and we are accepting applications from qualified developers.

Apply now for the San Francisco workshop!

If you don’t live near San Francisco, don’t worry! We plan to offer several other app workshops in the near future and we’ll announce them here, of course!

Happy Hacking!

The Mozilla BlogLaunching the Ford-Mozilla Open Web Fellows Program, a Global Initiative to Recruit the Heroes of the Open Internet

By Mark Surman, Executive Director, Mozilla Foundation; and Darren Walker, President, Ford Foundation We are at a critical point in the evolution of the Internet. Despite its emergence as an integral part of modern life, the Internet remains a contested … Continue reading

Meeting NotesMozilla Project: 2014-09-29

All-hands Status Meeting Agenda

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

Friends of Mozilla

  • Congratulations to Rabimba Karanjai for being awarded a Loft Video Game Innovation Fellowship from the Entertainment Software Association, for his Firefox OS game Math Racer. Best wishes to him for his trip to Washington DC on October 1-3 to present his game to White House and Congressional representatives interested in games in STEM education.
  • Congratulations to Leona Szalai, who localizes social media content for Firefox into Hungarian, on her recent nuptials.
  • Thank you to Brian King and Guillermo Movia for hand-carrying swag across 3 continents so Marcelo Poli could receive his app reviewer prizes.
  • Thank you to JP for making Community Building a P1 this week!
  • Thank you to Sofien (Chaasof) for being a star Wiki gardener.
  • Thank you to everyone who put in extra hours on last week’s NSS security chemspill. An especially large thank you to Kai Engert for driving the patches to the finish line and landing them on the myriad release branches we had to deal with.

Upcoming Events

Tuesday, 30 September
  • Brown Bag event: Firefox OS HDMI Dongle
    • 11:30a-1:30p at Mozilla MTV MozSpace, in the MTV Commons
    • Will be available via AirMozilla
    • Come pick up a device to try out!
Thursday, 02 October
  • 10:00 AM Pacific / 17:00 UTC: Grow Mozilla discussion — a forum for discussing community building at Mozilla

Project Status Updates (voice updates)

Firefox

Speaker Location: MV (cbeard) London (johnath)

  • Firefox at 10 years stuff (cbeard)
  • Unheralded Heroics
    • Chemspills
    • Mac signing
Cloud Services

Speaker Location: San Francisco (Bill Maggs)

Mozilla Location Service – Look for a new, much improved Mozstumbler in Google Play Store in the coming weeks! Many, many community stumbling events in planning stages. Contact your rep or Pierros Papadeas (ppapadeas@mozilla.com).

Firefox Accounts – FxA is available for Mozilla services. It’s not hard! Resources on MDN here. If you would like FxA to do auth for your service, please contact Bill Maggs (bill@mozilla.com) or Chris Karlof (ckarlof@mozilla.com).

Mozilla Communities

Speaker Location: Mark Surman (Toronto); William Quiviger (remote)

  • Update on Community Tiger Team activities.
  • Moving forward with six Contribution Challenges.
  • Team is also working on: survey to better understand community health and a communications plan.
  • William Quiviger to give an update on the FXOS Local Content Challenge

Contribution Challenges:

  • Firefox : Firefox 10
    • Business Owner’s: Winston/Eric; Community Liaisons: Kristin Baird/Brian King
    • Defining a plan targeted at driving downloads as part of the Firefox 10th Anniversary campaign.
  • Firefox Growth:
    • Business Owner: Chris More; Community Liaison: Larissa Shapiro
    • Identifying opportunities for community participation as part of the Growth team initiatives.
  • FXOS Local Content:
    • Business Owner: Sakina Goth; Community Liaison: William Q.
    • Finalizing plan to produce a large volume of high quality hyper-local content for FXOS users in India and Mexico, in a very short time frame, and in parallel, train Mozillians to become skilled evangelists and developer mentors to ensure long-term sustained support and mentorship for local developers creating hyper-local content for FXOS
  • FXOS in market Communications:
    • Business Owner: Erica Jostedt/Tristan Nitot; Community Liaison: Guillermo Movia
    • Finalizing a communications plan to continue to drive momentum/exposure for FXOS post launch. Plan will focus activities in India & Mexico.
  • FXOS + Webmaker:
    • Business Owner: David Ascher; Community Liaison: Michelle Thorne
    • Finalizing plan focused on user research that helps us understand ways that ‘user generated apps’ can solve problems for the next billion web users. Beta testing to begin in Oct; with kickoff at MozFest.
    • Will actively play a role in shipping Mobile Webmaker (aka Appmaker) through user testing at Maker Parties and conduct interviews with feature phone users to understand the problems they want to solve.
  • Tiles:
    • Business Owner: Sean Bohan; Community Liaison: Michelle Marovich
    • Define a system to generate content for regional community tiles in 20 launch markets for October 15 and put an ongoing structure in place for regional communities to own the content schedule for regional community tiles.
IT/Operations

Speaker Location: MTV (guillermo)

Vidyo has released Vidyo Desktop v3.3.0 (27) with the below added features and fixes. This release has already been tested within IT and is ready to be released to the organization. Here are the details for the rollout:

Rollout Dates:
A week from now, this update will become mandatory on Monday 10/6/2014.
Today, you can download the client w/ the following links below.

New Features:
Join a conference with camera, mic and/or speakers muted Join a conference with your full screen shared and camera, mic, speakers muted Easier access to your rooms public link via client UI Many bug fixes for Windows, Mac and Linux.

Download Links

OS X: https://mozilla.box.com/s/8ap0iclutieqrnh5kq2j

Windows: https://mozilla.box.com/s/exlu99fpm07h0r4xkpqc

Ubuntu: https://mozilla.box.com/s/bmf2ukxe1avjq6a2bdz5

Ubuntu64: https://mozilla.box.com/s/yzjf3dnes6grn6dz470c

RPM: https://mozilla.box.com/s/92in19khtgr1yb7qitmo

RPM64: https://mozilla.box.com/s/wza4c8nzz3k01n5cnf6j

Note: after upgrading, a pop-up will appear saying that you do not have a current version. Please select “Not Now” and the do not remind me checkbox.

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
Sean Martell Art Director Update on the MozID logo project Remotely – my house outside Toronto Not sharing my screen, but when I’m finished talking I’d like to play a video available at the link shown here. Video is on this page. https://blog.mozilla.org/creative/
Marshall Erwin Privacy & Data Security Database dumping practices Mountain View No No Email questions to merwin@mozilla.com
Liz Compton Legal Affairs Manager Update from Legal San Francisco No https://mana.mozilla.org/wiki/display/LGL/Legal+Resources+Home, https://www.mozilla.org/en-US/about/legal/, https://www.mozilla.org/en-US/privacy/ Provide feedback on any of the above here: https://etherpad.mozilla.org/9wwHAN2CwL
Bill Mills Science Lab Community Manager Open Source Science Projects! Moz Vancouver No None Original call for proposals.
Sakina Groth Product Marketing Manager Developer Brown Bag: The first Firefox OS HDMI Dongle! Remote No None Go here to watch the brown bag presentations remotely tomorrow
Bhavana Bajaj Release Manger Update on Firefox OS Release Cadence (Readonly) No None Go here to watch the brown bag presentations remotely tomorrow or join us in MTV Commons at 9am PT on 9/30

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
Xidorn Quan Jet Villegas San Francisco Australia-Remote Layout
David Anderson Andreas Gal Mountain View Mountain View Graphics
Suzanne Hetrick Dave Slater Mountain View Mountain View Executive Assistant to Dave
Fabio Rios Michaela Smiley Remote San Francisco User Engagement
Lindsay Saunders Caitlin Galimidi Portland San Francisco Program Management – Marketplace
Fernando Jimenez Moreno David Scravaglieri Paris Netherlands-Remote Firefox OS Engineering
Sharyl Sun Jill Alvarez Mountain View San Francisco University Recruiter

<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 1054141 You can now configure Bugzilla to never send you email about changes made by a particular user
  • bug 891199 Clicking on “NEEDINFO” at the top of the page now scrolls you to the comment requesting the information
  • bug 1037663 When creating a bug, task-specific bug entry forms are now displayed

All changes.

Engagement
Web Compatibility

See the Minutes


  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 8600
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600

Air MozillaMozilla Weekly Project Meeting - HLS Stream

Mozilla Weekly Project Meeting - HLS Stream The Monday Project Meeting

Air MozillaMozilla Weekly Project Meeting

Mozilla Weekly Project Meeting The Monday Project Meeting

about:communityFirefox And The Academy

It’s September, so a lot of students are joining us in various Mozilla forums, hoping to make a contribution to an open source project. This is always a challenging time of year for Mozilla, and I’d like to say a few things about it. If you’re a student hoping to get involved or – even better – an educator who would like to involve their classes in open source projects or contribute specifically to Mozilla, I hope this will give you a sense of some of the challenges and pitfalls you may be facing and how we can work together to overcome them.

If you’re a veteran of Usenet from the days when Trumpet Winsock was a thing and dinosaurs roamed the earth, you recognize the particular flavor of Mozilla’s comms channels at this time of year. People who want to make a difference in the world want be a part of Mozilla and we’re always excited to hear from them, but September is a challenging time; we get a lot of requests for “student projects” and “easy bugs” that can be difficult to address, and the dropout rate from new participants grabbing “easy” [good first bug]s at this time of year is frustratingly high.

Part of these challenges are structural, of course, and some of those structures are out of our control – courses that are designed around software and development as a discrete, compartmentalizable thing, rather than a messy, rapidly evolving and organic process aren’t really compatible with the day to day process of shipping software. Likewise the benchmarks that make up a traditional academic evaluation process don’t really make sense in our context, so more often than not the goals and schedules of students and educators aren’t well-aligned with ours.

We’re grateful for any effort put in, large or small, to making Firefox better and supporting a free and open Web. Having said that: there are a few things that make working with Firefox in an academic context challenging and you should be aware of them.

The biggest one is that we can’t promise to accept a patch within a certain time frame. This can become a problem for both students and professors when getting the patch accepted into the main product is part of the criteria for a good grade in the course.

This has happened in the past: a student has done great work on a harder-than-expected bug, but it didn’t make it through our process – including testing, feedback, revision and more testing – by the time grades were assigned. Despite their effort, the student was undeservedly graded poorly.

This is bad for everyone when it happens – the student and professor both get discouraged, the value of their work (and of the course) gets harder to see, and if the student doesn’t stick with the patch long enough to carry it over the line, despite all that, Firefox doesn’t benefit and Mozilla’s engineers feel like they’ve wasted their time.

If you’re involved in shaping your curriculum, a better approach is to combine fixing the bug or delivering the project with a set of reports or presentations about the process. This presentation – maybe even a blog post, because working in the open is important – can be a discussion of what the student is working on and why it’s important, how the work progressed and what the process of getting a patch in looks like, as well as the challenges they’ve faced and what they’ve learned from it.

Making three or four “this is my experience and what I’ve learned so far” reports over the term a more important part of the grading process than the code itself helps enormously, both in terms of keeping everyone involved motivated and in reflecting the open, community-oriented values of the project. There are other options for instructors who are familiar with our processes – breaking up the grade up so that submitting a patch that builds, responding to the first review and so on all count, even if the patch isn’t ultimately accepted, is one possibility.

The second major challenge is finding bugs that are a good fit for their contributors. We’re getting better at that – good first bugs usually tell you what language they rely on ( [lang=c++] in the Bugzilla whiteboard flags, for example) and often have a pretty good outline of what a successful patch would look like and a mentor associated with them. And while we can’t promise to privilege students ahead of any other contributors, we certainly try to hold up our end of the bargain and answer new contributors’ questions promptly.

One thing that takes the edge off there is that class of bug – “good first bugs”, you can search for [good first bug] in the Bugzilla whiteboard – that are a nice, well-defined way to get involved. The idea behind “good first bugs” is that the major challenge of the bug isn’t the code itself, but learning how to get your development environment spun up, participating in development on IRC and Bugzilla, learning how to navigate our patch review and submission process.

It typically takes a few tries for most new contributors to get their patch through. Reviews for code format and quality, suitable tests, that sort of thing can all take an extra week or two to resolve, especially if you’re working on them around other classes. But most of our good first bugs can be resolved within a few weeks, well within a term.

You’ll have to judge for yourself if this is a good fit for your schedule, your students or your institutional goals. On the one hand, though GFBs are generally well-contained, Firefox uses every feature JS and C++ have to offer, so a certain amount of familiarity and comfort with the language is important. On the other, we’ve got a huge variety of Good First Bugs here, ranging from “correct this documentation” to “fix part of a JIT compiler”, so it’s likely that if you want to contribute, we can find a home for your efforts that will make millions of people’s lives just a little bit better.

More generally, if you’re interested in getting people involved with Mozilla in September, get in touch with us in June. Knowing in advance that people will be looking for new bugs or projects gives us time to talk to our team leads and project managers, to let us all find a place to put our efforts that will be helpful and valuable to everyone.

Which is all to say that small first-time bugs are often as inglorious as they are important; while they don’t seem like much, the small patches and first bugs of today come from the Web’s next generation of leaders.

Thank you,

– Mike Hoye – mhoye@mozilla.com

about:pixelsBuilding a Living Logo from Community Data: a Rough Working Prototype

The core component of our MozID project is a new “living logo” for Mozilla – one that is directly shaped by the activity of our community and evolves over time based on that activity. We’ve shared some examples of other living logos, and reported that we’re working with Pitch Interactive to build that data visualization, but the concept can still be a little abstract until you see it.

The good news is that now we have a rough working prototype that allows you to do just that.

To be clear, this does NOT at all represent how the final logo will look, but the prototype really does bring the idea to life in a much more significant way. First, check out this short video that gives some background explanation:

The prototype itself lets you take straightforward information about community activity (sourced from areweamillionyet.org) and turn them into a logo-ish shape. First, adjust details like opacity, shape of the curves or the particular sources of the data, then click the ‘transform’ link to see them all come together.

Here’s the prototype.

Our logo will be much more visually refined and styled than this, but it’s pretty eye-opening to see it all come together…especially considering that it will be a constantly shifting representation of the heart of Mozilla. I’m really excited about that part in particular.

Stay tuned for more details on this project coming soon!

WebmakerQ&A with MOUSE

MOUSE is an amazing organization that has been working with the Maker Party since the inception of the campaign in 2012. Through the MOUSE Squad program students learn to become digital media and technology experts in their schools and join a network of youth technology leaders. We had a chance to catch up with Senior Director Marc Lesser to talk more about the organization and how they’re participating in Maker Party this year.

MOUSE

What is your organization and what do you do?

MOUSE is a national non-profit youth organization founded in NYC that focuses on empowering learners from underserved schools to “have fun, do good, and make stuff.” Learners from MOUSE Programs build participatory identities by applying digital solutions to real-world problems.

What is the events will you be hosting or running during Maker Party?

MOUSE and Mozilla are joining forces to ready a WebMaking movement in schools across the US. 14 pioneering MOUSE program educators joined us in NYC for the first ever Summer WebMaker Institute – a 2-day intensive PD event preparing educators to return to their school community to integrate webmaking and empower your learners as mentors, too!

Why did you choose to get involved with Maker Party?

MOUSE has supported Maker Party from the start, and shares its mission to invigorate local and global efforts to help connect people and empower them by engaging with and participating through tools that help enrich learning and life.

Tell us what you’re most excited for at the event?

In 15 years working at the intersection of learning and technology, MOUSE has seen – and been an influencing part of – the field’s evolving obsession with “new literacies” emerging from the tools, practices, and culture of digital life. The Web, however, has long outlived mere faddism and yet the field of education has done little to help frame it’s tools, practices, and culture as a legitimate domain to help educators and learners focus on building critical skills and competencies. No group of educators is better prepared to help further the mission of building web literacies than the Coordinators of MOUSE’s program network.

Why is it important for youth and adults to make things with technology?

Beyond convenience and commerce, technology affords people an ability to extend the way they think and interact with their world. Changing the world will require both, for people to become smarter users and, most importantly to us, also makers::problem-solvers::producers of what comes next.

What is the feedback you usually get from people who attend or teach at your events?

That, while too often underestimated, there’s no substitute for the cognitive, community-oriented, and self-empowering outcomes of simply getting together and making things.

Why is it important for people and organizations to get involved in Maker Party?

Because everyone – people and organizations both – has the capacity to organize, host, teach things and learn things and it isn’t that often that, with such low barriers to entry, we can contribute to something so positive that matters to how we move forward as people.

How can people get in touch with your organization?

WebmakerMozFest 2014: Spotlight on “Science and the Web”

This is the fifth post in a series featuring interviews with the 2014 Mozilla Festival “Space Wranglers,” the curators of the many exciting programmatic tracks slated for this year’s Festival.

For this edition, we chatted with Kaitlin Thaney, the Space Wrangler for the Science and the Web track. Participants in this track will examine the potential of the open web to redefine how we experiment, analyze and share scientific knowledge.

What excites you most about your track?
This year we’ll build off the momentum of the global hackathon we had in July. We’re hosting a two-day sprint on projects around libraries, authoring tools for research, visualization, open data, and educational resources. I’m very excited to be experimenting with this format, since it worked so well during our summer sprint.

Who are you working with to make this track happen?

We have so many wonderful partners! We’re working with GitHub, CERN, the New York Public Library, iPython Notebook, Zooniverse, the Knight Lab, Propublica, School of Data, BioMed Central, the Wellcome Trust, and a number of others. We’re also thrilled to have mentors from our instructor community joining us.

How can someone who isn’t able to attend MozFest learn more or get involved in this topic?
We’ll be posting links to planning etherpads and repositories so that others can get involved. We’ll also be working to capture as much of the activity into teaching kits, resources, and write-ups to share after the event.

 

Inspired?

Head on over to the MozFest site to register!

WoMozWomoz supports #HeForShe campaign

Womoz supports the HeForShe campaign, launched by Goodwill Ambassador Emma Watson at the United Nations.

If you also want to show your support to gender equality, just take a photo of you holding a sign with #HeForShe and #Womoz written on it and send it on the social networks.

Some of our early supporters:

Follow us on twitter and Google plus, like us on facebook.

WoMozEmma Watson’s UN Speech Fully Localized in Bangla

We have established localization in the heart of our contribution , to be honest i , myself am a localizer and have started contributing through localizing the webmaker UI . But even after promising , i couldn’t contribute in localizing this wonderful yet thoughtful speech of my one of the most favourite actress Emma Watson ;) in the UN except for a few lines only as i am busy . So i forwarded the message of Larissa to my community and thanks to our awesome community lead Mahay Alam Khan , he lead and made the L10n done with the help of our awesome contributors just with in the blink of an eye.Special thanks goes to Seeam , Salman and others to get the job done . Indeed HeForShe!! ;)

6928873-large

Emma Watson on her speech in the UN

The Bengali localized version of Emma Watson UN Speech is as follows -

গত ২০ সেপ্টেম্বর ২০১৪ তারিখে নিউইয়র্কে অবস্থিত জাতিসংঘের প্রধান কার্যালয়ে হিফরসি  উদ্যোগ নিয়ে বক্তব্য দেন জাতিসংঘের নারী বিষয়ক কার্যক্রমের শুভেচ্ছা দূত এমা ওয়াটসন। তার পূর্ণাঙ্গ বক্তব্য:

আজ আমরা ‘HeForShe’ নামের একটা প্রচারনা শুরু করেছি।

আমি আপনাদের কাছে এ বিষয়টি তুলে ধরতে চাই কারন আপনাদের সহযোগিতা প্রয়োজন। আমরা লিঙ্গ বৈষম্য দূর করতে চাই এবং এ কাজে সবার সহযোগিতা প্রয়োজন।এটা জাতিসংঘের জন্য প্রথম একটি উদ্যোগ: আমরা চেষ্টা করছি লিঙ্গ বৈষম্যের বিষয়টিকে সবার কাছে তুলে ধরতে। যতটা সম্ভব মানুষের মাঝে বিষয়টি ছড়িয়ে দিতে। এবং আমরা শুধু কথাই বলতে চাই না, বাস্তবে যাতে এ বৈষম্য দূর করা যায় সেটি নিশ্চিত করতে চাই।

আমাকে নিয়োগ দেয়া হয়েছে ছয় মাস আগে এবং যত বেশি আমি নারীবাদ নিয়ে কথা বলেছি, ততই আমি বুঝতে পেরেছি যে, নারী অধিকার নিয়ে লড়াই করা আর পুরুষ বিদ্বেষী হওয়া একই কথা। যদি আমি একটা বিষয় নির্দিষ্ট করে জানি, তবে তা হচ্ছে: এটাকে বন্ধ করতে হবে।

প্রমান হিসেবে, নারীবাদের সংজ্ঞা হচ্ছে: “একটি বিশ্বাস, যে নারী এবং পুরুষ উভয়ের সমান অধিকার এবং সুযোগ থাকা উচিত। এটা উভয়ের জন্য রাজনৈতিক, অর্থনৈতিক এবং সামাজিক সমতার মতবাদ”।

আমি আট বছর বয়স থেকেই লিঙ্গ-ভিত্তিক ধারনা সম্পর্কে প্রশ্ন করতে শুরু করি। আমাকে “নেত্রী” হিসেবে ডাকা হত এবং আমি এটা নিয়ে দ্বিধায় ছিলাম। কারন আমি চাইতাম, আমাদের অভিভাবকদের জন্য তৈরি করা নাটকের পরিচালক হতে– কিন্তু ছেলেরা চাইতো না।আমার বয়স যখন ১৪ তখন থেকেই মিডিয়া আমাকে যৌন আকর্ষক ভাবে উপস্থাপন করতে শুরু করে।

যখন আমার বয়স ১৫ তখন আমার মেয়েবন্ধুরা খেলাধুলা থেকে নিজেদের সরিয়ে নিল কারন তারা পেসিবুহুল হিসেবে নিজেদের উপস্থাপন করতে চাইল না। যখন ১৮ বছর বয়স আমার ছেলে বন্ধু তাদের অনূভুতি প্রকাশ করতে পারে নি।

আমি সিদ্ধান্ত নিয়েছিলাম যে আমি একজন নারীবাদী ছিলাম এবং এটা তখন আমার কাছে তেমন জটিল মনে হয়নি। কিন্তু আমার সাম্প্রতিক গবেষণা আমাকে দেখিয়েছে যে, নারীবাদ এখন একটি অপ্রচলিত শব্দ হয়ে গেছে।

আপাতদৃষ্টিতে আমি এমন পর্যায়ের মহিলাদের মধ্যে পড়ি, যাদের অভিব্যক্তিকে খুব শক্তিশালী, আক্রমণাত্মক, আলাদা, পুরুষ বিদ্বেষী এবং আকর্ষণশূন্য বলে মনে হয়। কেন শব্দটি এত অস্বস্থিকর?

আমি ব্রিটিশ নাগরিক এবং চিন্তা করতাম একজন নারী হিসেবে আমার পুরুষ বন্ধু যা পাচ্ছে আমার ও তাই পাবার  অধিকার আছে। আমি মনে করি যে  নারী হিসেবে  সিধান্ত নেবার অধিকার আমার আছে। আমি মনে করি আমার দেশের নারীরা দেশের পলিসি এবং সিদ্ধান্ত নেবার ক্ষেত্রে তাকে উচিত। আমি মনে করি সামাজিক ভাবে আমি সেই সম্মানেই পাই যা একজন পুরুষ পাচ্ছে। কিন্তু দুখের বেপার সারা দুনিয়ায় নারীরা এসব অধিকার পায় না।

কোন দেশই দাবি করতে পারবেনা যে, তারা লিঙ্গ বৈষম্য দূর করতে পেরেছে।

আমি ভাগ্যবান সেই অধিকারগুলো আমি পেয়েছিলাম যা আমি মানবাধিকার হিসাবে বিবেচনা করি। আমার জীবন কেবল বিশেষ অধিকারপ্রাপ্ত যে, আমার মা-বাবা মেয়ে বলে আমাকে কখনো কম ভালোবাসেনি। আমি মেয়ে বলে, আমার স্কুল আমাকে কখনো সীমাবদ্ধ করেনি। আমার প্রশিক্ষকরা কখনোই ভাবেননি, আমি হয়ত কম দূরে যেতে পারবো কারণ একদিন আমিও একটি সন্তান জন্ম দিবো। এই প্রভাব বিস্তারকারীরা লিঙ্গবৈষম্য দূত ছিলেন যারা আজকের আমিকে তৈরি করেছে। তারা হয়ত জানেওনা, কিন্তু অসতর্ক ভাবেই তারাও নারীবাদী ছিলেন। এবং আমাদের এরকম আরও অনেক কে দরকার। এবং এখনো যদি আপনি এই শব্দটি কে ঘৃণা করেন – এই শব্দ কে গুরুত্ব না দিয়ে বরং এর পিছনের চিন্তাধারা এবং উচ্চাকাঙ্ক্ষা কে গুরুত্ব দিন। ১৯৯৭ সালে হিলারি ক্লিনটন বেইজিং-এ নারী অধিকার নিয়ে একটি বিখ্যাত বক্তব্য উপস্থাপন করেছিলেন। তখন তিনি যা যা পরিবর্তন করতে চেয়েছিলেন, তা এখনো রয়ে গেছে।

তবে যেটা আমার বেশি চোখে লেগেছে যে, শ্রোতাদের মধ্যে মাত্র ৩০  শতাংশ ছিল পুরুষ। কিভাবে আমরা পরিবর্তন আনবো, যেখানে মাত্র অর্ধেক লোক এসেছে বা এরকম কথাবার্তায় নিজেদেরকে স্বতঃস্ফূর্ত মনে করছে? পুরুষগণ– আমি আপনাদের এই আনুষ্ঠানিক আমন্ত্রণটি সম্প্রসারিত করার সুযোগ গ্রহণ করতে চাই। লিঙ্গ সমতার সমস্যাটি আপনারও সমস্যা। কারন আজ পর্যন্ত, একজন সন্তান হিসেবে, সমাজ আমার বাবার একজন অভিভাবক হিসেবে ভূমিকার চেয়ে মায়ের ভূমিকাকে কম মূল্য দিয়েছে; যদিও তাদের দুজনেরই আমার জীবনে সমান প্রয়োজন রয়েছে।

আমি তরুণদেরকে দেখেছি মানসিক রোগে ভুগতে। তারা সাহায্য চাইতে পারেনি, কারন তারা ভয় পেত যে সাহায্য চাইলে তাদেরকে কাপুরুষ মনে করা হবে। এমনকি যুক্তরাজ্যে ২০-৪৯ বছর বয়সী পুরুষ মারা যায় আত্মহত্যার কারনে; যা সড়ক দুর্ঘটনা, ক্যান্সার এবং হৃদরোগের চেয়েও বেশি। আমি পুরুষদের দেখেছি যে, সফলতার সংজ্ঞার কারনে তারা কিভাবে ভঙ্গুর হয়ে যায়। পুরুষদের মধ্যেও সম অধিকার নেই।

সমাজের লিঙ্গবৈষম্যে দ্বারা শৃঙ্খলাবদ্ধ পুরুষদের নিয়ে আমরা খুব বেশি কথা বলি না কিন্তু আমি অনুভব করেছি তাদের সীমাবদ্ধতা এবং এটাও বুঝতে পেরেছি যে যখন তারা এই শৃঙ্খল থেকে মুক্ত হবে তখন স্বভাবতই নারিরাও মুক্ত হবে । যদি পুরুষ মাত্রই আক্রমনাত্মক নাও হতে পারে তাহলে নারী মাত্রই নতমস্তক নহে । যদি পুরুষদের নিয়ন্ত্রণ করার প্রয়োজন না থাকে তাহলে নারীদেরও নিয়ন্ত্রিত হওয়ার আবশ্যকতা দেখি না ।

পুরুষ এবং মহিলা উভয়কেই মুক্ত মনে করা উচিত। পুরুষ এবং মহিলা উভয়কেই শক্তিশালী মনে করা . বিপরীতধর্মী শ্রেণী হিসাবে না দেখে দুইটি লিঙ্গকে একই বর্ণালিতে ফেলে দেখার সময় হয়েছে। যদি আমরা যা নই, তা দিয়ে আমাদের সংজ্ঞায়িত করা বন্ধ করি এবং আমরা সত্যিই যা, তা হিসেবে সংজ্ঞায়িত করতে শুরু করি, তাহলে আমরা আরও স্বাধীন হতে পারবো এবং এজন্যই HeForShe। এটা মুক্তির জন্য , স্বাধীনতার জন্য।

আমি চাই পুরুষেরা তাদের মজ্জার মধ্যে এটি ধারণ করুক , জাতে তাদের কন্যা , বোন এবং মায়েরা এই কুসংস্কার মুক্ত হতে পারেন এবং একই সাথে তাদের পুত্রদেরকে নিরাপদ ও মানবিক রাখার জন্যও – তাদের হারিয়ে যাওয়া স্বত্ত্বাকে তারা যেন খুঁজে পান এবং এভাবে যেন সার্থক ও স্বয়ংসম্পূর্ণ হয়ে উঠেন ।

আপনি চিন্তা করতে পারেন এই হ্যারি পটার এর মেয়ে টি কে? এবং সে জাতিসংঘের মঞ্চে কি করছে। এটি একটি ভালো প্রশ্ন এবং বিশ্বাস করুন আমি নিজেও নিজেকে জিজ্ঞাসা করছি এই একি কথা। আমি জানি না যদি আমি এখানে যোগ্যতাসম্পন্ন হই কিনা। আমারা সবাই জানি যে আমি এই সমস্যার ব্যাপারে যত্নশীল। এবং আমি এটি আরও ভালো করতে চাই এবং আমি  যখন দেখি তখন দেখি এবং সুযোগ পাই আমি মনে করি এটা আমার দায়িত্ত যে আমি কিছু বলি। ইংলিশ  এডমন্ড বুরক বলেনঃ “প্রকৃতপক্ষে খারাপ সকল স্বত্তার বিজয়কে নিশ্চিত করার জন্য কিছু ভাল নারী ও পুরুষের নিষ্ক্রিয় থাকাই যথেষ্ট ।”

এই বক্তৃতার জন্য আমার বিচলতা এবং আমার সন্দেহের সময়ে আমি নিজেকে দৃঢ় ভাবে বলেছি – যদি আমি না, তাহলে কে, যদি এখন না হয়, তাহলে কখন। যদি আপনার সামনে ঠিক একই সন্দেহ আসে যখন আপনার হাতে সুযোগ আছে, আমি আশা করবো আমার কথাগুলো আপনার জন্য সহায়ক হবে।

কারণ বাস্তবতা হচ্ছে এখনো যদি আমরা কিছু না করি তাহলে হয়ত ৭৫ বছর, কিংবা আমার মতে প্রায় একশ বছর লাগবে নারীদের একই কাজে পুরুষের সমান বেতন আশা করতে। ১৫.৫ মিলিয়ন কন্যা পরবর্তী ১৬ বছরে বাল্যবিবাহের স্বীকার হবে। এবং এই বর্তমান হারে ২০৮৬ সালের আগে সকল আফ্রিকান মেয়ের পক্ষে মাধ্যমিক শিক্ষা গ্রহন সম্ভব নয়। আপনি যদি সমতায় বিশ্বাস করেন, তাহলে আপনি তাদের মধ্যে একজন যারা অসাবধানী নারীবাদী আমি অাগেই ব্যক্ত করেছি এবং এইজন্য আমি আপনাকে সাধূবাদ জানাই।

আমরা একটি সংঘবদ্ধ শব্দের জন্য সংগ্রাম করছি কিন্তু ভাল খবর আমাদের সংঘবদ্ধ আন্দোলন আছে। এটা বলা হয় হিফরসি। আমি আপনাদের এগিয়ে আসার আমন্ত্রন জানাচ্ছি, দেখা হবে উচ্চকন্ঠে বলুন,

এবং জিজ্ঞাসা করুন নিজেকে যদি আমি না তাহলে কে ? যদি এখন না তাহলে কখন ?

ধন্যবাদ।

Software CarpentrySplitting the Repository

United Airlines messed up my travel again last weekend, so I finally had a chance to think some more about how Software Carpentry works and how we can make it work better. Having topic maintainers is one improvement; another, which was discussed at this month's lab meeting, is to break the bc repository that holds our lessons and workshop home pages into smaller and more manageable pieces.

The Problem

We face three related problems:

  1. The bc repository is too big. My copy (which admittedly includes a few pieces of ongoing work) takes up almost 100 MBytes. More importantly, it includes a bewildering mix of material: page templates, setup instructions, support tools, and more.

  2. Our scope keeps creeping. Software Carpentry's original aim was to teach scientists who were already programming how to program better. We now teach people who've never programmed before, in three languages, and have material on databases, regular expressions, and a bunch of other things. They're all useful, but they don't belong in a single repository any more than every useful piece of software in the world should be in a single large library.

  3. It's hard for people to explore and manage alternatives. Different instructors have different opinions about the best way to introduce certain topics: NumPy early vs. NumPy late in Python, branches before or after pull requests in Git, and so on. Instructors also want to use different examples for different audiences, e.g., bioinformatics data when teaching biologists and climate data when teaching climatologists. We could come up with a naming scheme and directory structure to manage this all in one repository, but again, that's not how we manage software.

The Proposal

Our proposal is to divide the current content of the bc repository between several new repositories. One of these will be the template for workshop websites; each of the others will contain one complete lesson, such as the introduction to the Unix shell for novices. Each of these repositories will be much smaller, and therefore easier to navigate, than what we currently have. As a fringe benefit, people will be able to subscribe to only the ones they care about most, so that they aren't flooded with comment and commit messages on topics they're less interested in.

We will seed these repositories using the content we currently have, but there's no reason to stop there. If a group of people want to fork one of those repositories and tweak the examples to be more relevant to economics, they can do so; if other people want to write a lesson that presents Git in an entirely new way, they can do that too. Software Carpentry will then be responsible for certifying lessons as fit for purpose, i.e., for saying, "This lesson is in our format, meets our quality standards, is aimed at our audience, covers the things we think are important." Any workshop that delivers certified lessons covering our core topics will then be allowed to use our name and logo, and people will have more freedom to develop and use "affiliated" lessons that are compatible with ours, but cover things we don't.

To implement this, we will start by specifying how a lesson should be laid out (just as Ruby on Rails and Django specify what key files must be called and where they must be put). We will then extract the novice Software Carpentry lessons from the bc repo, along with as much of their history as we can bring over. The bits and pieces needed to set up a home page for a workshop will be extracted in the same way into another repository. Almost all workshops will be able to set themselves up by cloning just that repository, which will (probably) contain only a couple of dozen files, then point at rendered lessons on the Software Carpentry website instead of having their own (redundant) copies.

FAQ

Who will certify lessons as "fit for purpose"?
In the short run, we'll certify the lessons we already have. In the long run, our topic maintainers, possibly in conjunction with some sort of scientific advisory board, will decide what meets our needs and standards.
Shouldn't we just use the best lesson for each level and topic?
Sure, but how will we know which lesson is best until we (a) have a better assessment process and (b) have lessons to assess? More importantly, what's best for an astronomer is unlikely to be best for an economist, so we're more likely to see lessons diverge by discipline than by teaching approach.
Can't we keep the lessons the same, but vary the datasets?
This doesn't work well in practice, since the wording throughout the lesson has to change when the data changes.
What happens if we wind up with too many lessons for people to sort through?
We'll cross that bridge when we get to it. (In reality, we're unlikely to have enough high-quality lessons in the next couple of years for it to be a real problem.)
How does this relate to Data Carpentry, Library Carpentry, etc.?
We will (hopefully) share lesson templates and any tools we build to support lesson creation and validation (e.g., something to check that a directory is laid out properly). Each project will then certify lessons as fit for its purposes, and workshops based on what lessons they contain.
What to do about the outstanding pull requests against the bc repository?
We will merge as many as we can, then ask the authors of the rest to redirect them.
How will people find lessons once they're spread out across multiple repositories?
We will start with a page of links on our web site, and worry about how to handle explosive growth if such growth occurs.
How will people keep up with changes to lessons?
We don't know, but we don't think the problem will be any worse than it is right now.
What if someone creates a lesson on topic X for community Y, then we realize there's a better way to teach X?
That's up to the group that certifies lessons: if the old approach is just less good than the new one, there's no reason to de-certify, but if we realize the old approach was just plain wrong, they may pull the certification. In practice, this is unlikely to come up in the next year, and we can figure it out then.
How will we handle resources that are shared by many or all lessons?
Dynamic resources like CSS files are easy: pages will load them from our web site. Compile-time resources like included files and page layouts) can be duplicated for now: Git submodules should do this for us, but our past experience with them hasn't been encouraging. We can include small data sets in the base lesson template for now, and worry about larger or more specialized data sets as we grow.
What about software setup and installation instructions?
We can't put these in a central site because instructors really do customize these frequently. We will therefore duplicate the instructions for now and figure something else out later.

Next Steps

The next steps are to create a layout template for our lessons, then extract our current novice lessons into new repositories based on that template. The most important thing will be to keep the template simple: really, really simple. To ensure this, we need volunteers who aren't experts in Git or page layout to act as a reality check on those who are. If you'd like to help in either capacity, please give us a shout: this will be one of the biggest changes we ever make, and we'd like everyone to be part of it.

Appendix: A Straw Man Lesson Template

This template is guaranteed not to be what we eventually use, but we hope it will serve as a starting point for discussion. If you have specific questions or suggestions, please add them to this GitHub issue rather than putting them in comments on this blog post so that the whole conversation is in one place.

Overall Layout

Each lesson is in a directory laid out as follows:

  1. index.md: home page for lesson
  2. dd-slug.md: topics (where 'dd' is a sequence number and 'slug' is a mnemonic, e.g., 03-functions.md)
    • We'll discuss file formats (e.g., whether or not to use the IPython Notebook for the master copy of each lesson) in a separate thread.
  3. introduction.md: slides for a 3-minute "why learn this?" presentation to give to learners at the start of a lesson
  4. glossary.md: definitions of key terms
  5. reference.md: cheat sheet for key commands, etc.
  6. guide.md: instructor's guide
  7. code/: sub-directory containing all code samples, which are executed from the root directory
  8. data/: sub-directory containing all data specific to this lesson
    • index.md: describes data sets
    • filename.xyz: single-file dataset
    • folder/: multi-file datasets are all in their own directories
  9. img/: images (including plots) used in lesson

Overall Index

The index.md file is structured as follows:

    # Lesson Title

    Paragraph of introductory material.

    > ## Learning Objectives
    >
    > * Overall objective 1
    > * Overall objective 2

    ## Topics

    * [Topic Title](dd-slug.html)
    * [Topic Title](dd-slug.html)

    ## Other Resources

    * [Introduction](intro.html)
    * [Glossary](glossary.html)
    * [Reference Guide](reference.html)
    * [Instructor's Guide](guide.html)
  

Topics

Each topic file's name is dd-slug.md, where 'dd' is a sequence number and 'slug' is a mnenominc, e.g., '03-functions.md'. Each topic should take 10-30 minutes to cover, and should be structured as follows:

    # Topic Title

    > ## Learning Objectives {.objectives}
    >
    > * Learning objective 1
    > * Learning objective 2

    Paragraphs of introductory material.

    ## Sub-heading

    Paragraphs of text.

    ~~~ {.python}
    some code:
        to be displayed
    ~~~
    ~~~ {.output}
    output
    from
    program
    ~~~

    > ## Challenge Title {.challenge}
    >
    > Description of challenge

    ## Another Sub-heading

    As above...

    > ## Key Points {.keypoints}
    >
    > * Key point 1
    > * Key point 2
  

Some features of this are:

  • We will use Pandoc for Markdown-to-HTML conversion, so we can use {.attribute} syntax for specifying things instead of the clunky postfix syntax our current notes use (because it's the only thing that Jekyll supports).
  • Rather than using <div class="whatever">...</div> to mark sections, this uses blockquotes whose headings have specific classes: the sections we need to mark are relatively small, and CSS will take care of displaying these the way we want.

Glossary

Each term in the glossary is laid out as a separate blockquote, with the term in a heading. Yes, this is odd, but we want to avoid putting HTML in Markdown, and we can't add identifiers to paragraphs using {#whatever} notation: that only works on headers.

    # Glossary

    > ## Term {#some-anchor}
    > The definition.
    > See also: [some word](#local-anchor)
  

Introductory Slides

Every lesson must come with a short slide deck (2-3 minutes) that the instructor can use to explain to learners what the subject is, how knowing it will help learners, and what's going to be covered. Slides are written in Markdown, and compiled into HTML using reveal.js.

Software CarpentryUCOSP as a Model

Software Carpentry's two-day workshops are just one of many ways to teach people practical skills. Term-long group projects are another model that I'm very fond of, and earlier this year, the four people who've been running the UCOSP program in Canada wrote a paper about what they've learned. Some of the lessons rhyme with what we've learned from Software Carpentry, but other insights are new. If you know of papers describing lessons learned from other innovative teaching projects, pointers in the comments section would be very welcome.

WoMozEmma Watson’s speech for gender equality at the UN

On September 20, 2014, UN Women Global Goodwill Ambassador, Emma Watson, delivered a moving speech at United Nations Headquarters in New York.
The transcript of this speech is available on the UN Women website (in english, spanish and french). The video has been uploaded on the HeForShe youtube account. But it sadly lacks subtitles. So, people started to subtitle the video on amara. As of now, it has been subtitled in english, chinese (traditional), french, portuguese and brazilian portuguese. More to come…

Moreover, it has already been translated to Bangladeshi by womoz here led by Maliha.

If you want to help, you cantranslate this speech and publish it on your community blog. You can also add the subtitles on amara.

Helps us spread the word everywhere in the world

 

SUMO BlogWhat’s up with SUMO? 26 September

The summer is gone, and the days are getting slightly shorter (at least here)… Fortunately, we have a bunch of great updates coming your way to take care of the post-summer blues ;-)

New arrivals to SUMO – warm welcomes going out to:

Saturday AoA IRC meetup!

Bangladesh community chat

Spam reporting mechanism updates

  • Forum spammers beware! There’s a few new toys in the Moderator arsenal, thanks to our SUMO Devs working relentlessly on improving the moderation system. Everyone can expect much less spam in the upcoming months, as our automated systems learn how to handle unwanted messages better. More details here.

SUMO day summary

  • Our first (revived) SUMO Day took place yesterday, and the results are in… The highlights? 97% of the questions responded to in 24 hrs and reaching 100% in 72 hours! Huge thanks to everyone involved!

Localizers gonna localize

  • As of this week, we reached a record number of 199 confirmed and active localizers in SUMO. Way to go, SUMO l10ns!
  • Also, the forever amazing Bangladesh L10ns have completed the localization of all 42 Webmaker articles. Go, Bangladesh!

Forum redesign starting soon!

  • It is upon us – when you start noticing changes in the Support Forums in the coming days – let us know what you think!

This week’s Monday meeting YT recording

  • We’ve had a minor outage and that’s why the video is avaialbile only today. You can find it here. If you want to be regularly updated about our meeting recordings going live, please subscribe to the YT channel.

That’s it for this update, more news coming your way soon! Stay tuned and have a great weekend ;-).

QMOFirefox 34 Aurora Testday, October 3rd

Greetings fellow mozillians,

We are happy to announce that Next Friday, on October 3rd, we’re going to hold the Firefox 34.0 Aurora Testday. We will be testing the latest Aurora build, with focus on areas affected by the most recent changes and fixes. Detailed instructions on how to get involved can be found in this etherpad.

No previous testing experience is required, so feel free to join via the #qa IRC channel and our moderators will offer you guidance and answer your questions as you go along.

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

When: October 3, 2014.

Air MozillaKernel Recipes (Paris)

Kernel Recipes (Paris) Cycle de conférence sur le noyau Linux les 25 et 26 septembre 2014 chez Mozilla à Paris Une douzaine de conférences, des intervenants venus du...

Software CarpentrySeptember 2014 Lab Meeting Report

After a two-month break for a sprint and some holidays, we held another monthly lab meeting this week. About 50 people showed up to talk about issues large and small; the key points are below.

  1. As mentioned last week, we are asking specific people to take charge of particular topics in our core material. They will not be responsible for developing lessons themselves (though they may of course do so). Instead, their job will be to keep issues and pull requests moving by reviewing, managing discussion, merging into the master branch, and so on. Our initial maintainers are:

    • Bash: Gabriel Devenyi and Christina Koch
    • Git: Matt Davis and Jessica Hamrick
    • Python: Azalee Bostroem and Trevor Bekolay
    • SQL: Abigail Cabunoc and Sheldon McKay
    • R: John Blischak and Denis Haine
    • Mercurial: Doug Latornell
    • MATLAB: Ashwin Srinath and Isabell Kiral-Kornek
    • Build system: Raniere Silva and Rémi Emonet
    • Windows installer: W. Trevor King and Ethan White
  2. Related to this, we are going to break up the bc repository. It currently holds both our lessons and the templates for creating workshop sites, and has become too large and too complicated to manage. Our plan is to have a one-to-one match between repositories and lessons (e.g., the novice/python lesson will be in a small repository of its own); we're working out a detailed proposal, and hope to have it up early next week. Trevor King, Trevor Bekolay, Ré Emonet, and Erik Bray have volunteered to help with the Git magic that will be needed to do this without losing history—more help will be very welcome when the time comes, particularly from people who aren't Git experts, and can therefore tell us whether what we're doing is usable.

  3. Greg Wilson's post on Building a Better Teacher and companion posts by Azalee Bostroem and Justin Kitzes have generated a lot of suggestions over the past three weeks about how we could share good teaching practices among our instructors. The specific suggestions made at this week's meeting were:

    1. Match each new instructor with an experienced instructor as a mentor. Azalee Bostroem, Erik Bray, Abigail Cabunoc, Matt Davis, Gabriel Devenyi, Ivan Gonzalez, Adina Howe Karin Lagesen, Bill Mills, Tracy Teal, and Naupaka Zimmerman all volunteered to be mentors; we'll match them with people who finished instructor training this summer.

    2. We'll set up a weekly or bi-weekly meeting in which people who have taught in the past couple of weeks can "hand off" what they've learned about the lessons to people who are going to teach in the coming couple of weeks. This will also be an opportunity for Greg Wilson to debrief recent instructors.

    3. We will ask instructors to send us their checklists after each workshop so that we can see what they actually did (and trim the things they didn't).

    4. We'll have "in-service days" a couple of times a year in which people who have been teaching for a while can find out what changes have been made to our lessons recently.

    5. Before we break up the bc repository, we're going to simplify things by using gh-pages as the main branch (i.e., the starting point for new features) instead of the master branch. We have been using master as a staging area (i.e., as a development branch, with gh-pages as the release branch), but this has been causing confusion. We won't delete master until outstanding pull requests are merged, but we'll set up our new lesson repositories with gh-pages as their default.

    6. Naupaka Zimmerman, Chris Kees, and Karin Lagesen volunteered to help us revamp our pre-assessment survey based on feedback we've received in the last few months. In particular, they'll make it easier to customize for particular workshops, and try to come up with questions that will help us discriminate more accurately between different levels of novice learner.

    7. Daniel Chen has received about 15 descriptions of what was actually taught in various workshops from those workshops' instructors. He, Fan Yang, and Marios Isaakidis will use these descriptions to revamp our post-workshop instructor survey to help us learn more about how our lessons are actually being used, and how well they're working.

    8. We're going to start using the term "workshop" instead of the term "bootcamp", since the latter is harder to translate in some languages, and has paramilitary connotations to some people.

    Many thanks to everyone who took part in these meetings—we have a lot of work in front of us, but a good crew to do it.

    Round 1 Attendees (18:30-19:30 Eastern on Thursday, Sept 25)

    • Greg Wilson (Software Carpentry / Toronto)
    • Bennet Fauber (University of Michigan)
    • Matt Davis
    • Damien Irving (University of Melbourne)
    • Isabell Kiral-Kornek (University of Melbourne)
    • Ashwin Srinath (Clemson University, SC)
    • Trevor Bekolay (University of Waterloo)
    • Balamurugan Desinghu (University of Chicago)
    • Sarah Supp (Univ Wisconsin - Madison)
    • Azalee Bostroem (UC Davis)
    • Kirill Palamartchouk (Newcastle University, UK) Sorry, unable to type today
    • Raniere Silva (University of Campinas, Brazil)
    • Gabriel Devenyi (McGill University)
    • Rémi Emonet (University of Saint &EACUTEtienne, FR)
    • Bill Mills (Mozilla Science Lab / Vancouver)
    • Trevor (Olympia)
    • Pauline Barmby (Western U, London Canada)
    • Jason Williams (Cold Spring Harbor Laboratory)

    Round 2 Attendees (11:00-12:00 Eastern time on Friday, Sept 26)

    • Greg Wilson (Software Carpentry / Toronto)
    • Kristjan Onu (Gagest / Montreal)
    • John Blischak (University of Chicago)
    • Denis Haine (Université de Montréal)
    • Nichole Bennett (University of Texas/Okinawa Institute of Science and Technology)
    • Abigail Cabunoc (Mozilla Science Lab / Toronto)
    • Ethan White (Utah State Univ/Univ of Florida)
    • François Michonneau (University of Florida)
    • Naupaka Zimmerman (U of Arizona)
    • Lynne Williams (Child and Family Research Imaging Facility/Vancouver)
    • Jose Beltran (Stockholm University)
    • Adina Howe (Argonne National Lab)
    • Fan Yang (Iowa State University)
    • Arliss Collins (Mozilla Science Lab)
    • Karin Lagesen (University of Oslo)
    • Marios Isaakidis (Cyprus University of Technology)
    • Janet Riley (Cantina Consulting, Boston)
    • Tracy Teal (Michigan State)
    • Sheldon McKay (New York)
    • Robert Till (CUNY - John Jay)
    • Amy Brown (no fixed address/Toronto)
    • Ivan Gonzalez
    • Olav Vahtras (KTH Stockholm)
    • JC Leyder
    • Tom (Sickkids)
    • Stephen Turner (University of Virginia)
    • Erik Bray (STScI)
    • Daniel Chen (CUMC)
    • Chris Kees (ERDC/Coastal & Hydraulics Lab)

Mozilla KoreaMozilla 한국 커뮤니티 리더쉽 변화에 대해

안녕하세요. Channy입니다.

오늘 우리 ‘Mozilla 한국 커뮤니티’의 리더쉽 변화에 대한 사항을 말씀드리고자 합니다.

우리 커뮤니티는 2002년 저의 개인적인 활동으로 시작하여, 2004년 Mozilla 사용자 커뮤니티가 되어 국내에 Mozilla 제품 보급 및 사용자 지원, 한국어 지역화, 웹 표준 및 오픈 웹 기술 전파를 위한 다양한 활동을 해 왔습니다. 그동안 많은 분들이 커뮤니티에 공헌해 주셨고, 그분들의 노고에 감사드립니다.

– 커뮤니티 역사 보기: http://www.mozilla.or.kr/community/about

뜻깊은 커뮤니티 10 주년 맞아
제가 10년간 커뮤니티를 이끌어 오면서 즐겁고 보람된 일도 많았지만 부족한 점도 적지 않습니다. 그래서, 제가 Mozilla 활동을 시작한 지 딱 10년째인 2012년 부터 커뮤니티 운영진들과 함께 향후 10년을 대비하여 커뮤니티 구조 변화를 하기로 결정하고 진행해 왔습니다.

그동안 다회의 코드 파티를 통해 Mozilla 각 영역의 새로운 공헌자를 오프라인에서 발굴하고, Firefox OS 앱 데이 및 Firefox 개발자 콘퍼런스, 개발자 행사 부스 참여 등 활동적인 운영 개선이 있었습니다.

http://www.mozilla.or.kr/wp/data/archive/2013/10/IMG_4221-600x444.jpg

그 이면에는 핵심 공헌자 및 운영진들의 봉사와 참여가 절대인 도움이었고, 그 중에서도 2년 전부터 저와 공동 리더 역할을 담당해 준 신현석님의 도움이 매우 컸습니다.

우리 커뮤니티 공동 리더인 신현석님은 국내 웹 표준 선도자 중에 한 분으로 웹 퍼블리셔로서 브라우저 QA엔지니어 및 프론트엔드 개발자로서 웹 업계에도 유명한 오피니언 리더입니다. 2004년에 커뮤니티 포럼이 처음 만들어질 때 부터 참여하여 600 여개의 답글을 달아주던 파워 유저였구요.

저와 함께 다양한 웹 표준 전파 활동을 함께해 왔습니다. 또한, Mozilla 커뮤니티 외에도 CSS 디자인코리아의 운영진으로도 활동했습니다.

신현석, 새로운 커뮤니티 리더로 선임
오는 10월 부터 Mozilla 한국 커뮤니티 내부의 여러 가지 활동에 대한 관리, 행사 개최 및 대외 발표, 공헌자에 대한 코칭 등 다양한 영역에서 신현석님이 단독으로 리더쉽을 발휘해 주실 것입니다.

20140924083551985

우리 커뮤니티가 10년을 맞는 이 시점에서 뜻깊은 일임인 동시에 앞으로 폐쇄된 모바일 환경에서의 개방 웹과 사용자 선택 및 기술 혁신을 한국에서 전파하는 구심점으로서 Mozilla의 중요성을 볼 때 매우 바람직한 변화라고 생각합니다. 신현석 리더는 그러한 변화에 오랫동안 준비된 분입니다.

저는 이제 일반 커뮤니티 멤버 및 공헌자로서 한 가지 영역을 맡아 활동하면서 현석님을 도와 커뮤니티가 잘 운영되도록 조언을 하는 역할을 맡을 예정입니다.

아울러 곧 한국 웹 20주년을 맞은 기념 콘퍼런스와 Mozilla 한국 커뮤니티 10주년 기념 파티도 10월에 개최할 예정인데요. 많은 관심을 가지고 참여해 주시면 감사하겠습니다.

이번 리더쉽 변경을 통해 Mozilla가 국내 웹 환경 및 IT 산업에 혁신을 주도하는 계기가 되기를 바랍니다. 아울러 아직도 많은 영역에서 커뮤니티 공헌자들의 참여를 절실히 기다리고 있습니다. Mozilla의 기술 철학에 공감하시는 분들의 많은 참여를 바랍니다.

– 커뮤니티 참여: http://www.mozilla.or.kr/community/join

윤석찬 (Channy Yun) 드림

본 글은 Channy’s Blog에도 함께 올려졌습니다.

hacks.mozilla.orgGenerational Garbage Collection in Firefox

Generational garbage collection (GGC) has now been enabled in the SpiderMonkey JavaScript engine in Firefox 32. GGC is a performance optimization only, and should have no observable effects on script behavior.

So what is it? What does it do?

GGC is a way for the JavaScript engine to collect short-lived objects faster. Say you have code similar to:

function add(point1, point2) {
    return [ point1[0] + point2[0], point1[1] + point2[1] ];
}

Without GGC, you will have high overhead for garbage collection (from here on, just “GC”). Each call to add() creates a new Array, and it is likely that the old arrays that you passed in are now garbage. Before too long, enough garbage will pile up that the GC will need to kick in. That means the entire JavaScript heap (the set of all objects ever created) needs to be scanned to find the stuff that is still needed (“live”) so that everything else can be thrown away and the space reused for new objects.

If your script does not keep very many total objects live, this is totally fine. Sure, you’ll be creating tons of garbage and collecting it constantly, but the scan of the live objects will be fast (since not much is live). However, if your script does create a large number of objects and keep them alive, then the full GC scans will be slow, and the performance of your script will be largely determined by the rate at which it produces temporary objects — even when the older objects aren’t changing, and you’re just re-scanning them over and over again to discover what you already knew. (“Are you dead?” “No.” “Are you dead?” “No.” “Are you dead?”…)

Generational collector, Nursery & Tenured

With a generational collector, the penalty for temporary objects is much lower. Most objects will be allocated into a separate memory region called the Nursery. When the Nursery fills up, only the Nursery will be scanned for live objects. The majority of the short-lived temporary objects will be dead, so this scan will be fast. The survivors will be promoted to the Tenured region.

The Tenured heap will also accumulate garbage, but usually at a far lower rate than the Nursery. It will take much longer to fill up. Eventually, we will still need to do a full GC, but under typical allocation patterns these should be much less common than Nursery GCs. To distinguish the two cases, we refer to Nursery collections as minor GCs and full heap scans as major GCs. Thus, with a generational collector, we split our GCs into two types: mostly fast minor GCs, and fewer slower major GCs.

GGC Overhead

While it might seem like we should have always been doing this, it turns out to require quite a bit of infrastructure that we previously did not have, and it also incurs some overhead during normal operation. Consider the question of how to figure out whether some Nursery object is live. It might be pointed to by a live Tenured object — for example, if you create an object and store it into a property of a live Tenured object.

How do you know which Nursery objects are being kept alive by Tenured objects? One alternative would be to scan the entire Tenured heap to find pointers into the Nursery, but this would defeat the whole point of GGC. So we need a way of answering the question more cheaply.

Note that these Tenured ⇒ Nursery edges in the heap graph won’t last very long, because the next minor GC will promote all survivors in the Nursery to the Tenured heap. So we only care about the Tenured objects that have been modified since the last minor (or major) GC. That won’t be a huge number of objects, so we make the code that writes into Tenured objects check whether it is writing any Nursery pointers, and if so, record the cross-generational edges in a store buffer.

In technical terms, this is known as a write barrier. Then, at minor GC time, we walk through the store buffer and mark every target Nursery object as being live. (We actually use the source of the edge at the same time, since we relocate the Nursery object into the Tenured area while marking it live, and thus the Tenured pointer into the Nursery needs to be updated.)

With a store buffer, the time for a minor GC is dependent on the number of newly-created edges from the Tenured area to the Nursery, not just the number of live objects in the Nursery. Also, keeping track of the store buffer records (or even just the checks to see whether a store buffer record needs to be created) does slow down normal heap access a little, so some code patterns may actually run slower with GGC.

Allocation Performance

On the flip side, GGC can speed up object allocation. The pre-GGC heap needs to be fully general. It must track in-use and free areas and avoid fragmentation. The GC needs to be able to iterate over everything in the heap to find live objects. Allocating an object in a general heap like this is surprisingly complex. (GGC’s Tenured heap has pretty much the same set of constraints, and in fact reuses the pre-GGC heap implementation.)

The Nursery, on the other hand, just grows until it is full. You never need to delete anything, at least until you free up the whole Nursery during a minor GC, so there is no need to track free regions. Consequently, the Nursery is perfect for bump allocation: to allocate N bytes you just check whether there is space available, then increment the current end-of-heap pointer by N bytes and return the previous pointer.

There are even tricks to optimize away the “space available” check in many cases. As a result, objects with a short lifespan never go through the slower Tenured heap allocation code at all.

Timings

I wrote a simple benchmark to demonstrate the various possible gains of GGC. The benchmark is sort of a “vector Fibonacci” calculation, where it computes a Fibonacci sequence for both the x and y components of a two dimensional vector. The script allocates a temporary object on every iteration. It first times the loop with the (Tenured) heap nearly empty, then it constructs a large object graph, intended to be placed into the Tenured portion of the heap, and times the loop again.

On my laptop, the benchmark shows huge wins from GGC. The average time for an iteration through the loop drops from 15 nanoseconds (ns) to 6ns with an empty heap, demonstrating the faster Nursery allocation. It also shows the independence from the Tenured heap size: without GGC, populating the long-lived heap slows down the mean time from 15ns to 27ns. With GGC, the speed stays flat at 6ns per iteration; the Tenured heap simply doesn’t matter.

Note that this benchmark is intended to highlight the improvements possible with GGC. The actual benefit depends heavily on the details of a given script. In some scripts, the time to initialize an object is significant and may exceed the time required to allocate the memory. A higher percentage of Nursery objects may get tenured. When running inside the browser, we force enough major GCs (eg, after a redraw) that the benefits of GGC are less noticeable.

Also, the description above implies that we will pause long enough to collect the entire heap, which is not the case — our incremental garbage collector dramatically reduces pause times on many Web workloads already. (The incremental and generational collectors complement each other — each attacks a different part of the problem.)

Benchmark Code

function bigHeap(N) {
    var result = [];
    for (var i = 0; i < N; i++)
        result.push({ 'number': i, 'prev': result[-1] });
    return result;
}
 
function add(a, b) {
    return [a[0] + b[0], a[1] + b[1]];
}
 
function vecfib(n) {
    var v1 = [0, 0];
    var v2 = [1, 1];
   for (var i = 0; i < n; i++) {
      var v = add(v1, v2);
      v1 = v2;
      v2 = v;
   }
   return v1;
}
 
var t = {};
var iters = 10000000;
t.smallheap_start = Date.now();
var dummy1 = vecfib(iters);
t.smallheap_end = Date.now();
H = bigHeap(10000000);
t.bigheap_start = Date.now();
var dummy2 = vecfib(iters);
t.bigheap_end = Date.now();
 
print("Small heap: " + ((t.smallheap_end - t.smallheap_start) / iters) * 1000000 + " ns/iter");
print("Big heap: " + ((t.bigheap_end - t.bigheap_start) / iters) * 1000000 + " ns/iter");

SUMO BlogThursday, September 25th 2014, is SUMO Day!

SUMO Days are back! In our efforts to provide the best support possible in 2013, we used to gather together on the support forum every other Thursday and try to answer every incoming question on that day. Unfortunately due to many changes in the SUMO org and lack of resources we had to temporarily suspend this. It is now time to bring the SUMO Days back into play!

We’ll be answering questions in the support forum and helping each other in #sumo on IRC all day today, across time zones.

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.

The HelpDesk folks are also joining us, so Rachel (guigs) will be monitoring and ready to answer your questions on #sumo during PST time.

Let’s do it and …Happy SUMO Day!!

Rumbling Edge - Thunderbird2014-09-22 Calendar builds

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

  • Fixed: 501689 – Investigate making storage asynchronous
  • Fixed: 577461 – Status of date invitation in response emails is not shown
  • Fixed: 673089 – Automate Lightning Beta Releases
  • Fixed: 881285 – Remove obsolete nightly builds from nightly/latest-comm-central and nightly/latest-comm-aurora
  • Fixed: 1022120 – Week-view: labels in the day headers don’t change from long to short format
  • Fixed: 1041299 – Sending invitations with configured cc/bcc is broken
  • Fixed: 1045223 – Creating events per drag doesn’t take default status values into account
  • Fixed: 1045417 – Event attendee with a comma in display name gets splitted in two attendees
  • Fixed: 1047227 – Lightning 3.3 no event cancellation button
  • Fixed: 1048878 – Events’ order In the Unifinder doesn’t persist across Thunderbird’s sessions
  • Fixed: 1049341 – Cannot edit meeting attendee list once invite created
  • Fixed: 1054679 – Make the CalDAV provider async safe
  • Fixed: 1055111 – Make calCachedCalendar async safe
  • Fixed: 1059474 – update certificate exception handling in lightning to deal with bug 940506
  • Fixed: 1063085 – Get rid of calIDateTime::jsDate
  • Fixed: 1064552 – Fix postflight_all after the objdir move
  • Fixed: 1067007 – [mozmill] tests do not work after TB build changes
  • Fixed: 1068075 – Fix failure caused by [TypeError: redeclaration of variable ...]
  • Fixed: 1068853 – TEST-UNEXPECTED-FAIL | /builds/slave/test/build/mozmill/testLocalICS.js | testLocalICS.js::testLocalICS

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 - Thunderbird2014-09-22 Thunderbird comm-central builds

Thunderbird-specific: (31)

  • Fixed: 934874 – Thunderbird: Header labels in message reader have last letter of aria-label truncated
  • Fixed: 950335 – “Force encryption” changed by “Use encryption if available” after XMPP wizard
  • Fixed: 966655 – Scrollbar shown for recipient list when empty (involving screen dpi scaling): slightly insufficient default height of msgHeadersToolbar cripples visibility of recipients rows (see Bug 1056404)
  • Fixed: 994655 – Allow ESC key to hide automatical attachment reminder notification bar when focus is in message subject
  • Fixed: 1022209 – msgButton is null error when get new messages button not found on toolbar
  • Fixed: 1024578 – attachment notification no longer collapses duplicate keywords
  • Fixed: 1039452 – Near-perma orange: TEST-UNEXPECTED-FAIL | test-attachment-reminder.js | test-attachment-reminder.js::test_manual_attachment_reminder
  • Fixed: 1039453 – TEST-UNEXPECTED-FAIL | test-charset-edit.js | test-charset-edit.js::test_wrong_reply_charset + test-charset-edit.js::test_no_mojibake
  • Fixed: 1040009 – .mozconfig configure options are ignored if objdir path is absolute
  • Fixed: 1041211 – Toolbox border still visible when all toolbars collapsed
  • Fixed: 1044439 – No rule to make target `/home/josiah/comm-central/mozilla/intl/locale/src/props2arrays.py’, needed by `charsetalias.properties.h’ Build regression due to bug 1038537
  • Fixed: 1046318 – glodaFacetView.css references non-existing attachment-col.png
  • Fixed: 1046328 – update certificate exception handling in thunderbird to deal with bug 940506
  • Fixed: 1046563 – tab bar UI broken on windows classic theme, TB31
  • Fixed: 1052071 – Style of quota indicator not as nice as it used to
  • Fixed: 1054260 – Can not drag main window by title bar
  • Fixed: 1054738 – toolkit/library/target fails to link on Thunderbird MacOSX 10.8 Opt builds
  • Fixed: 1055926 – Mozmill tests don’t run due to no mozinfo
  • Fixed: 1056285 – Titlebar broken in fullscreen on OS X Yosemite
  • Fixed: 1056404 – In addressing widget, only 2 recipient rows shown (including empty line) in spite of mail.compose.addresswidget.numRowsShownDefault=3; (caused by bug 966655)
  • Fixed: 1057708 – Fix bustage caused by ‘Bug 1055281 – Make it an error to add a non-existent directory to LOCAL_INCLUDES’
  • Fixed: 1057759 – Port bug 803812 to TB – “Restart to Update” button label in about dialog is vague
  • Fixed: 1058873 – Permanent Orange: TEST-UNEXPECTED-FAIL | test-account-tree.js::test_account_open_state (Test Failure: a != b: ‘true’ != ‘false’)
  • Fixed: 1059192 – Permanent orange: TEST-UNEXPECTED-FAIL | test_searchSuggest.js | contains an error
  • Fixed: 1060281 – Mac universal build error: “autoconf.mk:3: /config/emptyvars.mk: No such file or directory”
  • Fixed: 1060890 – Static-link the CRT into Thunderbird executable (/mail/app/moz.build). Port Bug 1023941 Part 1
  • Fixed: 1062750 – Double border on main toolbar on Aero
  • Fixed: 1062833 – tooltipUsernames is not defined
  • Fixed: 1063919 – windows bustage: calbasecomps.dll : fatal error LNK1120: 13 unresolved externals
  • Fixed: 1064698 – TEST-UNEXPECTED-FAIL | C:\slave\test\build\tests\xpcshell\tests\mail\base\test\unit\test_windows_font_migration.js | test failed (with xpcshell return code: 0)
  • Fixed: 1065885 – Remove jschar from mail and mailnews

MailNews Core-specific: (35)

  • Fixed: 66763 – Deleting a folder fails when there is already a folder with the same name in Trash
  • Fixed: 324467 – TBird 1.5 fails to automatically filter on message body, if Anti-Virus quarentining is ON(mailnews.downloadToTempFile=true). POP3 not IMAP.
  • Fixed: 332639 – force display of Sender header if S/MIME sender is the signer
  • Fixed: 681632 – crash [@ nsMsgWindow::GetOpenFolder(nsIMsgFolder**)] beginning in version 6 [fixed by bug 679626]
  • Fixed: 799821 – Folders misbehave when LSUB does not return mailbox flags
  • Fixed: 858337 – Implement header parsing in JSMime
  • Fixed: 859269 – upgrading to 20.0b1 hangs on “looking for folders” on uw-imap server (Bad configuration of an UW-IMAP server was unfortunately exposed by unplesant change to ‘LIST “” “*” use again’ by bug 799821)
  • Fixed: 882968 – Clean up and move DEFINES and friends to moz.build in comm-central
  • Fixed: 944526 – Include account name in status bar messages when sending/receiving/getting/downloading/fetching new News messages
  • Fixed: 1005336 – startup or shutdown crash in nsObserverService::RemoveObserver(nsIObserver*, char const*) via nsMsgIncomingServer. reference to nsImapIncomingServer released off the main thread in destructors, due to preferences no longer use threadsafe refcounting
  • Fixed: 1008718 – sending to wrong email (list) if “name” is in address book twice and one of them is a mailing list
  • Fixed: 1020696 – Improve composition tests
  • Fixed: 1037505 – test_pop3MoveFilter.js failure matching messages
  • Fixed: 1046998 – Modify test_copyThenMoveManual.js to use Promises
  • Fixed: 1047981 – Port |Bug 1047924 – When building with ac_add_options –enable-extensions extensions are put expanded into the wrong location in dist/bin| to comm-central
  • Fixed: 1052327 – crash [@ PL_strnchr | nsParseMailMessageState::ParseHeaders() ]
  • Fixed: 1052943 – Move additions to C*FLAGS into moz.build and do not link against the static RTL
  • Fixed: 1053444 – Remove MOZ_APP_COMPONENT_MODULES from comm-central
  • Fixed: 1054357 – Update c-c to address non-backward compatible changes to JS let semantics
  • Fixed: 1054526 – Move LDFLAGS / WIN32_EXE_LDFLAGS out of Makefiles for c-c
  • Fixed: 1054536 – Port *FLAG and related changes to config.mk
  • Fixed: 1054727 – TEST-UNEXPECTED-FAIL | check-sync-dirs.py | build file copies are not in sync, port mozconfig.cache and client.mk changes from m-c to c-c
  • Fixed: 1055867 – Move RCFLAGS and RCINCLUDE to moz.build and hardcode manifest name
  • Fixed: 1056948 – Port bug 559505 to c-c (need to package xulstore)
  • Fixed: 1057478 – Port bug 899585 modifying nsIAlertsService to mailnews
  • Fixed: 1057537 – nsImapMailFolder::OnStartRequest generating error because it is not an nsIRequestObserver
  • Fixed: 1057847 – Fix some more xpcshell-test failures due to warnings in the system logs
  • Fixed: 1059551 – Bayesian spam filter won’t compile since bug 1057912
  • Fixed: 1060258 – Permanent Orange: TEST-UNEXPECTED-FAIL | test_cleanup_msf_databases.js (and some other gloda tests)
  • Fixed: 1060715 – TEST-UNEXPECTED-FAIL | /builds/slave/test/build/tests/xpcshell/tests/mailnews/news/test/unit/test_biff.js | 8 == 9 – See following stack: and other failures
  • Fixed: 1060901 – [tb31.1 only] expand mail list broken for lists whose description is quoted
  • Fixed: 1060959 – comm-central/configure: line 544: test: : integer expression expected
  • Fixed: 1061338 – Port DELAYLOAD_LDFLAGS from bug 944800
  • Fixed: 1062630 – Port bug 1041941 to c-c
  • Fixed: 1063469 – some trivial “assignment to undeclared variable” in TB core.

Windows builds Official Windows, Official Windows installer

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

Mac builds Official Mac

Mozilla Korea[중요] Mozilla 전 제품 보안 패치 필수!

오늘 Mozilla 전 제품에 대해 보안 업데이트(“chemspill”)가 진행됩니다. 이유는 인증서 보안 취약성에 의한 것이며, 이는 익명의 독립 연구자들이 제보해 준 내용에 의한 것입니다.

간단히 설명하여 SSL 보안 웹 사이트에 접근할 때, 가짜 사이트로 가장한 곳을 감지하기 어려운 문제로서 Mozill 전 제품 뿐만 아니라 보안 모듈인 NSS를 사용하는 모든 전 세계 제품에 해당합니다.

해결 방법
현재 사용하시는 Firefox, Thunderbird 및 SeaMonkey 등을 업데이트하십시오. (Nightly, Aurora, Beta 및 정식 출시 등 제품 채널과 상관 없이 모든 버전에 해당됨).

Firefox OS는?
보안 패치는 이미 Firefox 브랜치(1.4이상)에 올라와 있고, 파트너들이 이미 고객들에게 패치를 진행하고 있습니다.

관련 보안 공지는 여기를 참고하십시오.

Meeting NotesMobile: 2014-09-24

Schedule

  • Next merge: 2014-10-13

Topics for This Week

Quality/Stability Check-in
We are past the half way point for Fx35. Make sure you have regressions well in hand for features landing in Fx35.
Remote Debugging
We changed the listening port for remote debugging.
Mobile Platform & Media Goals
https://wiki.mozilla.org/User:Blassey/2014Q4Goals

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.

  • Vikneshwar fixed bug 1066514 – Renamed home_history_list layout to home_list and HistoryListView to HomeList
  • Vivek fixed bug 1066062 – Add additional fields to about:feedback submission and is (still) working on bug 1007436 – Revamp visual design of about:feedback
  • Manu Jain fixed bug 1061944 – Clicking link loses text selection on Android before content script click listener runs
  • zucchini helped update MDN pages about mobile add-on APIs

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>

  • Still working on using SurfaceTexture with MediaCodec
  • Having another go at bug 1059797

Alan K. (ack)

JChen

<Read Only>

Fixed
Working on

GCP

Highlights:

  • WebRTC hardware AEC/NS bug landing
  • Reverse engineering Chrome source for WebRTC sandboxing
  • Intel VP8 Hardware acceleration for WebRTC
  • Reviews
  • Standalone WebRTC

Past:

Present:

Randall Barker

Last Week:

  • Landed bug 1066879 The SSDP implementation can sometimes take too long to discover a device.
  • Landed bug 1048425 Enable support for tab sharing with Roku device.
  • Landed bug 1053426 Fennec crashes when tab sharing is active.
  • Set up private channel with Roku WebRTC Player to enable testing. Contact me privately if you would like access to the channel.

Next Week:

  • Investigate new method for implementing standalone WebRTC.
  • Investigate sending H.264 instead of VP8 video to standalone WebRTC.

Eugen Sawin

Last week

Next week

  • bug 1051654 – APKs for previous versions of Nightly and Aurora stick around in Downloads
  • Janus Proxy
    • Investigate mozjpeg issue
    • Look into <picture> element injection (postponed)
    • Add TCP/socket stats (postponed)

Brian Nicholson

<Read Only>

WesJ

  • Bug 815682 – Lock screen widget/shortcut for Guest Sessions on Android 4.2 and above. Finally landed. Fixing stuff.
  • Bug 1069182 – Unable to exit out of Guest Browsing via system notification
  • Bug 1064669 – GooglePlayServicesUtil.isGooglePlayServicesAvailable takes ~212ms during startup
  • Bug 816318 – Use System download manager on GB+. Landed, but need to add some build flags. Are debating how/when this will ship with people
  • Bug 989094 – Webrtc permissions prompt should remember your last choice. backed out.
  • Bug 1063896 – Regression: missing thumbnails in top sites; thumbnails replaced with tiny Favicons
  • Bug 897711 – [guest] Provide an indicator for guest mode in the UI
  • Bug 1042199 – Widget for searching from error pages
  • Bug 1058150 – Use a restricted profile for guest mode

LucasR

<Read Only>

Last week

Next week

  • More tab strip
  • Some toolbar

liuche

<Read Only>

  • bug 1059792 – First run external intent (test fixing)
  • bug 1014293 – Private browsing contextual hint
  • bug 1011712 – Reader mode contextual hint
  • Continuing work on contextual hints, onboarding

Margaret

Highlights:

  • Search activity v1 final stretch
  • “Firefox Confidential” add-on
  • Some settings refinements
  • Met with AMO team to talk about mobile add-on experience

Past:

Present:

mcomella

<Read Only>

Past
  • bug 1066253 – Display favicon in tab strip instead of toolbar in new tablet UI
  • bug 1069686 – Move tab_strip_* to layout-large
Present
  • Browser toolbar refresh
    • bug 1071267 – Revise door hanger behavior in new tablet toolbar
    • bug 1071878 – Sites without favicons should show an empty rectangle rather than a globe
    • bug 1058909 – Implement new tablet toolbar display mode
    • bug 1019127 – Remove updateChildrenEnabledStateForEditing
    • bug 960746 – Back/forward button state can get out of sync on tablets
  • bug 1020534 – Tablet toolbar icons hard to read on dark lightweight themes
Future
  • Herding bug 941155 (fix talos on mobile to have pageloader tests working in regular mode and nochrome mode) along
  • bug 939350 – Create Python linter wrapper
  • bug 983437 – Delay FHR pruning until the screen is off
  • bug 989441 – Centralized documentation for writing tests
  • bug 1058902 – Implement new tablet browser toolbar editing mode

rnewman

  • VANCOUVER
  • SplitAPK proposal surfaced with Coop and Nick; next steps: a build config. Coop?
  • Reviews.
Fixed
Working on

Martyn Haigh

Last Week

Next Week

BLassey

Fixed
Working on
Looking At

bug 1058363- Show helper app icon before page finishes loading

Antlam

  • Past
  • Upcoming
    • bug 1052004: Toolbar refinements V1 with Lucas
      • Taking a look at how Tablet’s redesign affects Mobile too
    • bug 1063058: Panels UI Clean up
    • Onboarding visuals with Yuan
    • Tablet V1 wrap up
    • Firefox Search V1 wrap up
    • Second screen V1 wrap up

Robin

  • Past
    • Began filing for overflow menu re-org – bug 1069035
    • N2R
    • Mobile Add-ons meeting with Margaret
  • Upcoming
    • continue filing for overflow menu re-org
    • N2R

QA

Garvan

  • Stumbler is back on in nightly, hopefully stays on :)
  • I am heads-down on the pending MozStumbler play store release ATM, hopefully next week I’ll something useful to say about Fennec stumbling.

Feature Focus

Firefox 33 (Beta) – Release: Oct 14, 2014

Firefox 34 (Aurora) – Release: Nov 25, 2014

  • [ON TRACK] Provide a wifi toggle widget on error pages
  • [AT RISK] Tab mirroring (Roku)
  • [ON TRACK] Tab mirroring (Chromecast)
  • [ON TRACK] Toolbar Updates
  • [ON TRACK] Add support for Restricted Profiles (Prefer: safe)
  • [ON TRACK] Share handler overlay (landed but not turned on, nightly & aurora only)
  • [ON TRACK] Form auto-fill improvements, native client-side work
  • [ON TRACK] Kindle-related fixes
  • [ON TRACK] First-run Splash Screen Overlay

Firefox 35 (Nightly) – Release: Jan 6, 2015

  • [PROPOSED] Tablets: tabbed browsing refresh v2
  • [ON TRACK] Sync Tabs panel
  • [PROPOSED] Settings Rewrite (includes:bug 975377
  • [IN PROGRESS] Fatfennec: Minifying JS
  • [ON TRACK] Search activity v1
  • [ON TRACK] Moz Stumbler
  • [PROPOSED] Preferred web content language
  • [PROPOSED] Tablets: tabbed browsing refresh v1
  • [PROPOSED] Change default search engine to Bing
  • [IN PROGRESS] Fatfennec: Splitting the APK – gingerbread phone release
  • [BLOCKED] {{{1}}} Turn on HTTPS for Bing bug 958873

Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2014-09-24

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

  • CHEMSPILL: Shipping today
    • Firefox 32.0.3 (desktop and mobile)
    • Firefox ESR 31.1.1 and 24.8.1
    • Firefox for Android 31.1.0
    • 33 beta7 (out of band)
  • Note: In 33 beta7 we have disabled OMTC to gather stability data. The plan is to re-enable OMTC in beta8.

Firefox Desktop & Platform (Javaun/Chad/Martin)

Summary of Work In Progress
  • You can see the status of the current iteration (35.2) in progress here
Beta (33)
  • Provide info when “Show More Information” is selected for the OpenH264 plugin in the addon manager ( Bug 1039028 )
  • Backslashes included in a location bar input are converted to forward slashes on submission ( Bug 1042521 )
  • Autocomplete drop down list item should not be copied to the search fields when mouse over the list item ( Bug 1060888 )
  • Make the search suggestions popup on about:home/about:newtab more consistent with the main search bar’s popup for 33 ( Bug 1066794 )
  • Picture tag will not ride the trains to release in 33. (Bug 1017875)
Aurora (34)
  • Provide info when “Show More Information” is selected for the OpenH264 plugin in the addon manager ( Bug 1039028 )
  • Backslashes included in a location bar input are converted to forward slashes on submission ( Bug 1042521 )
  • Tab-modal onbeforeunload dialog can automatically be dismissed by navigation ( Bug 1046022 )
  • Theme switcher in customize mode can’t handle many themes ( Bug 1060623 )
  • Autocomplete drop down list item should not be copied to the search fields when mouse over the list item ( Bug 1060888 )
  • Missing inverted panel help icon on Yosemite ( Bug 1060944 )
  • toolkit/themes/osx/global/in-content/common.css uses broken @focusRingShadow@ – focused link styling on about:preferences et al. can’t be parsed correctly ( Bug 1062843 )
  • Disable e10s in safe mode (“Restart with Add-ons Disabled”) ( Bug 1063848 )
  • Make the search suggestions popup on about:home/about:newtab more consistent with the main search bar’s popup for 33 ( Bug 1066794 )
Summary of Recent Landings
  • Loop Firefox Account login UI will be in tomorrow’s Nightly
  • Team landed 82 bugs over the last week, for the first half of the 35.2 iteration.
  • Details of landings from the past week can be seen here
Priorities for the upcoming iteration
  • e10s on Nightly
  • Loop:
    • finalize accounts/contacts work
    • UX: design spike looking into “collaboration” use cases
  • “Panic button”: better-exposed “Clear Recent History” functionality
  • “Reset button on the web”: a mechanism to prompt users to reset Firefox when they try to download Firefox when already running the latest version
  • OS X Yosemite themeing work
  • New tab page performance investigations
  • Places performance work (main thread IO removal)
  • Translation trial followup

Firefox Mobile (Mark/Brad/Jenn)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Uplifts from the past week
Beta (33)
  • Lightweight theme preview is broken ( Bug 887755 )
  • Add telemetry for Settings usage ( Bug 996753 )
  • crash in mozilla::layers::TileClient::GetBackBuffer(nsIntRegion const&, mozilla::layers::TextureClientPool*, bool*, bool) ( Bug 1041744 )
  • Crash in gfxContext::PushNewDT (OOM) with reproducible test-case (reddit.com) ( Bug 1053934 )
  • Do not allow casting UI to appear if the video is an unsupported format ( Bug 1054920 )
  • Handle HomeFragment deletions by panel/type instead of universally ( Bug 1062257 )
  • crash in java.lang.NullPointerException: uriString at android.net.Uri$StringUri.<init>(Uri.java) ( Bug 1062904 )
  • “Learn More” link for the Mozilla Location Service is visible on Beta/Release despite MLS setting not available ( Bug 1063518 )
  • crash in webrtc::ViEInputManager::NumberOfCaptureDevices() ( Bug 1063547 )
  • Regression: missing thumbnails in top sites; thumbnails replaced with tiny Favicons ( Bug 1063896 )
  • Fix OOM crash in gfxAlphaBoxBlur::Init on large blur surface ( Bug 1067998 )
Aurora (34)
  • Regression: Browser menu has width issues ( Bug 1020505 )
  • Regression: No context menu action is invoked on long-tapping some links ( Bug 1062307 )
Landings from the past week
Nightly (35)
  • [guest] Provide an indicator for guest mode in the UI ( Bug 897711 )
  • Add support for element.style["css-property-name"] non-standard extension ( Bug 958887 )
  • Add android:summary text to settings ( Bug 965377 )
  • Remove margins on default home screen panels ( Bug 1022472 )
  • Clearing timer in Firefly shutdown is racy and not needed ( Bug 1042513 )
  • [Roku] Add marketing messages and imagery to the Firefox Roku channel ( Bug 1056040 )
  • Update Remote Tabs static panel styling for portrait phones ( Bug 1063765 )
  • Lost the ability to collapse (and then expand) a device’s tab set in the synced tabs panel ( Bug 1064304 )
  • Default specific prefs for ‘Firefox Confidential’ ( Bug 1064947 )
  • Add “version” (and “channel”?), nix “source” in about:feedback submission ( Bug 1066062 )
  • Can not install web apps; ” A coding exception was thrown and uncaught in a Task. Gecko: Full message: TypeError: aMessage.app.updateManifest is undefined” ( Bug 1066604 )
  • crash in java.lang.IllegalStateException: Error reading list.txt at org.mozilla.search.providers.SearchEngineManager.getAllEngines(SearchEngineManager.java) ( Bug 1067026 )
  • crash in android.content.res.Resources$NotFoundException: Resource is not a Drawable (color or path): TypedValue{t=0x1/d=$ a=3 r=$} at android.content.res.Resources.loadDrawable(Resources.java) ( Bug 1067429 )
  • Android action handler ‘Send tab to': Don’t offer ‘Reading list’ action if it has been turned off (low-memory devices) ( Bug 1067543 )
  • ‘New Tablet UI’ preference available on phones ( Bug 1068005 )
  • [roku] add a ‘beta’ label to the Roku channel until client code hits ‘release’ ( Bug 1068573 )
  • Firefox :: Options popup could not be closed by pressing * btn ( Bug 1068641 )
  • Unable to exit out of Guest Browsing via system notification ( Bug 1069182 )

Market Insights from the Market Strategy Team (Kev)

Worth a Read

  • Lots of talk on Privacy in the last week, with Tim Cook sending out an open letter around Apple’s efforts on Privacy and several stories on how Apple won’t have access to your phone data if encryption is on, followed quickly by Google saying Android L will have a similar feature (although there’s some hard questions on what effect that will have on the Android user base given Android’s fragmentation and update problems). This was then followed by articles going over that just because Apple and Google can’t get your data, law enforcement still can in a number of ways, although they’re not too chuffed about the changes. Long story short, organizations have realized that privacy means something to people, and are working to improve how their products protect users along with improve how those companies represent themselves (market themselves) to users. This will continue to be a big deal, but what the changes actually mean for users remain to be seen.
  • Apple continues to develop Safari on iOS and other platforms, adding capability to its platform to maintain compatibility with the web as an adjunct to its (huge) native ecosystem. They’ve learned some lessons from other competitors including Google and Microsoft, and are ensuring the rendering engine stays modern. Users will need modern devices to take advantage of the updates, and with iOS reported as not working terribly well on the 4S, it’s one of the first big fragmentations Apples mobile platform might see (the iPhone 4S and 4 represent about 20% and 10% of the iPhone’s market respectively), even with iOS adoption hitting 46% in a week.
  • As a follow-up to last week’s Android One overview, BGR India posted a review of Spice’s Android One phone offering, the $100USD Uno, and India Today reviews the Micromax Canvas. In a nutshell: an ok screen, Nexus-like software experience with acceptable performance, crappy battery life, a requirement of external storage to use media, and a price that feels higher than it should be. These are first generation models, and as software and hardware is updated over the coming months we’ll see if they can close the gap perceived between Android One phones and phones like the Moto E (which is a little more expensive, but not much).

Notes


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 SecurityRSA Signature Forgery in NSS

Issue

A flaw in the Network Security Services (NSS) library used by Firefox and other products allows attackers to create forged RSA certificates. Mozilla has released updates to fix this vulnerability and you should apply these updates to ensure your safety on the internet.

Impact to Users

Users on a compromised network could be directed to sites using a fraudulent certificate and mistake them for legitimate sites. This could deceive them into revealing personal information such as usernames and passwords. It may also deceive users into downloading malware if they believe it’s coming from a trusted site.

Status

The following updates have been released for Mozilla client products:

Firefox 32.0.3
Firefox for Android 32.0.3
Firefox for Android 31.1.1
Firefox ESR 31.1.1
Firefox ESR 24.8.1

Thunderbird 31.1.2
Thunderbird 24.8.1

SeaMonkey 2.29.1

Updates are also available for Beta and other development versions of these products.

Most users will receive these as automatic updates. In addition, they are available from our website for those who have disabled automatic updates (or from the Play store in the case of Firefox for Android).

Other products which incorporate the NSS library should upgrade their copy of NSS to one of the following:

NSS 3.16.2.1
NSS 3.16.5
NSS 3.17.1

Credit

We would like to thank the following researchers for reporting this issue:

Antoine Delignat-Lavaud of Inria Paris in team Prosecco
The Advanced Threat Research team at Intel Security

Additional information can be found in our advisory.

Air MozillaTalk with Susan Crawford

Talk with Susan Crawford Book Talk with Susan Crawford: The Responsive City

WebmakerMaker Party: private eye

Create a Wizard of Oz moment by pulling back the curtain to see who’s watching us on the Web. Turn on our Lightbeam tool, visit a  handful of websites, reveal who’s tracking you, and learn how to fight back. You’ll never look at the Web the same way again.

1) Gather

Get together in a room. It can be any room — your kitchen, a classroom, even a Skype chat. All you need is a computer.

2) Make

Walk your participants through these simple steps:
  • a) Install the Firefox add-on called Lightbeam. Using a Firefox browser, go to https://addons.mozilla.org/firefox/addon/lightbeam/ and click on the “Add to Firefox” button. Click the “Install Now” button in the dialog that pops up.
  • b) Go to five of your favorite sites, such as Facebook, YouTube, Netflix, New York Times, and Amazon.
  • c) Now click the Lightbeam icon in your toolbar. Take a look at the graph, which is now populated with the sites you’ve visited (in circles) and all the third parties that are active on those sites (triangles). A third party is another company, like an advertiser, that tracks what you do on sites you visit. You may not have realized it, but you’ve just interacted with all of those third party sites on top of the five sites you actually meant to visit.
  • d) Take this quiz!

Your Score:  

Your Ranking:  

  • e) Fight back! Enable Do Not Track on your Firefox browser. Click the Menu icon in your toolbar. Choose Preferences and click onto the Privacy pane. Set your Tracking preference to “Tell sites that I do not want to be tracked.”
  • f) Know that this doesn’t fully protect you. Companies are starting to support Do Not Track, but you may not notice  any changes initially. Mozilla is actively working with companies that have  started to implement Do Not Track, with others who have committed to doing so soon.    

3) Share

  • Help other people fight by back sharing what you’ve learned. Post a link to this exercise on Twitter or Facebook, send an email to your friends, or just talk to the person standing next to you. Help expose the data tracking that happens across the Internet.
  • BONUS POINTS: reward helpers with badges. If you had helpers or co-organizers you’d like to recognize, they can claim a free Skill Sharer badge here!

Air MozillaProduct Coordination Meeting

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

about:pixelsLogo Survey Results

As I mentioned last week, one of the ultimate goals of our MozID project (including the logo, but not limited to it) is to create design assets and materials that will help Mozillians everywhere communicate more effectively. To that end, it’s incredibly important that we understand how people use what’s available now and what they really need going forward so we can work towards solutions that will be meaningful.

To begin that conversation, we asked for input via a brief survey, and the results are very interesting. Here are a few topline takeaways:

* 91% of respondents have a Mozillians profile; people were pretty evenly distributed around the world.
* 61% currently get design information & assets from the Mozilla Style Guide.
* 82% of people would find easily available visual assets to be helpful.
* 62% would be likely to use an online tool to create their own customized logos.
* 83% would use the new Mozilla logo or a version of it customized for their own communities.
* 12% would prefer their existing community logo.
* Common use cases include websites, t-shirts, event materials and other swag.

If you’d like to dig in deeper, the full set of results is available here.

This has been helpful to me, because one of our ideas is to create an online tool that would allow Mozillians to create their own custom versions of the new logo. We’re not sure how that would work yet – perhaps it would be based strictly on that user’s data, or perhaps there would be more direct opportunities to directly tweak the details to fit your preferences, or perhaps both – but it does seem like there’s interest in such a thing. I know there are some really good community specific logos out there (Mozilla Mexico has one of my favorites, for example), and we want to be sensitive to that legacy, but if we could create a system that would feel both standardized across Mozilla and also unique to each individual or local community that would be really cool.

Many thanks to the 600+ people who responded to our survey. We’ll be asking follow-up questions AND sharing some design ideas soon…watch this space for details!

Air MozillaBugzilla Development Meeting

Bugzilla Development Meeting Help define, plan, design, and implement Bugzilla's future!

WebmakerMozFest 2014: Spotlight on “Art and Culture of the Web”

This is the fourth post in a series featuring interviews with the 2014 Mozilla Festival “Space Wranglers,” the curators of the many exciting programmatic tracks slated for this year’s Festival.

For this edition, we chatted with Kat Braybrooke, Paula Le Dieu, and Erik Nelson, the Space Wranglers for the Art and Culture of the Web track. Participants in this track will explore the programs, practices and inspirations of open and networked digital art forms.

What excites you most about your track?
This is the first time that Mozfest will be featuring the extraordinary role of artists and curators in exploring the affordances of the open web, so we’re really pulling out all the shots to make this track something special. We have more than 25 artists and organisations bringing their work and provocations to Mozfest. Every one of them is creating work that not just invites but requires participation, and as such breaks down the walls between artists and audiences. This is a track that puts you in the middle of artistic and cultural practice with the open web as a lens. From Mozfest’s first ever gallery, OPEN STUDIO, to a set of very hands-on artistic and cultural heritage skillshares, we’re definitely going to be “breaking the Internets” together!

Who are you working with to make this track happen?
We are lucky enough to work with an amazing and eclectic set of artists and organisations at the forefront of arts and culture on the open web this year. Due to space limitations, we could only take on about 25% of the submissions proposed, so the ones we are featuring are of extremely high caliber. Whether it is the extraordinary folks at archive.org collecting web culture and making it available as the creative home of contemporary culture, or new kinds of collaborations between Europeana, London’s National Archives, Creative Commons and Rhizome holding interactive skill-share sessions, or the unique experiences created by ginger coon in Canada and the delightful playfulness of Parapara in Japan, the global workshops and experiences on offer will truly help everyone realise their own creative potentials.

How can someone who isn’t able to attend MozFest learn more or get involved in this topic?
Join us at our track’s hub where we will be collecting together the tools, featuring artist and partner collaborations and keep everyone up to date about the track leading up to, during and following Mozfest. We can’t wait to see the creative and crazy things everyone comes up with together in London!

Inspired?

Head on over to the MozFest site to register!

Meeting NotesMozilla Platform: 2014-09-23

Need To Know

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

Notices/Schedule (lmandel)

Next Merge: October 13, 2014 Next Release: October 14, 2014
Trains
Central: 35 Aurora: 34 Beta: 33 Release: 32
  • Desktop 32.0.2 shipped last Thursday, included a fix for a start-up crash. Crash rates on release are now back to pre 29 levels. (That’s good.)
  • 33 beta6 shipped today (desktop and mobile)
  • only 3 betas left! We need your fixes. See the 33 tracked bugs list

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.)

OrangeFactor (ryanvm)

  • Past week’s OrangeFactor: 4.17 (last week: 3.66).
  • Android and B2G continue to dominate the top of the list. bug 906716 (B2G emulator “timed out after 1000 seconds of no output”) is #1 by a 2:1 margin.
  • 17 intermittent failures fixed in the last week – List (16 the week prior) – Thanks!.
    • Thanks to Rail Aliiev for fixing bug 1047760, a long-running issue that affected all builds running on AWS.

MemShrink (njn)

  • No update.

Stability (kairo)

<Read Only>

  • Release crash rates have improved significantly since we released 32, almost back to levels we had before shipping 29
  • Beta crash rates are still ~25% worse than they were right before we shipped 32, we’ll try to turn off OMTC and see if that makes up for the difference and which crash signatures this affects. In 34, we’ll have better tooling to analyze the crashes around OOM, which are a large chunk of those (somewhat expected as OMTC needs more memory).
  • Desktop Nightly shows a number of e10s crashes. Please let us know if you see crashes of the whole browser at startup, as those are must-fix before enabling it.
  • Android Beta needs someone in GFX to look into getting a patch for bug 1067018.
  • Android Nightly needs someone to fix ImageLib bug 1069369, which accounts for >50% of our crashes there.

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.)

A*Team (jgriffin)

  • The A-Team is working on Q4 goals. If you’d like us to work on something in Q4, and it doesn’t appear anywhere on our Trello board at https://trello.com/b/3BjXQCEp/projects, please contact me!

Developer Tools (prouget)

<Read Only>

  • devtools overhead (Fx Desktop E10S & FxOS): from 7-8MB to 2-3MB.
  • Simulator 2.2 released. 2.0 and 2.1 updated.

Electrolysis (e10s) (blassey/blake/jimm/cpeterson)

  • We’re currently working on Milestone 3 bugs – M3 Bug List
  • Please help dogfood e10s in Nightly!
  • Notable bugs fixed in the last week:
    • bug 899347 – Click-to-play support
    • bug 1067164 – Opening external links in e10s results in empty tab (regression, fixed by backout)
    • bug 1067351 – Fixed file upload crash (e.g. attaching patches to Bugzilla!)
    • bug 1064847 – Fixed YouTube video playback
    • bug 1068210 – Crashed tab’s “Try Again” button reloads just the current page to avoid browser hang

Firefox Desktop (gavin)

Summary of Work In Progress
  • You can see the status of the current iteration (35.2) in progress here
Summary of Recent Landings
  • Loop Firefox Account login UI will be in tomorrow’s Nightly
  • Team landed 82 bugs over the last week, for the first half of the 35.2 iteration.
  • Details of landings from the past week can be seen here
Priorities for the upcoming iteration
  • e10s on Nightly
  • Loop:
    • finalize accounts/contacts work
    • UX: design spike looking into “collaboration” use cases
  • “Panic button”: better-exposed “Clear Recent History” functionality
  • “Reset button on the web”: a mechanism to prompt users to reset Firefox when they try to download Firefox when already running the latest version
  • OS X Yosemite themeing work
  • New tab page performance investigations
  • Places performance work (main thread IO removal)
  • Translation trial followup

Firefox Mobile (snorp/blassey/mfinkle)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Landings from the past week
Nightly (35)
  • [guest] Provide an indicator for guest mode in the UI ( Bug 897711 )
  • Add support for element.style["css-property-name"] non-standard extension ( Bug 958887 )
  • Add android:summary text to settings ( Bug 965377 )
  • Remove margins on default home screen panels ( Bug 1022472 )
  • Clearing timer in Firefly shutdown is racy and not needed ( Bug 1042513 )
  • [Roku] Add marketing messages and imagery to the Firefox Roku channel ( Bug 1056040 )
  • crash in java.lang.NullPointerException: uriString at android.net.Uri$StringUri.<init>(Uri.java) ( Bug 1062904 )
  • Update Remote Tabs static panel styling for portrait phones ( Bug 1063765 )
  • Regression: missing thumbnails in top sites; thumbnails replaced with tiny Favicons ( Bug 1063896 )
  • Lost the ability to collapse (and then expand) a device’s tab set in the synced tabs panel ( Bug 1064304 )
  • Default specific prefs for ‘Firefox Confidential’ ( Bug 1064947 )
  • Add “version” (and “channel”?), nix “source” in about:feedback submission ( Bug 1066062 )
  • Can not install web apps; ” A coding exception was thrown and uncaught in a Task. Gecko: Full message: TypeError: aMessage.app.updateManifest is undefined” ( Bug 1066604 )
  • crash in java.lang.IllegalStateException: Error reading list.txt at org.mozilla.search.providers.SearchEngineManager.getAllEngines(SearchEngineManager.java) ( Bug 1067026 )
  • crash in android.content.res.Resources$NotFoundException: Resource is not a Drawable (color or path): TypedValue{t=0x1/d=$ a=3 r=$} at android.content.res.Resources.loadDrawable(Resources.java) ( Bug 1067429 )
  • Android action handler ‘Send tab to': Don’t offer ‘Reading list’ action if it has been turned off (low-memory devices) ( Bug 1067543 )
  • Fix OOM crash in gfxAlphaBoxBlur::Init on large blur surface ( Bug 1067998 )
  • ‘New Tablet UI’ preference available on phones ( Bug 1068005 )
  • [roku] add a ‘beta’ label to the Roku channel until client code hits ‘release’ ( Bug 1068573 )
  • Firefox :: Options popup could not be closed by pressing * btn ( Bug 1068641 )
  • Unable to exit out of Guest Browsing via system notification ( Bug 1069182 )

Firefox OS Connectivity (vchang)

<Read Only>

  1. https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2014-09-23

Firefox OS Devices/Porting (ericchou)

<Read Only>

  • Bluetooth (members: Shawn Huang, Ben Tian, Jamin Liu, Jocelyn Liu)
    • BLE API discussion on dev-webapi
    • NFC workweek(9/15 ~ 9/19) @ Berlin. Shawn and Jamin gave two talks related to BT/NFC applications.
    • Current status of PTS test for Firefox OS 2.1
      • bug 1064733 – BlueZ – All bugs have been resolved fixed and verified.
      • bug 1064739 – Bluedroid – 7 blockers.
    • bug 1062697 – AVRCP metadata doesn’t update on carkit – patch ready (2.0?)
  • Media Playback (members: Bruce Sun, Blake Wu, Star Cheng)
    • bug 1053051 – When operate I-frame seek, video player position was not changed – r+ (2.0?)
    • bug 1059679 – BT headset can not play music when do some operates – WIP (2.0?)
    • bug 1033903 – Use GraphicBuffer with android::MediaCodec to reduce the overhead of memcpy video data – WIP (2.2 feat?)
  • Device Storage (members: Alphan Chen, Eden Chuang)
    • bug 1060196 – Should forbid ejecting SD card when user is playing music which is stored in SD card – landed (2.1+)
    • Next week team will start to do the initial survey of supporting “Apps on SD card” for Firefox OS. The target will be 2.2.

Firefox OS RIL (htsai)

<Read Only>

  1. https://wiki.mozilla.org/TPE_RIL_team/2014-09-23#Team_memebers.27_updates

GFX (milan)

<Read Only>

  • Work week: OMTC+Tiling+APZ

Media (mreavy)

<Read Only>

  • Loop had a server failure over the weekend (database full). Making sure that doesn’t happen again
  • Continuing to clean up OpenH264 and Screensharing issues for launch in 33
    • Set initial default allowed_domains for screensharing; created a process for adding people
      • We want the need for this to go away as soon as possible
  • b2g 2.0 webrtc whack-a-mole
    • Waiting on a drop with new DSP firmware to allow H.264 resolution changes
    • Hardware AEC support looks like it will work
  • Working on hooking WebAudio to WebRTC PeerConnection inputs (outputs already work)
    • Chrome has the opposite problem ATM
  • Prototype patch to up getUserMedia audio sample rate to 32K (want 44100/48000)

Necko (dougt/jduell)

<Read Only>

  • HTTP/2 is now on aurora, so far things are sticking and going well!
  • Alt-svc support almost done (bug 1003448)
  • Network change detection very close–hoping it will land any day now :) (bug 939318)
  • Network predictor also getting close but probably won’t be done by end of Q3

Performance (vladan)

Fixes:

  • bug 1038342: Firefox will now trigger a crash if shutdown hangs for more than a minute
  • bug 937306: Properly fixed our WaitMessage use on Windows. This should address user reports of pages not loading unless the user is moving the mouse. Needed for OMTC to be enabled on Windows for Firefox 33.
  • bug 768802: Some good news: Flash 15 fixed a long-standing Flash bug that caused it to steal browser focus whenever the plugin process was launch or relaunched. This bug has plagued users for over 2 years, ever since Flash protected-mode was released.
  • bug 918317: A C++ version of AsyncShutdown is now available
  • bug 998863: Patch for fixing #1 cause of Firefox multi-second hangs (initialization of out-of-process plugins) will land soon. Please keep an eye out for plugin-related crashes over the next month. Contact aklotz or vladan if you spot any

Telemetry:

  • bug 1045108: Unclaimed Telemetry probes will expire in Firefox 40! Please correct the expiration version yourself or comment in bug 1045108, or contact rvitillo or vladan. The unclaimed probes will stop collecting data!
  • bug 1067372: We’re adding new meta fields to Histograms.json for better automated regression detection

Misc:

Ongoing perf work:

  • The performance of the new tab animation and the newtab page have regressed considerably since Australis first landed. Fx-team and Perf team will be meeting to work on this in MV on September 29th. See bug 1059558 etc.
  • Work on improving performance of the Places system together with the fx-team bug 834545, bug 1043863, etc
  • Measuring impact of GC & CC on Firefox UI animation smoothness bug 1017055

Seceng (tanvi)

  • Added load information (loadInfo) to all gecko created channels bug 1038756

Roundtable

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

<Read only beyond this point>

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

10:36 KaiRo: Sylvestre, lmandel: I also filled in the bug number for the AsyncShutdown stuff and nominated it for tracking
10:39 bsmedberg: KaiRo: did you ping yoric about it?
10:39 lmandel: KaiRo: Thanks. I'm going to mention the crash level in the engineering meeting unless you want to do it.
10:43 KaiRo: bsmedberg: I did and he didn't respond in #developers so I put a ni? on him right now, as well as on gfritzsche, who worte a patch around shutdown stuff in the location where this is in
10:43 KaiRo: lmandel: sure, if you do that, I can go read-only for this meeting, I think
10:43 bsmedberg: ok thanks
10:45 KaiRo: Bas is asking who it was he should ping for the OMTC disabling patch
10:46 KaiRo: bsmedberg: who did offer to help Bas with the disabling patch?
10:46 bsmedberg: I don't know
10:47 KaiRo: so it isn't just me who doesn't remember that part
10:48 KaiRo: oh, I guess they talked about RyanVM
11:01 KaiRo: cpeterson: I'm going read-only for today's meeting even though my written update isn't completely short, but lmandel will cover the important desktop beta part
11:01 cpeterson: KaiRo: ok
11:01 lmandel: KaiRo: desktop beta?
11:02 KaiRo: lmandel: the stuff around OMTC is what you wanted to mention, right? or the release part?
11:02 lmandel: KaiRo: Oh. OMTC.
11:02 tanvi: is the physical room in sf warfield?
11:02 lmandel: KaiRo: I was going to just mention that crash rates on release are back to pre 29 levels.
11:02 lmandel: KaiRo: I can talk about OMTC as well.
11:02 RyanVM|sheriffduty: lmandel: just pushed to beta, fwiw
11:02 KaiRo: lmandel: ah, ok. not sure if it's needed in detail as we just discussed it with gfx anyhow
11:05 lmandel: RyanVM|sheriffduty: Thanks
11:05 vladan: lmandel: what were the causes for the spike in crashes? 
11:05 RyanVM|sheriffduty: i'm here, but fine with not doing an audio update
11:05 RyanVM|sheriffduty: apparently forgot to save his update on the wiki too
11:07 cpeterson: RyanVM: do you want us to jump back to you?
11:09 jesup: autocrash on hanging shutdown: \o/
11:10 vladan: jesup: :)

Engineering Meeting Details

  • Tuesday 2014-09-2311:00 am Pacific Standard Time
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
  • 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

Software CarpentryFeedback from Imperial College London

On 16-17 September, EPCC's ARCHER headed down to Imperial College London to run a Software Carpentry bootcamp. My colleague Arno Proeme made his instructor debut, covering version control and Git and good programming practice, while I covered shell hints and tips, automation and Make, and testing.

We had 31 attendees stay the course, out of the 34 who were present at the outset. Most attendees were from Imperial College London and the Institute of Cancer Research (many of whose peers had attended the Greenwich bootcamp last October), with a few attendees from other London institutions (Queen Mary University of London, University of Greenwich, University College London, King's College London, Royal Holloway, University of London) and a couple coming in from Birmingham and Oxford.

The good points and bad points, written on sticky notes during the final session, were as follows:

Good points Bad points
Content was relevant to my work Should be more targeted to people with similar knowledge, background (a mix of backgrounds makes it too hard or too easy for some people to follow)
Interesting and very useful topics More hands on exercises to apply what was learned would have been helpful
The selection of topics was great as I have found myself trying to learn things like git or software testing for quite some time but always in the rush of some deadline No syntax highlighting on projector code
Lots of things covered More use of Etherpad for copying code please
Wide range of tools introduced I sometimes got behind due to missing/wrong syntax
Useful range of tools introduced SQL?
Examples used for teaching were interesting in that they expanded my views of what the taught tools had to offer Python bit slow
Git Too few days
Learned Git No pens :( [for the sign-in form and sticky notes]
Good pace of teaching
Nice and helpful instructors
Friendly teachers
Free of charge!!! :-)
I believe this is a greatly important initiative Thanks!

A number of attendees also commented via e-mail afterwards how they found the bootcamp both informative and enjoyable. One stated that they

took quite a bit away from it and will try implementing these practises and testing habits into my research (looking forward to getting over the learning hump :) )

There were a lot more set-up issues for this bootcamp than for the last bootcamp I was on at Cranfield in July. During the Git session, one attendee had never used "vi". Running the Software Carpentry installer to install "nano" revealed that the attendee had not installed Python. Other attendees also had problems with editors not being installed, or not being available on the PATH. Another complication arose from Anaconda Python and Canopy Python both being present on one attendee's machine which caused ipython to stop working, though, fortunately Python itself worked fine. One attendee had problems with Anaconda Python clashing with their native Python installation, which was resolved by manually setting the PATH. One attendee had the software installed on a remote machine which they could access, but their remote machine could not connect out to the web!

Some of these could have been averted had attendees installed, or at least tried to install, the required software, and run the Software Carpentry installation test scripts before they arrived. They did not do so despite at least 3 e-mails and a 30 minute pre-Welcome slot on the first day for egistration and software set-up. Next time we'll schedule the software set-up after the Welcome session.

The other issue was solely my responsibility - trying to cram too much in and sacrificing practicals for time, instead walking attendees through these via live coding. Next time I'll be more diligent in giving attendees time to try things by themselves, trying to reinforce a few concepts more deeply than covering many but with no opportunity for self-guided problem solving.

Arno, and our EPCC colleagues Mario Antonioletti and Alistair Grant will be attending the Software Carpentry: Instructor Training at TGAC this October. The four of us will then run a Software Carpentry workshop, sponsored ARCHER and PRACE, in Edinburgh in early December.

Mozilla SecurityPhasing Out Certificates with SHA-1 based Signature Algorithms

Many of the certificates used by secure websites today are signed using algorithms based on a hash algorithm called SHA-1. The integrity of the hash algorithm used in signing a certificate is a critical element in the security of the certificate. Weaknesses in hash algorithms can lead to situations in which attackers can obtain fraudulent certificates. Mozilla, along with other browser vendors, is working on a plan to phase out support for the SHA-1 hash algorithm.

SHA-1 is nearly twenty years old, and is beginning to show its age. In the last few years, collision attacks undermining some properties of SHA-1 have been getting close to being practical. Collision attacks against the older MD5 hash algorithm have been used to obtain fraudulent certificates, so the improving feasibility of collision attacks against SHA-1 is concerning. In order to avoid the need for a rapid transition should a critical attack against SHA-1 be discovered, we are proactively phasing out SHA-1.

We encourage Certification Authorities (CAs) and Web site administrators to upgrade their certificates to use signature algorithms with hash functions that are stronger than SHA-1, such as SHA-256, SHA-384, or SHA-512. Mozilla’s CA Certificate Maintenance Policy section 8 says: “We consider the following algorithms and key sizes to be acceptable and supported in Mozilla products: SHA-1 (until a practical collision attack against SHA-1 certificates is imminent) …” NIST Guidance recommended that SHA-1 certificates should not be trusted beyond 2014. However, there are still many Web sites that are using SSL certificates with SHA-1 based signatures, so we agree with the positions of Microsoft and Google that SHA-1 certificates should not be issued after January 1, 2016, or trusted after January 1, 2017. In particular, CAs should not be issuing new SHA-1 certificates for SSL and Code Signing, and should be migrating their customers off of SHA-1 intermediate and end-entity certificates. If a CA still needs to issue SHA-1 certificates for compatibility reasons, then those SHA-1 certificates should expire before January 2017. More information is available in Mozilla’s list of Potentially Problematic CA Practices.

We plan to add a security warning to the Web Console to remind developers that they should not be using a SHA-1 based certificate. We will display an additional, more prominent warning if the certificate will be valid after January 1, 2017, since we will reject that certificate after that date. We plan to implement these warnings in the next few weeks, so they should be appearing in released versions of Firefox in early 2015. We may implement additional UI indicators later. For instance, after January 1, 2016, we plan to show the “Untrusted Connection” error whenever a newly issued SHA-1 certificate is encountered in Firefox. After January 1, 2017, we plan to show the “Untrusted Connection” error whenever a SHA-1 certificate is encountered in Firefox.

Please check your SSL and Code Signing certificates and replace any which use the SHA-1 hash algorithm, and contact mozilla.dev.security.policy if you have comments or concerns.

Mozilla Security Engineering Team

Air MozillaGiovanni Charles "Hello there, have some user experience"

Giovanni Charles Giovanni Charles, "A UX centric approach to re-inventing the FTU" Nicola Greco, "Exploiting the Remote Debugger and WebIDE"

Air MozillaFirefox Anywhere

Firefox Anywhere This fun video was created by Miss Yuna Jong, a designer in Mozilla Taipei office, Taiwan.

WebmakerWebmaker and the MDN team up

Mozilla WebMaker and the Mozilla Developer Network (MDN) are both projects that focus on the importance of web literacy. They do so in different ways, with Webmaker focused on teaching the web through making and the MDN focused on helping people learn the web. But Webmaker and MDN are two sides of the same coin, and as such, we’ve teamed up to help each other expand our offerings.

To begin building bridges, Webmaker is supporting the MDN in developing a learning area on MDN for beginners who wish to learn the web on their own.

The MDN Learning Area aims to provide simple but complete documentation around many of the Web Literacy Map’s skills, written to help beginners learn the web. It is divided into a glossary of terms and a set of learning articles.

The glossary provides simple definitions for the jargon techies use. This glossary will help those who are interested in the web to start a journey on any topic. Learning the vocabulary of the web is one of the first steps towards web literacy.

The learning articles provide more in-depth information for self directed learners. We are beginning to organize various articles into pathways, which will help guide learners towards a specific goal.

To help support learners, we’re building and improving tools like:

We are currently working to build out the MDN articles that can lead a learner through the many resources the Webmaker and MDN communities have. We are looking for people to contribute to the MDN wiki. Help us make sure our beginner learning content is engaging or help by building projects that focus on specific Web Literacy skills using the Webmaker toolset.

Everything you need to know to help build the Learning Area on the MDN is available on MDN. If you have questions or comments, do not hesitate to reach us on our mailing lists or IRC channels:

  • MDN: dev-mdc@lists.mozilla.org or #mdn on irc.mozilla.org
  • WebMaker: webmaker@lists.mozilla.org or #teachtheweb on irc.mozilla.org

See you soon :)

Meeting NotesMozilla Project: 2014-09-22

All-hands Status Meeting Agenda

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

Friends of Mozilla

Upcoming Events

This Week
  • QE (Quality Engineering) is relaunching the Testdays program with a new focus on mentorship – activities are scheduled all week – please join us in the #qa channel on irc.mozilla.org
Tuesday, 23 September
Wednesday, 24 September

Homebrew Website Club Meetup

  • Portland (@MozPDX) and San Francisco (@MozSF)! (CHI & MSP off this week)
  • 17:30-18:30 Writing Hour
  • 18:30-19:30 IndieWeb discussions and hack night

Are you creating your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy?

If so (or you want to!), come on by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project…

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

Mozillians Town Hall – Brand Initiatives

Supporting Cultural Heritage Open Source Software

  • Sept 24 and 25, happening in Atlanta, GA, USA and online
  • Mozillian Jennie Rose Halperin will be speaking
Thursday, 25 September
Friday, 26 September

PyCon India 2014

  • Sep 26-28 in Bangalore, India
  • Mozillian Abdul Rauf helping to organize
Saturday, 27 September

Accessibility Camp Toronto

  • Toronto, Canada
  • Mozillian David Bolter attending
  • Mozilla sponsorship

Project Status Updates (voice updates)

Firefox

Speaker Location: SF (Eric)

Firefox For Android

Speaker Location: remote (mfinkle)

  • Guest browsing indicator in the System Notification area
  • File downloads are being added to the System Download Manager
    • Costs an Android permission
    • Interactions might to be improved
Firefox OS

Speaker Location: MTV (Asa Dotzler)

  • Firefox OS launched in Bangaladesh! Grameenphone (local Telenor operator/carrier) lauched the (Symphony manufactured) GoFox F15 for approximately $60 last week.
  • Mozilla is beginning transition to KitKat builds for the Flame. Will be posting a KitKat-based Firefox OS 2.0 “testing” build to the MDN Flame page this week.
  • This last week, about 100 people checked in just over 200 fixes to Firefox OS. First time contributors to Firefox OS this week included:
    • Zhenqing Liu <zhenqing.liu@spreadtrum.com> fixed bug 1021838 FX OS crash in nsWifiMonitor::Onready(unsigned int, nsIWifiScanResult**)
    • Phil Ringnalda [philor] <philringnalda@gmail.com> fixed bug 968645 Forms mochitests disabled on b2g desktop
    • Lars T Hansen [lth] <lhansen@mozilla.com> fixed bug 1068539 Gecko not booting anymore due to “bad serialized structured data (unhandled typed array element type)”
    • Goutam <goutamnair7@gmail.com> fixed bug 1023259 The contact number is shown incompletely in the contact detail screen of SMS conversion when the contact phone label is more than 19 characters.
    • gauravmittal <gauravmittal1995@gmail.com> fixed bug 1057795 Clean up MozL10n API use in Cost Control
    • Andreas Larsson <andreas3.larsson@sonymobile.com> fixed bug 1069810 Homescreen application does not handle basic authentication in icon urls.
  • Foxtrot applications evaluated. Results to be sent out to all applicants today or tomorrow. Phone shipments still TBD — still waiting on builds.
  • Mozilla has received 500 VIA Vixen tablets for the Tablet Contribution Program. The TCP coordinators have just begun planning for the application process.
Content Services

Speaker Location: NYC (Sean Bohan)

  • Tiles
    • Tiles continues in Beta
    • Tiles Delivery Service testing GeoIP support for per country Tiles
    • The l10n team has done an amazing job getting Mozilla tiles translated, with 34 countries completed in less than 2 weeks. Thanks to CHoffman, Pike, MatJaz, the l10n team and the contributors who all helped

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
William Reynolds Product manager for Community Tools Get vouched, vouch others on Mozillians.org Mozilla SF No Display this blog post Wiki with FAQ, Original announcement about vouching changes
Michelle Thorne Webmaker Mentor Team Maker Party 2014. Party don’t stop! Mozilla Toronto Yes File:Makerparty 2014 recap.pdf 127K Webmakers host over 2513 Maker Parties
Anthony Duignan-Cabrera The Open Standard The Open Standard Mozilla NYC No No https://wiki.mozilla.org/The_Open_Standard

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
Johan Lorenzo Tony Chung Mountain View Paris Mobile QA
Francisco Picolini Robyn Chau Mozilla Las Vegas Madrid Community Events

<meta>

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

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

IT

Vidyo has released Vidyo Desktop v3.3.0 (27) with the below added features and fixes. This release has already been tested within IT and is ready for a second round of testing and feedback. If you would like to help test, please use the download links below to install the client and add your feedback to the feedback doc also linked below. Please update us as we would like to release the client to all of Mozilla by Monday 9/28 or 10/6 depending on feedback received.

Note: after upgrading, a pop-up will appear saying that you do not have a current version. Please select “Not Now” and the do not remind me checkbox.

Features
Join a conference with camera, mic and/or speakers muted
Join a conference with your full screen shared and camera, mic, speakers muted
Easier access to your rooms public link via client UI
Many bug fixes for Windows, Mac and Linux

Download Links
OS X: https://drive.google.com/a/mozilla.com/file/d/0BzyYWLVB7bEcZnd6M2RnNWhybVU
Windows: https://drive.google.com/a/mozilla.com/file/d/0BzyYWLVB7bEcXy11aWhoTzNzRVk
Ubuntu: https://drive.google.com/a/mozilla.com/file/d/0BzyYWLVB7bEcQlIzdmppYmJKQ00
Ubuntu64: https://drive.google.com/a/mozilla.com/file/d/0BzyYWLVB7bEcNXZYeDBVcG9iT00
RPM: https://drive.google.com/a/mozilla.com/file/d/0BzyYWLVB7bEcNkhRcFZJOURVenc
RPM64: https://drive.google.com/a/mozilla.com/file/d/0BzyYWLVB7bEcVE5pU3RmRXJPYjQ

Feedback Doc https://docs.google.com/a/mozilla.com/spreadsheet/ccc?key=0AjyYWLVB7bEcdEYxaldFYXVqcGpxdW02dGNYUDN5QVE&usp=sharing

Automation & Tools
bugzilla.mozilla.org

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

  • bug 1021902 You can now see a history of a review’s requests (time taken, etc). Look for the “Review History” link on their profile page.
  • bug 1052851 It’s now possible to search for bugs where the assignee hasn’t logged in to Bugzilla for a while (eg. http://mzl.la/1AQRMd7)

All changes.

Engagement
Web Compatibility

Web Compat Summary

  • closed 104 Desktop issues, 7 Mobile issues
  • opened 4, Desktop issues, 5 Mobile issues
  • Started a discussion about our future plans for 2015, and quarter goals in 2014.
  • We had a temporary issues with GitHub which closed all the Webcompat repos for a couple of hours, but came back on after we contacted them.

  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 8600
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600

Software CarpentryLearning Goals

A few weeks ago, Greg Wilson asked me how to better express the learning objectives listed in the Software Carpentry lessons. My main concerns with the existing goals are that they focus too much on specific skills, rather than attitude changes, and is that they are generally stated as lesson descriptions (more like instructor goals or a lesson outline) rather than as learning goals for participants.

One improvement would be to frame things in terms of what will help someone change their practice soon, with less focus on skill mastery. If nobody can write a nested loop or use Git by the end of the workshop, but everybody adopts a sensible research workflow within a few months, the workshop ought to be considered a huge success. If everyone learned all of Python in two days and never used it in their research work, it would be a failure. These goals are hinted at in some of the topic-level pages for lessons and appear in the Instructor Guide, but aren't clearly set out in the lessons themselves.

For example, the lesson on conditionals in Python says:

The final example asks them to build a command-line tool that works with the Unix pipe-and-filter model. We do this because it is a useful skill and because it helps learners see that the software they use isn't magical. Tools like grep might be more sophisticated than the programs our learners can write at this point in their careers, but it's crucial they realize this is a difference of scale rather than kind.

That's great, but it isn't clear to instructors how the activities support these goals or how they'll know if this is being achieved. Here's a clumsily-worded alternative:

With reference to the Software Carpentry online resources, official documentation (man pages for Unix stuff, docs.python.org for Python, etc.) and appropriate internet searching (e.g., Stack Overflow), the participant will be able to choose a data structure for collecting information when looping over a file (e.g., a list or dictionary) that works and yields readable code.

In addition, the lesson should articulate some very specific skill goals where all (or at least most) participants will enjoy some success during the workshop. This is very important for motivation to continue with learning rather than shut down. For example:

By the end of this lesson, participants will be able to use Python to pattern-match lines in a simple CSV file containing headers and print results as output.

Goals like these give something meaningful to assess during the lesson to see if the immediate skill lesson has been successful (where I'm using the word "assess" in the broad sense: it's nice for later reporting if there are recorded observations or test/quiz data from students, but at a minimum the helpers will see if everyone has processed the file as described). Meanwhile, including the attitude/approach goals will emphasize that the real value of the workshop is an overall change in research practice.

The smaller goals also give a bit more of a sense of lesson size, which is very helpful if one wants to start chaining together or remixing lessons. Some course design strategies suggest a hierarchy of goals, such as:

  • course goals: a few broad statements relating to the purpose and philosophy of the course (for Software Carpentry, goals related to more productive research and programming in general);
  • topic goals: more detailed than course goals, these are basically a way of grouping the more specific goals (e.g., learners will be able to automate tasks associate with plain text files); and
  • learning goals (or lesson goals): splitting the topic goals into 10-15 minute chunks to help get a better sense of how much time it might take to cover everything.

Some ideas for doing this are on pages 8-12 of A Self-Directed Guide to Designing Courses for Significant Learning (a resource used in UBC's local course design workshop).

A lot of these changes are moving away from "I want them to know this thing once I explain it" to "I want them to be able to do this measurable thing". There are more examples, including some from introductory programming courses, in these two documents (which are taken from this page). I would also recommend some of these ideas for learning goals for the instructor training. It gives the various lesson blocks clearer purpose, which can help with passing materials on to new instructors.

QMOThe end of #testday

In our effort to relaunch (and reinvigorate) Testdays, it was decided that we would try moving our primary communication channel back to the #qa channel. The reason for this decision was to bring people to where we live and work day to day, and to not have event participants cordoned off from the rest of us.

We originally thought we should shut down #testday and auto forward people to #qa immediately but I’ve decided it would be prudent to have a transitional period. This transitional period begins now.

The #testday channel will be shut down on October 1, 2014  and all traffic forwarded to #qa. If you’re running an event between now and then, I encourage you to begin directing your people to use #qa.

If you have questions or concerns regarding this decision, feel free to speak up in my dev-quality post.

Meeting NotesMobile: 2014-09-17

Schedule

  • Next merge: 2014-10-13

Topics for This Week

Tablet UI
The new WIP tablet UI refresh has started landing in Nightly
Startup Profiling
We started looking at startup profiles again

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.

  • Dominique Vincent fixed bug 1058027 – about:home is unresponsive to hardware menu button on returning to main activity on 2.3 devices and bug 1062904 – NPE in “Set image as”
  • Manu Jain fixed bug 1066320 – Crop lightweight theme image if it’s larger than the displayable area
  • Mark Capella fixed bug 1044940 – Favicons in the bookmarks table should be read and written correctly and bug 1064657 – Add testSelectionHandler test to ensure readOnly input elements can’t be cut

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>

  • {bug|1037147} – Remove SharedTextureHandle and friends
  • Working on getting MediaCodec decoder landable. Fighting YUV conversion issues.

Alan K. (ack)

  • waiting for QA cycle on cloudsync, will uplift when that’s done
  • demoed adhoc/mesh on fxos last friday for the foundation/webmaker guys
  • starting on standalone webrtc with gcp
  • (taking some time this week to blog)

JChen

<Read Only>

Fixed
Working on

GCP

<Read Only>

Fixed
Working on
  • Standalone WebRTC reviews
  • WebRTC standboxing
  • B2G DSP based echo cancellation
  • SafeBrowsing update behavior

Randall Barker

Last Week:

  • Posted patch for bug 1066879 The SSDP implementation can sometimes take too long to discover a device.
  • Fixed standalone WebRTC after rebase.
  • Investigating bug 1053426 Fennec crashes when tab sharing is active (No leads yet)

Next Week:

  • Continue investigating bug 1053426 Fennec crashes when tab sharing is active.
  • Land bug 1066879 The SSDP implementation can sometimes take too long to discover a device.
  • Set up private channel with Roku WebRTC Player to enable testing. Waiting on Roku to do this.
  • Continue to try and land standalone code (currently blocked on WebRTC refactor).
  • Land bug 1048425 Enable support for tab sharing with Roku device. Possible once private channel has been set up.
  • Investigate sending H.264 instead of VP8 video to standalone WebRTC. (Not certain how critical this is as performance of VP8/OpenGL appears adequate)

Sylvain Cleymans

Last week: Fixing performance tests, integrating the new image compression binary

Next week == nullptr

Brian Nicholson

  • Hi
  • bug 788073 – Use platform touch redirection
  • bug 1030896 – Swipe-to-dismiss for search activity
  • Trying to figure out tablet resource crash (bug 1067429)
    • Always crashes at resource style/GeckoActionBar
    • Spent awhile trying to downgrade, no luck
  • Set up Hackintosh VM to play around with iOS

WesJ

<Read Only>

  • bug 1063896 – Regression: missing thumbnails in top sites; thumbnails replaced with tiny Favicons. Uplifting
  • bug 1066892 – Basic database migration tests. Trying to fix some try problems.
  • bug 989094 – Webrtc permissions prompt should remember your last choice
  • bug 897711 – [guest] Provide an indicator for guest mode in the UI
  • bug 1042199 – Widget for searching from error pages. This changes how/when we decide what url to show in the urlbar. If you see the wrong url appearing ping me.
  • bug 1058150 – Use a restricted profile for guest mode

LucasR

<Read Only>

Last week

Next week

  • More tab strip
  • Some toolbar refinements

liuche

<Read Only>

  • bug 1062257 – Fix “Remove” behavior for home panels
  • bug 1014293 – WIP Private browsing contextual hint
  • Next: Finish up onboarding follow-ups and contextual hint, search activity feedback

Margaret

Highlights:

  • Search activity hacking, mainly focused on nailing down UX
  • Starting work on “November to Remember” add-ons
  • Attending add-ons work week on Monday (and maybe Tuesday) next week in MV

Past:

Present:

mcomella

<Read Only>

Past
  • Browser Toolbar refresh
    • bug 1065712 – Move new_tablet_* to the appropriate directories
    • bug 1066250 – Consider always showing URL in toolbar in new tablet UI
  • bug 1001655 – Replace applicable Strings in test code with StringHelper references
  • bug 960746 – Back/forward button state can get out of sync on tablets
  • bug 1062338 – Regression: Back button icon missing in menu on some small screen (?) hardware (?) devices
  • bug 956858 – Menu is incorrectly accessible via hardware menu button in editing mode
Present
  • Browser toolbar refresh
    • bug 1058909 – Implement new tablet toolbar display mode
    • bug 1066253 – Display favicon in tab strip instead of toolbar in new tablet UI
    • bug 1019127 – Remove updateChildrenEnabledStateForEditing
  • bug 1020534 – Tablet toolbar icons hard to read on dark lightweight themes
Future
  • Too busy with other things:
    • Herding bug 941155 (fix talos on mobile to have pageloader tests working in regular mode and nochrome mode) along
    • bug 939350 – Create Python linter wrapper
  • bug 983437 – Delay FHR pruning until the screen is off
  • bug 989441 – Centralized documentation for writing tests

rnewman

<Read Only>

Overview
  • Upgrading to Mavericks. That burned a couple of days!
  • Services/devices prep.
  • Helping Garvan with service delay stuff.
  • Assorted fixes (see below).
  • Lots of reviews and discussions.
  • Platform priority review meeting.
Next
  • Finishing up Accept-Language.
  • FHR for search activity.
  • Services/devices.
Fixed
Working on

nalexander

<Read Only>

  • Code: Remote Tabs home panel has landed and stuck (bug 1014994). Most old and new features landed: bug 1064304, bug 977161, bug 1063765. Down to UI polish and split-pane tablet view for 35 cycle.
  • Reviews: been avoiding reviewing ckitching’s patches that make annotation processing a Real Child. Action in bug 1064554 and bug 1067217.
  • Testing: instrumentation tests have landed in automation and mozharness (meta bug is bug 1064004). TBPL and treeherder in the works. Trying to carve out time to write the actual test harness; follow bug 903537.
  • Search Activity: patches up to fetch search engines at build time from region.properties (like suggestedsites): bug 1065306.
Past
Present

BLassey

Fixed
Working on
  • bug 1054959 – Add ‘send videos’ and ‘send tabs’ from desktop to a second screen

Antlam

  • Past
    • Ongoing co-ordination with Arcadio’s team for Firefox for Android’s website
    • bug 1064304: Sync tabs panel design
    • bug 1060413: V1 visuals for default state of tablet UI
    • bug 1063058: Began Panels UI wrangling
    • bug 1051973: Firefox Search: suggestions/history UI
    • N2R bugs co-ordination
  • Upcoming
    • bug 1024816: Tablet UI: Tab overflow
    • bug 1060413: Tablet UI: Default/normal UI
    • bug 1064415: Tablet UI: New tabs tray
    • Firefox Search P1 bugs
    • Tablet’s overview presentation with Yuan
    • Onboarding visuals
    • Launcher discussions

Yuan

  • Last week
    • Talked to mozilla.org and marketing about Firefox Android product page
    • Initial brainstorming with Anthony and Robin on improving web content display on Fennec
    • Discussed N2R and addons with Robin
    • Gave UX feedback to

Robin

  • Add-ons! Exploring Add-on panel and possible interactions. Reverting back to Etherpad for NR2 (instead of Google Doc).
  • About to file bugs for Menu re-org/consolidation.
  • Launcher discussion with Anthony and Yuan.

WebRT

  • only just back and already causing trouble
  • phonescreened half-dozen candidates for open position over the last few weeks, and interviewing a couple this week and the next
  • delayed meeting to discuss next phase of Runtime development until after my other project’s milestone next week
  • bug 960584 – notify user of download progress indication when fetching APK – reverted pending resolution of dependency
  • bug 1021395 – Web app machinery dumps lots of semi-sensitive data to logcat – investigating ChromeWorker/ctypes crasher
  • bug 1029691 – Manifest not being checked on APK installation – needs to be rebased and finished

QA

Garvan

  • (late to meeting, in another one, will be there)
  • Stumbler failed the Autophone startup tests, for two reasons, 1) was on by default (oops), and 2) was getting started too early and the thread init is contending with other operations for CPU/thread space. Fixed
  • The pref is gecko-based, which needs to change, will follow up with Richard and Nick on this.

Feature Focus

Firefox 33 (Beta) – Release: Oct 14, 2014

Firefox 34 (Aurora) – Release: Nov 25, 2014

  • [ON TRACK] Provide a wifi toggle widget on error pages
  • [AT RISK] Tab mirroring (Roku)
  • [ON TRACK] Tab mirroring (Chromecast)
  • [ON TRACK] Toolbar Updates
  • [ON TRACK] Add support for Restricted Profiles (Prefer: safe)
  • [ON TRACK] Share handler overlay (landed but not turned on, nightly & aurora only)
  • [ON TRACK] Form auto-fill improvements, native client-side work
  • [ON TRACK] Kindle-related fixes
  • [ON TRACK] First-run Splash Screen Overlay

Firefox 35 (Nightly) – Release: Jan 6, 2015

  • [PROPOSED] Tablets: tabbed browsing refresh v2
  • [ON TRACK] Sync Tabs panel
  • [PROPOSED] Settings Rewrite (includes:bug 975377
  • [IN PROGRESS] Fatfennec: Minifying JS
  • [ON TRACK] Search activity v1
  • [ON TRACK] Moz Stumbler
  • [PROPOSED] Preferred web content language
  • [PROPOSED] Tablets: tabbed browsing refresh v1
  • [PROPOSED] Change default search engine to Bing
  • [IN PROGRESS] Fatfennec: Splitting the APK – gingerbread phone release
  • [BLOCKED] {{{1}}} Turn on HTTPS for Bing bug 958873
  • [PROPOSED] Privacy: DDG as a built in search engine

Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2014-09-17

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

  • 32.0.1 updates are disabled
  • 32.0.2 driver
    • bug 1063052 Firefox 32+ startup crash in nsFrame::BoxReflow
  • 33 beta4 desktop released yesterday
  • 33 beta4 mobile released today
  • lmandel is soliciting feedback on 32. If you didn’t attend yesterday’s post mortem, please send feedback via e-mail.

Firefox Desktop & Platform (Javaun/Chad/Martin)

Summary of Work In Progress
  • You can find the most recently completed iteration (35.1) performance report here
  • You can see the status of the current iteration (35.1) in progress here
  • OMTC maybe in 33 if some linger issues can be resolved, more next week on this once final determination can be made. (Bug 899785)
  • Picture Tag is currently slated for 33 but may push back to 34 depending on the outcome of some bugs currently being investigated. (Bug 1017875)
Uplifts
Beta (33)
  • Enhance tiles more specifically than eTLD+1/baseDomain (e.g., no enhance bugzilla.mozilla.org for mozilla.org) ( Bug 1045760 )
  • Include OpenH264 plugin in FHR data ( Bug 1053745 )
  • Avoid flushing layout and making it dirty repeatedly in ToolbarIconColor.inferFromText ( Bug 1061947 )
Aurora (34)
  • Undo the pref for the temporary hangserver for beta channels until Socorro is awesome ( Bug 791244 )
  • Backslashes included in a location bar input are converted to forward slashes on submission ( Bug 1042521 )
  • Tab-modal onbeforeunload dialog can automatically be dismissed by navigation ( Bug 1046022 )
  • Missing inverted panel help icon on Yosemite ( Bug 1060944 )
  • toolkit/themes/osx/global/in-content/common.css uses broken @focusRingShadow@ – focused link styling on about:preferences et al. can’t be parsed correctly ( Bug 1062843 )
  • disable unified autocomplete for Firefox 34 ( Bug 1064776 )
Summary of Recent Landings
  • Team landed 42 bugs over the last week, to close out the 35.1 iteration.
  • Details of landings from the past week can be seen here

Firefox Mobile (Mark/Brad/Jenn)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Uplifts from the past week
Beta (33)
  • Remove gradients from form elements ( Bug 763671 )
  • Lightweight theme preview is broken ( Bug 887755 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange(PinSiteDialog.java) ( Bug 1041448 )
  • crash in mozilla::layers::TileClient::GetBackBuffer(nsIntRegion const&, mozilla::layers::TextureClientPool*, bool*, bool) ( Bug 1041744 )
  • Regression: Back button icon missing in menu on some small screen (?) hardware (?) devices ( Bug 1062338 )
  • “Learn More” link for the Mozilla Location Service is visible on Beta/Release despite MLS setting not available ( Bug 1063518 )
  • crash in webrtc::ViEInputManager::NumberOfCaptureDevices() ( Bug 1063547 )
  • crash in java.lang.NoSuchMethodError: android.os.Bundle.getString at org.mozilla.gecko.preferences.GeckoPreferences.setupPreferences(GeckoPreferences.java) ( Bug 1065531 )
Aurora (34)
  • Regression: Browser menu has width issues ( Bug 1020505 )
  • Too many differing background greys throughout the browser ( Bug 1055536 )
  • crash in java.lang.IllegalStateException: Already registered Wifi:Enable at org.mozilla.gecko.EventDispatcher.registerListener(EventDispatcher.java) ( Bug 1061030 )
  • Regression: No context menu action is invoked on long-tapping some links ( Bug 1062307 )
  • Use empty string as title if no title provided when adding a bookmark ( Bug 1062552 )
Landings from the past week
Nightly (35)
  • Synchronous initialization of search service when handling open search tag ( Bug 1017903 )
  • [Roku] Removing an entry from history will only take effect after restarting the Roku app ( Bug 1025923 )
  • about:home is unresponsive to hardware menu button on returning to main activity on 2.3 devices ( Bug 1058027 )
  • [roku] update wording in the public roku channel app ( Bug 1064222 )
  • Search activity startup crash @ java.lang.IllegalArgumentException: Couldnt find search engine for identifier: yahoo at org.mozilla.search.providers.SearchEngineManager.createEngine(SearchEngineManager.java) ( Bug 1065123 )
  • Regression: Downloading is broken ( Bug 1066671 )

Market Insights from the Market Strategy Team (Kev)

Something to Think About

The stock Android browser, which is the default browser on Android versions below 4.4, has a vulnerability that allows malicious sites to bypass the same-origin policy and execute an XSS attack. Metasploit contains a live exploit for the bug, which could potentially affect more than half of Android browser users. Updating the stock browser is not really something that’s been done since Kitkat came out, although Google has apparently said they’ll launch a fix, it’s just unclear how that fix will be delivered.
Why we should care: A continually updated, modern browser that works on the majority of Android devices is something every Android user should want (and know about). Firefox for Android meets that need, and we should consider reminding people of the risk and solutions that Firefox brings to older versions of Android.

Worth a Read

  • Google launched Android One in India Monday. They’re using a familiar “the next x billion Internet users” line, and tying “One” to the user. Lots of hardware partners with MediaTek and Qualcomm as the chipset providers, with some phones coming with data included for installing apps from Google Play to help drive use, some region-specific features (like dual sim support, offline YouTube, monthly included data for the play store, etc.), and Google managing the software update process. Also notes on intent to expand through Southeast Asia in the near future. Android One website
  • Google appears to be experimenting with making simple searches a little more useful in Chrome on Android. A flag can be set to enable answers (accessed via chrome:flags), which makes use of the search suggest facility to deliver more than just keywords. Search monetization and use has been more difficult on mobile, and this is a good example of some of the ways search providers are going to look to make search more of a go-to, and perhaps generate revenue from for things like location specific results, promotion weighting, etc. Answers has also been available on Desktop Chrome for a while, but the answers delivered are more limited than what’s being delivered on mobile.

Notes


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

Meeting NotesSeaMonkey: 2014-09-16

Agenda

  • Who’s taking minutes? -> Ratty
  • Nominees for Friends of the Fish Tank:
    • The Release Team (Callek and Ewong)
      • tonymec proposes the SeaMonkey RelEng unit (as a group) for “citation to the order of the day (Mention in Dispatches) with Order of the Fish Tank and fourragère for courage and gallantry above and beyond the call of duty in particularly hostile circumstances, culminating in the reestablishment of nightly en-US builds of SeaMonkey for all four supported platforms, to wit: Linux32, Linux64, Windows32 and Mac-Universal”. Linux builds in 17 other languages, as well as for en-US, and langpacks for the same, are published every night by Adrian Kalla, named Friend of the Fish Tank for this reason two fortnights ago, on his l10n.mozilla-community.org user site, for Linux32 and Linux64 and for trunk, aurora, beta and occasionaly release branches.

Action Items

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

NEW

  • bug 1057920 SeaMonkey’s CVS dependency really should be removed. (currently used only for Releng Automation, and SeaMonkey Website).
    • IanN will create a separate bug for the releng automation stuff and will find out what is required to get the work done.

OPEN

  • http://weblogs.mozillazine.org/seamonkey/ has not been updated since November 2012, the last version listed is 2.14 (bug 956561); move blog to blog.mozilla.org if possible Assigned: mcsmurf.
    • blog account has been created in bug 973886
    • Callek has imported old blogs from mozillazine
    • some sprucing / branding needs to happen next
  • bug 998807 Sync account creation or device pairing fails with exception in BrowserIDManager
    • mcsmurf will look into this

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

  • Buildmaster is up and running, and produces en-US builds, see Friends of the Fish Tank above. Builds and langpacks in 18 languages including en-US are available unofficially thanks to A.Kalla, see also FOFT above.
    • 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.
  • comm-* will be building out of mozilla-* (bug 648979 etc.). Jcrammer has completed the coding. The decision to merge c-c into m-c has been kicked down the road into the next quarter or two.
    • Recent work on this:
    • bug 1040009 .mozconfig configure options are ignored if objdir path is absolute
    • bug 1035599 Pseudo-merge m-c and c-c’s objdir
  • [16th September 2014]
    • [rsx11m] The most recent Windows nightly builds were 13-Jun-2014 09:36 for 2.30a1 and 21-Jul-2014 10:17 for 2.29a2. [ewong] Besides infrastructural issues, comm-central has flattened the objdir, which needs further infra changes. [IanN] There has been a lot of build system changes in the last few months.
    • [comm-central]
    • [comm-aurora]
    • [comm-beta]
      • Linux-debug busted due to bug 1053081)
      • OSX debug busted (not yet determined)
  • [1st September 2014]
    • All Linux64 machines(except the buildbot master) have decided to go on strike/AWOL/whatever. (Not good, obviously, but not something Callek or ewong can do until DCOps kickstart them, and since Monday is a holiday, it’ll be after Tuesday before anything’s done.) bug 1058385 Ergo, All trees are closed.
      • w0ts0n from #it took a look at sea-hp-linux64-9 and said it had a ‘Disk error’. (Again, not good. In fact, exactly the same situation as sea-hp-linux64-2.)
    • Thankfully, the last slave (-13) went AWOL *after* the 2.29b2 release. (If it was going to go AWOL, after release would be the best time; of course, *not going AWOL* would’ve been preferential.)
    • Buildbotcustom/config release code is still being tweaked to get release done.
  • pymake has been discontinued. We need to install the latest Mozilla-build and tooltool on our windows builders (tracked by bug 1023644 )
  • No langpacks since 29th August 2013 on trunk. Needs investigating.
    • Windows and Mac trunk langpacks directories have been removed on the FTP server, maybe for lack of recent XPIs (later than 2.20a1). Latest Linux langpacks are dated 29 August. Callek told Tonymec on IRC he has a hunch about why but more pressing things to do first.
    • In Bug 902876 Comment 12 Mcsmurf is waiting for feedback from the build team on how to proceed.

Release Train

  • SeaMonkey 2.29 was released on 7th September 2014.
  • There shall be a 2.30 beta soon. Schedule TBA.
  • Useful Firefox Release Schedule link: Releases Scheduling

Extensions and Plugins Compatibility Tracking

  • Firefox & Thunderbird Add-on Converter for SeaMonkey
  • 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.

    Add-on Converter for SeaMonkey: http://addonconverter.fotokraina.com/

    • There is a long list of Firefox and Thunderbird extensions that have been successfully converted in the Mozillazine thread[1]. Can someone go through the thread and add the list of successful conversions to SeaMonkey/AddonCompat.
  • bug 1060858 Ghostery 5.3.1 does not support SeaMonkey. Ghostery depends on the Addon-SDK. Since the SDK has been rewritten to support Firefox Australis redesign, Ghostery no longer works for SeaMonkey. Ratty has emailed info@ghostery.com regarding this.
  • See Basics page. Please only list current changes here.
  • Addon Compatibility Listings
  • Ratty filed bug 957149 to push an updated version of DOMi to addons.mozilla.org to pick up the latest fixes. Depends on:
  • 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)

  • [From a previous meeting:] There is a problem with the metrics server, so no current data is available
  • See Basics page for the usual reminders.
2.29

open tracking (0)
tracking requests (0)
targeted (0)
fixed (6)

 If you want Firefox 32.0 to take another crack at importing your passwords,
  1. In about:config, right-click signon.importedFromSqlite and choose Reset.
  2. Type about:support into the address bar and press Enter.
  3. Click the Show Folder button.
  4. Exit Firefox.
  5. Delete the logins.json file from the profile folder.
     This assumes you didn't save or modify any passwords in Firefox 32.0. If you did, not only will they all be lost, but the key3.db decryption key won't match the old signons.sqlite database from Firefox 31.0.
 There's a neat Password Exporter add-on:
 https://addons.mozilla.org/addon/password-exporter/
 Install it, then you get an option to import/export your passwords on the Tools>Options>Security tab.
 Export Passwords file which is automatically dated to .xml or .csv.
 Then install 32.0 or greater.
 You can then simply import all your passwords effortlessly.
2.Next
  • Stalled. Needs a kick.
    • bug 937809 Add DuckDuckGo to the default search engines list. a=Callek land this ASAP.
    • 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 ab 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.
    • bug 793634 Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
      • bug 795354 Migrate SeaMonkey Linux builders to CentOS 6.
    • bug 846635 Use asynchronous getCharsetForURI in getShortcutOrURI. bug 834543 Add asynchronous version of setCharsetForURI and getCharsetForURI. Tracked in:
      • bug 896947 Use asynchronous version of setCharsetForURI and getCharsetForURI in getShortcutOrURI and other places.
    • 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: 36 new, 3 fixed, 4 triaged.

  • Low triaging effort.
  • 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

Open reviews/flags:
38 review
6 super-review
1 ui-review
4 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.

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).

IanN
  • Usual testing, reviewing and commenting.
  • Fixed
  • Fixed for c-c:
    • bug 882968 Clean up and move DEFINES and friends to moz.build in comm-central
    • bug 1055867 Move RCFLAGS and RCINCLUDE to moz.build and hardcode manifest name
  • Fixed for m-c:
  • Fixed for m-i:
  • Pending check in:
    • bug 1039003 Port |bug 633773 Use Google’s HTTPS search by default|, |bug 958883 Use HTTPS for Yahoo searches| and search plugin parts of |bug 959576 Create a component to get the list of priority domains| to Thunderbird
  • Checked in pending review:
  • Waiting for feedback/review:
  • 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 1060897 Static-link the CRT into Instantbird executable (/im/app/moz.build). Port bug 1023941 Part 1
    • 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:

  • bug 986935 Dispatch restoration notifications asynchronously.
  • bug 1005336 Make sync runnable helpers more threadsafe.
  • bug 1060047 Use Plugin Host to enumerate plugins.

Checked in to mozilla-central:

  • bug 1054289 Setting document.hash while the page loads doesn’t work.

Checked in to comm-release:

Needs checkin:

  • bug 870556 Try to improve performance of the IMAP download queue.

Waiting for review:

  • bug 1061990 Cache size does not update after clearing cache.

Still waiting for review:

Ratty

Needs checkin (waiting for greener tree):

  • bug 1035171 Switching tabs triggers onLocationChange with LOCATION_CHANGE_SAME_DOCUMENT flag.
  • bug 1039933 While composing mail, there exists an empty line in attachment context menu when right clicked on the attachment area
  • bug 1040771 Allow about: pages to opt in to IndexedDB optionally specifying a desired origin.
  • bug 1041327 Record submission event for plugin crashes [notifications] includes bug 1024672.

Fixed:

  • bug 1053166 Replace openResultPopuup typo in autocomplete.xml by openPopup.

Working on:

rsx11m

Looking into:

  • bug 1060852 Expose privacy.trackingprotection.enabled in Privacy preferences and account for removal of Do-Not-Track options.

Needs testing:

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

Other:

  • Bug triage and commenting for SeaMonkey and Thunderbird.
  • End-user information and discussion on MozillaZine.
stefanh

Waiting for review:

  • bug 333910 nsITheme for menu/scrollbox arrows (Widget: Cocoa).
  • bug 973644 Port bug 967970 – Set NSDisablePersistence to prevent disk leaks.

Any other business?


SeaMonkey Meeting Details

Meeting NotesMozilla Platform: 2014-09-16

Need To Know

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

Notices/Schedule (lsblakk/sylvestre/lmandel)

Next Merge: October 13, 2014 Next Release: October 14, 2014
Trains
Central: 35 Aurora: 34 Beta: 33 Release: 32
  • 32.0.1 updates disabled today, maybe 32.0.2…we’ll see
    • candidate driver: bug 1063052 Firefox 32 startup crash in nsFrame::BoxReflow
  • Beta4 desktop releases today, mobile tomorrow
  • Beta5 (desktop) go to build Thursday
  • Beta6 (desktop and mobile) go to build Monday

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.)

  • Saturday, September 20, is the Tree Closing Window. See bug 1065514 for details. hg.mozilla.org will be offline for a period of time, so trees will be closed. This is likely to be from 0900-1300PT, but time will be confirmed on Wednesday. Look for the notice with final times later this week.

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)

  • We just halted 32.0.1 updates due to bug 1063052.
  • Beta still has GFX issues on both desktop (OMTC/D3D11) and Android (AlphaBoxBlur bug 1028802).
  • Prompt for e10s on Nightly triggered us seeing a lot of e10s crashes, we need a lot of work there until we’ll be able to ship anything there or even turn on by default.

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.)

A*Team (jgriffin)

<Read Only>

Blog and newsgroup posts:

Desktop Platform (bsmedberg)

<Read Only>
Mac V2 signing work is our top priority and we hope to have that on nightly next week.

Developer Tools (prouget/bgrins)

DOM (jst/overholt)

Electrolysis (e10s) (blassey)

  • Please help dogfood e10s in Nightly!
  • e10s bugs fixed in the last week: http://is.gd/ksQL9N
  • To get more testing from Nightly users:
    • bug 1064885 – Added e10s opt-in prompt in Nightly
    • bug 1064886 – Added “Enable E10S” checkbox in Firefox Preferences pane
    • Disable e10s if a11y (bug 1047076) or safe mode bug 1063848 are enabled (to avoid known issues, for now)
    • We might enable e10s for all Nightly users (for just one day) to get broader testing during Nightly 35. So now is a good time to report any critical e10s bugs you are seeing.

Firefox Desktop (gavin)

Summary of Work In Progress
  • You can see the status of the current iteration (35.1) in progress here
Summary of Recent Landings
  • Team landed 42 bugs over the last week, to close out the 35.1 iteration.
  • Details of landings from the past week can be seen here

Firefox Mobile (snorp/blassey/mfinkle)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Landings from the past week
Nightly (35)
  • Lightweight theme preview is broken ( Bug 887755 )
  • Synchronous initialization of search service when handling open search tag ( Bug 1017903 )
  • [Roku] Removing an entry from history will only take effect after restarting the Roku app ( Bug 1025923 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange(PinSiteDialog.java) ( Bug 1041448 )
  • crash in mozilla::layers::TileClient::GetBackBuffer(nsIntRegion const&, mozilla::layers::TextureClientPool*, bool*, bool) ( Bug 1041744 )
  • about:home is unresponsive to hardware menu button on returning to main activity on 2.3 devices ( Bug 1058027 )
  • Regression: Back button icon missing in menu on some small screen (?) hardware (?) devices ( Bug 1062338 )
  • “Learn More” link for the Mozilla Location Service is visible on Beta/Release despite MLS setting not available ( Bug 1063518 )
  • crash in webrtc::ViEInputManager::NumberOfCaptureDevices() ( Bug 1063547 )
  • [roku] update wording in the public roku channel app ( Bug 1064222 )
  • Search activity startup crash @ java.lang.IllegalArgumentException: Couldnt find search engine for identifier: yahoo at org.mozilla.search.providers.SearchEngineManager.createEngine(SearchEngineManager.java) ( Bug 1065123 )
  • crash in java.lang.NoSuchMethodError: android.os.Bundle.getString at org.mozilla.gecko.preferences.GeckoPreferences.setupPreferences(GeckoPreferences.java) ( Bug 1065531 )
  • Regression: Downloading is broken ( Bug 1066671 )

Firefox OS Devices/Porting (ericchou)

<Read Only>

  • Bluetooth (members: Shawn Huang, Ben Tian, Jamin Liu, Jocelyn Liu)
    • BLE API discussion on dev-webapi
    • Shawn and Jamin will participate in NFC workweek from 9/15 ~ 9/19 and will give two talks related to BT/NFC applications.
    • PTS test for Firefox OS 2.1 (current aurora) has begun. Jocelyn is the owner this time and will co-work with TPE QA.
  • Media Playback (members: Bruce Sun, Blake Wu, Star Cheng)
    • bug 1064376 – [KK] Regression in playing few clips on v2.1 – landed (2.1+)
    • bug 1039182 – Add getGrapicBuffer interface to MediaCodecProxy – landed
    • bug 1036849 – Video part in MP4 DASH on B2G does not work – WIP
  • Device Storage (members: Alphan Chen, Eden Chuang)
    • bug 1060196 – Should forbid ejecting SD card when user is playing music which is stored in SD card – feedback+ (2.1+)

Firefox OS RIL (htsai)

<Read Only>

  1. https://wiki.mozilla.org/TPE_RIL_team/2014-09-16

GFX (milan)

  • Proposed high level priorities for graphics for the next few releases (e.g., 35-38) are being discussed (and possibly modified) by product and execs. The proposed list top five – let’s see if it changes:
    • E10S support
    • B2G memory usage and performance
    • APZ on B2G: Project Silk support, OOP support, “fake overscroll”
    • WebGL Desktop performance
    • WebGL Mobile performance

JS (naveed)

<Read Only>

  • Compiler (JIT)
    • bug 1062869: Add ability to execute recover instructions ahead of bailouts. This improves Scalar Replacement for arguments given to multi-basic-block inlined functions. This also one step forward to “eager” escape analysis.
    • bug 894596: Patch to allow inlining global variable values. Investigating possible performance regressions associated with the patch.

Media (mreavy)

<Read Only>

  • Fixed problem with Webrtc and H.264 under very high packet loss (bug 1054624)
  • Resolved Screensharing issues on Windows due to multiple threads (MediaManager, D3D9 in gfx/compositor) which made windows calls without running on a Windows messageloop – thanks jimm!
  • working on policy for additions to screensharing whitelist
  • ScreenSharing now *must* occur from an https: site for security/privacy reasons

Necko (dougt/jduell)

<Read Only>

  • No update this week.

Performance (vladan)

Update next week

Roundtable

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

<Read only beyond this point>

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

11:02 cpeterson: https://wiki.mozilla.org/Platform/2014-09-16
11:05 bsmedberg: blassey: jimm: I'll be following up with you later about the e10s crashes
11:05 blassey: ok
11:06 lmandel: bsmedberg: I see readonly update about v2 sigs. Do you want to tell people what that means?
11:06 cpeterson: e10s content crashes are up about 100x since the e10s opt-in prompt
11:06 bsmedberg: lmandel: not really, do you think I need to?
11:06 lmandel: bsmedberg: Only if you think people will be impacted in their work.
11:07 lmandel: bsmedberg: We should probably call out when this is done so that people know.
11:07 KaiRo: hmm, do I only voip badly in those larger meetings? I didn't hear complaints in the smaller ones I'm usually in
11:07 bsmedberg: I think rstrong will be sending an email around to dev.platform when the current oranges/issues are solved before we actually flip things over
11:07 lmandel: KaiRo: You were fine in the channel meeting.
11:07 lmandel: bsmedberg: k
11:08 KaiRo: lmandel: ok, maybe the added traffic of more people on the meeting tips it over or so
11:09 KaiRo: btw, "Firefox is not starting now" seems to be a quite common issue with e10s
11:09 armenzg_mtg: cpeterson, I will mention it here
11:09 armenzg_mtg: I tried e10s on Linux Desktop nightly recently and it was a pretty awful experience
11:10 armenzg_mtg: enabling it by default even for one day will be pretty terrible for nightly testers
11:10 KaiRo: snorp: did you get a crash reporter at all for that non-starting thing with e10s?
11:10 snorp: KaiRo: yeah, standby, will paste
11:11 snorp: https://crash-stats.mozilla.com/report/index/c5ef1fca-fde0-44c8-95ef-680052140916
11:11 KaiRo: snorp: ok, good to know, startup crashes sound like the first thing we need to fix
11:11 snorp: yes.
11:11 armenzg_mtg: cpeterson, what is the preferred way to give feedback about e10s?
11:11 KaiRo: xpc::AddonWindowOrNull
11:11 KaiRo: sounds like fun with add-ons
11:12 cpeterson: armenzg_mtg: you can mention e10s problems in #e10s or just file a bug. Be sure to include the word "e10s" in your bug summary so our e10s triage queries will find it!
11:13 dveditz: armenzg: there's a link to file bugs at https://wiki.mozilla.org/Electrolysis#Contributing
11:13 armenzg: cpeterson, dveditz thank you gentlemen - I will dog food again
11:13 dveditz: also descriptions of known issues and links to known bugs for dupe finding
11:13 dveditz: on that page
11:13 dveditz: I mean a link to a query
11:14 KaiRo: snorp: can you file this one? sounds like this specific signature only exists today
11:14 snorp: KaiRo: https://bugzilla.mozilla.org/show_bug.cgi?id=1068163
11:14 cpeterson: armenzg: TBH, if you had e10s crash problems, you might want to wait a day before dogfooding again for some recent fixes to make their way to mozilla-central and then Nightly builds.
11:15 KaiRo: snorp: awesome, thanks. the signature seems to be all only today's build. fun.
11:15 snorp: KaiRo: yay
11:15 armenzg: cpeterson, I'm good with crashes - IIRC I was having responsiveness issues
11:15 cpeterson: armenzg: oh, that problem has not been fixed yet <:)
11:15 snorp: heh
11:15 snorp: cpeterson: what causes it
11:16 snorp: shouldn't it be *more* responsive
11:16 armenzg: cpeterson, k thanks
11:16 armenzg: snorp, in some cases :P
11:16 cpeterson: snorp: I don't know the cause, but there is likely some IPC bottleneck between parent and content process.
11:17 cpeterson: snorp: the browser should be more responsive (because its UI thread is not blocked on content as much), but all tabs run in the same process that can block each other.

Engineering Meeting Details

  • Tuesday 2014-09-1611:00 am Pacific Standard Time
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
  • 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

Meeting NotesMozilla Project: 2014-09-15

All-hands Status Meeting Agenda

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

Friends of Mozilla

  • Thank you for the Mozillians who supported Mozilla’s presence at JSfest in Berlin last week, as part of Reject.JS, CSSconf EU, and JSConf EU.
    • Tim Taubert, Freddy Braun, Christian Heilmann, Jeff Griffiths, Angelina Fabbro, Axel Hecht, Margaret Leibovic, Guillaume Marty, Gregor Wagner, Jan Jongboom, Romain Gauthier, Soledad Penades, Julian Viereck, Tom Schuster, Jordan Santell.
  • Thank you to Clint Talbert, Rebecca Billings, Hal Wine, and Karl Thiessen for volunteering at the joint event with Open Hatch at CCSF this weekend!
  • Thank you to Rosana for her amazing work on ReMo camp.
  • Thank you to Denelle Dixon-Thayer, Sean Bohan, Darren Herman, Jason Schmidt, Lara Fischer-Zernin, JB Piacentino and Mike Manning for a great “spiel” at Germany’s Digital Marketing Exposition.
  • “Obrigado” to Marco Aurélio Krause for localization of the Firefox Activations Directory into Portuguese. “Muchas Gracias” to Ricardo Palomares for localization into Spanish.
  • Thanks to Firefox app developer Varun Malhotra, who is now developing & testing apps with Firefox app-manager and his new Intex Cloud FX Phone, despite some initial setup challenges.
  • Big thank you to Clarissa Sorenson for bringing community training to her weekly New Hire orientation sessions!

Upcoming Events

Wednesday, 17 September
  • S2LQ 2014 in Quebec City, Quebec, Canada
    • Frédéric Harper will be presenting “L’état de l’Open Source en 2014 Est-ce que l’Open Source n’est vraiment qu’une question de logiciel libre? Quels en sont les avantages? Y a-t-il anguille sous roche? En se basant sur l’expérience de Mozilla avec Firefox, ainsi que sur l’ensemble de son parcours professionnel, Frédéric Harper vous parlera de l’état de l’Open Source en 2014.”
  • FITC Web Unleashed 2014 in Toronto, Canada
    • Vladimir Vukicevik, Frédéric Harper, tofumatt presenting
Thursday, 18 September
  • 10:00 AM Pacific / 17:00 UTC: Grow Mozilla discussion — a forum for discussing community building at Mozilla
  • Nordic.js in Stockholm, Sweden
    • Robert Nyman presenting “The Five Stages of Development”
    • Sergi Mansilla presenting “The Fourth Dimension”
Friday, 19 September
  • From the Front in Bologna, Italy
    • Christian Heilmann presenting “Rubbing the Sankara Stones the Wrong Way”
Next Week
  • 24-September — Mozillians Town Hall : Brand Initiatives (10:00am PT – 11:00am PT)

Project Status Updates (voice updates)

Firefox

Speaker Location: Toronto (johnath)

Firefox for Android

Speaker Location: (remote: mfinkle)

  • New Tablet UI
    • The new WIP tablet UI refresh has started landing in Nightly
    • Use the “Setting > Display > Enable new tablet UI” to enable it
Firefox OS

Speaker Location: Asa Dotzler (Vidyo fail. Potch, can you read off the names of the four first time committers to Firefox OS? Thanks!)

Content Services

Speaker Location: Darren Herman via Vidyo – NYC

  • Please check out the Subscribe To Web brown bag on Thursday A movement to create an alternative to advertising to fund the Web
  • Tiles has landed in Beta, an open call to all Mozillians if you have friends or family in advertising or marketing and want to make an introduction for us, pls contact contentservices@mozilla.com
  • Thanks to all who made Dmexco (Cologne, Germany) a success. Our presentations and participation were received well.
Webmaker

Speaker Location: nonverbal

  • Today is the last official day of the Maker Party campaign (though the making never stops!). We’ll share an update with numbers/successes next week.
Mozilla Communities

Speaker Location: Surman / Mitchell – Berlin

  • A month back, we assembled a tiger team on the community goal.
    • Mark Surman, Mitchell, Mary Ellen Muckerman, David Boswell, Brian King, Michelle Thorne, Kristin Baird
    • Working with community teams from across Mozilla
  • Our first action is to pilot the idea of “contribution challenges” to tie the volunteer community to new initiatives that aim to have immediate term impact on topline goals.
  • Over this past weekend, the team worked with the reps at RemoCamp this weekend to iterate and advance the challenges and define volunteer community ownership.
  • Working with the business owner for each goal, these are the challenges that we have prioritized to do between now and the end of the year:
  • Firefox : Firefox 10 and Growth
    • Define a number of initiatives that promote Firefox growth, that we can test during the Firefox 10 campaign. These are a combination of promotions based around events, product features, and so on. The ultimate goal is drive downloads.
  • FXOS Local Presence:
    • Produce a large volume of high quality hyper-local content for FXOS users in India and Mexico, in a very short time frame, and in parallel, train Mozillians to become skilled evangelists and developer mentors to ensure long-term sustained support and mentorship for local developers creating hyper-local content for FXOS
  • FXOS in market Communications:
    • Enable our local communities to be the ongoing voice of FFOS / mozilla in their locales through a range of communications channels, as appropriate in their locals.
  • FXOS + Webmaker:
    • Training and user surveys that help us understand ways that ‘user generated apps’ can solve problems for the next billion web users.
    • Will actively play a role in shipping Mobile Webmaker (aka Appmaker) through user testing at Maker Parties and conduct interviews with feature phone users to understand the problems they want to solve.
  • Tiles:
    • Define a system to generate content for regional community tiles in 20 launch markets for October 15 and put an ongoing structure in place for regional communities to own the content schedule for regional community tiles.

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
John Slater Creative Director Update on the MozID logo project + how you can help San Francisco Not sharing my screen. Please display this page. https://blog.mozilla.org/creative/
Scott DeVaney Editorial Manager, Firefox Marketplace New Marketplace redesign San Francisco Not sharing my screen Please display this page. https://wiki.mozilla.org/Marketplace/Contributing/Apps/CommunityCuration

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
Shing Lyu Brian Huang Taipei Taipei Firefox OS / QA Engineer
Eden Chuang Eric Chau Taipei Taipei Firefox OS / Software Engineer
Scott Wu Mike Tsai Taipei Taipei Firefox OS / UX Designer
Bobby Chien Howie Chang Taipei Taipei Firefox OS / Engineering Project Manager
Wesly Huang Wayne Chang Taipei Taipei Firefox OS / Technical Account Manager
Alastor Wu Randy Lin Taipei Taipei Firefox OS / Software Engineer
Jonathan Hao Ethan Tseng Taipei Taipei Firefox OS / Software Engineer
Ricky Chien Tim Chein Taipei Taipei Firefox OS / Software Engineer
Paul Johnson Geoffrey MacDougall Toronto San Francisco Marketing and Communications for the Foundation
Andrew Osmond Mike Habicher CA Remote CA Remote Firefox OS / Software Engineer
Matt Rosenberg Anthony Duignan-Cabrera New York Seattle Remote Senior Editor, West Coast, The Open Standard
Kevin Zawacki Anthony Duignan-Cabrera New York New York Senior Editor, East Coast, The Open Standard
Cory Price Chris More Mountain View Mountain View Senior Web Project Engineer (Technical Project Manager), Engagement’s user facing websites and web applications
Eugene Jung Albert Villarde Mountain View Office Mountain View Office Desktop Systems
Kory Salsbury Melissa O’Connor San Francisco Office San Francisco Office End User Services

<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 1054138 You can now filter Bugmail by specifying a string which matches that field’s name

All changes.

Engagement

  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 8600
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600

Meeting NotesThunderbird: 2014-09-11

Thunderbird meeting notes 2014-09-11
Today’s minutes taker, please don’t forget to :
– save etherpad before clearing for this meeting, if etherpad wasn’t previously cleared (but copy “Action items” to the top before clearing)
– after end of meeting, copy entire etherpad contents to a new dated wiki page on http://mzl.la/tbstatus so that they will go public in the meeting notes blog.
– save etherpad, copy “Action items” to “Action items from last meetings”, and clear the rest of etherpad comments

Attendees

  • rkent, florian queze, irving, rolandtanglao, magnus

Action items from last meetings

  • rkent and wsmwk to unblock / deal with bienvenu bugs

Current status and discussions

  • no progress on “bienvenu” bugs
  • comm-central changes on hold pending mercurial changes and signoff by smedberg
  • discussion about kent’s modification to Thunderbird governance proposal is positive
  • much work on summit and video from mconley and rkent
  • summit agenda planning, rkent to ask in tb-planning

Round Table

jcranmer

  • Likely won’t be at meeting today, one of my meetings changed time slots to start 30m before this one
  • according to gps, hg partial checkouts are targetted to land 3.2, more likely to land in 3.3 (release dates of Nov 1/Feb 1, respectively)
    • bsmedberg has said this is his blocker for letting c-c merge into m-c
    • gps plans to make it a high priority to update to newer hg quickly, and now has a new role to make that more possible
  • Played with putting OpenLDAP server in a Docker container

JosiahOne (Not at meeting)

  • Have done reviews and have been giving feedback in bugs, but personal development time has slowed. My development machine has to have a part replaced on Saturday plus I have papers and college applications to finish this month, so availability will be limited until around the time of the Summit.
  • OS X Codesign V2 status is coming along, I’m mostly just waiting for a finished version of the Fx implementation.

rkent

  • Summit: we really need a group of people to work on the agenda. Volunteers?
  • Discussion of reorg plan?

mconley

  • Now acting as interface between TB community and ProTravel Inc
    • The attendees list has been garnered from the wiki, along with 2 extras from Fallen and Florian for Calendar / Chat. Waiting to hear from a few more.
  • Re-connected with Aaron Mandel about a fundraising video. Quote is approximately $600 (+tax), since he likes Mozilla and wants to give us a deal
    • We need to find a good variety (accents, countries of origin, languages) members of the TB community who are comfortable / articulate in front of the camera (about 5-7 people), and come up with “our story”. I suggested our audience be current TB users who don’t actually know what’s happening with Thunderbird.
    • Quickly talk about where Thunderbird came from, the transition to community development, and where we are now – and why we need help. Instead of just talking heads, these interviews will be interspersed with shots of people checking their email, doing calendaring, chatting, etc.
    • We need the quick and punchy stuff: “Put users in control of their email”, “Your email is yours, even when you’re offline”, “Lots of tweaks and add-ons for power users”
    • We also need to send Aaron TB art / assets for graphical work.
    • Once we have our story, we’ll put together a really basic script, so we know who to put in front of the camera, and what questions to ask.
    • Then, I’ll meet with Aaron face-to-face 2 weeks before we shoot to make sure we have everything we need
    • During the summit (probably the Friday), we’ll pull our 5-7 people aside, ask them the questions we’ve scripted (maybe several times to get the sound bites we want), and then Aaron will cut together the video.

clokep (Not attending)

  • Been in contact with some of the DarkMail developers, have been trying to get them to ask questions in #maildev, but they seem to like to ask through me.
    • They’ve said things like “Random people don’t get answers there”
    • More likely they’re working during times when “we’re” not online.

Support team

Action Items

  • mconley: Come up with a short-list of volunteers to go on camera, send out emails with questions on them to get responses, find the responses that resonate, and from that, assemble our script.

Meeting NotesMobile: 2014-09-10

Schedule

  • Next merge: 2014-10-13

Topics for This Week

Tablet refresh v0 soon in Nightly (disabled by default)
Tentative merge to m-c happening tomorrow.

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.

  • Julien Sanchez fixed bug 680392 – Localize trademark notice string in about:firefox
  • manu.jain13 fixed bug 1060423 – Cut function in a readonly textarea
  • amoghbl1 fixed bug 1019045 – Unify magnifying glass/search icon
  • eedens fixed bug 1042960 – Create UI elements for facet bar
  • Tristan Pollitt fixed bug 1057613 – Telemetry for search widget buttons
  • vivek fixed bug 799562 – Update about:feedback to use new feedback API

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>

Alan K. (ack)

JChen

Fixed
Working on

GCP

<Read Only>

Last week

  • bug 1059573 Add support to using DSP-based echo canceller and noise suppressor

Next week

  • bug 1059573 Add support to using DSP-based echo canceller and noise suppressor
  • Standalone WebRTC
  • Media sandboxing

Randall Barker

Last week:

  • Fixed minor issues with Roku Player (aspect ratio, detect dropped stream, etc.)
  • Created SSDP/ECP simulator to debug discovery issues.
  • Rebased standalone WebRTC code and it broke. Started fixing.

Next week:

  • Finish fixing standalone WebRTC.
  • Set up private channel with Roku WebRTC Player to enable testing. Waiting on Roku to do this.
  • Investigate bug 1053426 Fennec crashes when tab sharing is active (Looks to be memory leak)
  • Continue to try and land standalone code.
  • Investigate sending H.264 instead of VP8 video to standalone WebRTC. (Not certain how critical this is as performance of VP8/OpenGL appears adequate)
  • Land bug 1048425 Enable support for tab sharing with Roku device. Possible now that there is something to test against.

Eugen Sawin

Past

Present & Future

  • Janus Proxy
    • Investigating performance issues (using the new metrics and marionette tests)
    • Looking into <picture> element injection
    • Adding TCP/socket stats
  • bug 1034114 – WebApp startup slowed significantly by debug server

Sylvain Cleymans

Last week:

  • Fixed performance testing

Next week:

  • Finish performance testing
  • Finish image compression

Brian Nicholson

  • Transitioning to dougt’s team to work on privacy and security
  • Wrapping up review queue and some bugs

WesJ

<Read Only>
Landing these guys (its taking a bit)

  • bug 1058150 – Use a restricted profile for guest mode. Landed again this morning.
  • bug 966493 – Cannot request fullscreen when inside a touchstart event.
  • bug 815682 – Lock screen widget/shortcut for Guest Sessions on Android 4.2 and above Widgets. Chasing down some Android 2.3 nits. There are little changes for this scattered through startup. Hopefully with:
  • bug 897711 – [guest] Provide an indicator for guest mode in the UI. it will be clear if we make a mistake. :)
  • bug 1042199 – Widget for searching from error pages. This changes how we decide what url to show in the urlbar a bit.

Also looking at:

  • bug 901360 – Convert to Downloads.jsm in Firefox for Android and bug 1063217 – Support a PDF DownloadSaver
  • bug 1064611 – Allow requesting cached content from nsIWebNavigation. For better offline/error experiences.

LucasR

<Read Only>

Last week

  • Top crasher fix
    • bug 1041448 – crash in java.lang.NullPointerException: at org.mozilla.gecko.home.PinSiteDialog$3.onFocusChange(PinSiteDialog.java)
  • Prep work to merge larch to m-c
    • bug 1053252 – Create different package name for larch so it can be installed beside Nightly
  • Tablet refresh (Fixing reftest failures)
    • bug 1014987 – Display tabs horizontally
    • bug 1015447 – Add a new tab from horizontal tab strip
    • bug 1017307 – Close a foreground tab on horizontal tab strip
    • bug 1017313 – Close a background tab from horizontal tab strip
    • bug 1018426 – Switch a tab on horizontal tab strip
  • Toolbar refresh
    • bug 1055536 – Too many differing background greys throughout the browser
    • bug 1057438 – Rewrite FadedTextView
    • bug 1060394 – Move FadedTextView to the widget package
    • bug 1061508 – Consider fading edge in toolbar’s title instead of ellipsis
    • bug 1063914 – Restore edit mode’s [x] icon
  • Misc
    • bug 1020505 – Regression: Browser menu has width issues
    • bug 1062231 – Menu share icon is misaligned to the right
    • bug 1065369 – Consolidate ‘add tab’ behaviour in Tabs

Next week

  • Merge larch to m-c
  • More tablet and toolbar stuff

liuche

<Read Only>

  • Follow-ups for Onboarding (bug 1059792, bug 1063748)
  • bug 1062257 – “Remove” behavior in home panels
  • reviews, chatting with UX about future onboarding
  • Next: search activity, Private browsing contextual hints

Margaret

<Read Only>

Highlights:

  • Settings telemetry
  • Search activity
  • Attending JSConf EU this weekend

Past:

Present:

mcomella

<Read Only>

Past
Present
  • Browser toolbar refresh
    • bug 1058909 – Implement new tablet toolbar display mode
  • bug 1001655 – Replace applicable Strings in test code with StringHelper references
  • bug 960746 – Back/forward button state can get out of sync on tablets
  • bug 1020534 – Tablet toolbar icons hard to read on dark lightweight themes
  • bug 1062338 – Regression: Back button icon missing in menu on some small screen (?) hardware (?) devices
Future
  • Too busy with other things:
    • Herding bug 941155 (fix talos on mobile to have pageloader tests working in regular mode and nochrome mode) along
    • bug 939350 – Create Python linter wrapper
  • bug 983437 – Delay FHR pruning until the screen is off
  • bug 989441 – Centralized documentation for writing tests

rnewman

<Read Only>

  • Attempting to kick-start a discussion around services to boost usage. Please chime in. https://mobile.etherpad.mozilla.org/service-brainstorming
  • Hacking away at dead code and obsolete libraries.
  • Landing stages of splitapk work.
  • Got frustrated, decided to fix Sync’s scheduling on desktop. We now sync automatically when your machine wakes from sleep.
  • Reviews, advice, perf, etc. etc. — the usual.
Fixed
Working on
Upcoming
  • Accept-Language stuff.
  • More perf/APK work.

nalexander

<Read Only>

  • Code: Remote Tabs home panel has landed (bug 1014994). Many small tickets still open to hammer out issues (bug 1063742, bug 1063765) and re-instate cut features (bug 1064304). Split pane tablet view should hit review this week.
  • Reviews: working with ckitching to make annotation processing a Real Child. ckitching claims significant code size wins (~100s of kb) if we can make Proguard obfuscate our sources safely. Action in bug 1064554.
  • Testing: first meetings (jlund, gbrown) and feedback cycle for running instrumentation tests in automation (meta bug is bug 1064004).
  • Testing: |mach robocop| has landed (bug 874729).
Past
Present

Antlam

  • Past
    • Toronto Work week
    • N2R project moving forward
    • Started co-ordination with Arcadio’s team for Firefox for Android’s own website
    • bug 946471: Firefox channel on Roku
    • Firefox Search UX work
  • Upcoming
    • bug 1065065: Firefox Search visuals for history items
    • bug 1060413: V1 visuals for default state of tablet UI
    • Tablet’s overview presentation with Yuan

Yuan

  • Last week
    • Synced up with Robin on addons and N2R
    • Presented launcher and lock screen study to mobile team
    • Talked to Arcadio about onboarding “Get Started”
    • Worked with Anthony on Tablet Refresh
    • Gave UX feedback to bug 1062257, bug 1061612, bug 1060678
  • This week
    • Continue the work on Tablet Refresh with Anthony
    • Coordinate with mozilla.org and creative team on Android product page and in-product onboarding: bug 1064538
    • Follow up the implementation of Share to Firefox, light-weight onboarding screen
    • Give UX feedback to bug 847435,bug 989094.

Robin

Last week

  • Met with Yuan and Anthony re: (N2R)
  • Add-on research
  • Menu refresh

This week

  • N2R \m/
  • Continue Add-on research
  • Continue Menu refresh
  • Syncing up with Anthony and Yuan
  • Provided feedback on bug 1044401

WebRT

  • bug 960584 – notify user of download progress indication when fetching APK – landed
  • bug 1021395 – Web app machinery dumps lots of semi-sensitive data to logcat – WIP rebased
  • bug 1029691 – Manifest not being checked on APK installation – needs rebasing

QA

Garvan

Feature Focus

Firefox 33 (Beta) – Release: Oct 14, 2014

Firefox 34 (Aurora) – Release: Nov 25, 2014

  • [ON TRACK] Provide a wifi toggle widget on error pages
  • [AT RISK] Tab mirroring (Roku)
  • [ON TRACK] Tab mirroring (Chromecast)
  • [ON TRACK] Toolbar Updates
  • [ON TRACK] Add support for Restricted Profiles (Prefer: safe)
  • [ON TRACK] Share handler overlay (landed but not turned on, nightly & aurora only)
  • [ON TRACK] Form auto-fill improvements, native client-side work
  • [ON TRACK] Kindle-related fixes
  • [ON TRACK] First-run Splash Screen Overlay

Firefox 35 (Nightly) – Release: Jan 6, 2015

  • [PROPOSED] Tablets: tabbed browsing refresh v2
  • [ON TRACK] Sync Tabs panel
  • [PROPOSED] Settings Rewrite (includes:bug 975377
  • [IN PROGRESS] Fatfennec: Minifying JS
  • [ON TRACK] Search activity v1
  • [ON TRACK] Moz Stumbler
  • [PROPOSED] Preferred web content language
  • [PROPOSED] Tablets: tabbed browsing refresh v1
  • [PROPOSED] Change default search engine to Bing
  • [IN PROGRESS] Fatfennec: Splitting the APK – gingerbread phone release
  • [BLOCKED] {{{1}}} Turn on HTTPS for Bing bug 958873
  • [PROPOSED] Privacy: DDG as a built in search engine

Details

  • Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 99998
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 99998
  • irc.mozilla.org #mobile for backchannel
  • Mobile Vidyo Room

Meeting NotesFirefox/Gecko Delivery Planning: 2014-09-10

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

  • Chemspills :(
    • Firefox for Android 32.0.1 built yesterday, may ship as early as today
      • bug 1046017 Taps are offset on some devices
      • Ride along: bug 1063971 setRemoteDescription call without success-callback freezes PeerConnection queue (FF32 regression)
    • Firefox Desktop 32.0.1, candidate bugs
      • bug 1062452 Firefox 32.0 crashes frequently in aticfx32.dll with switchable Intel+ATI graphics
      • bug 1063048 Firefox 32 startup crash in _VEC_memzero | _VEC_memzero
      • bug 1063052 Firefox 32 startup crash in nsFrame::BoxReflow
      • Ride along: bug 1046645 Mixed content favicon is shown when loading a SSL site right after opening a new tab
      • Ride along: bug 1063971 setRemoteDescription call without success-callback freezes PeerConnection queue (FF32 regression)
  • Beta
    • 33.0 beta2 shipped yesterday
      • Enabled second screen sharing (aka chromecast), which was disabled in beta1
    • Desktop beta3 gtb Thursday
    • Desktop and mobile beta4 gtb Monday
      • Last 33 beta release that will have loop enabled

Firefox Desktop & Platform (Javaun/Chad/Martin)

Summary of Work In Progress
  • You can find the most recently completed iteration (34.3) performance report here
  • You can see the status of the current iteration (35.1) in progress here
Uplifts
Beta (33)
  • New error page is poor color contrast. ( Bug 1009812 )
  • Intermittent ERROR: AsyncShutdown timeout in profile-before-change Conditions: [{“name”:”Experiments.jsm shutdown”,”state”:”(none)”,”filename”:”resource://app/modules/experiments/Experiments.jsm”,”lineNumber”:408},… ( Bug 1012924 )
  • about:networking hostname list not clearing after deleting history ( Bug 1020539 )
  • New error pages are unable to be styled by 3rd party complete themes ( Bug 1035536 )
Aurora (34)
  • Implementation: Use something other than a modal dialog to ask for setting the default browser ( Bug 951627 )
  • Support RTL mode in the panel ( Bug 1050309 )
  • Use HiDPI ICO favicons throughout the UI ( Bug 1052174 )
  • Fix typos and improve some of the Loop text ( Bug 1058258 )
  • 5.68% tart windows regression on fx team (v.34) August 15 from bug 862563 ( Bug 1060460 )
Summary of Recent Landings
  • Team landed 31 bugs over the last week, for the first half of the 35.1 iteration.
  • Details of landings from the past week can be seen here

Firefox Mobile (Mark/Brad/Jenn)

Work In Progress

You can find more on upcoming feature plans in the[roadmap]

Uplifts from the past week
Release(32)
Beta (33)
  • Add UI telemetry for managing search engines ( Bug 1007523 )
  • Taps are offset on some devices ( Bug 1046017 )
  • Browser menu missing dividers in Android L Preview ( Bug 1050780 )
  • Setting to clear data on quit doesn’t clear tabs from last time panel ( Bug 1052387 )
  • Notify Gecko when browser history is cleared from HistoryPanel ( Bug 1060678 )
  • Casting video is disabled on Beta ( Bug 1063893 )
Aurora (34)
  • Change ‘Cast to’ term to ‘Send to ‘ in-product ( Bug 1054912 )
  • java.lang.NoSuchMethodError: android.net.ConnectivityManager.isActiveNetworkMetered ( Bug 1057626 )
  • crash in java.lang.IllegalStateException: Already registered Wifi:Enable at org.mozilla.gecko.EventDispatcher.registerListener(EventDispatcher.java) ( Bug 1061030 )
Landings from the past week
Nightly (35)
  • Remove gradients from form elements ( Bug 763671 )
  • Create a synced tabs panel (Bug 1014994)
  • Regression: Browser menu has width issues ( Bug 1020505 )
  • Not obvious that browser menu is scrollable on small screen devices ( Bug 1048300 )
  • Crash on stop attempt after display wake up – java.lang.NullPointerException @ org.mozilla.gecko.ChromeCast.end(ChromeCast.java:254) ( Bug 1055020 )
  • [Roku] tapping the back button on Android doesn’t dismiss the ‘cast to device’ dialogue ( Bug 1055484 )
  • Too many differing background greys throughout the browser ( Bug 1055536 )
  • crash NPE in: Attempt to invoke interface method void org.mozilla.gecko.util.EventCallback.sendSuccess(java.lang.Object) on a null object reference at org.mozilla.gecko.ChromeCast$VideoPlayCallback.onStatusUpdated(ChromeCast.java) ( Bug 1055553 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.ChromeCast$VideoPlayCallback.onStatusUpdated(ChromeCast.java) ( Bug 1055554 )
  • Kindle: No way to remove Firefox account ( Bug 1056707 )
  • WEBGL_draw_buffers extension incorrectly exposed in Firefox on some GLES3 devices ( Bug 1056947 )
  • Telemetry for search widget buttons ( Bug 1057613 )
  • Cut function in a readonly textarea ( Bug 1060423 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.overlays.ui.ShareDialog.slideOut(ShareDialog.java) ( Bug 1061685 )
  • Autophone – webappstartup test does not run ( Bug 1062097 )
  • Menu share icon is misaligned to the right ( Bug 1062231 )
  • Regression: No context menu action is invoked on long-tapping some links ( Bug 1062307 )
  • Use empty string as title if no title provided when adding a bookmark ( 1062552 Bug 1062552 )

Market Insights from the Market Strategy Team (Kev)

Something to think About

There’s been some talk about how HTTPS by default would help mitigate things like Comcast’s Open Wifi hotspots helpfully performing content injection of ads into people’s browsing session(s) and other deep-packet inspection by various parties. This type of activity has the potential to become another war of attrition between browser orgs and adware/malware providers, and brings the certificate store into the spotlight. The certificate store, and continuing to validate its content, is something we should probably pay more attention to as more and more content is delivered via HTTPS as a default.
Why we should care: Trust is important, and so is encrypting traffic end-to-end. As more of that traffic is encrypted, the cert store can become a target for malware. We need to ensure that as we push HTTPS, we also keep an eye on the pieces that make it work.

Things we’re working on

https://wiki.mozilla.org/Mobile/Janus

Pinning on tiles.services.mozilla.com

bug 1030135

Worth a Read

  • In addition to the addition of NFC to the iPhone 6, Apple also introduced its Pay system to make NFC transactions more appealing to retailers and payment providers. Just incorporating NFC hasn’t been enough to get mobile payments off the ground in the US, and Apple’s partnering with banks, credit companies, and payment providers may give it the boost it needs. developer site here.
  • Oracle will only certify Firefox ESR for use with its E-Business Suite, citing Firefox’s 6-week release as a pain point. Chrome is still not officially certified. Good opportunity to make a little noise around ESR in the corporate environment.

Notes

Marketing, Press & Public Reaction (Arcadio)

  • Non-Verbal Update
  • Firefox 32 Press as of Sept 4 (Android and Desktop)
  1. Europe: 90+ stories
  2. LATAM: 14+ Stories
  3. US: 18+ stories including a nice piece on WebRTC (Hello) and Roku/Chromecast support on Android on Techcrunch
  • Accounts snippet support in progress
  1. Numbered list item
  • Sync landing page revision currently on demo server ready for QA
  1. Sync landing page launch pushed to w/o 9/15

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

Meeting NotesMozilla Platform: 2014-09-09

Need To Know

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

Notices/Schedule (lmandel)

Next Merge: October 13, 2014 Next Release: October 14, 2014
Trains
Central: 35 Aurora: 34 Beta: 33 Release: 32
  • Desktop: Remaining throttled until Thu as we investigate candidate 32.0.1 drivers
  • Android: Going to build with 32.0.1 today.
    • Driver
    • Ride along candidates:
      • bug 1063971 setRemoteDescription call without success-callback freezes PeerConnection queue (FF32 regression)
      • bug 1064247 FF32 generates invalid a=fmtp:0 profile-level-id fmtp
  • 33 beta 2 ships today
  • 33 beta 3 desktop – gtb Thu
  • 33 beta 4 desktop/mobile – gtb Mon
  • Firefox 32 post mortem, Tue Sep 16, 2014, 10am PT, ReleaseCoordination Vidyo

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.)

OrangeFactor (ryanvm)

<Read Only>

  • Past week’s OrangeFactor: 3.44 (last week: 5.01).
  • The top of the list is mostly dominated by mobile failures, both B2G and Android.
  • Waiting on Aurora approval requests for MediaStreamGraph refactor fixes that were causing frequent oranges.
  • 16 intermittent failures fixed in the last week – List – Thanks!.

MemShrink (njn)

  • Boris Zbarsky fixed a bad memory leak. If you were seeing ghost windows in your Nightly build recently, this is probably the reason. The patch has been backported to Aurora.

Stability (kairo/bsmedberg)

  • Release has about 10% of all crashes in three bugs that are somewhat concerning: bug 1062452 (~5%, GFX), bug 1063048 (~3%, GFX), bug 1063052 (~1%, Layout)
  • Desktop Beta has high crash rates due to multiple GFX crashes in the top ranges, probably OMTC/D3D11 work
  • Mobile Beta has two GFX bugs that cause bad crash rates: bug 1028802 (was supposed to be fixed in 33 but isn’t), bug 1041744

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.)

A*Team (jgriffin)

<Read Only>

Blog and newsgroup posts:

DOM (jst/overholt)

  • Service Worker hackathon is on (in Arlington)!
  • DOM Window bindings are here to stay (no more pref).

Electrolysis (e10s) (blassey)

  • Please help dogfood e10s in Nightly!
  • This week, more fixes landed for browser usability and add-ons
  • List of tested add-ons (compatible and incompatible): http://arewee10syet.com

Firefox Desktop (gavin)

<Read Only>

Team meetings in Toronto last week

Summary of Work In Progress
  • You can find the most recently completed iteration (34.3) performance report here
  • You can see the status of the current iteration (35.1) in progress here
Summary of Recent Landings
  • Team landed 31 bugs over the last week, for the first half of the 35.1 iteration.
  • Details of landings from the past week can be seen here

Fx 34 Demos:

  • No longer freezing with findbar on huge pages
  • Lightweight theme switching from customize mode
  • Screen/app sharing
  • Loop FxA – login backend and toolbar button states
  • Remoting about: pages
  • parsing search URLs to show search terms in awesomebar results

Firefox Mobile (snorp/blassey/mfinkle)

Work In Progress
  • WebRTC OpenGL on Roku – fixing and tweaking
  • Moz Stumbler is almost there. Needs a permission bump to land.
  • Remote Tabs home panelbug 1014994expected to land by EOW
  • Janus https://wiki.mozilla.org/Mobile/Janus
    • Stream transfer rate and memory profiling metrics

You can find more on upcoming feature plans in the[roadmap]

Landings from the past week
Nightly (35)
  • Remove gradients from form elements ( Bug 763671 )
  • Regression: Browser menu has width issues ( Bug 1020505 )
  • Taps are offset on some devices ( Bug 1046017 )
  • Not obvious that browser menu is scrollable on small screen devices ( Bug 1048300 )
  • Browser menu missing dividers in Android L Preview ( Bug 1050780 )
  • Change ‘Cast to’ term to ‘Send to ‘ in-product ( Bug 1054912 )
  • Crash on stop attempt after display wake up – java.lang.NullPointerException @ org.mozilla.gecko.ChromeCast.end(ChromeCast.java:254) ( Bug 1055020 )
  • [Roku] tapping the back button on Android doesn’t dismiss the ‘cast to device’ dialogue ( Bug 1055484 )
  • Too many differing background greys throughout the browser ( Bug 1055536 )
  • crash NPE in: Attempt to invoke interface method void org.mozilla.gecko.util.EventCallback.sendSuccess(java.lang.Object) on a null object reference at org.mozilla.gecko.ChromeCast$VideoPlayCallback.onStatusUpdated(ChromeCast.java) ( Bug 1055553 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.ChromeCast$VideoPlayCallback.onStatusUpdated(ChromeCast.java) ( Bug 1055554 )
  • Kindle: No way to remove Firefox account ( Bug 1056707 )
  • WEBGL_draw_buffers extension incorrectly exposed in Firefox on some GLES3 devices ( Bug 1056947 )
  • Telemetry for search widget buttons ( Bug 1057613 )
  • java.lang.NoSuchMethodError: android.net.ConnectivityManager.isActiveNetworkMetered ( Bug 1057626 )
  • Cut function in a readonly textarea ( Bug 1060423 )
  • Notify Gecko when browser history is cleared from HistoryPanel ( Bug 1060678 )
  • crash in java.lang.IllegalStateException: Already registered Wifi:Enable at org.mozilla.gecko.EventDispatcher.registerListener(EventDispatcher.java) ( Bug 1061030 )
  • crash in java.lang.NullPointerException: at org.mozilla.gecko.overlays.ui.ShareDialog.slideOut(ShareDialog.java) ( Bug 1061685 )
  • Autophone – webappstartup test does not run ( Bug 1062097 )
  • Menu share icon is misaligned to the right ( Bug 1062231 )
  • Regression: No context menu action is invoked on long-tapping some links ( Bug 1062307 )
  • Use empty string as title if no title provided when adding a bookmark ( 1062552 Bug 1062552 )
  • Casting video is disabled on Beta ( Bug 1063893 )

Firefox OS Connectivity (vchang)

<Read Only>

    1. https://wiki.mozilla.org/TPE_CONNECTIVITY_GROUP/2014-09-09

Firefox OS Devices/Porting (ericchou)

  • Bluetooth (members: Shawn Huang, Ben Tian, Jamin Liu, Jocelyn Liu)
    • Woodduck Bluetooth bring-up issues
    • The team has begun BLE API implementation
  • Media Playback (members: Bruce Sun, Blake Wu, Star Cheng)
    • bug 1033915 – Integrate MP3FrameParser with MediaCodecReader – landed (2.1 feat+)
      • MediaCodec integration (pref off) has been done after this was landed.
    • MSE for Firefox OS has been removed from v2.1 after discussion with related people.
  • Device Storage (members: Alphan Chen, Eden Chuang)
    • bug 1061117 – Screenshot/take pictures would let device reboot when MTP enabled – r+ (2.1+)

GFX (milan)

  • Direct2D issues in play: some on the release channel (e.g., unrelated to OMTC), may need to play with the blacklist
  • Current work in progress
    • Tiling on desktop
    • WebGL performance
    • B2G 2.0, 2.1
  • Working with PMs on the priorities for 36-39 releases.

Layout (jet/dbaron)

  • CSS Working Group F2F meeting now in progress.
  • Issues from last week’s heavy landings now fixed (bug 967844,bug 1059033)
  • bug 931668 Big perf wins from new style system optimizations
  • bug 997101 App startup perf wins (re-)landed after race condition removal bug 1063073
  • bug 1022825 CSSOM Smooth Scrolling for APZ platforms (like B2G)

Media (mreavy)

<Read Only>

  • Continuing cleanup from MediaStreamGraph refactor (bug 848954)
  • Windows UI-loop screensharing fixes almost ready
  • Accidental disabling in FF32 of a permissive response to sites that didn’t include success/failure callbacks to setRemoteDescription() (spec violation, but common in examples); fix landed and noiminated for any 32.1.
    • patch to warn people we’re going to deprecate spec-non-compliance ready
  • Dealing with some final B2G 2.0 issues with WebRTC/OMX video codecs/HW AEC at QC’s request to cut CPU use
  • Lots of work on Loop!
    • Loop is slated to be disabled in Beta/33 soon.
    • Planning to ride the train to release in 34

Necko (dougt/jduell)

  • bug 936814: Resource Timing cross-origin requests finally working. A few (easier to fix) bugs and we’ll be able to finally expose Resource Timing to the DOM.
  • Google.com HTTP/2 kerfuffle: they turned on some of their services with a broken HTTP/2 implementation that worked with Chrome (also broken) but not Nightly (spec-compliant). They backed off and reverted to HTTP/1.1 for now

Performance (vladan)

No update

Seceng (ckerschb)

  • New CSP backend (compiled code) is on average 15x faster than old one that we removed in Fx 34.

Shumway (tschneidereit)

  • New version of Shumway merged, still off by default, to Nightly 35. To test, flip “shumway.disabled” pref to false.

Roundtable

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

<Read only beyond this point>

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 2014-09-0911:00 am Pacific Standard Time
  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 98411
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 98411
  • 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

Meeting NotesMozilla Project: 2014-09-08

All-hands Status Meeting Agenda

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

Friends of Mozilla

A huge “spaceba” to Max Zhilyaev for marketing tag line translations for the Russian activations directory. “Domo Arigato Gozaimasu” to Manabu Ito for marketing tag line translations for the Japanese activations directory. “Děkuji” to Michal Stanke for localization of the Czech activations directory.

Jorge Aparicio (japaric) created the Eulermark benchmark from the Project Euler problems, demonstrating that Rust compares favorably to C++ in many cases.

Thank you to Bob Reyes for wrangling the Mozilla Philippines community work last week!

All hail CodingFree, who worked over the weekend to review several updates to the ConnectA2 app to help fix the connectivity issues in India.

Upcoming Events

Monday, 08 September

Please send your contribution opportunities for the Community Newsletter to jhalperin@mozilla.com

The latest edition of DevPulse is out – take a peek to see all the great stuff happening in the world of developers, the web & Mozilla, and email diane@mozilla to be added to the email dist list.

Tuesday, 09 September

3pm-3.30pm BST: Introduction to Web Audio – live from Mozilla London!

12pm – 1pm PT: reddit AMA on net neutrality with Dave Steer and Chris Riley. Please participate here.

Intern Presentations!

  • 1:00PM 1:00- Filipe Gonçalves, “Coping with memory addiction: tricking Firefox OS for fun and profit” SF
  • 1:30PM 1:30- Bernardo Rittmeyer, “TBD” SF
  • 2:00PM 2:00- John Zeller, “TBD” SF
  • 2:30PM 2:30- Chance Zibolski, “Heka, the “Swiss Army Knife” of Data” SF

Bi-weekly Markeplace Community Meeting: 10am Pacific. It’s getting easier to plug into this project, so come and see how you can make an impact this month.

Mozilla Wiki team meeting (Wiki Working Group): 8:30am PT / 15:30 UTC (in your timezone). Agenda & How-to participate: MozillaWiki:Team#Meetings

Wednesday, 10 September

A Day of Action to protect net neutrality (read about Mozilla’s involvement here)

Homebrew Website Club Meetup

  • Chicago, Minneapolis, Portland (@MozPDX), and San Francisco (@MozSF)!
  • 17:30-18:30 Writing Hour
  • 18:30-19:30 IndieWeb discussions and hack night

Are you creating your own website? Indie reader? Personal publishing web app? Or some other digital magic-cloud proxy?

If so (or you want to!), come on by and join a gathering of people with like-minded interests. Bring your friends that want to start a personal web site. Exchange information, swap ideas, talk shop, help work on a project…

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

Mozpub

  • Mozfest Volunteer social in the common space at Mozilla LDN from 18:30- 21:00
  • Sign up here to attend

Intern Presentations!

  • 1:00- Sylvain Cleymans, “Better, faster, lighter: improving the mobile web experience with the Janus proxy” MV
  • 1:30- Dean Johnson, “TBD” MV
  • 2:00- Ian Kronquist, “TBD” MV
  • 2:30- Tyler Smith, “TBD” MV
Thursday, 11 September

Reject.JS

  • Berlin, Germany
  • Romain Gauthier presenting “WebRTC – A Tale of Beekeeping”

Intern Presentations

  • 1:00- Robert Bindar, “Hacking through notifications” SF
  • 1:30- Sean Bolton, “Why We Build How We Build” SF
  • 2:00- Roshan Vid, “TBD” SF
  • 2:30- Laleh Aghababaie Beni, “TBD” SF

FOSSETCON

  • Orlando, FL, US Sept 11-13
  • Brandon Johnson: “Databases: from root to riches”
Friday, 12 September

RemoCamp in Berlin, until Sept 14th.
More info on the wiki: https://wiki.mozilla.org/ReMo/Council/ReMo_Camp_2014

CSSconf EU

  • Berlin, Germany
  • Angelina Fabbro and Jeff Griffiths attending

Web Audio Hack Day

  • Berlin, Germany
  • Soledad Penades running workshop
Saturday, 13 September

JSConf EU – third of our “Big 5 Developer Events” for 2014

  • Berlin, Germany Sept 13-14
  • Tim Taubert: “Keeping secrets with JavaScript: An Introduction to the WebCrypto API”
  • Frederick Braun: “We’re struggling to keep up (A brief history of Browser Security Features)”
  • Jan Jongboom: “Abusing phones to make the internet of things”
  • Christian Heilmann, Angelina Fabbro, Jeff Griffiths, Margaret Leibovic, Guillaume Marty, Gregor Wagner, Jordan Santell attending
  • Mozilla sponsoring and running Hacker Lounge

Project Status Updates (voice updates)

Firefox

Speaker Location: Toronto first, then Remote (johnath, then Winston)

  • Growth team update – Winston Bowden (remote)
    • Quick update on the team, our goals, and how to get involved. Want to learn more? Visit our wiki page (https://wiki.mozilla.org/Growth_Team) and if you have questions or feedback, please contact Eric Petitt, Chris More or Winston Bowden or visit us in #growth on IRC.
      • Buttons make a difference
      • Instadownloads
      • Download Rescue
Firefox for Android

Speaker Location: remote (mfinkle)

  • Fx32
    • First release with some feedback-based changes appearing
    • Cleaner startup appearance with suggested site thumbnails
    • Pick your UI language from inside Firefox
  • Fx33
    • Send videos to second screen
    • More feedback-based changes
    • Better tab handling
Firefox OS

Speaker Location: Faramarz Rashed / Chris Lee – Mountain View

  • Already seeing value from our team changes —
    • OS team is focused on delivering the best product to all our users (differentiation)
    • Devices team is focused on working with our partners to deliver the optimal product to their markets
  • We wrapped up our v2.1 FL milestone last week — best development cycle to date, great work by everyone on the team!
  • v2.1 FC is our next milestone on Oct 13 — team is laser focused on quality/stability/perf
  • Release changes coming after 2.1 and we’ll share an update soon once those have been finalized.

Speaker Location: Asa Dotzler in Mountain View

  • Arvin Huang is a grad student at National Cheng Kung University in Taipei, and he fixed his first 2 Firefox OS bugs this week, a pair of [good first bug][mentor-lang=zh] (http://mzl.la/1pIjDG2) Gaia Build jshint error bugs.
  • Last tuesday, Mozilla branched Firefox OS 2.1/Gecko 34 and opened OS 2.2 development. (Also, mozilla-b2g28_v1_3 has been shut down.)
  • Over the last week, ~130 Mozillians contributed code to resolve ~300 Firefox OS issues.
  • The top three contributors by volume were
    • John Lu in Taipei, who worked heavily on Lockscreen and Keyboard
    • Arthur Chen, also in Taipei, brought us some serious new feature work on APN
    • and Keven Grandon, out of San Francisco, landed lots of improvements to Rocketbar/Homescreen, and browsing.
  • Foxtrot program is delayed while we wait on proper nightly builds from our partner. An email to this effect will go out this week. While we don’t yet have a definite date, it’s our hope to get things moving in weeks, not months.
  • Mozilla Flame stock nearly exhausted. We’re ordering more Flames to give away to our community of contributors. If Firefox OS is your job and you don’t have a Flame to work on, please let me know ASAP (asa@mozilla.com)
  • VIA Vixen tablets on the way. We’ll open a second round of tablet applications, similar to first round. Vixen contributors will work within the larger Tablet Contribution Program to further the development of Firefox OS for larger form factors.

      A taste of recent Firefox OS changes:

  • bug 1057578 – New overscroll effect. Scrollable content is stretched uniformly along the overscrolled axis
  • bug 1033549 – Data tracking on a per app basis.
  • bug 903683 – Support for user configurable 24 hour time format
  • bug 1032631 – EU roaming APN support
  • bug 1026685 – CMAS Alert channel support. Location-based messaging for governments
  • bug 1011738 – Theme support for b2g/gaia
  • bug 1060081 – Support for Flame Kitkat (KK) builds
  • bug 1060879 – Fixes first tap on keyboard being inaudible
  • bug 1046336 – New homescreen unlock and keyboard sounds.
  • bug 985334 – Long press on a key, the first choice should be the key that is pressed.
  • bug 1054184 – Keyboard 2.1 often misses first keystroke
  • bug 1061439 – Prevent IMEngine from touching layouts when inputcontext is gone
  • bug 1048792 – Keyboard should not autocorrect words with different char count than input
  • bug 1048869 – Keyboard autosuggest nearby keys algorithm doesn’t value vertical alignment enough
  • bug 1016184 – Enable touch caret on B2G and fix the existing test case failures
  • bug 1029943 – Enable selection carets on B2G and fix the existing test case failures
  • bug 1042713 – Remove notification icons from status bar now that we have ambient notifications
  • bug 1035250 – Show cell and wifi status indicators as users progress through First Time Experience
  • bug 1054352 – New videos in FTE tutorial for Vertical Scroll, Sheets, Universal Search, Notifications
  • bug 1038723 – Visual refresh of the utility tray and ambient notifications.
  • bug 1056969 – Prettifies the data connection indicators in the statusbar
  • bug 1030925 – Visual Refresh in Messaging
  • bug 1041765 – Messaging thread view redesign
  • bug 1048845 – Messaging Compose Panel refresh (subject behavior change)
  • bug 1048362 – Messaging Compose Panel refresh (highlight actionable part)
  • bug 1043177 – Contacts App: The current Contact edit page is quite messy
  • bug 885110 – Email App: Switch to whiteout-io email.js libraries
  • bug 1019816 – Developer option to store logcat to sdcard by shaking the phone
Content Services
Webmaker

Brett Gaylor, remote from Victoria BC

  • A few images from the Maker Party to whet your appetite for our final retrospective
Mozilla Communities

Speaker Location: non-verbal / Surman

  • As noted last meeting, we’re actively looking for new ways community can have impact on topline goals in Q3/Q4.
  • We’ve developed a tentative set of goals for this time frame, which are:
    • Maintain momentum on our community goal (Q3/4)
    • Start new community initiatives / challenges that interest volunteers and have positive impact on our product goals (Q3/4)
    • Involve leadership from across the project and within regional communities (Q3/4)
    • Design an even more ambitious plan for 2015+ (Q4)
  • We’ll be discussing these goals and short term community ‘challenges’ tied to products at ReMo camp in Berlin next weekend.
  • Full update from Mitchell / Surman coming on this topic next week. Non-verbal for today.
Web Compat

Speaker Location: Vidyo (miketaylr)

FYI: Our team is doing some work to clean up the Tech Evangelism product, moving valid issues to the Desktop component. Going forward, please use that rather than language specific products.

Recent bug fixes:

Bugs wanted: http://webcompat.com/

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
Dave Steer Director of Advocacy Net neutrality Day of Action + reddit AMA SF no https://blog.mozilla.org/netpolicy/2014/09/04/a-day-of-action-to-protect-net-neutrality/, https://www.reddit.com/r/IAmA/, http://mzl.la/nnpetition
Anthony Duignan-Cabrera Editor in Chief of the Site-Formerly-Called-Mozilla-Voices The NEW name for Mozilla Voices is… NYC no https://blog.mozilla.org/community/2014/09/04/mozilla-voices-has-a-new-name/
Lukas Blakk, Kronda Adair, Debbie Cohen, Dino Anderson, and the awesome, trailblazing cohort ASCEND Project The Ascend Project is a 6 week, full time training program that provides financial support, equipment, meals, transit, and childcare reimbursement in order to remove many of the barriers to immersive learning in Open Source technology. Portland in da haus No No ASCEND Project
Josh Carpenter Virtual Reality Research Call for generative artists & creative coders SF No Yes

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
Tom Tromey Jordan Santell SF Office US Remote Firefox Content Tools
Matt Rosenberg ADC Duignan-Cabrera New York Office US Remote Marketing Communications
Brittany Storoz Fred Wenzel Portland Office NYC Apps Engineering
Alberto Pastor Michael Henretty San Francisco Office Barcelona Firefox OS

<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 1056162 Bugzilla can now create short URLs for bug searches (using bit.ly)

All changes.

Engagement

  • Dial-in: conference# 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/Vancouver: +1 778 785 1540, x92 Conf# 8600
    • CA/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
    • US/Toll-free: +1 800 707 2533, (pin 369) Conf# 8600

Mozilla Web DevelopmentBeer and Tell – September 2014

September’s Beer and Tell has come and gone.

A practical lesson in the ephemeral nature of networks interrupted the live feed and the recording, but fear not! A wiki page archives the meeting structure and this very post will lay plain the private ambitions of the Webdev cabal.

Mike Cooper: GMR.js

Mythmon is a Civilization V enthusiast, but multiplayer games are difficult — games can last a dozen hours or more. The somewhat archaic play-by-mail format removes the simultaneous, continuous time commitment, and the Giant Multiplayer Robot service abstracts away the other hassles of coordinating turns and save game files.

GMR provides a client for Windows only, so Mythmon created GMR.js to provide equivalent functionality cross platform with Node.js. It presents an interactive command line UI. This enables participation from a Steam Box and other non-windows platforms.

Bramwelt: pewpew

Trevor Bramwell, summer intern for the Web Engineering team, presenting a homebrew clone of space invaders he calls pewpew. He built is using PhaserJS as an exercise to better understand prototypal inheritance. You can follow along as he develops it by playing the live demo on gh-pages.

Cvan: honeyishrunktheurl

Chris Van shared two new takes on the classic url shortener. The first is written in go, with configuration stored in JSON on the server. It was used as an exercise for learning go. The second is an html page that handles the redirect on the server side.

He intends to put them into production on a side project, but hasn’t found a suitable domain name.

Cvan: honeyishrunktheurl

Chris Van held the stage for a second demo. He showed how the CSS order property can be used to cheaply rearrange DOM nodes without destroying and re-rendering new nodes. An accompanying blog post delves into the details. The post is worth a read, since it covers some limitations of the technique that came up in discussion during the demo.

Lonnen: Alonzo, pt II

Last time he joined us, Lonnen was showing off a scheme interpreter he was writing in Haskell called Alonzo. This month Alonzo had a number of new features, including variable assignment, functions, closures, and IO. Next he’ll pursue building a standard library and adding a test suite.


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!

WebmakerMozFest 2014: Spotlight on “Source Code for Journalism”

This is the third post in a series featuring interviews with the 2014 Mozilla Festival “Space Wranglers,” the curators of the many exciting programmatic tracks slated for this year’s Festival.

For this edition, we chatted with Erika Owens, the Space Wrangler for the Source Code for Journalism track. Participants in this track will design next-generation web solutions to solve critical issues facing news organizations and help journalism thrive on the open web.

What excites you most about your track?

It’s been awesome to see the journalism track evolve over the past few years, and continue to build connections across other tracks at MozFest and between events. This year was the first time OpenNews hosted our own conference, SRCCON, which was heavily inspired by MozFest. Several sessions are coming to MozFest from SRCCON or from last year’s MozFest, so it’s going to be great to see how these sessions take shape and expand beyond the conferences.

Who are you working with to make this track happen?

Our growing community of Knight-Mozilla Fellows is contributing several sessions (plus, we get to welcome the 2015 class of Fellows at MozFest). News nerds from organizations around the United States and Europe are also participating, as well as several folks from the civic hacking community.

How can someone who isn’t able to attend MozFest learn more or get involved in this topic?

Keep up with our community calls for updates before and after the festival. We’ll recap parts of the event and have follow up on our site Source as well.

 

Inspired?

Head on over to the MozFest site to register!