http://bluesock.org/~willkg/blog/mozilla/input_status_20150619

As of kernel 4.0.4 (and probably earlier), writing to /proc/.../mem at a page which is mapped PROT_NONE causes a kernel BUG at mm/memory.c, which kills the writing process. This breaks rr, although I have a workaround which I'm about to land; the workaround temporarily makes the PROT_NONE regions we're writing to PROT_WRITE.

Trevor reported this in the kernel bugzilla already, though I was able to come up with a nice small test program.

http://robert.ocallahan.org/2015/06/bug-in-newer-linux-kernels-affecting-rr.html

This is what I saw when I woke up.

(Taken with my Firefox OS phone.)

Update: Sudbury
So, it took us 8 hours to reach Sudbury. Sudbury is only about a 3 and half hour drive by car on the highway. You could call this a leisurely pace.

We are now on tracks that were originally owned by the Canadian Northern Railway (not to be confused with the Northern Railway of Canada, whose tracks we were on before). These tracks stretch across the country from Vancouver to Quebec City. Canadian Nothern Railway was the second railway to provide transcontinental service across Canada (the first being Canadian Pacific Railway, who still dominate Canada’s rail industry today).

Now these tracks are owned by CNR (Canadian National Railway).

Update: Hornepayne

If you look at a population map of Canada, you’ll see there’s a mostly unpopulated gap between Sault Ste Marie and Kenora, separating western Canada from eastern Canada. I’m currently in that gap.

I didn’t realize it would be so hard to get internet here. I haven’t managed to get an internet connection since leaving Sudbury, and I suspect I won’t be able to until we’re near Thunder Bay.

I’m supposed to be working today, but lack of internet is really hindering what I can do. I spent a while glued to my phone, hoping to glimpse a bar of service or two, but eventually gave up. It’s frustrating, because I’m trying to submit a patch for review, and I was hoping to get it approved before this weekend. I don’t like my chances of getting it reviewed next week when everyone’s busy at Whistler.

After a while, I went to the observation car and stared out the window, which I found relaxing. There seem to be countless beautiful lakes and rivers up here. We never seem to be far from a watercourse. I wonder if these rivers were a route used by fur traders in the early days of Nouvelle France.

The train stopped a couple times to drop off canoeists. I suspect we’re in a part of the country only accessible by rail.

I saw a beaver! You know, I’ve been in Canada all these years, and I think that’s the first time I’ve actually seen a beaver.

