Mozilla Nederland LogoDe Nederlandse
Mozilla gemeenschap

Byron Jones: happy bmo push day!

Mozilla planet - di, 15/07/2014 - 08:40

the following changes have been pushed to

  • [1029500] bug.attachments shouldn’t include attachment data by default
  • [1032323] canonicalise_query() should omit parameters with empty values so generated URLs are shorter
  • [1027114] When sending error to Sentry for webservice failures, we need to first scrub the username/login/password from the query string
  • [1026586] Using Fira as default font in Bugzilla
  • [1027182] – SQL to remove bug_user_last_visit not correct
  • [1036268] REST webservice should return http/404 for invalid methods
  • [1027025] comment.creator has no real_name
  • [1036795] comment.raw_text is returned by the bzapi compatibility extension
  • [1036225] Return a link to the REST documentation in “method not found” errors
  • [1036301] change the description of the “bug id” field on bugmail filtering preferences tab to “new bug”
  • [1028269] Firefox OS Pre-load App Info Request Form
  • [1036303] add a list of tracking/project/etc tracking flags to the bugmail filtering prefs page

discuss these changes on

Filed under: bmo, mozilla
Categorieën: Mozilla-nl planet

Mozilla- Comes With Another Innovation. - Argyll Free Press

Nieuws verzameld via Google - di, 15/07/2014 - 07:49

Argyll Free Press

Mozilla- Comes With Another Innovation.
Argyll Free Press
Mozilla is planning to launch a basic worldwide workshop on how to use internet and other fundamental digital expertise. It will start from next two months and they set the target of around 100,000 to take part in it. “Mozilla science lab” is the name ...

Categorieën: Mozilla-nl planet

Firefox smartphones to be launched in India in July, says Mozilla COO - Digitimes

Nieuws verzameld via Google - di, 15/07/2014 - 07:46

Firefox smartphones to be launched in India in July, says Mozilla COO
Mozilla initially launched Firefox smartphones in the Latin America and Europe markets in July 2013 and has sold about one million units, Gong said. Mozilla has been able to cooperate with only 1-2 mobile telecom carriers in each country in the two ...

Categorieën: Mozilla-nl planet

Google a Mozilla omezují podporu plug-inů: které přestanou fungovat? - LUPA

Nieuws verzameld via Google - di, 15/07/2014 - 06:33

Google a Mozilla omezují podporu plug-inů: které přestanou fungovat?
Prohlížeče Google Chrome a Mozilla Firefox v posledních měsících omezují podporu plug-inů a padají konkrétní termíny, kdy některé plug-iny přestanou být podporované. Důvodů k odklonu od plug-inů je více než dost. Tradičním argumentem je bezpečnost.

Categorieën: Mozilla-nl planet

Nicholas Nethercote: Poor battery life on the Flame device?

Mozilla planet - di, 15/07/2014 - 01:28

The new Firefox OS reference phone is called the Flame. I have one that I’m using as my day-to-day phone, and as soon as I got it I found that the battery life was terrible — I use my phone very lightly, but the battery was draining in only 24 hours or so.

It turns out this was because a kernel daemon called ksmd (kernel samepage merging daemon) was constantly running and using about 3–7% of CPU. I detected this by running the following command which prints CPU usage stats for all running processes every five seconds.

adb shell top -m 5

ksmd doesn’t seem very useful for a device such as the Flame, and Alexandre Lissy kindly built me a new kernel with it disabled, which improved my battery life by at least 3x. Details are in the relevant bug.

It seems that plenty of other Flame users are not having problems with ksmd, but if your Flame’s battery life is poor it would be worth checking if this is the cause.

Categorieën: Mozilla-nl planet

Amy Tsay: The AMO Reviewer Community Turns 10

Mozilla planet - ma, 14/07/2014 - 20:07

