This is the sumo weekly call

https://air.mozilla.org/weekly-sumo-community-meeting-july-13-2016-20160713/

Last month I spent a week working on IoT projects with a group of 40 researchers, designers and coders… in Anstruther, a small fishing village in Scotland. Not a high-tech hub, but that was the point. We immersed ourselves in a small community with limited connectivity and interesting weather (and fantastic F&C) in order to explore how they use technology and how ubiquitous physical computing might be woven into their lives.

The ideamonsters behind this event were Michelle Thorne and Jon Rogers, who are putting on a series of these exploratory events around the world this year as part of the Mozilla Foundation’s Open IoT Studio. The two previous editions of this event were a train caravan in India and a fablab sprint in Berlin (which I also attended, and will write up as well. I SWEAR.).

Michelle and Jon will be writing a proper summary of the week as a whole, so I’m going to focus on the project my group built: Bubble.

Context

From research conducted with local fishing folk, farmers from a bit inland, and a group of teenagers from the local school, we figured out a few things:

• Mobile connectivity is sparse and unreliable throughout the whole region. In this particular town, only about half the town had any service.
• The important information, places and things aren’t immediately obvious unless you know a local.
• Just like I was, growing up in a small town: The kids are just looking for something to do.

Initially we focused on the teens… fun things like virtual secret messaging at the red telephone boxes. Imagine you connect to the wifi at the phone box, and the captive portal is a web UI for leaving and receiving secret messages. Perhaps they’re only read once before dying, like a hyperlocal Snapchat. Perhaps the system is user-less, mediated only by secret combinations of emojis as keys. The street corner becomes the hangout, physically and digitally.

We meandered to public messaging from there, thinking about how there’s so much to learn and share about the physical space. What’s the story behind the messages to fairies that are being left in that phone box? I can see the island off the coast from here – what’s it called and what’s out there? Who the hell is Urquardt and what’s a “wynd”? Maybe we make a public message board as well – disconnected from the internet but connected to anything within view.

We kept going back to the physical space. We talked about a virtual graffiti wall, and then started exploring AR and ways of marking up the surroundings – the people, the history, the local pro-tip on which fish and chips shop is the best. But all of this available only to people in close physical proximity.

Implementation

Given the context and the constraints, as well as watching direction some of the other groups were going in, we started designing a general approach to bringing digital interactivity to disconnected spaces.

The first cut is Bubble: A wi-fi access point with a captive portal that opens a web page that displays an augmented reality view of your immediate surroundings, with messages overlaid on what you’re seeing:

A few implementation notes:

• We used a Raspberry Pi 3, running as a wi-fi access point.
• It ran a node.js script that served up the captive portal web UI.
• The web UI used getUserMedia to access the device camera awe.js for the AR bits and A-Frame for a VR backup view on iOS.
• We designed a logo and descriptive text and then lasercut some plaques to put up where hotspots are.

Designs, board, battery and boxes:

Challenges:

• Captive portals are hobbled web pages. You can’t do things like use getUserMedia to get access to the camera.
• iOS doesn’t have *any* way to let web pages access the camera.
• Power can be hard. We talked about solar and other ways of powering these.
• Gotta hope they don’t get nicked.

Bubble was an experimental prototype. There are no plans to work further on it at this time. If you’re interested, everything is on Github here. You can read more about the design here (PDF).

Thanks to fellow team members Julia Gratsova, Katie Caldwell, Vladan Joler. (Sadly, no Julia in the phonebox!)

https://autonome.wordpress.com/2016/07/12/bubble-and-tweak-iot-at-the-ends-of-the-earth/

I’m happy to announce that we now have an official set of curl stickers that you can get. Sorry, that came out wrong. That you should get! The first official curl stickers ever and they’re all based on our new and shiny logo.

These stickers are designed and sold by the great folks over at unixstickers.com and for every purchase you do, a small percentage of that adds up to stickers for me so that I can hand them out to peeps I meet.

Go order your own set!

https://daniel.haxx.se/blog/2016/07/12/curl-stickers/

https://rail.merail.ca/posts/thoughts-about-partial-updates-on-demand.html

Firefox 47 Release and Firefox iOS 4.0