Most of the signs on this train are embossed with Braille. The signs use uncontracted Braille. I notice that the English is prefixed with dot-6 (

https://tedclancy.wordpress.com/2015/06/19/the-canadian-day-2/

Last Thursday we had our weekly call about the Reps program, where we talk about what’s going on in the program and what Reps have been doing during the last week.

Summary

• Reps improvement: What are the things you would like to improve?
• Reps in the future: How do you see the program in the next year? What a Rep role should be?
• Road to Whistler: What would you like Council/Peers to do during the Work Week?

AirMozilla video

Don’t forget to comment about this call on Discourse and we hope to see you next week!

https://blog.mozilla.org/mozillareps/2015/06/19/reps-weekly-call-june-18th-2015/

https://tedclancy.wordpress.com/2015/06/19/musical-interlude/

I have no idea where I am. It is completely dark outside and I can’t see a thing.

https://tedclancy.wordpress.com/2015/06/19/37/

We just passed Richmond Hill Centre. I recognize it from the giant Cineplex.

This is an emerging transit hub for York Region. Langstaff GO station is here, and two VIVA lines meet here. There are plans to extend the TTC’s Yonge subway line all the way to here, but they’re held up by the fact that the Yonge Line is already at capacity with regards to ridership.

I remember when there was a proposal to build a casino here, but that didn’t happen. Occasionally you hear people complain that Richmond Hill (and nearby Markham) is too dominated by Chinese people. That’s obviously bullshit. If this place was dominated by Chinese people, there would have been a casino here years ago.

https://tedclancy.wordpress.com/2015/06/19/richmond-hill/

The train is currently stationary, and I figure we’re in York Region, north of Toronto. We passed a sign saying “Parc Downsview Park” about 10 minutes ago, so that must mean we’re on Metrolinx’s Barrie Line (formerly the CNR Newmarket Sub).

According to Wikipedia, this is the oldest trackage in Ontario, dating back to 1835. This track was laid by the Northern Railway of Canada, which was acquired by Grand Trunk Railway in 1888, which was in turn absorbed into CNR in 1923. CNR sold this trackage to Metrolinx in 2009.

I guess we’re waiting for a freight train to pass. (They said that would happen a bit.)

Oh, we’re moving again.

https://tedclancy.wordpress.com/2015/06/19/york-region/

Hace poco cuentaFox estaba presentado problemas al conectarse con el servicio web para obtener los datos de las cuotas y hoy les traemos una actualizaci'on que solventa este problema.

Desde Mozilla han informado que el Addon SDK (CFX) no ser'a utilizado m'as desarrollar complementos y en su lugar recomiendan JPM, una nueva herramienta para compilar complementos que brinda muchas m'as ventajas a los desarrolladores.

Por esta raz'on, desde ahora habr'an dos versiones de cuentaFox:

• una compilada con CFX que no recibir'a nuevas funcionalidades y  mantendr'a 3.0.X para la versi'on
• otra empaquetada con JPM (recomendada) que recibir'a nuevas caracter'isticas, estar'a alojada en GitLab y es necesario utilizar Firefox 38 o superior para que funcione.

?Qu'e hay de nuevo en cuentaFox 3.1?

• Uso de JPM para compilar el complemento.
• Cambio del servicio web a utilizar.
• Ahora el 'icono de la barra de herramientas muestra emoticons que representan el estado de la cuota.
• Adicionado el bot'on Actualizar.
• Cambiado algunos botones de la interfaz.

A continuaci'on se muestran algunas capturas de esta:

Si deseas colaborar en el proyecto pues hacerlo desde GitLab. Si tienes alguna nueva funcionalidad en mente, por favor h'aznosla saber dejando un issue.

Instalar cuentaFox 3.1 (es necesario tener Firefox 38 o superior)

Instalar cuentaFox 3.0.1

Esperamos que les guste es nueva versi'on, cualquier duda o sugerencia, por favor d'ejenla en los comentarios.

http://firefoxmania.uci.cu/problemas-con-el-cuentafox-solucionado/

I’m currently sitting aboard Via Rail’s The Canadian, waiting for the train to depart from Toronto’s Union Station. I’m on my way to a company-wide Mozilla event in Whistler.

This isn’t the first time I’ve travelled on Via Rail, but this is the first time I’ll be travelling all the way to Vancouver.

I’m thinking I might live blog it.

Update: Vaughan

The train is currently stationary, and I figure we’re probably in Vaughan, north of Toronto. We passed a sign saying “Parc Downsview Park” about 10 minutes ago, so that must mean we’re on Metrolinx’s Barrie Line (formerly the CNR Newmarket Sub).

According to Wikipedia, this is the oldest trackage in Ontario, dating back to 1835. This track was laid by the Northern Railway of Canada, which was acquired by Grand Trunk Railway in 1888, which was in turn absorbed into CNR in 1923. CNR sold this trackage to Metrolinx in 2009.

I guess we’re waiting for a freight train to pass. (They said that would happen a bit.)

Oh, we’re moving again.

Update: Richmond Hill

We just passed Richmond Hill Centre. I recognize it from the giant Cineplex.

I remember when there was a proposal to build a casino here. But that didn’t happen.

Occasionally you hear people complain that Richmond Hill (and nearby Markham) is too dominated by Chinese people. That’s obviously bullshit. If this place was dominated by Chinese people, there would have been a casino here years ago.

Update: ???

I have no idea where I am. It is completely dark outside and I can’t see a thing.

Update: Musical interlude

https://tedclancy.wordpress.com/2015/06/19/the-canadian/

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

Extension signing

• This is the first version of Firefox that will enforce our new signing requirements. All AMO add-ons have already been signed and we’re in the process of reviewing non-AMO add-ons. In this version, there’s a preference to disable the signing requirement (xpinstall.signatures.required), which will be removed in 41.

General

• Remove widget module from SDK. The ui module is the recommended alternative.
• Remove support for distribution/bundles.
• Make FUEL warn deprecation to the console on first usage. The FUEL library was introduced long ago to make extension development easier, but it has been superseded by the SDK and various JS Modules. It is now deprecated.
• Rename String.prototype.contains to String.prototype.includes. The contains function still works as an alias, but it will be removed soon.
• Remove support for destructuring for-in.
• Remove Dict.jsm. You can use Map instead.
• Remove temporary aliases for -moz-text-decoration-*.

XPCOM

• Stop supporting binary XPCOM components except as part of the application. There’s a possibility that this will be delayed to 41, but if you have a Firefox add-on that relies on binary XPCOM components, you should update your code as soon as possible.
• Remove nsISSLErrorListener.
• Deprecate old keywords API. The new API is PlacesUtils.keywords.
• Remove nsINSSCertCache.
• Remove GetImplementationLanguage from DOMClassInfo. This removes the implementationLanguage property.
• Get rid of sessionstore-state-write notification.
• Remove several unused XPIDL element interfaces. The following interfaces were removed: nsIDOMHTMLBRElement, nsIDOMHTMLDivElement, nsIDOMHTMLHeadingElement, nsIDOMHTMLTableCaptionElement, nsIDOMHTMLTitleElement.

Themes

• Replace chrome copy of files by overrides.
• Use InContent prefs styling for add-on manager.

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

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

https://blog.mozilla.org/addons/2015/06/18/compatibility-for-firefox-40/

Zweiw"ochentliches Meeting der deutschsprachigen Community. ==== German speaking community bi-weekly meeting.

https://air.mozilla.org/german-speaking-community-bi-weekly-meeting-20150618/

Weekly Mozilla Reps call

https://air.mozilla.org/reps-weekly-20150618/

TL;DR My last day at Mozilla already happened, but I’m still me. I bring together disparate things to foster learning, spread openness and design for participation. I’m a creative generalist who likes to make stuff, and I’m open to exploring opportunities. About 5.5 years ago I took a broken dream to the first Mozilla Festival (at the time it was called Drumbeat) in Barcelona. Going to this festival with my struggling project was a last ditch effort, I was hanging on, trying to make it work. Drumbeat was the place that I was finally able to let go, start over, try again. The people I met there gave me new ideas, they introduced me to a way of working that fit with how my brain operates. Drumbeat lit a fire under me. I met Mozillians. [caption id="" align="alignnone" width="500"] photo by Mozilla Europe[/caption] I’ve resisted the status quo because when I've questioned it, I don't usually receive satisfactory answers. Over the years, Mozillians taught me how to focus my defiance towards a common good. It’s that focus that has cultivated me and my way of being in the professional space. I believe in open, and I believe that what Mozilla is trying to do for the world is a just cause. Openness can be hard, but in my experience the right thing is always more difficult. Last Monday was my final day as a paid contributor, and I’m in the process of detangling Mozilla from my own identity. We’ve grown up together in this community. We have rallied around a nascent vision and made it something that is resonating throughout the world. I am proud to have contributed to every aspect of the Foundation’s work - from strategy to learning design to prototyping to evangelism to community management to production - I’ve helped Mozilla innovate in the teaching and learning space. Our work has inspired people, and I’ll always be a Mozillian. But I want to be more too. Mozilla is a part of me, but it can no longer define me. [caption id="" align="alignnone" width="640"] photo by Doug Belshaw[/caption] I don’t know what’s next for me, and that's ok. I will continue to think and write and make and learn and fail, and I will continue to embody the open ethos. Even when it’s hard, especially when it’s hard. In the immediate future, I will pause, breathe and take stock. I can literally do anything with the competencies and skills I’ve developed and honed over the years. That feels like a powerful invitation to do the right things. There is a lot of right in the world. I’m looking for something where I can design learning/engagement opportunities, develop leaders and apply open practices, digital/web literacies and all things geeky. I want to help people/orgs grow, collectively, as they allow me to grow together with them. I want to shift power structures and community dynamics, be a voice for people who need one and just be who I am – defiant, curious, unwavering in the ideals of open. If you think you have a right thing for me, let me know. You all know how to find me. laura [at] this domain is where you started interacting with me in 2010, and it’s where you can continue to do so. You can also find me on twitter or LinkedIn (or just google me, I'm all over the web). I hope some of you reach out - there are plenty of wonderful memories and new ideas to discuss, and I will always be here for my Mozilla friends.