A decade ago, Firefox introduced the world to a customizable web browser. For the first time, you could use add-ons to personalize your entire browsing experience—from the look and feel of buttons, to tab behaviors, to content filtering. Anyone with coding skills could create an add-on and submit it to (AMO) for others to use. The idea that you could experience the web on your own terms was a powerful one, and today, add-ons have been downloaded close to 4 billion times.

Each add-on listed on AMO is thoroughly reviewed to ensure its privacy and safety, and volunteer reviewers have shouldered much of this effort. To properly inspect an add-on, a reviewer has to dig into the code—a taxing and often thankless chore. Nobody notices when an add-on works as expected, but everybody notices when an add-on with a security flaw gets through. These reviewers are truly unsung heroes.

From the beginning, volunteers recognized the importance of reviewing add-ons, and self-organized on wiki pages. As add-ons grew in popularity, it became necessary to hire a few people out of this community to keep it organized and nurtured. Ten years later, volunteers are still responsible for about half of all add-on reviews (about 150 per week). Our top volunteer reviewer is approaching 9,000 reviews.

As a community manager working with volunteer reviewers, I’m sometimes asked what the secret is behind this enduring and resilient community. The secret is there isn’t just one thing. Anyone who’s ever tried giving away free food and booze as their primary community-building strategy has learned how quickly the law of diminishing returns kicks in.

What’s In It For Me?

To understand why people get involved with reviewing add-ons, and why they stay involved, you only have to understand human nature. Altruism tells just part of the story. People are often surprised when I tell them that many reviewers began volunteering for selfish reasons. They are add-on developers themselves, and wanted their add-ons to be reviewed faster.

Some of these developers authored add-ons that are used by tens of thousands, sometimes millions of people, so it’s important to be able to push out updates quickly. Since reviewers are not allowed to review their own add-ons, the only way to speed things up is to help burn down the queue. (Reviewers can also request expedited reviews of their add-ons.) Also, they can learn how other people make add-ons, which in turn helps them improve their own.

Intrinsic Motivation

People who create add-ons are people who write code, so the code itself can be interesting and intrinsically motivating. In Drive: The Surprising Truth About What Motivates Us, Daniel Pink writes that self-motivated work tends to be creative, challenging, and non-routine, and add-on reviewing has it all: every piece of code is different (creative), security flaws can be cleverly concealed (challenging), and reviewers contribute at their own pace (non-routine).

Not Just Carrots and Sticks

A few years ago, we began awarding points for add-on reviews and introduced a leaderboard that lets reviewers see their progress against other reviewers. The points could also be redeemed for swag as part of an incentive program.

While this is admittedly a carrot-and-stick approach to engaging contributors, it serves a larger purpose. By devoting time and resources to sending handwritten notes and small tokens, we are also sending the message that reviewers are important and appreciated. When you open your mailbox and there’s a Fedex package containing a special-edition t-shirt in your size, you know your efforts haven’t gone unnoticed.

Community and Responsibility

AMO reviewers know that they play an important role in keeping Firefox extensible, and that their work directly impacts the experience people have installing add-ons. Since about half of the hundreds of millions of Firefox users have add-ons installed, that is no small feat. I’ve heard from reviewers that they stick around because they like being part of a community of awesome people who are responsible for keeping add-ons safe to use in Firefox.

The Magic Formula

Online communities are complex, their fabric woven from a mesh of intrinsic and extrinsic, selfish and altruistic motivations. A healthy, lasting community benefits from a combination of these factors, in varying proportions, some of them driven by the community and some by the attentive community-builders tasked with nurturing it. There isn’t a silver bullet; rather, it’s about finding your own magic formula and knowing that often, the secret ingredient is whatever it is that makes us human.

Happy 10th birthday, AMO reviewers.

Categorieën: Mozilla-nl planet

Mark Côté: BMO mid-2014 update

Mozilla planet - ma, 14/07/2014 - 19:42

Here’s your mid-year report from the offices, basements, and caverns of BMO!


