Mozilla Nederland LogoDe Nederlandse

Abonneren op feed Mozilla planet
Planet Mozilla -
Bijgewerkt: 1 maand 2 uur geleden

Firefox UX: What’s new in Firefox Preferences

vr, 03/11/2017 - 04:04

Hi! I’m Tina Hsieh, the UX designer in charge of the Firefox Preferences (or “Options” on Windows) redesign. The Preferences team is launching a few great changes in Preferences starting from Firefox 56. Exciting, right? Then you probably will be interested in knowing what we’ve done to create our brand new Preferences redesign.

As we started looking into Firefox, we noticed that our Preferences has been lacking love for a while. The user research result from project Onboarding shows that not only advanced users visit Preferences for customizing their Firefox, but also some first-time users go directly to Preferences for playing around with cool stuff. Since one of our design principles is “Adaptable”, which means we care about giving control of the entire browser experience to each of our users. Therefore, the goal of the Firefox Preferences redesign is to make our Preferences much easier for users to understand how to configure their Firefox to fulfill their specific needs.

Problem identification<figcaption>The eight categories in Firefox 55</figcaption>

After reviewing the old information architecture (IA), we had some questions about the eight categories. Could users go directly to what they’re looking for? Would they get lost in our structure? Are the text labels straightforward enough for them to understand? Before kicking-off the redesign project, we conducted a pilot Treejack test and validated the problems.

What is Treejack?

Treejack is a questionnaire-based method for evaluating the ability to find items in a hierarchy. It helps us to discover if users can locate settings in the right categories. The test result shows that only 50% of the tasks were completed by 237 participants, which we weren’t satisfied with. Therefore, we decided to take a bold step forward with a new IA.

Research, design, and content strategy

We have a team dedicated to the redesign project: UX designers, UX researchers, and a content strategist. UX researchers work with UX designers to keep an eye on the interaction area. Together with our content strategist, we can ensure that the redesigned structure can solve the findability issue and also promote Firefox’s core values.

The three methods we used for the redesign:

  • Card sort:
    Card sorting is a well-known method for IA design that allows participants to group and put settings in an order that makes sense to them. Through this process, we can have a peek of a user’s mindset. It also helps us to see which category names are used, and not used.
  • Treejack:
    As I mentioned earlier, it’s a tool for us to address the findability issue. We used it as a pilot test to kick off the project, and also used it as a validation to see if the proposals of the different grouping methods and different text labels improved.
  • User test:
    Treejack and Card sort are both quantitative tests. With the qualitative user tests, we can see how participants navigate our high-fidelity prototype for accomplishing tasks and how many potential traps are in the proposed structures.
    Participants’ reactions are very valuable to us. Sometimes participants thought they successfully completed the task, but in fact, they failed. That helps us understand the real problems of the proposal.
Our Insights

1. Merging categories “Privacy” and “Security” helps.

Undoubtedly, “Privacy” and “Security” are strongly connected to each other, so the differentiation between them wasn’t clear. “Privacy & Security” got the highest scores in all tests.

<figcaption>Merge “Privacy” and “Security” into “Privacy & Security”</figcaption>“It helps reduce confusion and makes me more sure about where to look for certain things.”“I really like the privacy and security was all in one tab since they are so similar.”

Our participants were delighted with this change.

2.“General” is necessary in Preferences, but having both “General” and “Advanced” can easily confuse users.

64% of participants created the category “General” in the open card sorting test. However, when we asked participants to make some specific changes (e.g. change the way how Firefox handles email links on websites, or customize the the way Firefox does updates) in the proposed structure including both “General” and “Advanced” categories, participants struggled.

<figcaption>Remove the unclear “Advanced” category to eliminate the confusion</figcaption>

Therefore, we eliminated any confusion by sorting the original advanced settings to the dedicated categories. The failure rate of the “General only” proposal was amazingly reduced a lot in our follow-up tests.

3. Configuring what results should be shown when typing in the address bar is more considered as a privacy-related function.

There is a set of settings in Preferences which allows users to decide if they want to hide their browsing history, bookmarks, or open tabs from the search results. Should it be considered as search-related settings? Or privacy-related settings?

<figcaption>The Address Bar settings have relationship with both “Search” and “Privacy & Security”</figcaption>

From the user testing result, we noticed that the use case for these settings is more privacy-related than search related, so we keep the address bar settings under “Privacy and Security” since it is where people instinctively go.

4. A technical terminology “Sync” confuses over half of the participants.

We should always be careful with using technical terminology. From the test result, we learned that over 53% of participants couldn’t understand the label “Sync” in the pilot treejack test. Therefore, we started to propose different labels without technical terms.

<figcaption>Replace the label from “Sync” to “Firefox Account”</figcaption>

In the end, it was a gratifying result! When we replaced the category name to “Firefox Account”, 12% more participants chose the right answer compared to the previous result.

So…here comes our new IA!One more thing

We all know that there is a thing that you have been waiting years for. And we’ve heard your voices: The search feature (finally!) has also landed in Firefox 56, Yay! :)

Another exciting thing coming! Thanks to Helen, our Preferences visual designer, Firefox Preferences is on the train of the new Photon style look. What is Photon? What does that look like? Try it out on your Firefox Beta now!

What’s new in Firefox Preferences was originally published in Firefox User Experience on Medium, where people are continuing the conversation by highlighting and responding to this story.

Categorieën: Mozilla-nl planet

Air Mozilla: Reps Weekly Meeting Nov. 2, 2017

do, 02/11/2017 - 17:00

Reps Weekly Meeting Nov. 2, 2017 This is a weekly call with some of the Reps to discuss all matters about/affecting Reps and invite Reps to share their work with everyone.

Categorieën: Mozilla-nl planet

Air Mozilla: Reps Weekly Meeting Nov. 2, 2017

do, 02/11/2017 - 17:00

Reps Weekly Meeting Nov. 2, 2017 This is a weekly call with some of the Reps to discuss all matters about/affecting Reps and invite Reps to share their work with everyone.

Categorieën: Mozilla-nl planet

Karl Dubost: Discover The Fatwigoo

do, 02/11/2017 - 08:46

I'm a uBlock and uMatrix user with a very agressive setting. I block everything. It makes the Web faster, more performant, less prone to bugs and security issues. In my text only version of the Web, there are surprises. Sites entirely made of JavaScript which are not at all readable. It's a kind of Occam's razor where it helps me decide if I should spend time to configure my browser to make the page more readable. If the cost/benefit ratio is too high, I just ignore the site.

But let me introduce you to the "Fatwigoo", an interesting animal which is populating the CSS-less and JS-less landscape of Web pages. You can choose to pronounce it "Fa-twee-goo" or "fat-wee-goo". I prefer the latter. You can partly reproduce the screenshot (below) with going to this article on A List Apart with Firefox and select in the View Menu ➜ Page Style ➜ No Style.

These are created by the inline SVG in the page. These SVG icons are stretching by default to the width of the viewport. Nothing wrong with that, but you can improve the rendering for people like me who prefers sad-boring-peaceful web pages.

How To Solve The Fatwigoo

The icon for twitter in this page is represented by this SVG.