In London, Mozlondon, we had a session on creating a SUMO Release Report a few weeks after major updates to Mozilla products. This post will be the first to include testimonials from users and submissions from users in the community to make it unique to SUMO. With the intention to highlight all of the work that the community comes to accomplish together, the user testimonials, feedback, copious issues found, brought to attention and solved, knowledge base articles created, and collaborated on, as well as article translations to so many languages and organized social media this report shows how much we need your help. Core Community Members and new ones are equally as important.  We have highlighted the issues that were and are actively being tracked down to improve Firefox and other Mozilla products.

We have lots of ways to contribute, from Support to Social to PR, the ways you can help shape our communications program and tell the world about Mozilla are endless. For more information: [https://goo.gl/NwxLJF]

Customer Kudos to the SUMO community

1104 users said “thank you” out of the 7300 answers during this time.

We cannot include all of the thank yous that were received, however these are many of the community members that also received thank yous from Firefox users. Shout outs to Fred, cor-el, Seburo, philipp, Matt, Zenos, Scribe, jscher2000, James, Wayne Mary, Chris Ilias, Christ1, the-edmeister, Tonnes, Toad-Hall. They all received direct thank yous from users and their solved issues.

Feedback and community highlights

• Great support from John 99, jscher2000, and FredMcD
  • Firefox becomes non-responsive, 40% CPU, 1.6 Gb private, then crashes
• Great support from Seburo
  • Urgent FireFox Update Notice

Knowledge Base

**No articles were linked from major publications (via Google Analytics.) but if you see any in your region, please mention them.

Localization

Support Forum Threads

One of the major impacted issues during the first three weeks of the release was an increase in reports to fake updates and malware from those updates. Many of them were reported and still be investigated.

• I received an “urgent Firefox Patch” notification: is this legitimate?
• Is this a patch from firefox? Firefox-patch.exe
• I got a Urgent Firefox update from https://phaitxiaoshoubang.org/8301092144808/e8f07d9270bdade361fab48a9d15e67e.html Should I manually install ?
• I got a red screen with the Firefox logo that says “Urgent Firefox update” asking to save the file firefox-patch.exe. This this real?
• More on this in this thread post: here

Not solved top viewed threads – GA

• ads.loadreviews.com pops up cannot got beyond it

In this spreadsheet: https://docs.google.com/spreadsheets/d/1YjeyJs-VrofC0qMkf5uv5DUtJzsZjrfopEBarZ-ePTI/edit#gid=1219676230

Bugs Created from Forum threads – SUMO Community

• [Noah] This typo has embarrassingly been in release on the Argentina locale since July 2015! :The word “nombre” (name) was misspelled “mombre”.
  • https://bugzil.la/1282867 – [es-AR] Translation update proposed for browser/chrome/browser/preferences/sync.dtd:changeSyncDevice
  • https://twitter.com/DonPollin/status/745140430128328704

Bugs mentioned

• “version 47.0 browser is not responding when i want to see print version”
  • https://support.mozilla.org/en-US/questions/1126533 Printing
• A significant crash caused by Flash was investigated, still hunting down the link…they uplifted it for beta 4
• There were not many this time, if you recall any for next time we would love to hear about them. What was searched  searched:
  • Opened bugs first three weeks in bugzilla
  • ‘bug’ keyword in open search
  • All threads from those three weeks can be seen: in this sheet titled, “Forum -> ” Link to Google Sheet

Social Support Highlights

Brought to you by Sprinklr

Total contributors in program

In this time we had a total of 14 of you login and participate in the Firefox 47 release.

New users added in period of the report

Welcome Magno, Daniella, Luis, and TheoC to the team you were very active these past three weeks and thank you for supporting Mozilla Open Source users on Facebook and Twitter on the Sprinklr tool.

Top 5 Contributors

Number of Replies: 111

Trending issues in Sprinklr

Outbound top engagement:

Each Facebook outbound post reached one person for support, the two major engagements overlapped with Code Emoji and the plane,

Top Twitter Posts

This version we removed the tag summary and are currently working on items that translate to more specific categories. Not working will be removed and more will be added. However taking a deep dive in the top categories for outbound messages to Mozilla Open Source product users this what we found.

• “Not working” is associated with these suggested troubleshooting steps and categories: antivirus was mentioned 3 times, malware  was mentioned once, trying a Firefox Refresh 1, hanging 1, Trying Safe mode 1, and Kaspersky 1, changing a Firefox setting was mentioned once, and a more complicated website issue was asked to troubleshoot in the forums. This can be concluded to be some of the most common troubleshooting steps for Firefox for Desktop described here: http://mzl.la/16zLrEU

• “Crashes” is associated with outbound troubleshooting that  say check out how to ttp://mzl.la/14A6XM2 or go to the support forum 50/50 of the time.

• “Video” tags were the third top category and basic troubleshooting were to clear the cache, asks if the website is the issue and suggests html5.

https://blog.mozilla.org/sumo/2016/07/12/firefox-47-support-release-report/

Topical Data Post: Pokemon Go

I live in Canada which means we hear a lot about things that are United States-only. The latest (and the largest, outstripping in volume and velocity even the iPhone (which I may misremember being the last must-have-thing back in 2007)) is the hit augmented-reality mobile game Pok'emon GO.

One gameplay mechanic of Pok'emon GO (I am told) revolves around hatching eggs. These eggs hatch not after a certain period of time, but after you have walked a certain distance with the application open on your phone.

The kicker is that the distance is measured in kilometres, a unit whose use the United States and United Kingdom have evaded (yes, despite the latter’s metrication since 1965). People in the United States are being confronted with unfamiliar distance units of 2km, 5km, and 10km.

This, via some Twitter jabs, lead me to Google Trends and a prediction: what if Pok'emon GO’s release date in a region that still uses miles as a unit of distance could be detected simply through the rise in search volume for the term “5km”?

So far, the data for the United States is consistent:

I await the UK launch date to follow-up.

:chutten

https://chuttenblog.wordpress.com/2016/07/12/units-and-data-pokemon-go/

Weekly project updates from the Mozilla Connected Devices team.

https://air.mozilla.org/connected-devices-weekly-program-update-20160705/

Q3 planning is in full swing. Chief priorities continue to be the migration to TaskCluster (TC) from buildbot, and release process improvements.

Modernize infrastructure:

Aki finished porting configman to python3 (merged!). https://github.com/mozilla/configman/pull/163

Windows try builds were enabled on TC Windows 2012 worker types in staging (allizom) (win32/win64, opt/debug). If all goes well, this will propagate to production in the coming days. This is the first set on non-Linux tasks we’ve had running reliably in TC, which is obviously a huge step in our migration away from buildbot.

Improve Release Pipeline:

Aki wrote dephash to pin python requirements to versions+hashes: http://escapewindow.dreamwidth.org/247093.html https://github.com/escapewindow/dephash https://pypi.python.org/pypi/dephash

Aki got signtool working with py3 (reproducibly this time), using requests. https://github.com/escapewindow/signtool https://pypi.python.org/pypi/signtool

We implemented a short cache for Balrog rules, which greatly reduced load on the database. https://bugzilla.mozilla.org/show_bug.cgi?id=1111032

Kim stood up beta builds with addon signing preferences disabled. This allows addon developers to test their addons prior to signing on release-equivalent builds. https://bugzilla.mozilla.org/show_bug.cgi?id=1135781

Improve CI Pipeline:

Francis disabled valgrind buildbot builds. Turning stuff off in buildbot #feelsgoodman. https://bugzilla.mozilla.org/show_bug.cgi?id=1278611

Kim enabled Android x86 builds on trunk running in TC. https://bugzilla.mozilla.org/show_bug.cgi?id=1174206

See you next week!

http://coopcoopbware.tumblr.com/post/147294191175

http://dtor.com/halfire/2016/07/12/end_of_an_experiment.html

Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us an email! Want to get involved? We love contributions.

This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

Updates from Rust Community

News & Blog Posts

• Announcing Rust 1.10.
• Refining Rust's RFCs.
• Translating C to Rust using Corrode (and how you can help).
• Rust and Rest. Lessons Learned from talking to Sentry's HTTP API from Rust.
• Pairing cryptography in Rust.
• Shave some time from your Travis builds.
• Overview of open source game engines in Rust.
• Rust & Docker in production @ Coursera.
• Integer 32, a Rust consultancy startup by Carol Nichols and Jake Goulding.

New Crates & Project Updates

• Dyon 0.8 is released.
• Corrode. Automatic semantics-preserving translation from C to Rust.
• Rustls. A new, modern TLS library written in Rust.
• rulinalg. A linear algebra library in Rust designed for machine learning, extracted from rusty-machine.
• task-hookrs. A Rust library for writing taskwarrior hooks and general interfacing with taskwarrior.
• jsf. A simple JSON file store.
• This week in Rust docs 12.

Crate of the Week

No create was selected for CotW.

Submit your suggestions for next week!

Call for Participation

Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

Some of these tasks may also have mentors available, visit the task page for more information.

• [easy] cargo: Warn on duplicate entry points for libs and bins.
• [easy] cargo: Can't specify precise crate version if there are multiple versions.
• [easy] cargo: Add --dry-run to cargo publish.
• [easy] rust: E0502 not rendered correctly.
• [easy] rust: Move some tests into run-pass-valgrind.
• [moderate] rust: Convert compiler-rt builtins to a Rust crate.
• [moderate] rust: Teach rustc to print CPU, etc. features.
• [easy] rustfmt: Overlong function signatures.
• [easy] rustfmt: Overlong impl signatures.
• [easy] rust-by-example: Add a Mutex chapter.
• [easy] rust-by-example: Add an Arc chapter.
• [easy] imag: Make imag forward --debug and --verbose to subcommands.
• [moderate] imag: Add Iterator-shortcut for iter.fold(Ok(()), ...).

If you are a Rust project owner and are looking for contributors, please submit tasks here.

Updates from Rust Core

100 pull requests were merged in the last two weeks.

• Implement workspaces in Cargo.
• Drive trans from the output of the translation item collector.
• std: Stabilize APIs for the 1.11.0 release.
• Update jemalloc to include a fix for startup issues on OSX 10.12.
• Cargo: Add support for RUSTDOCFLAGS.
• Add x86 intrinsics for bit manipulation (BMI 1.0, BMI 2.0, and TBM).
• Added a pretty printer for &mut slices.
• Use lazy iterator in vec/slice gdb pretty printers.
• Introducing TokenStreams and TokenSlices for procedural macros.

New Contributors

• CrLF0710
• Hariharan R
• Ivan Nejgebauer
• Jared Manning
• Kaivo Anastetiks
• Mike Hommey
• Phlogistic Fugu
• Sam Payson
• Ximin Luo

Approved RFCs

Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

• RFC 1327: Dropck Eyepatch. Refine the unguarded-escape-hatch from RFC 1238 (nonparametric dropck).

Final Comment Period

Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are:

• Default and expanded errors for rustc.
• Dedicated strike team to resolve unsafe code guidelines.
• RFC process for formatting style and Rustfmt defaults.
• Introduce more conventions around documenting Rust projects.
• Allow all literals in attributes.
• Add global_asm! for module-level inline assembly.
• Exclude macros from importing with #[macro_use(not(...))].
• Add space-friendly arguments. Add -C link-arg and -C llvm-arg which allow you to pass along argument with spaces.
• Add support for 128-bit integers.
• Add a used attribute to prevent symbols from being discarded.
• Add language support for bitfields.

New RFCs

• Add an unwrap! macro.
• Semantic "private in public" enforcement. Enforce that public APIs do not expose private definitions at the semantic level, while allowing the use of private aliases and blanket implementations for convenience and automation.
• Disjointness based on associated types. During coherence checking, when determining if the receivers of two impls are disjoint, treat bounds with disjoint associated types as mutually exclusive bounds.

Upcoming Events

• 7/13. Rust Community Team Meeting at #rust-community on irc.mozilla.org.
• 7/13. Rust Boulder/Denver - Hello, Rust!.
• 7/14. Rust release triage at #rust-triage on irc.mozilla.org.
• 7/14. Columbus Rust Society: Monthly Meeting.
• 7/18. Rust Paris Meetup #30.
• 7/20. Rust Community Team Meeting at #rust-community on irc.mozilla.org.

If you are running a Rust event please add it to the calendar to get it mentioned here. Email Erick Tryzelaar or Brian Anderson for access.

fn work(on: RustProject) -> Money

• Rust developer at The Blackbird.
• Engineering positions at Zcash mention Rust.

Tweet us at @ThisWeekInRust to get your job offers listed here!

Quote of the Week

No quote was selected for QotW.

Submit your quotes for next week!

This Week in Rust is edited by: nasa42, llogiq, and brson.

https://this-week-in-rust.org/blog/2016/07/12/this-week-in-rust-138/

This piece is about too few names for too many things, as well as a kind of origin story for a web standard. For the past year or so, I’ve been contributing to a Mozilla project broadly named Marionette — a set of tools for automating and testing Gecko-based browsers like Firefox. Marionette is part of a larger browser automation universe that I’ve managed to mostly ignore so far, but the time has finally come to make sense of it.

The main challenge for me has been nailing down imprecise terms that have changed over time. From my perspective, “Marionette” may refer to any combination of two to four things, and it’s related to equally vague names like “Selenium” and “WebDriver”… and then there are things like “FirefoxDriver” and “geckodriver”. Blargh. Untangling needed.

Aside: integrating a new team member (like, say, a volunteer contributor or an intern) is the best! They ask big questions and you get to teach them things, which leads to filling in your own knowledge. Everyone wins.

The W3C WebDriver Specification

Okay, so let’s work our way backwards, starting from the future. (“The future is now.”) We want to remotely control browsers so that we can do things like write automated tests for the content they run or tests for the browser UI itself. It sucks to have to write the same test in a different way for each browser or each platform, so let’s have a common interface for testing all browsers on all platforms. (Yay, open web standards!) To this end, a group of people from several organizations is working on the WebDriver Specification.

The main idea in this specification is the WebDriver Protocol, which provides a platform- and browser- agnostic way to send commands to the browser you want to control, commands like “open a new window” or “execute some JavaScript.” It’s a communication protocol¹ where the payload is some JSON data that is sent over HTTP. For example, to tell the browser to navigate to a url, a client sends a POST request to the endpoint /session/{session id of the browser instance you're talking to}/url with body {"url": "http://example.com/"}.

The server side of the protocol, which might be implemented as a browser add-on or might be built into the browser itself, listens for commands and sends responses. The client side, such as a Python library for automating browsers, send commands and processes the responses.

This broad idea is already implemented and in use: an open source project for browser automation, Selenium WebDriver, became widely adopted and is now the basis for an open web standard. Awesome! (On the other hand, oh no! The overlapping names begin!)

Selenium WebDriver

Where does this WebDriver concept come from? You may have noticed that lots of web apps are tested across different browsers with Selenium — that’s precisely what it was built for back in 2004-2009². One of its components today is Selenium WebDriver.

(Confusingly³, the terms “Selenium Webdriver, “Webdriver”, “Selenium 2” and “Selenium” are often used interchangeably, as a consequence of the project’s history.)

Selenium WebDriver provides APIs so that you can write code in your favourite language to simulate user actions like this:

client.get("https://www.mozilla.org/")
link = client.find_element_by_id("participate")
link.click()

Underneath that API, commands are transmitted via JSON over HTTP, as described in the previous section. A fair name for the protocol currently implemented in Selenium is Selenium JSON Wire Protocol. We’ll come back to this distinction later.

As mentioned before, we need a server side that understands incoming commands and makes the browser do the right thing in response. The Selenium project provides this part too. For example, they wrote FirefoxDriver which is a Firefox add-on that takes care of interpreting WebDriver commands. There’s also InternetExplorerDriver, AndroidDriver and more. I imagine it takes a lot of effort to keep these browser-specific “drivers” up-to-date.

Then something cool happened

A while after Selenium 2 was released, browser vendors started implementing the Selenium JSON Wire Protocol themselves! Yay! This makes a lot of sense: they’re in the best position to maintain the server side and they can build the necessary behaviour directly into the browser.

It started with OperaDriver in 2009-2011, and then others followed such as ChromeDriver and Mozilla’s geckodriver with Marionette.⁴ This is where the motivation for a WebDriver standard comes from.

Let’s Review

Selenium Webdriver (a.k.a. Selenium 2, WebDriver) provides a common API, protocol and browser-specific “drivers” to enable browser automation. Browser vendors started implementing the Selenium JSON Wire Protocol themselves, thus gradually replacing some of Selenium’s browser-specific drivers. Since WebDriver is already being implemented by all major browser vendors to some degree, it’s being turned into a rigorous web standard, and some day all browsers will implement it in a perfectly compatible way and we’ll all live happily ever after.

Is the Selenium JSON Wire Protocol the same as the W3C WebDriver protocol? Technically, no. The W3C spec is describing the future of WebDriver⁵, but it’s based on what Selenium WebDriver and browser vendors are already doing. The goal of the spec is to coordinate the browser automation effort and make sure we’re all implementing the same interface; each command in the protocol should mean the same thing across all browsers.

A Fresh Look at the Marionette Family

Now that I understand the context, my view of Marionette’s components is much clearer.

• Marionette Server together with geckodriver make up Mozilla’s implementation of the W3C WebDriver protocol.
• Marionette Server is built directly into Firefox (into the Gecko rendering engine) and it speaks a slightly different protocol. To make Marionette truly WebDriver-compatible, we need to translate between Marionette’s custom protocol and the WebDriver protocol, which is exactly what geckodriver does. The Selenium client can talk to geckodriver, which in turn talks to Marionette Server.
• As I mentioned earlier, the plan for Selenium 3 is to have geckodriver replace Selenium’s FirefoxDriver. This is an important change: since FirefoxDriver is a Firefox add-on, it has limitations and is going to stop working altogether with future releases.
• Marionette Client is Mozilla’s official Python library for remote control of Gecko, but it’s not covered by the W3C WebDriver spec and it’s not compatible with WebDriver in general. Think of it as an alternative to Selenium’s Python client with Gecko-specific features. Selenium + geckodriver should eventually replace Marionette Client, including the Gecko-specific features.
• The Marionette project also includes tools for integrating with Mozilla’s intricate test infrastructure: Marionette Test Runner, a.k.a. the Marionette test harness. This part of the project has nothing to do with WebDriver, really, except that it knows how to run tests that depend on Marionette Client. The runner collects the tests you ask for, takes care of starting a Marionette session with the right browser instance, runs the tests and reports the results.⁶

As you can see, “Marionette” may refer to many different things. I think this ambiguity will always make me a little nervous… Words are hard, especially as a loose collection of projects evolves and becomes unified. In a few years, the terms will firm up. For now, let’s be extra careful and specify which piece we’re talking about.

Acknowledgements

Thanks to David Burns for patiently answering my half-baked questions last week, and to James Graham and Andreas Tolfsen for providing detailed and delightful feedback on a draft of this article. Bonus high-five to Anjana Vakil for contributions to Marionette Test Runner this year and for inspiring me to write this post in the first place.

http://www.erranderr.com/blog/webdriver-ontology.html

In the lead-up to the London all hands we had a Town Hall where Mark Mayo and Nick Nguyen previewed the three year strategy for Firefox.  That talk mostly covered an emerging area of focus and investment we’re calling the Context Graph.

This last week, Nick posted a vision for the Context Graph over at Medium. If you haven’t, I encourage you to go read it at medium.com/@osunick

So what is the Context Graph. The context graph is an understanding of how pages on the web are connected to each other and to a user’s current context. With Context Graph, we’re going to build a recommendation engine for the Web and features that help people discover relevant content outside of the popular search and social silos.

What does that look like in practice? Well, if you’re learning about how to do something new, like bike repair, our recommender features should help you learn bike repair based on others who have already taken the same journey on the Web. If you’re on YouTube watching a music video, Firefox should help you find the top lyrics or commentary sites that embed or link to that YouTube video. Or, if you’re walking into a WalMart, our mobile apps should automatically show you WalMart’s website or perhaps a WalMart deals and coupons site.

Building a recommendation engine for thew Web is a large project that will take time and effort but we believe the payoff for users and the health of the Open Web is going to be well worth it.

To dig deeper, I highly recommend Nick’s post at medium.com/@osunick and check out the wiki page at wiki.mozilla.org/Context_Graph.

https://asadotzler.com/2016/07/11/context-graph/

The Monday Project Meeting

https://air.mozilla.org/mozilla-weekly-project-meeting-20160711/

Hello mozillians!

Last week on Friday (July 8th), we held another successful event – Firefox 48 beta 6 Testday.

Thank you all for helping us making Mozilla a better place – akash, Karthikeya L K, Iryna Thompson, Moin Shaikh, Ilse Mac'ias, Corey Sheldon, Ciprian Georgiu, Julie Myers (a.k.a. SnoopyRules), Bhuvana Meenakshi.K, Prasanth p, Mano @Manokarr, Nazir Ahmed Sabbir, Hossain Al Ikram, Tanvir Rahman, Azmina Akter Papeya, Khalid Syfullah Zaman, Mohammad Maruf Islam, Md.Majedul islam, Samad Talukdar, Kazi Sakib Ahmad, Zayed News, Maruf Rahman, Md.Tarikul Islam Oashi, Aminul Islam Alvi, Akash, Rakib Rahman, Ria, Rezaul Huque Nayeem, Sayed Ibn Masud and Saddam Hossain.

A big thank you goes out to all our active moderators too!

Results:

• there were 24 verified bugs during testday: Bug 1254311, Bug 1278021, Bug 1242256, Bug 1156450, Bug 1257599, Bug 1261430, Bug  1246606, Bug 1184950, Bug  1228258, Bug 1283072, Bug  1276117, Bug 1272986, Bug 1275915, Bug 1275927, Bug 982121, Bug 1191966, Bug 1273344, Bug 1178462, Bug 1018721, Bug 1018619, Bug 1274017, Bug 1274453, Bug 1251382 and Bug 1090380 .
• 1 new issue: Bug 1285719
• some failures were mentioned for APZ feature in the etherpad ; therefore, please add the requested details in the etherpad or, even better, join us on #qa IRC channel and let’s figure them out

https://quality.mozilla.org/2016/07/firefox-48-beta-6-testday-results/

https://danielpocock.com/lets-encrypt-torpedoes-cost-free-rtc

Summer in its full heat has started in Japan. I'll follow the sun, Beatles.

Webcompat Life

Progress this week:

Today: 2016-07-11T09:55:26.360775
346 open issues
----------------------
needsinfo       5
needsdiagnosis  74
needscontact    33
contactready    50
sitewait        165
----------------------

You are welcome to participate

We had a short team meeting.

Webcompat issues

(a selection of some of the bugs worked on this week).

• offsetWidth creates issue on this site. Hallvord may have found the origin of the issue. It would require a test case to show the differences in between Blink, Edge and Gecko to be extra-sure. The definition of offsetWidth in Gecko: NS_IMETHOD GetOffsetWidth(int32_t *aOffsetWidth) = 0; which leads to OffsetWidth() BUT Daniel found the culprit. This is fixed in Aurora and Nightly so will be soon working on production releases.
• Google Search and Firefox Android (when faking the user agent to be Chrome) is giving an almost working site. There's only one issue when requesting images on the tab. Almost there. Note that this is already working in Firefox Nightly because of the implementation of some WebKit properties.

WebCompat.com dev

• I finally came around fixing a "bug" when rewriting Link headers I had introduced in webcompat.com and that one of our interns discovered when solving another issue.
• Fixed our contributions guidelines to be a bit stricter on the Pull Request review policy. Summary: You should not merge if you are the pull request submitter and the pull request needs an r+ before expecting to move forward.
• Started to work on a logging feature for webcompat.com to detect potential abuse of the service. For now, let's not over-engineer it and make it very simple. It requires the service for log rotation and keep only the last two weeks, and the actual logging in Flask, and also a change of policy.
• Also trying to make a bit more square the repo for issue parsing so that external people can participate. This is in progress.
• When interacting a lot with GitHub, I was thinking it would be nice to have an up-to-date mocking python module of GitHub API. Maybe that could be done by parsing the API documentation and extracting the tables and responses and then creating the mocking service. Just food for thoughts. Even better would be github giving a JSON file describing all routes, HTTP codes, and responses.

Reading List

• Rust and Rest. Replace REST by HTTP in that article and it's a nice read.

Follow Your Nose

• Previous Worklog
• Bugzilla Activity
• Github Activity

TODO

• Document how to write tests on webcompat.com using test fixtures.
• ToWrite: Amazon prefetching resources with for Firefox only.

Otsukare!

http://www.otsukare.info/2016/07/08/worklog-summer

http://tantek.com/2016/190/b1/state-of-indieweb-summit

http://escapewindow.dreamwidth.org/247717.html

http://escapewindow.dreamwidth.org/247489.html

My co-mentor Kate Glazko wrote agreat blogpost the other day about her work mentoringManel RhaiemonProject Haiku.

I am no longer working in Connected Devices, so my experience as a mentor has been a bit different than Kate's. But I will say that we were fortunate to all be able to be together in London at the Mozilla Work Week to sync up and spend some time together.

Since the Work Week, I have tried to be in daily communication with Manel to find out how she is doing on her project. The Outreachy experience is unique in that the intern is remote, so I think communication is critical (just as it is in many Mozilla teams that are geographically distributed). We can talk about her project, but we can also take opportunities to explore professional development and prep her for her eventual entrance into the tech workforce.

The ability to listen is also important - and I am always keen to hear what she thinks about her internship experience, as well as the larger scope of what Mozilla is doing.

So far from my perspective this has been a great experience - I feel the same way I did about the Outreachy mentorship as I did last year when I was a co-mentor for TechWomen. I look forward to working with both Kate and Manel until the internship concludes at the end of August.

http://mozillamarciaknous.wix.com/mozcommunity#!Reflections-from-my-Outreachy-mentorship/c218b/577fce6b0cf2e63d2661334f