This year we’re spending a lot of time on performance. As nearly everyone knows, Bugzilla’s an old Perl app from the early days of the Web, written way before all the technologies, processes, and standards of today were even dreamt of. Furthermore, Bugzilla (including BMO) has a very flexible extension framework, which makes broad optimizations difficult, since extensions can modify data at many points during the loading and transforming of data. Finally, Bugzilla has evolved a very fine-grained security system, crucial to an open organization like Mozilla that still has to have a few secrets, at least temporarily (for security and legal reasons, largely). This means lots of security checks when loading or modifying a bug—and, tangentially, it makes the business logic behind the UI pretty complex under the hood.

That said, we’ve made some really good progress, starting with retrofitting Bugzilla to use memcached, and then instrumenting the database and templating code to give of reams of data to analyze. Glob has lots of details in his post on BMO perf work; read it if you’re interested in the challenges of optimizing a legacy web app. The tl;dr is that BMO is faster than last year; our best progress has been on the server side of show_bug (the standard Bug view), which, for authenticated users, is about 15% faster on average than last year, with far fewer spikes.

Bugs updated since last visit

Part of an effort to improve developer productivity, in June we rolled out a feature to give a new way for users to track changes to bugs. BMO now notes when you visit a bug you’re involved in (when you load it in the main Bugzilla UI or otherwise perform actions on it), and any changes to that bug which occur since you last visited it will show up in a table in My Dashboard. Read more.

Bugmail filtering

Another improvement to developer productivity centred around notifications is the new bugmail filtering feature. Bugzilla sends out quite a lot of mail, and the controls for deciding when you want to receive a notification of a change to a bug have been pretty coarse-grained. This new feature is extremely customizable, so you can get only the notifications you really care about.

BzAPI compatibility

There have been several broad posts about this recently, but it’s worth repeating. The original Bugzilla REST API, known as BzAPI, is deprecated in favor of the new native REST API (on BMO at least; it isn’t yet available in any released version of the Bugzilla product). If possible, sites currently using BzAPI should be modified to use the new API (they are largely, but not entirely, compatible), but at a minimum they should be updated to use the new BzAPI compatibility layer, which is hosted directly on BMO and sits atop the new REST API. The compatibility layer should act almost exactly the same as BzAPI (the exceptions being that a few extra fields are returned in a small number of calls). At some point in the not-too-distant future, we’ll be (transparently) redirecting all requests to BzAPI to this layer and shutting down the BzAPI server, so it’s better to try to migrate now while the original BzAPI is still around, in case there are any lingering bugs in the compatibility layer.

More stuff

As usual, you can see our current goals and high-priority items for the quarter on the BMO wiki page.

Categorieën: Mozilla-nl planet

Doug Belshaw: Web Literacy 'maker' badges

Mozilla planet - ma, 14/07/2014 - 18:34

{cross-posted from the Webmaker blog)



To help with Maker Party (launching tomorrow!) we’ve been working on a series of Web Literacy ‘maker’ badges. These will be issued to those who can make digital artefacts related to one or more competencies on the Web Literacy Map.

The structure of each of the Webmaker resources page for each competency (e.g. Navigation) is:

  • Discover
  • Make
  • Teach

We’re not currently badging the ‘Discover’ level, and the ‘Teach’ level is currently covered by the Webmaker Mentor badge. These new ‘Make’ badges are our first badges specifically for web literacy.

How you can help

We’re planning to launch these badges at the end of July. Before we do so, we want to make sure the process works smoothly for everyone, for each badge. We’re also very much interested in your feedback on the whole process.

Here’s what to do. Go to the link below and follow the instructions. You’ll need to either make something related to one of the Web Literacy Map competencies, or link to something you’ve made before.

Questions? Comments? I’m @dajbelshaw or you can email me at

Categorieën: Mozilla-nl planet

Mark Surman: The Instagram Effect: can we make app making easy?