<svg version="1.1" xmlns="" xmlns:xlink="" x="0px" y="0px" enable-background="new 0 0 274 224" viewBox="0 0 274 274" xml:space="preserve"> <path d="M273.7,27.2c-10.1,4.5-20.9,7.5-32.2,8.8c11.6-6.9,20.5-17.9,24.7-31c-10.8,6.4-22.8,11.1-35.6,13.6 C220.3,7.7,205.7,0.9,189.6,0.9c-31,0-56.1,25.1-56.1,56.1c0,4.4,0.5,8.7,1.5,12.8C88.3,67.4,47,45.1,19.3,11.2 c-4.8,8.3-7.6,17.9-7.6,28.2c0,19.5,9.9,36.6,25,46.7c-9.2-0.3-17.8-2.8-25.4-7c0,0.2,0,0.5,0,0.7c0,27.2,19.3,49.8,45,55 c-4.7,1.3-9.7,2-14.8,2c-3.6,0-7.1-0.4-10.6-1c7.1,22.3,27.9,38.5,52.4,39c-19.2,15-43.4,24-69.7,24c-4.5,0-9-0.3-13.4-0.8 c24.8,15.9,54.3,25.2,86,25.2c103.2,0,159.6-85.5,159.6-159.6c0-2.4-0.1-4.9-0.2-7.3C256.7,48.3,266.2,38.5,273.7,27.2z"> </path> </svg>

Throw in there a width attribute.

<svg version="1.1" xmlns="" xmlns:xlink="" x="0px" y="0px" enable-background="new 0 0 274 224" viewBox="0 0 274 274" width="50px" xml:space="preserve"> … </svg>

And suddenly the icon will just be a small 50px icon in the page. It's not an issue because anyway you are already adjusting size, colors, etc. through CSS. The CSS will set the right size for the users who are using Pathécolor web pages.

Before - After


Fatwigoo example


Fatwigoo example


Categorieën: Mozilla-nl planet

Gary Kwong: Presenting in different languages, places

do, 02/11/2017 - 03:25

tl;dr: Speaking in public can be daunting for most people. In this post, I will share some tips on how to give effective presentations/speeches in various languages around the world.

Anyone who has delivered a public presentation will know that it can be a nerve-wracking experience. It requires content knowledge, audience understanding, and above all, confidence to convey your message effectively. These can be gained via practice, and lots and lots of it.

I have been very lucky to have had many chances to give talks these past 10 years, so I would like to share some insights with you, as to how I do it.

Examples: (links to external sites where available)

  • Open source development (Mozilla/Firefox):
    • University (NUS) classrooms (2008-2011)
    • Open source meetups, Seoul (2012)
      • In South Korea (English with an interpreter to Korean)
    • HKOSCON (20162017), open source meetups (2013, 2014 [via here], 2017)
      • In Hong Kong (English or Cantonese)
    • JavaScript work week, Toronto (2014)
      • In Canada (English)
    • Open source meetups, Tokyo (2015)
      • In Japan (English with an interpreter to Japanese)
    • COSCUP (Unconference 2016, 2017) Taipei, open source meetups
      • In Taiwan (Mandarin)
  • Recently, Eastern/Western cultural differences at various conferences:
    • HKOSCON 2017 in Hong Kong (English)
    • COSCUP 2017 in Taipei (Mandarin)
    • SITCON 2017 in Hong Kong (Cantonese)

(You can view some of the videos below)

It is clear that I steer towards speaking in Asia, and that is precisely my motive. I use the knowledge that I have gained in the Western world (North America, with a little bit of Western Europe) and attempt to help bridge the Eastern/Western gap. Generally, I find that the Eastern world (northeast Asia, some southeast Asia) seems much more enthusiastic to know more about the Western side, rather than the other way around.

