Mozilla vai bloquear "conteúdo não essencial" em Flash no Firefox
A Mozilla anunciou nesta quarta-feira, 20, que o Firefox vai passar a bloquear conteúdos Flash que "não sejam essenciais para a experiência do usuário". A mudança, que começa a funcionar no mês que vem, é semelhante ao que tem acontecido com os ...
Mozilla vai restringir ainda mais o Flash no FirefoxTecnoblog (blog)
Mozilla anuncia o fim do suporte ao Flash no Firefoxcanaltech (Blogue)
Firefox dá mais uma 'machadada' no FlashNotícias ao Minuto (liberação de imprensa)
alle 5 nieuwsartikelen »Google Nieuws
This is the sumo weekly call
The interesting Google transfer protocol that is known as QUIC is being passed through the IETF grinding machines to hopefully end up with a proper “spec” that has been reviewed and agreed to by many peers and that will end up being a protocol that is thoroughly documented with a lot of protocol people’s consensus. Follow the IETF QUIC mailing list for all the action.I’d like us to join the fun
Similarly to how we implemented HTTP/2 support early on for curl, I would like us to get “on the bandwagon” early for QUIC to be able to both aid the protocol development and serve as a testing tool for both the protocol and the server implementations but then also of course to get us a solid implementation for users who’d like a proper QUIC capable client for data transfers.implementations
The current version (made entirely by Google and not the output of the work they’re now doing on it within the IETF) of the QUIC protocol is already being widely used as Chrome speaks it with Google’s services in preference to HTTP/2 and other protocol options. There exist only a few other implementations of QUIC outside of the official ones Google offers as open source. Caddy offers a separate server implementation for example.the Google code base
For curl’s sake, it can’t use the Google code as a basis for a QUIC implementation since it is C++ and code used within the Chrome browser is really too entangled with the browser and its particular environment to become very good when converted into a library. There’s a libquic project doing exactly this.for curl and others
The ideal way to implement QUIC for curl would be to create “nghttp2” alternative that does QUIC. An ngquic if you will! A library that handles the low level protocol fiddling, the binary framing etc. Done that way, a QUIC library could be used by more projects who’d like QUIC support and all people who’d like to see this protocol supported in those tools and libraries could join in and make it happen. Such a library would need to be written in plain C and be suitably licensed for it to be really interesting for curl use.a needed QUIC library
I’m hoping my post here will inspire someone to get such a project going. I will not hesitate to join in and help it get somewhere! I haven’t started such a project myself because I think I already have enough projects on my plate so I fear I wouldn’t be a good leader or maintainer of a project like this. But of course, if nobody else will do it I will do it myself eventually. If I can think of a good name for it.some wishes for such a library
- Written in C, to offer the same level of portability as curl itself and to allow it to get used as extensions by other languages etc
- FOSS-licensed suitably
- It should preferably not “own” the socket but also work in-memory and to allow applications to do many parallel connections etc.
- Non-blocking. It shouldn’t wait for things on its own but let the application do that.
- Should probably offer both client and server functionality for maximum use.
- What else?
Deep in IT
Mozilla aktualizovala plán vývoje Firefoxu
Deep in IT
Firefox pomalu blíží k vícevláknovému běhu a konci klasických pluginů. Oba procesy už řadu měsíců běží a řadu měsíců ještě potrvá, než běžný uživatel pocítí kompletní důsledky a zlepšení. Firefox logo 2012. Aktualizovaná roadmapa některé věci mění.
Mozilla n'impose plus de compte Firefox pour son Test Pilot
Mozilla a modifié son programme Test Pilot pour séparer la connexion à un compte Firefox, et les données qui peuvent être collectées auprès des testeurs. Un choix dû certainement au test du Context Graph, qui oblige Mozilla à marcher sur une ligne ...
Browser plugins, especially Flash, have enabled some of our favorite experiences on the Web, including videos and interactive content. But plugins often introduce stability, performance, and security issues for browsers. This is not a trade-off users should have to accept.
Mozilla and the Web as a whole have been taking steps to reduce the need for Flash content in everyday browsing. Starting in August, Firefox will block certain Flash content that is not essential to the user experience, while continuing to support legacy Flash content. These and future changes will bring Firefox users enhanced security, improved battery life, faster page load, and better browser responsiveness.
Over the past few years, Firefox has implemented Web APIs to replace functionality that was formerly provided only by plugins. This includes audio/video playback and streaming capabilities, clipboard integration, fast 2D and 3D graphics, WebSocket networking, and microphone/camera access. As websites have switched from Flash to other web technologies, the plugin crash rate in Firefox has dropped significantly:
Firefox will continue this trend by blocking specific Flash content invisible to users. This is expected to reduce Flash crashes and hangs by up to 10%. To minimize website compatibility problems, the changes are initially limited to a short, curated list of Flash content that can be replaced with HTML. We intend to add to this list over time.
Later this year, we plan to expand this list to include the use of Flash to check content viewability, a common practice to measure advertising. This will improve Firefox performance and device battery life. We will make this change at the same time Firefox implements the equivalent HTML Intersection Observer API (Firefox bug 1243846) and recommend that content producers currently using Flash to measure viewability adopt this new API as soon as it is available.
In 2017, Firefox will require click-to-activate approval from users before a website activates the Flash plugin for any content. Websites that currently use Flash or Silverlight for video or games should plan on adopting HTML technologies as soon as possible. Firefox currently supports encrypted video playback using Adobe Primetime and Google Widevine as alternatives to plugin video.
We continue to work closely with Adobe to deliver the best possible Flash experience for our users. Our engineering partnership has led to improvements in high-DPI support on Windows, enhanced sandboxing, and an accelerated Flash rendering pipeline that improves performance and stability.
These changes are part of our ongoing efforts to make browsing safer and faster without sacrificing the Web experiences our users love. As we announced last year, Firefox plans to drop support for all NPAPI plugins, except Flash, in March 2017. The next major Firefox ESR (Extended Support Release) release, also scheduled for March, will continue to support plugins such as Silverlight and Java until early 2018, for those users who need more time for their transition.
We are experimenting with many other features and improvements that will make Firefox an even more awesome platform for discovery and collaboration. We welcome your feedback and feature requests.
Mozilla má plán: V příštích šesti měsících čekejte zcela předělaný Firefox
Firefox a jeho mateřská Mozilla se na ně připravují už roky. Mozilla se chce stát opět technologickým lídrem, což v praxi znamená, že se musí nejprve srovnat s konkurencí v tom, jak funguje jádro Firefoxu. Programátoři tedy připravují jeho nový motor s ...
en meer »
Weekly project updates from the Mozilla Connected Devices team.
After much delays, collectively we picked a balmy first weekend of June and Berlin as our host city for a localization hackathon. We had four representing each of Dutch/Frisian and Ukrainian communities, three of German, one of South African English. Most of them had not been to an l10n hackathon, many have never not met in person within the community even though they had been collaborating for years.
As with the other hackathons this year we allowed each team to plan how they spent their time together, and set team goals on what they wanted to accomplish over the weekend. The localization drivers would lead some group discussions. As a group, we split the weekend covering the following topics:
A series of spectrograms where attendees answer yes/no, agree/disagree questions by physically standing on a straight line from one side of the room to the other. We learned a lot about our group on recognition, about the web in their language, and about participation patterns. As we’re thinking about how to improve localization of Firefox, gaining insights into localizers hearts and life is always helpful.
Axel shared some organizational updates from the Orlando All-Hands: we recaped the status of Firefox OS and the new focus on Connected Devices. We also covered the release schedule of Firefox for iOS and Android.
We spent a bit more time talking about the upcoming changes to localization of Firefox, with L20n and repository changes coming up. In the meantime, we have a dedicated blog post on l20n for localizers, so read up on l20n there. Alongside, we’ll stop using individual repositories and workflows for localizing Firefox Nightly, Developer Edition, Beta, and release. Instead the strings needed for all of them will be in a single place. That’s obviously quite a few changes coming up, and we got quite a few questions in the conversations. At least Axel enjoys answering them.
Our renewed focus on translation quality that resulted in development of the style guide template as a guideline for localization communities to emulate. We went through all the categories and sub-categories and explained what was expected of them to elaborate and provide locale specific examples. We stressed the importance of having one as it would help with consistency between multiple contributors to a single product or all products and projects across the board. This exercise encouraged some of the communities who thought they had a guide to review and update, and those who didn’t have one to create one. The Ukrainian community created a draft version soon after they returned home. Having an established style guide would help with training and on boarding new contributors.
We also went over the categories and definitions specified in MQM. We immediately used that knowledge to review through live demo in Pontoon-like tool some inconsistencies in the strings extracted from projects in Ukrainian. To me, that was one of the highlights of the weekend: 1) how to give constructive feedback using one of the defined categories; 2) Reoccurring type of mistakes either by a particular contributor or locale; 3). Terminology consistency within a project, product or a group of products, especially with multiple contributors; 4) Importance of peer review
For the rest of the weekend, each of the community had their own breakout sessions, reviewed their own to-do list, fixed bugs, completed some projects, and spent one on one time with the l10n drivers.
We were incredibly blessed with great weather. The unusually heavy rain that flooded many parts of Germany stopped during our visit. A meetup like this would not be complete without experiencing some local cultures. Axel, a Berlin native was tasked to show us around. We walked, walked and walked and with occasionally public transportation in between. We covered several landmarks such as the Berlin Wall, the Brandenburg Gate, several memorials, the landmark Gedächtniskirche as well as parks and streets crowded with the locals. Of course we sampled cuisines that reflected the diverse culture that Berlin had been: we had great kebabs and the best kebabs, Chinese fusion, the seasonal asparagus and of course the German beer. For some of us, this was not the first Berlin visit. But a group activity together, with Axel as our guide, the visit was so much memorable. Before we said goodbye, the thought of next year’s hackathon came to mind. Our Ukraine community had volunteered to host it in Lviv, a beautiful city in the western part of the country. We shall see.
Reunión bi-semanal para hablar sobre el estado de Mozilla, la comunidad y sus proyectos. Bi-weekly meeting to talk (in Spanish) about Mozilla status, community and...
the following changes have been pushed to bugzilla.mozilla.org:
-  Rename “Triage Report” link on Reports page.
-  Allow explicit specification of an API key in scripts/issue-api-key.pl
-  Please add Katharina Borchert and CIO to recruiting lists
-  certain github commit messages are not being auto-linkified properly
-  develop a nightly script to revoke access to legal bugs from ex-employees
discuss these changes on mozilla.tools.bmo.
This quarter’s main focus is on:
- Debugging tests on interactive workers (only Linux on TaskCluster)
- Improve end to end times on Try (Thunder Try project)
For all bugs and priorities you can check out the project management page for it:https://wiki.mozilla.org/EngineeringProductivity/Projects/Debugging_UX_improvements
In this email you will find the progress we’ve made recently. In future updates you will see a delta from this email.
PS = These status updates will be fortnightly
Debugging tests on interactive workersAccomplished recently:
- Landed support for running reftest and xpcshell via tests.zip
- Many UX improvements to the interactive loaner workflow
- Make sure Xvfb is running so you can actually run the tests!
- Mochitest support + all other harnesses
Thunder Try - Improve end to end times on try
Project #1 - Artifact builds on automationTracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1284882
- Landed prerequisites for Windows and OS X artifact builds on try.
- Identified which tests should be skipped with artifact builds
- Provide a try syntax flag to trigger only artifact builds instead of full builds; starting with opt Linux 64.
Project #2 - S3 Cloud Compiler CacheTracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1280641
- Sccache’s Rust re-write has reached feature parity with Python’s sccache
- Now testing sccache2 on Try
- We want to roll out a two-tier sccache for Try, which will enable it to benefit from cache objects from integration branches
Project #3 - MetricsTracking bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1286856
- Preliminary analytics / research based on job data from Treeherder found at: http://nbviewer.jupyter.org/url/people.mozilla.org/%7Ewlachance/try%20analysis.ipynb
- Which jobs finish last?
- Which jobs have the highest wait times?
- Which jobs have the longest total wall clock time (i.e. are the largest consumers of resources)
- Putting Mozharness steps’ data inside Treeherder’s database for aggregate analysis
- TaskCluster Linux builds are currently built using a mix of m3/r3/c3 2xlarge AWS instances, depending on pricing and availability. We’re going to be looking to assess the effects on build speeds of using more powerful AWS instances types, as one potential way of reducing e2e Try times.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
Tabs vs Spaces: How They Write Java in Google, Twitter, Mozilla, and Pied Piper
In this post, we will highlight formatting guidelines and different Java coding styles in companies like Google, Twitter, Mozilla, the Java standard, and our own teams at Takipi. New Post: Tabs vs Spaces: How They Write Java in Google, Twitter and Pied ...
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.
- Mozilla is shipping its first production Rust code in Firefox 48.
- Linux perf gets Rust symbol demangling support.
- Testing strategies for Corrode. Corrode is a C to Rust translator.
- Rust for Node.js developers - Part 3. Crates, Modules and the web.
- How to package Rust applications to RPM using vendoring.
- A Rust-powered public web page in 5 minutes.
- Rust Project changelog for 2016-07-15. Updates to rustup, libc, net2, regex, websites.
- rustup 0.3 released. Includes fixes for downloading old releases, various cleanups, and preliminary (non-functional) rustls support.
- Lyon. GPU-based 2D graphics rendering experiments in Rust.
- Gluon. A static, type inferred and embeddable language written in Rust.
- Tango. Markdown-based Literate programming in Rust, integrated with Cargo.
- ScreenRuster. X11 screen saver and locker.
- These weeks in Servo 71.
- This week in Rust docs 13.
- This week in Ruma - July 17, 2016.
- What's coming up in imag 11.
This week has a belated Crate of the Week with Vincent Esche's self-submitted cargo-modules, which gives us the cargo modules subcommand that shows the module structure of our crates in a tree view, optionally warning of orphans. Thanks, Vincent!
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] imag: Make imag forward --debug and --verbose to subcommands.
- [moderate] rust: Very confusing error on attempt to pass path::Path by value. This is bad error message that is hit often. Good bug to get familiar with the compiler.
- [easy] rust: move coerce_match, coerce_calls and related tests into run-pass-valgrind. Just moving tests around. Easy introduction to the build system.
- [easy] rustbyexample.com is in need of maintainers. Good first tasks are writing Mutex examples and Arc examples.
- [hard] rustup: Write a GUI installer for rustup on Windows. This is involved but should be fun. It's an integration problem, writing a Windows GUI that hooks into the MSI installation system and calls into the rustup libraries. Required for rustup 1.0.
- [easy] cargo: Warn on the duplicate entry points for lib and bin.
- [easy] cargo: Can't specify precise crate version if there are multiple versions.
- [easy] error-chain: Display implementation should show the error's Display, not just the description. Looks like a simple fix.
- [easy] rust: Parsing inconsistencies (lambda, proc, return). This bug identifies some bugs where the rustc parser disagrees with the reference parser. Good first bug for someone interested in parsers.
- [easy] imag: --version and --versions yield helptext instead of version(s).
If you are a Rust project owner and are looking for contributors, please submit tasks here.Updates from Rust Core
105 pull requests were merged in the last two weeks.
- Match whole statements in macros
- Harder floats on MIPS
- New method new_parser_from_ts
- Non-Squiggly-braced Macros now need Semicolon
- Simplify Macro Hygiene
- Stable order for handling type projection bounds
- calling directly imported trait methods no longer crashes rustc
- Unicode 9.0 update
- Simplify error reporting (potentially plugin-breaking)
- readdir now also works on Solaris
- String interner cleanup
- &Mutex is now RefUnwindSafe
- Simplify LinkedList with Shared instead of Box
- Deprecated API spring clean
- Cargo can now enable dependencies' features
- cargo publish --dry-run
- Aravind Gollakota
- Ben Boeckel
- Ben Stern
- Dridi Boukelmoune
- Isaac Andrade
- Zhen Zhang
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
- RFC 1574: Introduce more conventions around documenting Rust projects.
- RFC 1644: Default and expanded errors for rustc.
- Promote ! to a type
- Add language support for bitfields.
- Add support for 128-bit integers.
- Add space-friendly arguments. Add -C link-arg and -C llvm-arg which allow you to pass along argument with spaces.
- Exclude macros from importing with #[macro_use(not(...))].
- Add global_asm! for module-level inline assembly.
- Allow all literals in attributes.
- RFC process for formatting style and Rustfmt defaults.
- Replace synchronization primitives with those from parking_lot.
- Dedicated strike team to resolve unsafe code guidelines.
- Add assert_ne to compliment assert_eq.
- Introduce non-panicking borrow methods on RefCell<T>.
- Propose asserts. This rfc proposes that the following macros be added: assert_gt, assert_lt, assert_ge, and assert_le.
- Procedural macros 1.1.
- Startup initialized statics. Introduce the ability to initialize (i.e., mutate) static items (even non-mut ones) at the beginning of main in a compiler-guaranteed safe manner.
- Unified machine word trait. Unify functionality peculiar to i8…i64 and u8…u64 in a trait containing the family of overflowing/checked/wrapping/saturating variants of arithmetic operations, as well as a few new ones.
- Add non-panicking abs() functions to all signed integer types.
- Add "panic-safe" or "total" alternatives to the existing panicking indexing syntax.
- 7/20. Rust Community Team Meeting at #rust-community on irc.mozilla.org.
- 7/21. Rust Hack & Learn Karlsruhe.
- 7/27. Rust Community Team Meeting at #rust-community on irc.mozilla.org.
Tweet us at @ThisWeekInRust to get your job offers listed here!Quote of the Week
fzammetti: Am I the only one that finds highly ironic the naming of something that's supposed to be new and cutting-edge after a substance universally synonymous with old, dilapidated and broken down?
paperelectron: Rust is as close to the bare metal as you can get.
Tracking protection is an interesting beast. A feature to help users but users think the site is broken. I guess it's something similar to habits. If you put a mask on your face and you have forgotten about it, you may be surprised that people do not want to talk to you.Webcompat Life
Progress this week:Today: 2016-07-19T11:32:54.030052 316 open issues ---------------------- needsinfo 5 needsdiagnosis 76 needscontact 20 contactready 41 sitewait 168 ----------------------
You are welcome to participateWebcompat issues
(a selection of some of the bugs worked on this week).
- issue with MLB site displaying the plays.
- Interesting CSS issue about display:table and max-height having a different behavior in Chrome and Firefox, maybe something related to a known issue. To be confirmed.
- Started to look at issue 722
the contain property, which indicates that the element’s subtree is independent of the rest of the page.
If I understand, this seems like something which would answer many of the complaints we hear from Web developers about CSS isolation. Specifically the layout term: contain: layout.
This value turns on layout containment for the element. This ensures that the containing element is totally opaque for layout purposes; nothing outside can affect its internal layout, and vice versa.
- Document how to write tests on webcompat.com using test fixtures.
- ToWrite: Amazon prefetching resources with <object> for Firefox only.
Writing good code is hard, writing a good analysis is harder. Peer-review is an essential tool to fight repetitive errors, omissions and more generally divulge knowledge. I found the use of a checklist to be invaluable to help me remember the most important things I should watch out for during a review. It’s far too easy to focus on few details and ignore others which might be catched (or not) in a successive round.
I don’t religiously apply every bullet point of the following checklist to every analysis, nor is this list complete; more items would have to be added depending on the language, framework, libraries, models, etc. used.
- Is the question the analysis should answer clearly stated?
- Is the best/fastest dataset that can answer the question being used?
- Do the variables used measure the right thing (e.g. submission date vs activity date)?
- Is a representative sample being used?
- Are all data inputs checked (for the correct type, length, format, and range) and encoded?
- Do outliers need to be filtered or treated differently?
- Is seasonality being accounted for?
- Is sufficient data being used to answer the question?
- Are comparisons performed with hypotheses tests?
- Are estimates bounded with confidence intervals?
- Should the results be normalized?
- If any statistical method is being used, are the assumptions of the model met?
- Is correlation confused with causation?
- Does each plot communicate an important piece of information or address a question of interest?
- Are legends and axes labelled and do the they start from 0?
- Is the analysis easily reproducible?
- Does the code work, i.e. does it perform its intended function?
- Is there a more efficient way to solve the problem, assuming performance matters?
- Does the code read like prose?
- Does the code conform to the agreed coding conventions?
- Is there any redundant or duplicate code?
- Is the code as modular as possible?
- Can any global variables be replaced?
- Is there any commented out code and can it be removed?
- Is logging missing?
- Can any of the code be replaced with library functions?
- Can any debugging code be removed?
- Where third-party utilities are used, are returning errors being caught?
- Is any public API commented?
- Is any unusual behavior or edge-case handling described?
- Is there any incomplete code? If so, should it be removed or flagged with a suitable marker like ‘TODO’?
- Is the code easily testable?
- Do tests exist and do they actually test that the code is performing the intended functionality?
There isn’t a single day going by right now where you can’t read a post or see a talk about diversity and inclusiveness in our market. And that’s a great thing. Most complain about the lack of them. And that’s a very bad thing.
It has been proven over and over that diverse teams create better products. Our users are all different and have different needs. If your product team structure reflects that you’re already one up against the competition. You’re also much less likely to build a product for yourself – and we are not our end users.
Let’s assume we are pro-diversity and pro-inclusiveness. And it should be simple for us – we come from a position of strength:
- We’re expert workers and we get paid well.
- We are educated and we have companies courting us and looking after our needs once we have been hired.
- We’re not worried about being able to pay our bills or random people taking our jobs away.
I should say yet, because automation is on the rise and even our jobs can be optimised away sooner or later. Some of us are even working on that.
For now, though, we are in a very unique position of power. There are not enough expert workers to fill the jobs. We have job offers thrown at us and our hiring bonuses, perks and extra offers are reaching ridiculous levels. When you tell someone outside our world about them, you get shocked looks. We’re like the investment bankers and traders of the eighties and we should help to ensure that our image won’t turn into the same they have now.
If we really want to change our little world and become a shining beacon of inclusion, we need not to only talk about it – we should demand it. A large part of the lack of diversity in our market is that it is not part of our hiring practices. The demands to our new hires make it very hard for someone not from a privileged background or with a degree from a university of standing to get into our market. And that makes no sense. The people who can change that is us – the people in the market who tick all the marks.
To help the cause and make the things we demand in blog posts and keynotes happen, we should bring our demands to the table when and where they matter: in job interviews and application processes.
Instead of asking for our hardware, share options and perks like free food and dry cleaning we should ask for the things that really matter:
- What is the maternity leave process in the company? Can paternity leave be matched? We need to make it impossible for an employer to pick a man over a woman because of this biological reason.
- Why is a degree part of the job? I have none and had lots of jobs that required one. This seems like an old requirement that just got copied and pasted because of outdated reasons.
- What is the long term plan the company has for me? We kept getting asked where we see ourselves in five years. This question has become cliché by now. Showing that the company knows what to do with you in the long term shows commitment, and it means you are not a young and gifted person to be burned out and expected to leave in a year.
- Is there a chance for a 4 day week or flexible work hours? For a young person it is no problem doing an 18 hours shift in an office where all is provided for you. As soon as you have children all kind of other things add to your calendar that can’t me moved.
- What does this company do to ensure diversity? This might be a bit direct, but it is easy to weed out those that pay lip service.
- What is the process to move in between departments in this company? As you get older and you stay around for longer, you might want to change career. A change in your life might make that necessary. Is the company supporting this?
- Is there a way to contribute to hiring and resourcing even when you are not in HR? This could give you the chance to ask the right questions to weed out applicants that are technically impressive but immature or terrible human beings.
- What is done about accessibility in the internal company systems? I worked for a few companies where internal systems were inaccessible to visually impaired people. Instead of giving them extra materials we should strive for making internal systems available out-of-the-box.
- What is the policy on moving to other countries or working remotely? Many talented people can not move or don’t want to start a new life somewhere else. And they shouldn’t have to. This is the internet we work on.
- What do you do to prevent ageism in the company? A lot of companies have an environment that is catering to young developers. Is the beer-pong table really a good message to give?
I’ve added these questions to a repo on GitHub, please feel free to add more questions if you find them.
FWIW, I started where I am working right now because I got good answers to questions like these. My interviews were talking to mixed groups of people telling me their findings as teams and not one very aggressive person asking me to out-code them. It was such a great experience that I started here, and it wasn’t a simple impression. The year I’ve worked here now proved that even in interviewing, diversity very much matters.
Photo Credit: shawncplus
The Monday Project Meeting
Once a month, web developers from across Mozilla get together to talk about the work that we’ve shipped, share the libraries we’re working on, meet new folks, and talk about whatever else is on our minds. It’s the Webdev Extravaganza! The meeting is open to the public; you should stop by!
The shipping celebration is for anything we finished and deployed in the past month, whether it be a brand new site, an upgrade to an existing one, or even a release of a library.Basket switch to Salesforce
First up was pmac, who shared the news that Basket, email newsletter subscription service, has switched to using Salesforce as the backend for storing newsletter subscriptions. In addition, the service now has a nifty public DataDog metrics dashboard showing off statistics about how the service is performing.Engagement Engineering Status Board
- Indexing 32+ new projects
- Added a 3rd build server
- Several performance optimizations that cut down build times by roughly 25%.
- C++ macro definitions, method overrides, pure virtuals, substructs, and more are all now indexed. In addition, you can now easily jump between header files and their implementations.
- UI improvements, including contrast improvements, a new filename filter, and jumping directly to files that are the only result of a query.
Erik also brought up Fathom, an experimental framework for extracting meaning from webpages. Fathom allows you to write declarative rules that score and classify DOM nodes, and then extract those nodes from a DOM that it analyzes.
This month we shipped the 1.0 version of Fathom, as well as a 1.1 release with a bug fix for Firefox support as well as an optimization fix. It’s available as an NPM module for use as a library.Roundtable
The Roundtable is the home for discussions that don’t fit anywhere else.Engagement Engineering Hiring – Senior Webdev and Site Reliability Engineer
Last up was pmac again, who wanted to mention that the Mozilla Engagement Engineering team is hiring a Senior Web Developer and a Site Reliability Engineer. If you’re interested in working at Mozilla, click those links to apply on our careers site!
If you’re interested in web development at Mozilla, or want to attend next month’s Extravaganza, subscribe to the email@example.com mailing list to be notified of the next meeting, and maybe send a message introducing yourself. We’d love to meet you!
See you next month!
Hit augmented-reality mobile gaming sensation Pokémon GO is now available in the UK, so it’s time to test my hypothesis about searches for 5km converted to miles in that second bastion of “Let’s use miles as distance units in defiance of basically every other country”:
Results are consistent with hypothesis.
(( Now if only I could get around how the Google Play Store is identifying my Z10 as incompatible with the game… ))