Mozilla planet - ma, 14/07/2014 - 18:04

Do you remember how hard digital photography used to be? I do. When my first son was born, I was still shooting film, scanning things in and manually creating web pages to show off a few choice pictures. By the time my second son was walking I had my first good digital camera. Things were better, but I still had to drag pictures onto a hard drive, bring them into Photoshop, painstakingly process them and then upload to Flickr. And then, seemingly overnight, we took a leap. Phones got good cameras. Photo processing right on the camera got dead simple. And Instagram happened. We rarely think about it, but: digital photography went from hard and expensive to cheap and ubiquitous in a very short period of time.

Mozilla on-device app making concept from MWC 2013 (Frog Design)

Mozilla on-device app making concept from MWC 2013 (Frog Design)

I want to make the same thing happen with mobile apps. Today: making a mobile app — or a complex interactive web page — is slow, hard and only for the brave and talented few. I want to make making a mobile app as easy as posting to Instagram.

At Mozilla, we’ve been talking about this for while now. At Mobile World Congress 2013 we floated the idea of making easy to make apps. And we’ve been prototyping a tool for making mobile apps in a desktop browser since last fall. We’ve built some momentum, but we have yet to solve two key problems: crafting a vision of app making that’s valuable to everyday people and making app making easy on a phone.

We came one step closer to solving these problems last week win London. In partnership with the GSMA, we organized a design workshop that asked: What if anyone could make a mobile app? What would this unlock for people? And, more interestingly, what kind of opportunity and imagination would is create in places where large numbers (billions) of people are coming online for the first time using affordable smartphones? These are the right questions to be asking if we want to create an Instagram Effect for apps.

Screen Shot 2014-07-14 at 6.08.08 PMScreen Shot 2014-07-14 at 6.09.00 PM Screen Shot 2014-07-14 at 6.08.47 PM

The London design workshop created some interesting case studies of why and how people would create and remix their own apps on their phones. A DJ in Rio who wanted to gain fans and distribute her music. A dabbawalla in Mumbai who wants to grow and manage the list of customers he delivers food to. A teacher in Durban who wants to use her Google doc full on student records to recruit parents to combat truancy. All of these case studies pointed to problems that non-technical people could more easily solve for themselves if they could easily make their own mobile apps.

Over the next few months, Mozilla will start building on-device authoring for mobile phones and interactive web pages. The case studies we developed in London — and others we’ll be pulling together over the coming weeks — will go a long way towards helping us figure out what features and app templates to build first. As we get to some first prototypes, we’re going get the Mozilla community around the world to test out our thinking via Maker Parties and other events.

At the same time, we’re going to be working on a broader piece of research on the role of locally generated content in creating opportunity for people in places whee smartphones are just starting to take at off. At the London workshop, we dug into this question with people from organizations like Equity Bank, Telefonica, USAID, EcoNet Wireless, Caribou Digital, Orange, Dalberg, Vodaphone. Working with GSMA, we plan to research this local content question and field test easy app making with partners like these over next six months. I’ll post more soon about this partnership.

Filed under: education, mozilla, webmakers
Categorieën: Mozilla-nl planet

David Burns: WebDriver F2F - London 2014

Mozilla planet - ma, 14/07/2014 - 16:15

Last week saw the latest face to face of the WebDriver Working Group held at Facebook. This meeting was important as this is hopefully the last face to face before we go to Last call allowing us to concentrate on issues that come up during last call.

This meeting was really useful as we were a number of discussions around the prose of the spec when it comes to conformance and usability of the spec, especially when given to implementors who have never worked on WebDriver.

The Agenda from the meeting can be found here

The notable items that were discussed are:

  • Merge getLocation and getSize to single call called getElementRect. This has been implemented in FirefoxDriver already
  • Describe restrictions around localhost in security section
  • How the conformance test will look (Microsoft have a huge raft tests they are cleaning up and getting ready to upstream!)
  • Actions has been tweaked from the original straw man delivered by Mozilla, hopefully see the new version in the next few weeks.