Here’s what I would like to share not just on how to deliver a talk, but also how to deliver an effective one:

  • Understand yourself first
    • Gain domain knowledge. Not knowing the content of your talk inside-out will usually contribute to a nervous experience and impact confidence
      • Before some of my Asian conference talks, I had also attended some in Europe and North America to have a feel on what it’s like on the “other” side
    • Don’t be afraid of making mistakes. If you are not a seasoned presentation speaker, you will inevitably stumble on some phrase that you should not have spoke about, or some topic that not all in the audience can comprehend
      • A student once commented, because most of them (students) did not have the chance to go overseas before, most of what I say would just be a “story”, they do not necessarily “feel” the impact
  • Language fluency
    • It helps a huge amount to be able to speak your audience’s native language fluently. No, I do not just mean speaking the standard form well, but to be able to spike your talk with interesting anecdotes, you must first understand their local cultural insights, which requires time to get used to.
      • i.e. tidbits between Canada & US will generally only work with North American audiences, Belgium/Netherlands generally European, Taiwanese cities (Taipei/Tainan/Kaohsiung) generally Taiwan-only
    • When one is multilingual, an average person must understand that it can be difficult (but not impossible) to attain perfect 100% fluency in each language, up to the level of local great speech talkers. Find some local examples that suit your style, i.e. I try to adopt a style that combines attributes of comedy, humour, personal experiences, etc, yet with a desire to push a message across.
    • You may find that certain (usually slang) phrases that are standard form in one part of the world can be highly offensive in another
      • I won’t list examples here, though
      • As a foreigner, you might or might not get a free pass. Make sure you ask someone trusted, why people seem to be laughing at a phrase you said that was not intended to be a joke
  • Local geography/customs
    • As an example, folks in US tend to mostly be monolingual, with the exception of folks who have friends or relatives from a foreign culture, or grew up among foreign immigrants, or people who study languages for fun, or for academic or other reasons.
      • No matter how hard you try, if someone has never tried speaking another language, they will rarely be able to understand how hard it can be. Folks for whom English is not their first language, will understand how difficult English can be
      • I’ve had some tell me they know everything about a particular language/culture just by virtue of having some parts of the family from those places, but they live across the world and have never flown across the oceans.
        • Honestly, I beg to differ. Even if I have been exposed to the culture overseas and speak the language fluently, whenever I head across the world to Hong Kong/Taiwan/Korea/Singapore, there are still many new phrases I have yet to learn, or some actions I am used to that can be awkward in those places. (e.g. giving hugs to friends of the opposite gender)
        • It is always good to learn from others
    • On the other hand, folks from US/North America/Western Europe are very much more direct than their Asian peers. If there is something going wrong, or a niggling question on their minds, they will usually never hesitate to point it out, or even just to ask a question in the middle of a lecture.
      • In Asia, people usually keep quiet when the presenter asks “Any questions?”. You often see a long queue of people asking questions after that though
        • Nobody wants to sound stupid if their question turns out to be a dumb one
        • Nobody wants to sound like a know-it-all if their question turns out to be a good one
        • Nobody wants to waste others’ time
      • The desire for conformity (groupthink) is intensely strong in Asian cultures which contrasts with individualism in Western ones
        • If things are going wrong in a company, people who are used to a Western culture are more likely to point them out sooner than those from a Eastern one. In the latter, folks do not want to be seen as “rocking the boat”, no matter whether it is sailing smoothly or about to sink
        • On the other hand, it can be difficult to make many differing opinions in a Western world agree to a compromise, whereas in the Eastern context, people agree on things usually in a hierarchical manner. Deciding on where to go to a meal together as a large group can occasionally get tricky in the former
      • People in parts of Asia are very polite (e.g. Japan), so if you inadvertently say something that is a local joke, they will just laugh behind your back, unlike Western folks generally, who might laugh right in front of you
      • Thus, Asian audiences may need more encouragement when waiting for questions. The period of time that I spend waiting after asking “Any questions?” can be arguably longer in some places than others
    • Local sensitivities
      • Don’t speak in Mandarin in Hong Kong if you know how to speak Cantonese (both with the same level of fluency and confidence)
      • Try not to unnecessarily stir up rivalries between territories unless you absolutely know what you are doing (China/Taiwan, China/Hong Kong, China/Japan, Belgium/Netherlands, US/Russia)
    • I’ve found that I cannot merely translate cultural references into another language or bring them across oceans. Examples:
      • Taipei (台北, in the north of Taiwan) folks might make fun of some of the perceptions of folks from Taichung (台中, central)/Tainan/Kaohsiung (台南/高雄 in the south), and vice versa
      • Likewise in US, in social conversations, the plural of “you” on the west coast is “you”, in Texas it’s probably “y’all”, and there are other variants in the east coast and maybe even Pittsburgh
      • Or in Canada, where the word “about” can have a different pronunciation than in the US in general
      • However, nobody in Sheung Shui (上水 in north Hong Kong/NT) will laugh at the Cantonese phrases used exclusively by people in Wong Chuk Hang (黄竹坑 in southern part of Hong Kong island) – there isn’t any difference in Cantonese because Hong Kong is smaller
        • Perhaps these folks might differ in English capabilities, but I digress
      • Likewise nobody in the east of Singapore (Tampines/Changi) will laugh at the Singaporean English (Singlish) used in the west (Jurong) or north (Woodlands) – there just isn’t any difference as Singapore is a small country
  • Appearance
    • If people don’t know you well, they are superficial and will judge you by your appearance or title
      • Of course, one’s hairstyle/dress style should not determine the content of the talk
      • And of course, one’s skin colour should not guarantee audience attention
      • If you’re listed as a “Doctor”, i.e. have a PhD, people are way more inclined to listen to what you have to say
        • Likewise if you are the head of a business or are a celebrity
      • Unfortunately, these might be what people in general, first look out for
    • Asian audiences may be more interested in a Western-looking/-sounding speaker
      • There is a tendency to worship anything/anybody foreign (崇洋)
        • Possible left-over remnants of colonialist influence
      • They are even more impressed when the foreigner speaks their native language fluently
        • So are Europeans (UK folks probably excluded)
        • In US and UK, very few people are often impressed when a foreigner speaks English on a level close to that of a native speaker
          • People always assume you speak English by default in those places
          • Thus, when someone does not understand English well, some folks try to speak slower and louder.
            • (A slower speed probably helps, but I’m not sure about increased loudness)
    • Westerners in Asia, on the other hand, almost always get charged “tourist prices”, automatic markups on costs of goods that the locals get
      • No matter how long they have been in that country, even decades
      • It can be difficult for them to fully assimilate
      • Likewise, it can be tough for them to learn local slang/creole language, e.g. Singlish – when Singaporeans have a foreigner in their group, they “automatically” switch to proper English. When he/she leaves, they context-switch back to Singlish.
  • Delivery method
    • Again, find a delivery style that suits you. Do you want to be stern or serious? Comical, able to solicit laughter yet still able to get your point across? Monotonous but concise?
      • Practice often, try different styles, and you will know which style you want to adopt
    • Presentation slides – to use or not to use?
      • Slides are very common. I’ve seen examples where they are concise (few words), lengthy (too wordy), full of pictures, comical. Adopt a style which suits you, but I’d say that having a wordy slide will result in audience attention being diverted to that of “reading the slide” instead of “listening to you”
      • Without slides, it is much more daunting and difficult. It is a little like giving a political speech, or stand-up comedy. The audience focuses on you. This is still something I’m trying to get used to, but it seems that:
        • Have some points written down or on a prompter/phone
          • You won’t have time reading entirely off it, your eyes should be focused on different parts of the audience alternately
            • A school teacher of mine used to advise staring at the clock “or an imaginary one” at the top of a lecture theatre if your nerves get in the way
        • Audience attention is entirely on you. They will be focused on your every word, every bit of silence. Thus, the pace of your speech should be suited to their level of listening speed
          • I find myself speaking English faster to Western (US/UK) folks than to people whose English is not their first language
  • And some other pointers…
    • Body/hand movements
      • Some of us, when we get nervous, we have little body motions that repeat, i.e. shifting weights constantly, or some of us don’t, i.e. stay completely motionless (except the mouth).
        • Know what you yourself are prone to doing under pressure (e.g. fidgeting), and try to avoid it on the spot. Again, knowing your content will immensely help your confidence which should minimise these movements.
      • There are times where suitable hand/body motions are necessary to convey your message, though these depend on whether you are stationary (i.e. at a podium) or whether you can walk around on a stage, with a microphone. Unfortunately, I don’t have much to advise on how to learn when to use what motions, yet.
    • Personal experiences
      • I’ve found personal anecdotes to be really useful. The audience treats anecdotes as something unique and authentic to you as a speaker. Ultimately, this something that AI cannot easily replicate yet, so if robots start teaching classes in the future, human teachers will likely still be around
    • Put yourself in the context of the audience
      • Praise their questions (no question is a bad question!), even if they sound too simple or dumb. Understand that it takes courage to ask questions in public for people who are not speaking up in their native language, or even just for people who are shy speaking up in general
    • The audience is a “mirror” for you, i.e. they can be an instant reflection of your engagement rating
      • If some are yawning/poking at a computer or phone, your topic might just be too boring, so move on! Or you might want to try another delivery style if you so desire
        • Or they just might be tired/running out of time/sitting in for the air-conditioning, so there’s nothing you can do about it
    • Wrap it up!
      • Think about your audience’s perspective as you wrap up your talk. Most of them will ask in their minds, “What’s in it for me as a _____?”
        • If it is a conference for students, then wrap up your talk explaining how this can help them in their school presentation, interviews, or even interaction with their foreign classmates
        • If it is a conference targeted at general software engineers, you could talk about how they can leverage your knowledge in their work or projects/hobbies, or open source
    • Feedback
      • I listen to recordings of myself speaking. Even as I cringe at the sound of my voice, when I realise I sound draggy on certain topics, I try to note when audiences laugh at certain successful topic deliveries, and use them again
      • Don’t be discouraged by people around you who tease. These people most likely have never given public talks, much less in multiple languages
        • They don’t know how daunting or uncomfortable it can be
        • They are likely to make up some reason for them not to do it. “Not for me/Not my cup of tea”

How about you? Do you have anything you would like to share?

Note: A big thank you to those who have supported the open source community and my interactions with them, especially Mozilla.

Note 2: Unfortunately, I don’t have much experience in South Asia (India)/Central Asia/Eastern Europe/Russia/Middle East/Africa/South America/Oceania/Antarctica, so I can’t speak for those places. It’ll be great to visit, though!

Note 3: This which started as an inside joke, I am actually thinking about whether I will eventually have enough content here to give a talk on a 3rd topic: “How to deliver an effective public speech, across languages and cultures”.

Note 4: While I’m always striving to improve, I also know that I may be not the best speaker of these topics. Please be understanding and let me know if there are parts that are just generally not good enough. English is not my first language, after all.

Note 5: You might have realised that I was trained in British English (hence the widespread use of “-ise” and “queue” vs “line”), but my speech/tone/choice of spoken words have started to shift to that of the American form. Ditto being trained in Simplified Chinese vs Traditional Chinese, which I can read.

Note 6: If you have read this far, you may have noticed that I have striven to be careful to avoid mentioning *all* people of a certain territory having a certain behaviour, but rather using words like “generally”, “might”, “probably”. Please feel free to mention if there are some pointers above that might be inaccurate.

Note 7: Don’t use it.

