The Participation Team was created back in January of this year with an ambitious mandate to simultaneously a) get more impact, for Mozilla’s mission and its volunteers, from core contributor participation methods we’re using today, and b) to find and develop new ways that participation can work at Mozilla.
This mandate stands on the shoulders of people and teams who lead this work around Mozilla in the past, including the Community Building Team. As a contrast with these past approaches, our team concentrates staff from around Mozilla, has a dedicated budget, and has the strong support of leadership, reporting to Mitchell Baker (the Executive Chair) and Mark Surman (CEO of the foundation).
For the first half of the year, our approach was to work with and learn from many different teams throughout Mozilla. From Dhaka to Dakar — and everywhere in between — we supported teams and volunteers around the world to increase their effectiveness. From MarketPulse to the Webmaker App launches we worked with different teams within Mozilla to test new approaches to building participation, including testing out what community education could look like. Over this time we talked with/interviewed over 150 staff around Mozilla, generated 40+ tangible participation ideas we’d want to test, and provided “design for participation” consulting sessions with 20+ teams during the Whistler all-hands.
Toward the end of July, we took stock of where we were. We established a set of themes for the rest of 2015 (and maybe beyond), are focused especially on enabling Mozilla’s Core Contributors, and I put in place a new team structure.Themes:
- Focus – We will partner with a small number of functional teams and work disproportionately with a small number of communities. We will commit to these teams and communities for longer and go deeper.
- Leaders – As a small staff team, we can magnify our impact by identifying and working with volunteer leaders around Mozilla (those Mozillians who engage and influence many more Mozillians). This will start with collecting information about our communities and having 1:1’s with 200+ Mozillians, and proceed to building more formal leadership and learning initiatives.
- Learning – We’re continuing the work of the Participation Lab, having both focused experiments and paying attention to the new approaches to participation being tested by staff and volunteer Mozillians all around the organization. The emphasis will be on synthesizing lessons about high impact participation, and helping those lessons be applied throughout Mozilla.
- Open and Effective – We’re investing in improving how we work as a team and our individual skills. A big part of this is building on the agile “heartbeat” method innovated by the foundation, powered by GitHub. Another part of this is solidifying our participation technology group and starting to play a role of aligning similar participation technologies around Mozilla.
You can see these themes reflected in our Q3 Objectives and Key Results.Team structure:
The Participation Team is focused on activating, growing and increasing the effectiveness of our community of core contributors. Our modified team structure has 5 areas/groups, each with a Lead and a bottom-line accountability. You’ll note that all of these team members are staff — our aim in the coming months is to integrate core contributors into this structure, including existing leadership structures like the ReMo Council.Participation Partners Global-Local Organizing Developing Leaders Participation Technology Performance and Learning Lead:
George Roter (acting)
Lucy HarrisBottom Line:
Catalyze participation with product and functional teams to deliver and sustain impactBottom Line:
Grow the capacity of Mozilla’s communities to engage volunteers and have impact
(includes Reps and Regional Communities)
Grow the capacity of Mozilla’s volunteer leaders and volunteers to have impactBottom Line:
Enable large scale, high impact participation at Mozilla through technologyBottom Line:
Develop a high performing team, and drive learning and synthesize best practice through the Participation Lab
We have also established a Leadership and Strategy group accountable for:
- Making decisions on team objectives, priorities and resourcing
- Nurturing a culture of high performance through standard setting and role modelling
This is made up of Rosana Ardila, Lucy Harris, Brian King, Pierros Papadeas, William Quiviger and myself.
As always, I’m excited to hear your feedback on any of this — it is most certainly a work in progress. We also need your help:
- If you’re a staff/functional team or volunteer team trying something new with participation, please get in touch!
- If you’re a core contributor/volunteer, take a look at these volunteer tasks.
- If you have ideas on what the team’s priorities should be over the coming quarter(s), please send me an email — .
As always, feel free to reach out to any member of the team; find us on IRC at #participation; follow along with what we’re doing on the Blog and by following [@MozParticipate on Twitter](https://twitter.com/mozparticipate); have a conversation on Discourse; or follow/jump into any issues on GitHub.
In the last week, we landed 37 PRs in the Servo repository!
In addition to a rustup by Manish and a lot of great cleanup, we also saw:
- Glennw fixed a bug where animations continued forever at full blast
- Martin Robinson landed the first bits of his massive ongoing stacking context / display list refactoring work
Servo on Windows! Courtesy of Vladimir Vukicevic.
Text shaping improvements in Servo:
At last week’s meeting, we discussed the outcomes from the Paris layout meetup, how to approach submodule updates, and trying to reduce the horrible enlistment experience with downloading Skia.
The Monday Project Meeting
These are the notes of my talk at SmartWebConf in Romania. Part 1 covered how Impostor Syndrome cripples us in using what we hear about at conferences. It also covered how our training and onboarding focuses on coding. And how it lacks in social skills and individuality. This post talks about the current state of affairs. We have a lot of great stuff to play with but instead of using it we always chase the next.
This is part 2 of 3.
- Part 1: never stop learning and do it your way
- Part 2: you got what you asked for, time to use it
- Part 3: give up on the idea of control and become active
When reading about the state of the web there is no lack of doom and gloom posts. Native development is often quoted as “eating our lunch”. Native-only interaction models are sold to us as things “people use these days”. Many of them are dependent on hardware or protected by patents. But they look amazing and in comparison the web seems to fall behind.The web doesn’t need to compete everywhere
This is true, but it also not surprising. Flash showed many things that are possible that HTML/CSS/JS couldn’t do. Most of these were interesting experiments. They looked like a grand idea at the time. And they went away without an outcry of users. What a native environment have and what we do on the web is a comparison the web can’t win. And it shouldn’t try to.
The web per definition is independent of hardware and interaction model. Native environments aren’t – on the contrary. Success on native is about strict control. You control the interaction, the distribution and what the user can and can’t see. You can lock out users and not let them get to the next level. Unless they pay for it or buy the next version of your app or OS. The web is a medium that puts the user in control. Native apps and environments do not. They give users an easy to digest experience. An experience controlled by commercial ideas and company goals. Yes, the experience is beautiful in a lot of cases. But all you get is a perishable good. The maintainer of the app controls what stays in older versions and when you have to pay the next version. The maintainers of the OS dictate what an app can and can not do. Any app can close down and take your data with it. This is much harder on the web as data gets archived and distributed.The web’s not cool anymore – and that’s OK
Evolution happens and we are seeing this right now. Browsers on desktop machines are not the end-all of human-computer interaction. That is one way of consuming and contributing to the web. The web is ubiquitous now. That means it is not as exciting for people as it was for us when we discovered and formed it. It is plumbing. How much do you know about the electricity and water grid that feeds your house? You never cared to learn about this – and this is exactly how people feel about the web now.
This doesn’t mean the web is dead – it just means it is something people use. So our job should be to make that experience as easy as possible. We need to provide a good service people can trust and rely on. Our aim should be reliability, not flights of fancy.
It is interesting to go back to the promises HTML5 gave us. Back when it was the big hype and replacement for Flash/Flex. When you do this, you’ll find a lot of great things that we have now without realising them. We complained when they didn’t work and now that we have them – nobody seems to use them.Re-visiting forms
Take forms for example. You can see the demos I’m about to show here on GitHub.
When it comes down to it, most “apps” in their basic form are just this: forms. You enter data, you get data back. Games are the exception to this, but they are only a small part of what we use the web for.
When I started as a web developer forms meant you entered some data. Then you submitted the form and you got an error message telling you what fields you forgot and what you did wrong.
<form action="/cgi-bin/formmail.pl"> <ul class="error"> <li>There were some errors: <ul> <li><a href="#name">Name is required</a></li> <li><a href="#birthday">Birthday needs to be in the format of DD/MM/YYYY</a></li> <li><a href="#phone">Phone can't have any characters but 0-9</a></li> <li><a href="#age">Age needs to be a number</a></li> </ul> </li> </ul> <p><label for="name">Contact Name *</label> <input type="text" id="name" name="name"></p> <p><label for="bday">Birthday</label> <input type="text" id="bday" name="bday"></p> <p><label for="lcolour">Label Colour</label> <input type="text" id="lcolour" name="lcolour"></p> <p><label for="phone">Phone</label> <input type="text" id="phone" name="phone"></p> <p><label for="age">Age</label> <input type="text" id="age" name="age"></p> <p class="sendoff"> <input type="submit" value="add to contacts"> </p> </form>
This doesn’t look much, but let’s just remember a few things here:
- Using labels we make this form available to all kind of users independent of ability
- You create a larger hit target for mobile users. A radio button with a label next to it means users can tap the word instead of trying to hit the small round interface element.
- As you use IDs to link labels and elements (unless you nest one in the other), you also have a free target to link to in your error links
- With a submit button you enable user to either hit the button or press enter to send the form. If you use your keyboard, that’s a pretty natural way of ending the annoying data entry part.
HTML5 supercharged forms. One amazing thing is the required attribute we can put on any form field to make it mandatory and stop the form from submitting. We can define patterns for validation and we have higher fidelity form types that render as use-case specific widgets. If a browser doesn’t support those, all the end user gets is an input field. No harm done, as they can just type the content.
In addition to this, browsers added conveniences for users. Browsers remember content for aptly named and typed input elements so you don’t have to type in your telephone number repeatedly. This gives us quite an incredible user experience. A feature we fail to value as it appears so obvious.
Take this example.
<form action="/cgi-bin/formmail.pl"> <p><label for="name">Contact Name *</label> <input type="text" required id="name" name="name"></p> <p><label for="bday">Birthday</label> <input type="date" id="bday" name="bday" placeholder="DD/MM/YYYY"></p> <p><label for="lcolour">Label Colour</label> <input type="color" id="lcolour" name="lcolour"></p> <p><label for="phone">Phone</label> <input type="tel" id="phone" name="phone"></p> <p><label for="age">Age</label> <input type="number" id="age" name="age"></p> <p class="sendoff"> <input type="submit" value="add to contacts"> </p> </form>
There’s a lot of cool stuff happening here:
- The birthday date field has a placeholder telling the user what format is expected. You can type a date in or use the arrows up and down to enter it. The form automatically realises that there is no 13th month and that some months have less than 31 days. Other browsers even give you a full calendar popup.
- The colour picker is just that – a visual, high-fidelity colour picker (yes, I keep typing this “wrong”)
- The tel and number types do not only limit the allowed characters to use, but also switch to the appropriate on-screen keyboards on mobile devices.
That’s a lot of great interaction we get for free. What about cutting down on the display of data to make the best of limited space we have?
Originally, this is what we had select boxes for, which render well, but are not fun to use. As someone living in England and having to wonder if it is “England”, “Great Britain” or “United Kingdom” in a massive list of countries, I know exactly how that feels. Especially on small devices on touch/stylus devices they can be very annoying.
<form action="/cgi-bin/formmail.pl"> <p> <label for="lang">Language</label> <select id="lang" name="lang"> <option>arabic</option> <option>bulgarian</option> <option>catalan</option> […] <option>kinyarwanda</option> <option>wolof</option> <option>dari</option> <option>scottish_gaelic</option> </select> </p> <p class="sendoff"> <input type="submit" value="add to contacts"> </p> </form>
However, as someone who uses the keyboard to navigate through forms, I learned early enough that these days select boxes have become more intelligent. Instead of having to scroll through them by clicking the tiny arrows or using the arrow keys you can start typing the first letter of the option you want to choose. That way you can select much faster.
This only works with words beginning with the letter sequence you type. A proper autocomplete should also match character sequences in the middle of an option. For this, HTML5 has a new element called datalist.
<form action="/cgi-bin/formmail.pl"> <p> <label for="lang">Language</label> <input type="text" name="lang" id="lang" list="languages"> <datalist id="languages"> <option>arabic</option> <option>bulgarian</option> <option>catalan</option> […] <option>kinyarwanda</option> <option>wolof</option> <option>dari</option> <option>scottish_gaelic</option> </datalist> </p> <p class="sendoff"> <input type="submit" value="add to contacts"> </p> </form>
This one extends an input element with a list attribute and works like you expect it to:
There is an interesting concept here. Instead of making the select box have the same feature and roll it up into a combo box that exists in other UI libraries, the working group of HTML5 chose to enhance an input element. This is consistent with the other new input types.
However, it feels odd that for browsers that don’t support the datalist element all this content in the page would be useless. Jeremy Keith thought the same and came up with a pattern that allows for a select element in older browsers and a datalist in newer ones:
<form action="/cgi-bin/formmail.pl"> <p> <label for="lang">Language</label> <datalist id="languages"> <select name="lang"> <option>arabic</option> <option>bulgarian</option> <option>catalan</option> […] <option>kinyarwanda</option> <option>wolof</option> <option>dari</option> <option>scottish_gaelic</option> </select> </datalist> <div>or specify: </div> <input type="text" name="lang" id="lang" list="languages"> </p> <p class="sendoff"> <input type="submit" value="add to contacts"> </p> </form>
This works as a datalist in HTML5 compliant browsers.
In older browsers, you get a sensible fallback, re-using all the option elements that are in the document.
This is not witchcraft, but is based on a firm understanding of how HTML and CSS work. Both these are fault tolerant. This means if a mistake happens, it gets skipped and the rest of the document or style sheet keeps getting applied.
In this case, older browsers don’t know what a datalist is. All they see is a select box and an input element as browsers render content of unknown elements. The unknown list attribute on the input element isn’t understood, so the browser skips that, too.
HTML5 browsers see a datalist element. Per standard, all this can include are option elements. That’s why neither the select, nor the input and the text above it get rendered. They are not valid, so the browser removes them. Everybody wins.A craving for control
Browsers and the standards they implement are full of clever and beautiful things like that these days. And we’ve loudly and angrily demanded to have them when they got defined. We tested, we complained, we showed what needed to be done to make the tomorrow work today and then we forgot about it. And we moved on to chase the next innovation.
How come that repeatedly happens? Why don’t we at some point stop and see how much great toys we have to play with? It is pretty simple: control.
But more on that in part 3 of this post.
Hace poco nos preguntaba como cambiar la contraseña maestra y hoy compartimos contigo los pasos para restaurar la contraseña en el navegador y en el cliente de correo. Si no lo sabías, mediante la contraseña maestra, puedes proteger tus nombres de usuario y tus contraseñas almacenadas localmente mediante una contraseña maestra. Si has olvidado tu contraseña maestra, debes restablecerla.
Por seguridad y en aras de evitar el robo de tus datos, al restablecer tu contraseña maestra, borrarás todos las contraseñas y todos los nombres de usuario que tengas almacenados localmente.
Pasos para restablecer la contraseña en Firefox:
- En la barra de direcciones de Firefox, introduce la siguiente dirección :
- Presiona la tecla Intro.
- Aparecerá la página “Restablecer la contraseña maestra”. Haz clic en Restablecer para restablecer tu contraseña maestra.
Pasos para restablecer la contraseña en Thunderbird:
- En el menú , ir hasta Herramientas y escoger Consola de errores.
- En el campo Código escribe openDialog(“chrome://pippki/content/resetpassword.xul”) y da clic en Evaluar. Aparecerá una ventana de confirmación donde podrás restablecer la contraseña maestra.
Por último, si deseas aumentar y fortalecer aún más la seguridad y tu privacidad en Firefox puedes instalar algunos de los complementos publicados en nuestra galería.
The custom made Firefox cufflinks have arrived! I’ll be working out shipping costs, and posting them out this week.
Mozilla klar med ny Firefox-browser - tager livet af 14 år gammel bug
Mozilla klar med ny Firefox-browser - tager livet af 14 år gammel bug. Efter 14 år har Mozilla nu fundet tid til at tage hånd om en bug, der rammer mange brugere af Firefox-browseren. 28. september 2015 kl. 11.03. 1 kommentar. Kim Stensdal ...
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.
- If you use unsafe, you should be using compiletest.
- Running Rust on the Rumprun unikernel.
- Survey of licenses used by Rust projects on crates.io.
- An introduction to timely dataflow, part 3. Learn more about timely dataflow by writing a breadth-first search on random graphs.
- These weeks in Servo 34.
- Get data from a URL in Rust.
- Debuger state machine in Rust.
- rust-todomvc. Implementation of TodoMVC in Rust in the browser.
- zas. A tool to help with local web development, inspired by Pow.
- Serve. Command line utility to serve the files in the current directory.
- Rodio. Rust audio playback library.
- io-providers. Defines "provider" traits and implementations for different types of I/O operations.
- rust-sorty. A Rust lint to help with the sorting of uses, mods & crate declarations.
- walkdir. Rust library for walking directories recursively.
88 pull requests were merged in the last week.Notable changes
- Correctly walk import lists in AST visitors.
- Remove region variable leaks from higher_ranked_sub().
- Always pass /DEBUG flag to MSVC linker.
- Do not drop_in_place elements of Vec<T> if T doesn't need dropping.
- Make function pointers implement traits for up to 12 parameters.
- Use BufWriter in fasta-redux for a nice speedup.
- Upgrade hoedown to 3.0.5.
- Add no_default_libraries target linker option.
- Remove the deprecated box(PLACE) syntax.
- Implement AsMut for Vec.
- Amit Aryeh Levy
- David Elliott
- Reza Akhavan
- Sebastian Wicki
- Xavier Shay
Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:
- Promote the libc crate from the nursery.
- Add an internationalization framework to the Rust compiler.
- Add an alias attribute to #[link] and -l.
- 9/30. RustBerlin Hack and Learn.
- 10/1. Rust Meetup Hamburg: Rusty Project Presentations.
- 10/12. Seattle Rust Meetup.
No jobs listed for this week. Tweet us at @ThisWeekInRust to get your job offers listed here!Crate of the Week
I'd like to add an appeal to all supporters of "repeatable tests". Don't let the worthy goal of repeatability override the worthier goal of actually finding bugs. Your deterministic tests usually cannot even make a dent in the vast space of possible inputs. With a bit of randomness thrown in, you can greatly improve you chances and thus make your tests more valuable. Also with quickcheck, you get to see a minimized input that makes your test fail, which you can then turn into a repeatable test easily.Quote of the Week
If one regards Rust as a critique to C++, it certainly should be seen as a constructive critique. — llogiq on /r/cpp.
Mozilla überarbeitet Online-Code-Editor Thimble
Mozilla hat einen Relaunch seines Online-Code-Editors Thimble vollzogen. Thimble ist als Teil des Mozilla Learning Networks auf HTML-Anfänger fokussiert und erlaubt das einfache Erstellen und Veröffentlichen von Webseiten direkt im Browser. Mozilla ...
Firefox has supported transform-origin on html elements since version 16 (even earlier if you count -moz-transform-origin), but it’s been a bit hit and miss using it on SVG elements.
Percentage units on SVG elements did not work at all, neither did center of course since that’s just an alias for 50%.
Fortunately that’s all about to change. Firefox 41 and 42 have a new pref svg.transform-origin.enabled that you can use to enable transform-origin support for SVG elements. Even better, Firefox 43 will not require a pref at all, it will support transform-origin straight out of the box.
Mozilla Updates Firefox To Include Built-In Messaging Features - Celebrity Cafe - Entertainment News (blog)
Celebrity Cafe - Entertainment News (blog)
Mozilla Updates Firefox To Include Built-In Messaging Features
Celebrity Cafe - Entertainment News (blog)
Mozilla introduced the Windows 10 version in August and the company also came up with a version of Firefox for the iPhone and the iPad to woo the customers. The Android version will also now detect and let you know if you bookmark the same page twice.
Mozilla Adds Instant Messaging to Firefox HelloNewsFactor Network
Firefox 42 Beta Lets You Block Trackers And Know Which Tab Is Playing That ...Tech Times
Firefox 42 beta introduces tracking protection, audio indicators for browser tabsiFreePress.com (blog)
Steelers Lounge (blog)
alle 16 nieuwsartikelen »
Mozilla usunęła w Firefoksie 14-letni błąd
Co ciekawe, w najnowszym lisku Mozilla rozwiązała problem, który był znany od… 14 lat! To nie żart. Chodzi o błąd związany z obsługą pamięci, który dotyczył popularnych rozszerzeń dla przeglądarki, jak Adblock Plus. Rozwiązanie problemu powinno ...
Once upon a time, I had to create 50+ logo options for any given client, simply because the Creative Director demanded it. Few appreciate (or remember) the mental effort and creative time it takes to make just one, polished concept. So producing pages and pages of logo variations required weeks of work… Meaning that nearly all of my billable time was devoted to 49 throw-away-ideas for the sake charging the client 80 hours and maybe winning a trophy. From my perspective, it was traumatic, tedious, and totally unnecessary.
But times have changed, and so has my role.
Today, there’s no fussy CD looming behind my desk dictating changes. Being both the Maker and the Boss, I instead work directly with my clients on the Content Services team, or elsewhere at Mozilla. This affords me the freedom to explore several, distinct ideas, instead of dozens.
So when the team asked me to create a logo for Zenko, I actually looked forward to the assignment.
Zenko is a reporting system used by Content Services at Mozilla for analyzing Directory or Suggested Site campaign data running in Firefox.
Developed by Data Scientist Matthew Ruttley, Zenko reports only aggregate numbers for several key user interactions. This data provides our team the information they need to assess the performance of a campaign, without using personal data. (Because the data is aggregated, it’s therefore anonymous.)
It’s simple. It’s helpful. It’s brilliant.
But how does one communicate any of these salient points through a logo?1.
The name itself provided the inspiration for this first option. According to Matthew, Zenko means “helpful fox” in Japanese (善狐).
Basically, if Firefox was an actual fox, it would fetch only the sticks you really wanted. It would sense your will, sprint into the forest foliage, and then return with perfect specimens. Finally, as an act of loving-devotion, the fox would lay them at your feet in a pretty presentation.
Although cute and clever-but-literal, this version was my least favorite. (But hey, I had to get it out of my system.)2.
Then I explored the notion of a report.
At the end of the day, Content Services uses Zenko to build final reports that are then submitted to a client. “Report” typically implies a text-based document that distills raw data into concrete terms. And whether they’re delivered on-screen or in a binder, we generally think of reports as things that have many, many pages.
Conversely, Zenko only pulls a limited amount of information. There are no tables of user data that reveal shopping trends, browsing history, or net worth. Just things like how many total Firefox users clicked on a particular suggested site in New Tab. Likewise, the reporting itself is limited, lightweight, and crystal clear.
Thus I envisioned a simple document that had been folded into a “Z”. With a point and tail to suggest rapid movement, the logo mark was set off-centered above the name for added interest.
While clear and professional, this option was the most boring of the bunch.3.
Taking a further step back, good reporting helps people solve problems.
In that sense, Zenko helps Content Services find meaningful shapes and patters hidden within basic numbers. The third option illustrates this idea by creating a recognizable, 3-dimensional icon from 2-dimensional objects; implying that Zenko helps you see what is otherwise hidden.
While a strong contender, this logo was missing one crucial element… A personality.4.
To that end, I decided to take another direction entirely. Something new. Something alien, even.
Word-marks can be a strong, identifiable alternative to an icon-first approach (think WIRED or Lyft). Besides, the ones that tend to work often work best with shorter names like Zenko. In this case, my intent was to communicate a particular idea through the letter-forms themselves: This is a product for higher lifeforms.
Because sometimes I do envision Zenko as part of a larger master-plan to invade the Internet Advertising industry and replace bad actors with advertisers that value user consent and control. (Okay, so maybe not an invasion, but hopefully it’s the start of something genuinely positive.)
It doesn’t take a data scientist to understand why this option wasn’t especially well received. Admittedly, my execution was a bit heavy-handed. For example, black and green don’t exactly suggest a happy invasion.5.
Which leads us to the final, and winning, version.
Bringing it all back to basics, I thought once more about the essential purpose of Zenko, which is to measure things. Only the thing being measured is very specific (a campaign in Firefox), and relates only to Firefox users generally. As such, Zenko is a very specific tool – one that was made just for the task at hand.
Starting with the notion of a measuring stick (like the ones I played with in elementary school), the simplest shapes possible were used to construct the letters in “Zenko.” The final result was a logo that could live anywhere, but still have it’s own identity. If somebody has never heard of it, they can at least surmise something about what it does. And if they do use Zenko, the meaning is immediately evident.
Winner, winner, chicken dinner.
Kinderfox: Mozilla gibt Eltern Kontrolle über Firefox für Android
Firefox 42 für Android-Tablets wird mit einer ersten Version von etwas erscheinen, was Mozilla intern Kidfox oder auch Kinderfox nennt. Spezielle Anpassungen und das Deaktivieren von Funktionen sollen den Mozilla-Browser geeigneter für Kinder machen.
Mozilla: Firefox-Beta erweitert privaten Modus um TrackingschutzGolem.de
Firefox 42 Beta verfügbar: Mozilla integriert neuen TrackingschutzWinFuture
Mozilla Firefox 42: erste Beta bietet Tracking-Schutz mit Werbeblocker-Funktionsilicon.de
alle 39 nieuwsartikelen »
Mozilla Adds Instant Messaging to Firefox Hello
Mozilla has given users another reason to consider its Firefox Web browser -- the latest update, announced yesterday, adds instant text messaging capabilities to Firefox Hello, the desktop VoIP client it introduced last fall. In October, Mozilla ...
en meer »
Mozilla details new Firefox Update types it is going to implement
Ghacks Technology News
Firefox updates work like most other software update systems out there currently. The browser communicates with a server to find out if an update is available, and if it is, starts to download and install it based on the user's preferences (some prefer ...
New Fierfox browser includes instant messagingCelebrity Cafe - Entertainment News (blog)
Firefox 41 Released with AdBlock Plus Memory Improvements and MoreHerald Current
alle 5 nieuwsartikelen »
Their patch addresses a problem with cubic congestion control, which is the default algorithm on many Linux distributions. The problem can be roughly summarized as the controller mistakenly characterizing the lack of congestion reports over a quiescent period as positive evidence that the network is not congested and therefore it should send at a faster rate when sending resumes. When put like this, its obvious that an endpoint that is not moving any traffic cannot use the lack of errors as information in its feedback loop.
The end result is that applications that oscillate between transmitting lots of data and then laying quiescent for a bit before returning to high rates of sending will transmit way too fast when returning to the sending state. This consequence of this is self induced packet loss along with retransmissions, wasted bandwidth, out of order packet delivery, and application level stalls.
Unfortunately a number of common web use cases are clear triggers here. Any use of persistent connections, where the burst of web data on two separate pages is interspersed with time for the user to interpret the data is an obvious trigger. A far more dangerous class of triggers is likely to be the various HTTP based adaptive streaming media formats where a series of chunks of media are transferred over time on the same HTTP channel. And of course, Linux is a very popular platform for serving media.
As with many bugs, it all seems so obvious afterwards - but tracking this stuff down is the work of quality non-glamorous engineering. Remember that TCP is robust enough that it seems to work anyhow - even at the cost of reduced network throughput in this case. Kudos to the google team for figuring it out, fixing it up, and especially for open sourcing the result. The whole web, including Firefox users, will benefit.
Usually, pending counts clear overnight as less code is pushed during the night (in North America) which invokes fewer builds and tests. However, as you can see from the graph above, the Windows test pending counts were flat last night. They did not clear up overnight. You will also note that try, which usually comprises 63% of our load, has very highest pending counts compared to other branches. This is because many people land on try before pushing to other branches, and tests aren't coalesced on try.
The work to determine the cause of high pending counts is always an interesting mystery.
- Are end to end times for tests increasing?
- Have more tests been enabled recently?
- Are retries increasing? (Tests the run multiple times because the initial runs fail due to infrastructure issues)
- Are jobs that are coalesced being backfilled and consuming capacity?
- Are tests being chunked into smaller jobs that increase end to end time due to the added start up time?
Joel Maher and I looked at the data for this last week and discovered what we believe to be the source of the problem. We have determined that since the end of August a number of new test jobs were enabled that increased the compute time per push on Windows by 13% or 2.5 hours per push. Most of these new test jobs are for e10s.
Increase in seconds that new jobs added to the total compute time per push. (Some existing jobs also reduced their compute time for a total difference about about 2.5 more hours per push on Windows)The e10s initiative is an important initiative for Mozilla to make Firefox performance and security even better. However, since new e10s and old tests will continue to run in parallel, we need to get creative on how to have acceptable wait times given the limitations of our current Windows tests pools. (All of our Windows test run on bare metal in our datacentre, not on Amazon).
Release engineering is working to reduce this pending counts given our current hardware constraints with the following initiatives:
To reduce Linux pending counts:
- Added 200 new instances to the tst-emulator64 pool (run Android test jobs on Linux emulators) (bug 1204756)
- In process of adding more Linux32 and Linux64 buildbot masters (bug 1205409) which will allow us to expand our capacity more
Ongoing work to reduce the Windows pending counts:
- Disable Linux32 Talos tests and redeploy these machines as Windows test machines (bug 1204920 and bug 1208449)
- Reduce the number of talos jobs by running SETA on talos (bug 1192994)
- Developer productivity team is investigating whether non-operating specific tests that run on multiple windows test platforms can run on fewer platforms.
How can you help?
Please be considerate when invoking try pushes and only select the platforms that you explicitly require to test. Each try push for all platforms and all tests invokes over 800 jobs.
Go Faster is a broad initiative at Mozilla that is focused on shipping things to users much faster than the current 6 week cycle. One important part of this project is having a mechanism to make Firefox aware of updates they need or may want to download. This is nothing entirely new of course - we've been shipping updates to users since Firefox 1.5 - but with Go Faster we will be updating bits and pieces of Firefox at a time rather than always updating the entire install. In this post I'm going to outline these new types of updates that we've identified, and talk about how things will work in the Glorious Future.A Primer on Updates
Firefox updates work on a "pull" system, meaning Firefox regularly queries the update server (Balrog) to ask if there's an update available. For example, my Firefox is currently polling for updates by making a GET request to this URL:https://aus5.mozilla.org/update/3/Firefox/41.0/20150915150946/Linux_x86_64-gcc3/en-GB/beta/default/default/default/update.xml
All of the information in that URL is mapped against a set rules in Balrog, and eventually points to a single release. If that release is newer than the incoming one (based on the incoming version and buildid), Balrog returns the information necessary for the client to update to it:<updates> <update type="minor" displayVersion="41.0" appVersion="41.0" platformVersion="41.0" buildID="20150917150946" detailsURL="https://www.mozilla.org/en-GB/firefox/41.0/releasenotes/"> <patch type="complete" URL="http://download.mozilla.org/?product=firefox-41.0build3-complete&os=linux64&lang=en-GB" hashFunction="sha512" hashValue="ea0757069363287f67659d8b7d42e0ac6c74a12ce8bd3c7d3e9ad018d03cd6f4640529c270ed2b3f3e75b11320e3a282ad9476bd93b0f501a22d1d9cb8884961" size="48982398"/> </update> </updates>
It's important to note that Balrog only contains metadata about the update. The actual payloads of the updates are hosted on CDN networks.New Types of Updates
We've identified three different new types of updates that we'll be implementing as part of Go Faster. They are:
- System Addons: These are core (aka required) parts of Firefox that happen to be implemented as Addons.
- Security Policy: This is a medium sized piece of JSON that instructs NSS about special security policies to enforce for various websites.
- Optional Features: These are optional parts of Firefox that may be implemented as Addons or other means.
Each one of these will be implemented as an additional update request to Balrog (we may collapse these into a single request later). Eg, Firefox will look for new System Addons by making a GET request to an URL such as:https://aus5.mozilla.org/update/3/SystemAddons/41.0/20150915150946/Linux_x86_64-gcc3/en-GB/beta/default/default/default/update.xml
The responses will vary a bit depending on the type of update. More on that below.System Addons
Seeing as Firefox can't function without them, System Addons may seem like a contradiction at first. The advantages are quite clear though: with them, we can ship updates to self contained pieces of Firefox at a substantionally faster rate. Shipping an update to all of Firefox takes nearly 24 hours (when we're moving as fast as we can); shipping an update to a System Addon could take as little as minutes.
Although they are implemented as Addons, we can't simply ship them through the AMO. Because Firefox cannot function without them we must ship them in the installers and full updates that happen every 6 weeks. This has the nice side effect of minimizing dependency problems -- we won't run into a case where Firefox updates but System Addons don't, which could cause incompatibilities. In between the 6 week cycles Firefox will poll Balrog for updates to System Addons and apply them as they become available. This graph may show this more clearly:
As you can see, Firefox 50.0 can be assumed to have any of Fizz 1.0, 1.1, 1.2, 1.3, or 2.0, while Firefox 51.0 is known to only have Fizz 2.0 (but may receive newer versions later).
When Firefox pings Balrog for System Addon updates, the response will look something like this:<updates> <addons> <addon id="email@example.com" URL="http://download.cdn.mozilla.net/fizz-1.1.xpi" hashFunction="sha512" hashValue="abcdef123456" version="1.1"/> <addon id="firstname.lastname@example.org" URL="http://download.cdn.mozilla.net/pop-2.5.xpi" hashFunction="sha512" hashValue="abcdef123456" version="2.5"/> <addon id="email@example.com" URL="http://download.cdn.mozilla.net/bam-3.4.xpi" hashFunction="sha512" hashValue="abcdef123456" version="3.4"/> </addons> </updates>
Firefox will compare the list against its currently installed versions and update anything that's out of date. The exact details on where System Addons will live on disk are still being ironed out.Security Policy
Every version of Firefox ships with the most up-to-date set of security policies that were available when it was built. However, these policies are updated more frequently than we ship, and it's crucial that we keep them up to date to keep our users safe. As with System Addons, Firefox will regularly ping Balrog to check for updated security policies. When one is found, Firefox downloads it from Kinto, which will serve it an incremental update to its security policies. The details of this process have been outlined in much more detail by the Cloud Services team.
The Balrog response for these updates is extremely simple, and simply contains a version that Firefox passes along to Kinto:<updates> <settings> <setting id="security" lastModified="129386427328"/> </settings> </updates> Optional Features
These are parts of Firefox that are not core to the browser, but may be useful to subsets of users. For example: We currently ship a ton of hyphenation dictionaries as part of Firefox for Android. These are locale-specific, so only one ever gets used for each user. We can also distribute opt-in features that not everyone wants or needs, eg: Developer Tools may be a good candidate (there are no plans to do so at this time though).
Optional features may also be implemented in various ways. Hyphenation dictionaries are simple zip files, while something like Developer Tools would likely be an Addon. They will not be included in Firefox installers or update packages. Instead Firefox will regularly query Balrog to see what packages may be available to it. Some things may automatically install based on the user's environment (eg: hyphentation dictionaries for your locale), while other things may require opt-in (eg: optional features).
Balrog responses are not yet set in stone for these, but Kinto is likely to be involved, so the response may end up being similar to the one above for Security Policy updates.Summary While System Addons, Security Policy, and Optional Features overlap in some areas, each has its own unique combination of requirements. The chart below summarizes these: Required? Shipped in Installer? Payload Type Payload Location System Addons Yes Yes Addons CDN Security Policy Yes Yes JSON Kinto Optional Features No No Anything Kinto
Mozilla Fixes 14-Year-Old Bug in Firefox 41
Developers at Mozilla pushed out Firefox 41 this week and brought some much needed relief to Adblock Plus users by finally fixing a 14-year old bug in the browser. The update addresses a longstanding issue with how the browser handles memory usage by ...
Mozilla takes on the problems with web content blockingBetaNews
Mozilla Brings Instant Messaging to Firefox 41, Tracking Protection to Firefox 42Datamation
Mozilla fixes 14-year old Firefox bug, turbocharges Adblock PlusExtremeTech
VentureBeat -Tech Times -Maximum PC
alle 121 nieuwsartikelen »