To read what was discussed you can see the notes for Monday and Tuesday.

Categorieën: Mozilla-nl planet

台灣成Firefox OS研發重鎮,年內將成Mozilla全球最大辦公室 - iThome Online

Nieuws verzameld via Google - ma, 14/07/2014 - 13:02


台灣成Firefox OS研發重鎮,年內將成Mozilla全球最大辦公室
iThome Online
Mozilla推出Firefox OS手機系統已滿一年,今年將從歐美、拉丁美洲擴大進入亞洲市場。基於Firefox OS發展需要,Mozilla台灣分公司Firefox OS佔全球研發團隊一半以上,台北辦公室今年內更將成為Mozilla全球最大規模的辦公室。 Mozilla是在2011年來台設立分 ...
Firefox OS滿週年目標終止平台壟斷、擴大連網聯合新聞網
Firefox OS亞洲市場本季推出25美元手機台灣亮相Sogi! 手機王
Firefox OS耕耘一年有成,智慧型手機成功打入歐洲與中南美洲市場數位時代
alle 5 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Mozilla Reps Community: Rep Of The Month : June 2014 – Shreyas Narayanan Kutty

Mozilla planet - ma, 14/07/2014 - 12:39

Shreyas Narayanan KuttyShreyas Narayanan Kutty came to Reps as an already inspirational leader and role model in the Firefox Student Ambassadors program. In addition to organizing a number of successful MozCafes, Shreyas has led a charge to empower kids on the web through the Webmaker initiative ‘Kidzilla’ and a longer-term call to action in schools to start Webmaker Clubs.

Shreyas has inspired others in his community and across the world with blog posts and photos and a teaching kit which have been featured in Mozilla publications.

In addition to his FSA and Reps contribution, Shreyas has been a key participant in Hive India and most recently, Mozcamp Beta, where his Popcorn video ‘I am Mozillian’, featuring 19 different states of India stole the show.

See past featured Reps..

Categorieën: Mozilla-nl planet

David Burns: Bugsy 0.3.0 - Comments!

Mozilla planet - ma, 14/07/2014 - 12:07

I have just released the latest version of Bugsy. This allows you to get comments from Bugzilla and add new comments too. This API is still experimental so please send back some feedback since I may change it to real world usage.

I have updated the documentation to get you started.

>>> comments = bug.get_comments() >>> comment[0].text "I <3 Cheese" >>> bug.add_comment("And I love bacon")

You can see the Changelog for more details.

Please raise issues on GitHub

Categorieën: Mozilla-nl planet

Firefox doit devenir l'anti-Chrome et Mozilla doit s'affranchir des fonds de Google ... -

Nieuws verzameld via Google - ma, 14/07/2014 - 09:57

Firefox doit devenir l'anti-Chrome et Mozilla doit s'affranchir des fonds de Google ...
Plusieurs mois après avoir démissionné de son poste de PDG de la fondation Mozilla, Brendan Eich a laissé entrevoir sa vision future de Firefox. Pour rappel, le navigateur de la fondation est en recul par rapport à ses principaux concurrents, 18,02 ...

Google Nieuws
Categorieën: Mozilla-nl planet

Mozilla kicks off global 'digital literacy' program - Sin Chew Jit Poh

Nieuws verzameld via Google - ma, 14/07/2014 - 09:22

Mozilla kicks off global 'digital literacy' program
Sin Chew Jit Poh
(WASHINGTON-AFP) - The Mozilla Foundation is expecting more than 100,000 people to participate in a series of events worldwide over the next two months teaching basic Internet use and other digital skills. The "Webmaker" events which run through ...

en meer »
Categorieën: Mozilla-nl planet

Aaron Train: Proxy Server Testing in Firefox for Android