And on to the videos themselves:

HKOSCON 2017 – Eastern/Western cultural differences (English) Hong Kong

HKOSCON 2017 – JavaScript fuzzing in Mozilla, 2017 (English) Hong Kong

COSCUP 2017 – JavaScript Fuzzing in Mozilla, 2017 (Mandarin) Taipei, Taiwan

SITCON 2017 – Discussion on cultural differences between Easterners & Westerners (Cantonese) Hong Kong

HKOSCON 2016 – Fuzzing and Mozilla: 2015 (English) Hong Kong


Categorieën: Mozilla-nl planet

Mozilla B-Team: happy bmo push day (belated)

do, 02/11/2017 - 03:14

release tag

the following changes have been pushed to

  • [1332016] Integrate the Socorro Lens into Bug Modal
  • [1264093] Create new bug entry form for client security bugs

discuss these changes on

Categorieën: Mozilla-nl planet

Mozilla Addons Blog: November’s Featured Extensions

do, 02/11/2017 - 01:34

Firefox Logo on blue background

Pick of the Month: User-Agent Switcher (revived)

by Linder
Quickly and easily change your user-agent. There are 26 options to choose from, including iOS, Android, and most common desktop browsers.

“Very simple. Very good.”

Featured: YouTube Video and Audio Downloader

by RayLo
Extremely simple yet powerful video and audio downloader.

“This is the last YouTube downloader you will try, there is no need to continue searching.”

Featured: Mute Tab

by Kelvin_b
Mute all open tabs with a single click.

“I love that all my tabs are automatically muted, as I often click several videos at once.”

Featured: Toolbox for Google Play Store

by Android Police
Adds helpful app browsing features like APKMirror, Android Police, and Appbrain to all Google Play store pages.

“Love it.”

Nominate your favorite add-ons

Featured add-ons are selected by a community board made up of add-on developers, users, and fans. Board members change every six months. Here’s further information on AMO’s featured content policies.

If you’d like to nominate an add-on for featuring, please send it to amo-featured [at] mozilla [dot] org for the board’s consideration. We welcome you to submit your own add-on!

The post November’s Featured Extensions appeared first on Mozilla Add-ons Blog.

Categorieën: Mozilla-nl planet

Mozilla Localization (L10N): L10N Report: November Edition

wo, 01/11/2017 - 23:47

Please note some of the information provided in this report may be subject to change as we are sometimes sharing information about projects that are still in early stages and are not final yet.


New localizers

  • Ian has just joined us to help localize Firefox for Android in Swahili! Welcome Ian!
  • The Italian team has a couple of new translators in training: sav22999 (Saverio) and gens (Gennaro). In the past few weeks they have been translating strings across several Mozilla projects, from software to and other web properties. Welcome to the group!

Are you a locale leader and want us to include new members in our upcoming reports? Contact us!

New community/locales added
  • The Swahili l10n team is kicking things off again after a moment of hiatus. We’re happy you are back!
  • The Occitan team is also back after a moment of pause. They’ve successfully translated Firefox for Android and are almost done with Firefox! Congrats!
  • Sardinian (sc) is starting to localize Firefox in Pontoon.
New content and projects What’s new or coming up in Firefox desktop

Today was the deadline to ship localization updates in Firefox Quantum (57). All translations added from now on in Pontoon will be shipping in Firefox 58.

Last week we made Form Autofill available for localization as part of the Firefox project on Pontoon. Currently it consists of 66 strings, and testing instructions are available in this document.

Talking about testing Firefox Desktop, take a look at the new QA view in Transvision to check keyboard shortcuts.

What’s new or coming up in Test Pilot

A lot of obsolete strings (65) have been finally removed from the Test Pilot website. This should make it easier for new locales that want to pick up this project for localization.

What’s new or coming up in mobile

As for desktop, today was the last day to get in your strings to ship localization updates in v57. All translations added from now on in Pontoon will be shipping in Firefox Android 58.

Firefox iOS v10 l10n deadline is today as well, both for localizing and testing your work. Friendly reminder that St3fan is from now on generating daily screenshots, which means once you’ve translated in Pontoon, you can check your work on the screenshots the next day! Come check them out here:

This is a truly useful feature that you should take advantage of, especially if you don’t have an iOS device to check your work on. A big thanks to St3fan for automating these daily and improving the general experience of testing!

Sneak peak: many cool new features are coming up with this v10! Amongst other things, the Firefox team has been focusing on Photon, New Tab and iOS 11 compatibility with iPhone X, Face ID, and drag and drop support for iPad.

If you want to try out the v10 Beta, it has been available since Friday Oct 27. Sign-up here:

Don’t be shy: file bugs, suggest features, and help make Firefox iOS overall one of the best mobile browsers out there!

Focus Android and iOS are currently in the testing phase for Granite version (l10n deadline for testing and screens is next Tues, Nov 7th). The screenshots are updated for both, please let us know if you have any questions or concerns:

And as usual, don’t be shy and file any bugs if you find issues, or request feature improvements if you have any! If you want to be added to the test builds, you can reach out to Delphine. Also, Focus for Android is available as a beta on the Play Store here.

What’s new or coming up in web projects

There are quite a few updates and new pages added to on a weekly basis for more than a month. This surge of change and new content should subside as we are closer to launch date. Thanks to you all for your timely responses and questions.

The new Firefox landing page comes in two versions. The longer version, which is in the form of CEO’s letter, will be available in 12 locales. For those who are impacted by the late decision and timing of the finalized content, thanks to your dedication to address these localization requests at this late stage before a major launch.

For Mobile, we have locale specific requests for id (Firefox Rocket) and zh-TW. A new type of project called Mobile Contextual Hints create challenges for the select locales, as localizers must find creative ways to fit localized content in a tight space.

For the monthly email request from marketing team, we are making progress in convincing the team to move the project to Pontoon and communication through bugzilla, instead of individual emails.

What’s new or coming up in Foundation projects

The IoT survey results have been published! It will be promoted via various channel in the next days, but you can be amongst the first people to read it here. It’s great to see the diversity of respondents being represented in the report. And if you speak Spanish, in addition to our localized blog post, Univision published an article as well.

Also keep in mind that we’ve started ramping up our traditional fundraising campaign, now is a good time to complete the website translations and make sure everything looks good on the website. You might see a few edits to the website as we might try new experiments or land small improvements, or a few snippets to translate, but it shouldn’t be a lot of content. The main content that has yet to come is the fundraising emails (about 4 of them), they should all be ready mid-November and will target French, German, Spanish and Brazilian Portuguese in December. Stay tuned!

In terms of timing, the campaign will be quiet for the second half of November, to leave all the space to Quantum, then will ramp up again from the end of November and until December 31st.

  • Berlin Community meet-up: l10n has been invited to a cross-functional meeting from Nov 18-19, at the Mozilla Berlin office. The purpose of this meeting is to kick-off a conversation about volunteer leadership structures at Mozilla from the teams who are most connected to what we call “Non-Coding Enthusiasts”
  • Our last l10n hackathon this year is happening in Kolkata and on that same weekend:
  • Want to showcase an event coming up that your community is participating in? Reach out to any l10n-driver and we’ll include that (see links to emails at the bottom of this report)

We are still looking for an l10n intern next summer (“Community Localization Analyst”). You can apply here:

Friends of the Lion