http://www.zythepsary.com/work-in-progress/whats-next-for-laura/

I have been working with emails as a tool for the last 20 years. In different communities, setup, etc. I never felt overwhelmed by the number of emails, I have filtering strategies, I could talk about that in a separate post.

When projects using emails are going awry to havoc, most of the time is because people do not use emails in an optimum way. My main recommendation would be:

Always copy to an archived mailing-list. Never ever send private emails. (1)

In a previous working life, I have given a talk about Apprendre `a travailler avec le mail (French), Coralie translated it into English last year: Read Learning to work with e-mail.

(1): In the context of working on a project. Privates emails for HR, personal stuff, etc is fine. Anything which is about the project should be on a linkable, archived mailing-list.

Otsukare!

http://www.otsukare.info/2015/06/18/working-with-emails

Join director Brett Gaylor for a screening and discussion of 'Do Not Track' (https://donottrack-doc.com), a personalized documentary series about privacy and the web economy.

https://air.mozilla.org/brownbag-documentary-screening-do-not-track/

Nick Desaulniers will be speaking on, "Adaptive Bitrate Streaming: Let's build a Netflix clone."

https://air.mozilla.org/tech-talk-3/

Duration: 10 minutes This is a weekly status meeting, every Wednesday, that helps coordinate the shipping of our products (across 4 release channels) in order...

https://air.mozilla.org/product-coordination-meeting-20150617/

Watch mconley livehack on Firefox Desktop bugs!

https://air.mozilla.org/the-joy-of-coding-mconley-livehacks-on-firefox-episode-19/

I’m happy to report that we at Mozilla have started working with Chromium, Edge and WebKit engineers on creating a new standard, WebAssembly, that defines a portable, size- and load-time-efficient format and execution model specifically designed to serve as a compilation target for the Web. As reflected in the high-level goals, a central requirement for WebAssembly is that it integrate well with the rest of the Web platform and that the initial version run efficiently on current browsers using a client-side polyfill. As demonstrated, the polyfill can leverage asm.js to get great performance. For existing Emscripten/asm.js users, targeting WebAssembly will be as easy as flipping a flag. Thus, it is natural to view WebAssembly as the next evolutionary step of asm.js (a step many have requested and anticipated).

We’re pretty early into the overall process—there is no draft spec or even final formal standards body chosen, just a W3C Community Group, some initial prototyping and early cross-browser consensus on the high-level design documents. Going forward, there will be a lot more iteration and experimentation under the WebAssembly GitHub organization. For questions, check out the still-emerging FAQ. Brendan Eich also has a vibrant blog post with more context, history and JS perspective.

https://blog.mozilla.org/luke/2015/06/17/webassembly/