Mozilla planet - ma, 14/07/2014 - 09:00

Recent work on standing up a proxy server for web browsing in Firefox for Android is now ready for real world testing. Eugen, Sylvain, and James, from the mobile platform team have been working towards the goal of building a proxy server to ultimately increase privacy (via a secure connection), reduce bandwidth usage, and improve latency. Reduced page load times is also a high level goal. A detailed Wiki page is available at:

The time for testing is now.

How to Help
  • Install this (available here) proxy configuration (development server) add-on in Firefox for Android
  • Browse as you normally would (try your network connection and or WiFi connections)
  • File bugs in GitHub (make sure to compare with the proxy enabled and disabled)
  • Talk to us on IRC
Categorieën: Mozilla-nl planet

Leo McArdle: Letter to my MP on DRIP

Mozilla planet - zo, 13/07/2014 - 16:25

What follows is a copy of the email I just sent to my MP about the Data Retention and Investigatory Powers Bill (DRIP). I urge you to send a similar email right now.

Dear Robin Walker,

I have no doubt that by now you will have heard of the Data Retention and Investigatory Powers Bill (DRIP) which your Government and the Opposition will try to rail-road through Parliament next week. I also have no doubt that you will have heard of the great deal of criticism surrounding this bill, both from your colleagues within Westminster hailing from all parties, such as David Davis MP and Tom Watson MP, and those outside of Westminster, such as Jim Killock of the Open Rights Group.

In April the European Court of Justice (ECJ) ruled that the Data Retention Directive (DRD) was incompatible with the Charter of Fundamental Rights of the European Union and therefore that the 2006 act enabling the DRD in the UK was a breach of Human Rights. This means what was, and still is, the status quo when it comes to forcing companies to store data on their customers is a breach of fundamental Human Rights. This is the same status quo which the Home Secretary has said that DRIP merely retains. I think it is clear to see why I, and others, have such a problem with DRIP.

The ECJ ruling outlined some very clear ways in which the DRD could be made compatible with Human Rights law, by saying that this cannot be done on a blanket basis and that someone independent must supervise police access. These fundamental points are missing from DRIP.

Furthermore, DRIP goes far further than just retaining the status quo. It makes sweeping amendments to the Regulation of Investigatory Powers Act (RIPA) including the expansion of what a communications service provider is, the extension of these powers to outside the UK and an open door to allow the Government to make new regulations about data retention at will, without the need to debate them fully in Parliament. I am sure you agree that such huge amendments to RIPA need to be subject to full Parliamentary scrutiny.

It is perfectly clear to everybody, including you, I am sure, Mr Walker, that the Government is using the ECJ ruling as a pretext to force through, at great speed, legislation which affects Human Rights, without proper scrutiny or deliberation. The ECJ ruling was in April, and many warned as far back as 2006 that the DRD was flawed. The UK Government has had years to prepare for the DRD being struck down. There is no reason for this emergency legislation, other than to try and sneak sweeping changes under the noses of MPs who have been allowed to go on holiday.

Wherever you stand on where the balance should be between State Security and Civil Liberties (and I would not be surprised if we stand on opposite ends of that balance), you must agree that five days in nowhere near enough time to properly debate and represent all the views on this issue.

It is for this reason that I urge you as my elected representative to vote against DRIP, and do everything you can to urge your colleagues to do the same. At the very least, could you please push for a highly amended bill, with all the sections amending RIPA removed, which serves purely as a stopgap, not for a period of two years, but for a maximum of six months. We need to have this debate now, and not pass the buck on to the next Government in 2016, who will surely pass the buck on again.

In 2015 I will get my first opportunity to vote in a General Election, and while I may feel that this Government has done devastating things to this country, you, Mr Walker, may be able to differentiate yourself from a sea of blue if you stand up for Civil Liberties and Human Rights.

Yours sincerely,
Leo McArdle

Categorieën: Mozilla-nl planet