Image by Elio Qoshi

  • Kudos to Sara and Sandro for doing a great job in organizing the work of new volunteers in the Italian community.
  • A huge thanks to Reza who has taken on the task of producing Focus for Android screenshots on a regular basis, so that the entire l10n community can check their work. It’s a hard and time-consuming task – so from the L10n and mobile teams: thank you Reza!

Know someone in your l10n community who’s been doing a great job and should appear here? Contact on of the l10n-drivers and we’ll make sure they get a shout-out (see list at the bottom)!

Sad News

It is with great sadness that we are announcing that our Fulah localizer and friend Mamadou Niang has passed away last week. He will be missed and we’ll have more to share about this tragic matter in a subsequent blog post.

Useful Links Questions? Want to get involved?

Did you enjoy reading this report? Let us know how we can improve by reaching out to any one of the l10n-drivers listed above.

Categorieën: Mozilla-nl planet

Air Mozilla: Bugzilla Project Meeting, 01 Nov 2017

wo, 01/11/2017 - 22:00

Bugzilla Project Meeting The Bugzilla Project Developers meeting.

Categorieën: Mozilla-nl planet

Georg Fritzsche: Data preference changes in Firefox 58

wo, 01/11/2017 - 21:29

As part of the Photon UI refresh, the Firefox data preferences were streamlined. Where previously for historic reasons we had two controls, we now have one.

<figcaption>How the new Firefox data preferences look.</figcaption>

There are two notable changes here to previous versions:

  • There is only one control now for Firefox data submission.
  • There is a new control for SHIELD studies, which i won’t detail here.

As detailed in another post, this doesn’t change anything about the type of data being collected while it makes the data controls less confusing. However, it does have some technical consequences for Telemetry that we landed in Firefox 58.

What does this mean for Telemetry?

Previously we had two different sets of data we collected:

  • “opt-out” or “base” Telemetry: This was on by default on all Firefox channels.
  • “opt-in” or “extended” Telemetry: This was off by default on Firefox release and on by default on prerelease channels. Turning off “opt-out” Telemetry also turned this off.

Now the behavior is more streamlined:

  • There is just one control for data upload for Firefox, which is on by default.
  • Individual measurements are now collected from either all users or prerelease users.

So for Firefox we now just differentiate between “release data” and “prerelease data”. (For some specific features or studies there may still be explicit opt-in notifications, but this covers all standard Firefox data collection.)

While this has broader technical impact on Firefox data collection, the changes we landed should make this work mostly seamless.

What does this mean for me?

For Firefox users, there is no significant change; the data upload setting users chose is respected as before. The opt-in for additional Telemetry data went away; instead we always collect less data on Firefox release.

For most Firefox development, nothing should change. Telemetry takes care of doing the right thing for histograms, scalars & events internally.

Local builds from current mozilla-central should default to recording all the prerelease data but not upload it, without any extra build flags. about:telemetry allows you to confirm that.

For testing locally how release Telemetry behaves, there is a hidden pref: toolkit.telemetry.testing.overridePreRelease.

For Fennec development, nothing changed. Fennec still has the same Telemetry behavior and preference handling as before.

For writing Firefox tests, nsITelemetry.canRecordExtended can be used to check whether prerelease data is recorded. The pref toolkit.telemetry.testing.overridePreRelease can be used for tests that need to enable prerelease behavior.

For QAing Firefox data collection, you might need to override the prerelease status using the pref toolkit.telemetry.testing.overridePreRelease. The prerelease and sending status can be checked in about:telemetry.

If you are looking at Telemetry data, there are some changes. In Firefox 58, we will not receive the “extended” data from release anymore. This directly affects some parts of that provided release data from that small “opt-in” population:

  • the distribution and evolution dashboards will soon not show release data anymore.
  • telemetry.js and the aggregates service will not provide release data when 58 is released.

If you will be affected by these changes and need alternatives, please reach out to us.

The new Telemetry behavior

Here is an overview of how the important Telemetry controls now behave for Firefox Desktop.

Currently the naming of these various controls is inconsistent and confusing. While we focused on the minimal required changes first, we will clean this up in the near future. Updating the Telemetry documentation to match the new behaviors is on-going.

First, there are the main Firefox Telemetry preferences:

datareporting.healthreport.uploadEnabled: This is our main preference that controls whether Firefox can send data and follows the user choice. It didn’t see any change in behavior from these changes.

toolkit.telemetry.enabled: This preference is now locked to reflect prerelease or release builds (true and false respectively).

This previously matched the additional data control and controlled the “extended” Telemetry collection. It is also used in other places to control collecting additional data.

More data controls are on the nsITelemetry interface:

nsITelemetry.canRecordBase: This is generally true and reflects whether any Telemetry data can be recorded. Most code should never need this.

nsITelemetry.canRecordExtended: This reflects if Firefox is on a prerelease or release builds (true and false respectively).

There is also the releaseChannelCollection property in Histograms.json, Scalars.yaml & Events.yaml. These properties keep working seamlessly, with no action required. They now follow the prerelease status of the above settings.

Reaching out
  • If you have any questions reach out to :gfritzsche, :chutten, :dexter, :frank or the team.
  • For any specific issues, please file a bug. We are using bug 1406390 for tracking.

Data preference changes in Firefox 58 was originally published in Georg Fritzsche on Medium, where people are continuing the conversation by highlighting and responding to this story.

Categorieën: Mozilla-nl planet

Joel Maher: Keeping an eye on Performance alerts

wo, 01/11/2017 - 21:17

Over the last 6 months there has been a deep focus on performance in order to release Firefox 57. Hundreds of developers sought out performance improvements and after thousands of small adjustments we see massive improvements.

Last week I introduced Ionut who has come in as a Performance Sheriff.  What do we do on a regular basis when it comes to monitoring performance.  In the past I focused on Talos and how many bugs per release we found, fixed, and closed.  While that is fun and interesting, we have expanded the scope of sheriffing.

Currently we have many frameworks:

  • Talos (old fashioned perf testing, in-tree, per commit, all desktop platforms- startup, benchmarks, pageload)
  • build_metrics (compile time, installer size, sccache hit rate, num_constructors, etc.)
  • AWSY (are we slim yet, now in-tree, per commit, measuring memory during heavy pageload activity)
  • Autophone (android fennec startup + talos tests, running on 4 different phones, per commit)
  • Platform Microbenchmarks (developer written GTEST (cpp code), mostly graphics and stylo specific)

We continue to refine benchmarks and tests on each of these frameworks to ensure we are running on relevant configurations, measuring the right things, and not duplicating data unnecessarily.

Looking at the list of frameworks, we collect 1127 unique data points and alert on them with included bugs for anything sustained and valid.  While the number of unique metrics can change, here are the current number of metrics we track:

Framework Total Metrics Talos 624 Autophone 19 Build Metrics 172 AWSY 83 Platform Microbenchmarks 229 1127

While we generate these metrics for every commit (or every few commits for load reasons), what happens is we detect a regression and generate an alert.  In fact we have a sizable number of alerts in the last 6 weeks:

Framework Total Alerts Talos 429 Autophone 77 Build Metrics 264 AWSY 85 Platform Microbenchmarks 227 1082

Alerts are not really what we file bugs on, instead we have an alert summary when can (and typically) does contain a set of alerts.  Here is the total number of alert summaries (i.e. what a sheriff will look at):

Framework Total Summaries Talos 172 Autophone 54 Build Metrics 79 AWSY 29 Platform Microbenchmarks 136 470

These alert summaries are then mapped into bugs (or downstream alerts to where the alerts started).  Here is a breakdown of the bugs we have:

Framework Total Bugs Talos 41 Autophone 3 Build Metrics 17 AWSY 6 Platform Microbenchmarks 6 73

This indicates there are 73 bugs associated with Performance Summaries . What is deceptive here is many of those bugs are ‘improvements’ and not ‘regressions’.  If you figured it out, we do associate improvements with bugs and try to comment in the bugs to let you know of the impact your code has on a [set of] metric[s].

Framework Total Bugs Talos 23 Autophone 3 Build Metrics 14 AWSY 4 Platform Microbenchmarks 3 47

This is a much smaller number of bugs- now there are a few quirks here-

  • some regressions show up across multiple frameworks (reduces to 43 total)
  • some bugs that are ‘downstream’ are marked against the root cause instead of just being downstream.  Often this happens when we are sheriffing bugs and a downstream alert shows up a couple days later.

Over the last few releases here are the tracking bugs:

Note that Firefox 58 has 28 bugs associated with it, but we have 43 bugs from the above query.  Some of those bugs from the above query are related to Firefox 57, and some are starred against a duplicate bug or a root cause bug instead of the regression bug.

I hope you find this data useful and informative towards understanding what goes on with all the performance data.

Categorieën: Mozilla-nl planet

Air Mozilla: The Joy of Coding - Episode 118

wo, 01/11/2017 - 18:00

The Joy of Coding - Episode 118 mconley livehacks on real Firefox bugs while thinking aloud.

Categorieën: Mozilla-nl planet

Mozilla Reps Community: Resources Reps, what’s next?

wo, 01/11/2017 - 17:52


In the previous blog post, I wrote about the learnings that we got from the initial training session. And last Friday, we just announced the new graduates from the final phase of Resources Rep training. The assessment was made during the 3 weeks of the training (whether group or individual exercises) that started on the 2nd of October until 21st of October 2017. You can also see the full list of the Rep Resources graduates in the Reps portal. But I would like to quickly take you back on the initial purpose of Resources Reps.

What is a Resources Rep?

The idea behind the Resources Reps  is to have specialized Reps who are trained to help communities and other fellow Reps to plan strategically how they use the resources that the Reps program offers. This will ensures that resources of the program are used in the most impactful way and according to the guidance provided by Mozilla’s strategy and the Council.

When did the training happened?

The training sessions happened in 3 phases. The first one, which was the trial training, happened during 24th of July – 12th of August 2017. We asked  6 Reps to participate on this trial session to help us improve the training. After the trial training, we then opened the application for the rest of the Reps and decided to carry on with the first phase of the training with the India applicants during 11th of September – 1st of October. Finally, the last phase happened on the 2nd of October – 21st of October.

During the 3 weeks of the training, the candidates were asked to go through the training material and complete the quiz every  week. And in the end of each week (we decided to have the meeting on the weekend), we scheduled a video meeting for an hour in order to have work and discuss on the subject together.

What did we learn from the overall training?

On the trial training, the participants helped  a lot in terms of improving the content of the training. Thanks to them, now we have the receipt guideline to help the Rep identify which receipts are acceptable and which are not.

On the first phase of the training with Reps from India, we were experimenting with a new video conference tool, which surprisingly performed so much better than the tool that we usually use.

And on the second phase, I learned a lot about accessibility issues. Since we need to accommodate so many time zones, I decided to break the meeting into 2 sessions in each weekend. The first session is for the Asia, Europe, and Africa, and the other session is for the Pacific people who lived in North or South America.

The first meeting was rather challenging since we had people with problems on communication (more specifically a deaf participant and a person that was not able to follow up in English). This came to me as a shock, because that was something I was not prepared for. But fortunately, with some love of the local community, we were able to have an effective meeting. It’s super amazing to see how people were willing to help each other in the training. It was also a reminder for me to think about accessibility in advance for our future activities. For example like providing dial in details for a meeting could be so much beneficial for some people who don’t have access to a PC and can only join via phone. Or checking on the participants before the meeting in case there’s somebody who need special support. Because if we want to excel on diversity and inclusion, then we need to take further action to accommodate everyone.

How can I apply to be a Resources Rep?

For now we’re in the process of evaluating our current graduates. So in the meantime, we are not accepting more applications. But there’s a possibility we will reopen the application in the future. We’ll let you know for sure.

What’s next?

New Reps that  don’t have access to the budget and swag, can now ask for help from these Resources Rep. We will no longer need to assign the bug to the mentor if the request was made by a Resources Rep. And instead it will go directly to the review team. And ideally, the new Reps should choose Resources Rep who’s close to their region. So, for example if I’m a new Rep from the US, I will ask for help from Jason who in this case is the Resources Rep who live the closest to me. You can also see the group on the reps portal.

We’re also going to reshuffle the Review Team members in the near future. The Review Team is now discussing the recommendation list from the current Resources Rep to be sent to the council for the future candidates of the Review team. We’ll keep you updated for the process.

I also would like to thank the participants of the Resources Rep training. And especially for those who always make the time on their weekend to join the meeting in each week. Congratulations!

Categorieën: Mozilla-nl planet

Air Mozilla: Weekly SUMO Community Meeting November 1, 2017

wo, 01/11/2017 - 17:00

Weekly SUMO Community Meeting November 1, 2017 This is the SUMO weekly call

Categorieën: Mozilla-nl planet

The Mozilla Blog: 10 Fascinating Things We Learned When We Asked The World ‘How Connected Are You?’

wo, 01/11/2017 - 14:21

In August, Mozilla sent out a survey asking “How connected are you?

We inquired about people’s relationships with their connected devices, like smart TVs, Fitbits, and routers. Questions ranged from “What connected devices do you own? to “What is your biggest fear as we move toward a more connected future?”

Nearly 190,000 people around the world responded. People from the tiny islands of Tuvalu to the huge landmass of China and everywhere in between. (Mozilla released the survey in six languages: English, Spanish, German, Italian, French, and Portuguese.)

What we learned is fascinating. Like: People in India are more likely to own a smart appliance, whereas people in Argentina are more likely to own a smart TV. And: People everywhere are worried that a more connected future will jeopardize their privacy.

Below, read 10 fascinating things we learned. In the coming months, Mozilla will use these findings to help guide our advocacy and public education work around internet health.

#1: The world is pretty evenly divided between fear and optimism for a more connected future
The more tech savvy people are, the more optimistic they feel about a connected future. People who identified as the least tech savvy are most likely to be “scared as hell” about our more connected future—31% compared to the overall average of just 7%.

Respondents in India were the most optimistic about the connected future, with 25% being “super excited,” compared to the overall average of 7%. Mexico and Brazil also stood out as generally more optimistic countries. On the other hand, people in Belgium, France, the UK, Switzerland, and the U.S. expressed fear about the world becoming more connected.

#2: Everywhere in the world people are afraid of losing their privacy
When asked what they most fear about a more connected future, people overwhelmingly responded with loss of privacy (45%). All top responding countries pointed to the loss of privacy as their main concern, with the exception of Italy, which saw loss of connections with other people as their main concern.

The more tech savvy a respondent was, the more he or she was concerned about the loss of privacy. 33% of the least tech savvy group identified loss of privacy as their top concern—the number rose to 41% for average users, 48% for the savvy users, and 54% for the ultra tech savvy. Conversely, losing touch with one another was the highest concern for the least tech savvy respondents.

#3: The language of the connected future isn’t yet well known
Fewer than 30% of respondents said they could explain IoT (Internet of Things), botnets, blockchain, RFID, or Zero Day Vulnerability to a friend. Fewer than 40% of respondents said they could explain DDOS attacks or TOR. The only two things more than half of the respondents said they could explain to a friend were VPN (Virtual Private Network) and connected devices.

#4:  The smartphone vs laptop divide is real
In the United States, Canada, and the United Kingdom, more users reported owning a laptop than a smartphone. In most countries outside of North America and the UK—including Brazil, India, Argentina, Mexico, Italy, and Spain—more people reported owning a smartphone than a laptop. People who identified as the least technically savvy were more likely to own a laptop than a smartphone.

#5: When it comes to connected products, people around the world have different tastes
Respondents from Argentina, Brazil, and Mexico own smart TVs at the highest rate—50% reported owning one compared to the worldwide average of 40%. U.S. respondents reported the highest ownership of fitness trackers (20%), smart cars (15%), and connected thermostats (8%). Respondents from India and Brazil reported the highest ownership of smart appliances—15% compared to the worldwide average of 7%.

#6: People are divided over who is responsible for making connected devices private and secure
One-third of respondents believe the makers of connected products are responsible for building privacy and security into their devices. One-third believe it’s up to individuals to protect themselves online. The remaining third of respondents were divided between believing the government was responsible for online privacy and security and just not knowing who should be responsible.

#7: People aren’t sure who to trust to help them be secure online
Most respondents—40%—trust non-profit organizations the most to help them protect themselves online. The more technically savvy that people viewed themselves, the more they trusted nonprofits. On the flip side, 27% of people reported they just don’t know who to trust. That number jumps to 45% among people who identified as the least technically savvy. Almost nobody said they trusted the media (3%) or the government (2%) to help protect them online.

#8: People don’t seem all that excited about the world getting more connected
The top response to the question “What are you most excited about as we move toward a more digitally connected future?” was None of the Above (27%). People in Canada, France, the UK, and U.S. saw the least amount of benefits to a more connected future.

People who are excited about a connected future are looking forward to how much easier it will make life (26.7%). Brazilian respondents stood out as the most excited about how easy life will be—44% selected it as the top benefit. In India, educational benefits of the connected future were what got respondents most excited (32%).

#9: Privacy and security aren’t top concerns for people shopping for connected products
Nearly all people ranked price, features, and reliability as the top three things they consider when buying a new connected device, regardless of country or level of tech savviness. Security and privacy were ranked next. Overall, people reported friend or family recommendations and user reviews as the things they considered least when buying a new connected device.

#10: People all around the world like to take surveys

189,770 people responded to our survey. People from Andorra to Zambia and everywhere in between. The most responses came from France (18%), Italy (15%), Germany (13%), the United States (11%), and Brazil (7%).

At Mozilla, we believe in making data open and accessible to everyone.  If you would like to go deeper into this survey data, here are links to dig in:

  1. Raw survey data (.csv file, 105 mb)
  2. Top Line Results (.pdf)
  3. Top Line Results by Country (.pdf)
  4. Top Line Results by How Technically Savvy People Identified (.pdf)

Mozilla is making this data available under a CC BY 4.0 license.

Jen Caltrider is the Content Strategy Lead at the Mozilla Foundation

The post 10 Fascinating Things We Learned When We Asked The World ‘How Connected Are You?’ appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

The Mozilla Blog: $275K for Creative Gigabit Projects Across the U.S.

wo, 01/11/2017 - 13:00
From augmented reality training for first responders, to robotics classes for high school students, Mozilla is supporting bright ideas that leverage gigabit internet to create more open and innovative cities


Today, Mozilla is announcing $275,000 to support creative, educational technology projects across the U.S.

Mozilla is partnering with museums, universities, nonprofits, libraries, and high schools in Texas, Louisiana, Kansas, and beyond.

“We’re focusing on projects that leverage gigabit internet speeds — up to 250x average speeds — to make a positive impact in the communities we serve and across the country,” says Lindsey Frost, who directs Mozilla’s gigabit work. “Projects use augmented reality to train first responders; raise awareness about coastal erosion through virtual reality simulations; bring robotics into high school classrooms; and much more.”

Through the Mozilla Gigabit Community Fund — a partnership with the National Science Foundation and U.S. Ignite — Mozilla invests in projects that leverage lightning-fast gigabit internet connectivity to further education and workforce development.

“The gigabit projects we fund are built and piloted by community members to address real challenges in education and workforce development in their cities,” Frost explains. “It’s all part of our mission to build a healthy internet that fuels a more open, equitable, and inclusive society.”

The projects

The Mozilla Community Gigabit Fund provides funding to technologists, educators, and entrepreneurs in five gigabit cities: Austin, TX; Chattanooga, TN; Eugene, OR; Kansas City; and Lafayette, LA. Funding supports pilots of gigabit technologies in individual cities, but also efforts to scale pilots to all five communities.

Our 18 latest grantees receive funds ranging from $5,000 to $28,000. Grantees are:

PerSim Training Simulation for First Responders | Austin, TX. PerSim provides affordable, portable, and realistic AR training simulations to paramedics. Led by MedCognition.

Latinitas VR Cinema Chica | Austin, TX. Twenty Latina girls ages 10 and older will work with an experienced VR filmmaker to create short documentaries about Austin’s East Side. Films will be featured at the Cine Las Americas International Film Festival in May 2018. Led by Latinitas.

Dove Springs Coding Academy-GO! Future VR Project | Austin, TX. This project provides 40 low-income youth with coding lessons through a VR curriculum. Students will present their learnings at a VR College & Career Fair. Led by River City Youth Foundation.

Cine Joven Breaking Borders Project | Austin, TX. This project allows students from Austin, Texas and Monterrey, Mexico to co-create a 4K short film over high-bandwidth internet. The final film will be screened in Monterrey before a live audience. Led by Motion Media Arts Center.

Virtual Storytelling Curriculum | Austin, TX. This project introduces students to careers in technology, and hones their storytelling skills, by having them catalogue local historic landmarks using 360-degree video and VR. Led by E4 Youth.

Gigabit Technology and the Arts in Creative Action After School | Austin, TX. Technology meets art in this project, as educators and artists integrate VR headsets, 360-degree video, and a variety of applications into theater classes, art classes, and mural making. Led by Creative Action.

VR Field Trip to the USA | Austin, TX, Chattanooga, TN & Kansas City. This project uses 360-degree 4K video to connect local classrooms with others around the world. Students will act as cultural ambassadors for their city, remotely introducing international students to Austin, Kansas City, and Chattanooga. Led by PenPal Schools.

CERN + Gigabit Challenge | Austin, TX & Kansas City. This project connects critical research taking place at CERN with classrooms in Kansas City and Austin. Students can view physics calculations and research in real-time. Led by KC Metropolitan.

Networking the Classroom of the Future | Chattanooga, TN & Lafayette, LA. The Classroom of the Future pairs 4K microscopes and video streaming with local aquariums and science museums. It brings hands-on science and technology education directly into local classrooms. Led by the Enterprise Center.

City Synth | Eugene, OR. City Synth will work with engineers, technologists, and students from the South Eugene Robotics Team to transform the city of Eugene into a musical instrument. A series of interactive mixed-media installations will remix audio and video. Led by Integrated Arts.

Gigabit Residencies | Eugene, OR. This project provides residencies that will teach 200 students graphic design, audio engineering, and other skills by leveraging lightning-fast gigabit internet. The project also entails web-based professional development for teachers. Led by Lane Arts Council.

NEDCO | Springfield, OR. With this grant, low-income youth will have access to a mobile, interactive classroom that expands their horizons beyond the city of Springfield. The project entails high-quality interactive learning experiences and counseling opportunities. Led by NEDCO.

Redefining Women in Tech Interactive Video Learning Events | Eugene, OR. Redefining Women in Tech uses interactive 4K video alongside face-to-face meetings to help women navigate the often inequitable tech sector. This project will include job resource training, professional development opportunities, and community organizing to promote a more equitable industry. Led by Redefining Women in Tech.

Coder in Residence | Eugene, OR & Kansas City. The Coder in Residence program puts gigabots — gigabit-internet enabled robots — in elementary school classrooms. It provides robotics curriculum to students, and robotics curriculum professional development for educators. Led by Lane STEM.

Coastal Erosion VR | Lafayette, LA. The Lafayette Science Museum will develop “Coastal Quest,” a VR game that allows visitors to explore coastal erosion in Louisiana and select coastal defenses that slow or mitigate erosion. Led by Lafayette Science Museum.

Tiny House VR Project | Lafayette, LA. Students at David Thibodaux STEM Magnet Academy will create, design, test and demonstrate a VR walkthrough of the “Atomic Agora Tiny House.” This tiny house will be donated by Habitat for Humanity to families transitioning from shelters or displacement to permanent homes. Led by David Thibodaux STEM Magnet Academy.

Career readiness & 4K project | Lafayette, LA. High school students will participate virtually in a college level course via a 4K video stream. The project aims to increase college awareness and attainment rates for students, and develop a potentially scalable model. Led by University of Louisiana at Lafayette (ULL).

Kvasir-VR | Lafayette, LA . UL-Lafayette and David Thibodaux STEM academy will pilot an immersive VR field trip experience that allows educators and experts to guide and assess students through the Cleco Alternative Energy Center in Crowley, Louisiana. Led by University of Louisiana at Lafayette (ULL).

About the fund

The Mozilla Gigabit Community Fund provides grants and on-the-ground-staff to support projects that leverage gigabit internet to create more connected, open, and innovative U.S. cities. The Fund has granted more than $800,000 to over 60 projects during its four-year history.

The Fund is run in partnership with the National Science Foundation and U.S. Ignite.

Fund grantees can be individuals, nonprofits, and for-profits.

Fund cities are selected based on a range of criteria, including a widely deployed high-speed fiber network; a developing conversation about digital literacy, access, and innovation; a critical mass of community anchor organizations, including arts and educational groups; an evolving entrepreneurial community; and opportunities to engage K-12 school systems.

Past projects

The Mozilla Gigabit Community Fund has a diverse roster of grantees. Below, learn about just one: My Brother’s Keeper Coding Maker Space, which teaches young men of color web VR in Austin, Texas. View other gigabit grantees here.

The post $275K for Creative Gigabit Projects Across the U.S. appeared first on The Mozilla Blog.

Categorieën: Mozilla-nl planet

Emily Dunham: Better remote teaming with distributed standups

wo, 01/11/2017 - 08:00
Better remote teaming with distributed standups

Agile development’s artifact of the daily stand-up meeting is a great idea. In theory, the whole team should stand together (sitting or eating makes meetings take too long) for about 5 minutes every morning. Each person should comment on:

  • What they did since yesterday
  • What they plan on doing today
  • Any blockers, thigns they’re waiting on to be able to get work done
  • Anything else

And then, 5 minutes later, everybody gets back to work. But do they really?

Problems with in-person standups

When I’ve participated in stand-up meetings in person, I’ve noticed a few major flaws:

  • Context switching into and out of the meeting impacts a maker’s schedule by substantially more than the meeting’s planned 5 minutes.
  • People naturally tend to problem-solve during the meeting, and overcoming this urge to be helpful can be difficult and frustrating. However, allowing this problem-solving is a waste of most attendees’ time and can drag the meeting out to over an hour if left unchecked.
  • The content of the meeting isn’t recorded. If I run into an issue that I think I recall Jane saying she was blocked on last week, I can either interrupt her work to ask her about it, send her an email and wait for her to reply, or just fight it myself. I can’t look it up anywhere.
  • If a team decides to keep notes, this “office housework may be distributed inequitably among team members. Or if everyone takes turns taking notes, well... not everyone is necessarily skilled at note-taking, so there’s little guarantee that the notes will be consistently useful.

When an international team decides to pursue standup meetings through a synchronous medium like a phone or video call, it keeps all of these drawbacks while adding the problem of time zones. Let’s say your San Francisco-based company holds your daily standup at the perfectly sensible hour of 10am. Colleagues in New York City may love this, as it’s 1pm their time so they have plenty of time to prepare for the meeting. But your “perfectly reasonable” 10am standup isn’t so reasonable internationally: it’s 5pm for a colleague in London, 6pm in Paris, 6am the next day in Auckland, and sleep-worthy hours like 4AM the next day in Sydney and 2am, also the next day, in Tokyo.

Is demanding that some team members stay late at the office every day at the expense of family and personal commitments, or wake up before sunrise, the way that you want to treat your team? Is making a request like this, which disproportionately impacts your international colleagues, consistent with your values?

The better way: Robots!

If you’re familiar with my talks about community automation, you won’t be surprised at my excitement to share another robot which makes life better.

A team I’m on has recently started using a Slack app called Geekbot to perform asynchronous, inherently logged, on-task standup meetings. The only thing special about Geekbot is that somebody else has already done the coding, testing, and debugging – if your team uses IRC or another chat client, the basic “ask questions of each team member and post their answers, once per day” functionality is trivial to implement on any extensible platform.

These distributed, asynchronous standups are the best standup meetings I’ve ever participated in. Why?

  • They stay on task. You answer specific questions to the robot in PM, the robot posts your answers to a channel, and anyone who wants to chat about what you said has to do so outside the main thread of that conversation.
  • They’re asynchronous. If we added colleagues in any time zone, they could configure the bot to ping them at a time they find convenient, and the rest of the team could still keep up with their progress as long as everyone keeps reporting roughly every 24 hours.
  • Others’ updates minimize interruption. Rather than dropping what I’m doing to take a call for a meeting, I can use my ordinary chat-multitasking skills to read my colleagues’ updates while waiting on another task to complete.
  • They’re self-recording. I can look back after lunch and see what I claimed I’d get done today; I can search my chat logs for “who was working on that component?”. I strongly prefer to answer easy questions like this myself instead of interrupting others – I save that for the difficult, interesting questions – so I deeply appreciate this ability to solve my own problems with the meeting’s inherently perfect notes.

Basically, these robot-powered, distributed standup check-ins are showing all of the benefits, and none of the major drawbacks, of in-person standup meetings.

The catch: Culture

Why is it working? We’ve had similar standup type platforms before, and they work poorly if at all. I believe these standups are working better than prior attempts to automate the process for 2 main reasons:

  • The standups are performed in a convenient location. Rather than having to remember to log into some service which exists only for the standup, it comes to you in the chat medium where you were doing the rest of your team communication.
  • The team’s culture values filling them out. If someone skips a standup, others will ask them where they were or what was going on. If you added a bot without adding a culture of appreciating standups, everyone would simply ignore or block the bot and nothing would change.

So, assess how your standups are working. Do they take your target amount of time and stay focused? Can you refer to their contents later as you need to? If they could use improvement, it’s worth investigating how a robot could help you out.

Categorieën: Mozilla-nl planet