Planet Mozilla Projects

WoMoz: [Project Update] An Accessible Web – Special Program

mermi — Thu, 23 May 2013 18:49:17 +0000

For prior updates on my project, please see here and here

After a long time spent working with the students on web technologies and Mozilla projects, it’s time to organize a final event to celebrate the work accomplished.

This will take up a day during which each group will present the work they have been doing over the past few months. Additionally there is a competitive element between the presenting groups.

As well as developing their knowledge of webmaker project and technologies, they were able to create a webpage where they knew the whole structure of an HTML document.

Here are some examples of their work:

It should be noted that before working on the computer, we do a lot of work on paper. This allows for better and quicker uptake of things. Once that is done, we spend time on examples. The start of each class was spent on reviewing the previous classes.The less able students perhaps had some additional difficulties when they had to memorise things. The use of simple examples does not in anyway detract from their hard work.

The final session will be on May 30th 2013. It’s a friendly competition for people who were on the course. The topic is Mother’s Day (similar to to the thimble project called “Happy Mom’s Day”)

I’ll use this model and change the css and content a bit. It’ll then be up to the students to fill the HTML content.

You’ll find the details of the day here, feel free to add any suggestions

SUMO Blog: It’s Thursday, it’s SUMO Day!

Madalina — Thu, 23 May 2013 15:03:21 +0000

A new SUMO day is here!

Every other Thursday we’re organizing a SUMO day where we try to answer all the questions coming on the support forum. This Thursday, May 23rd is a new SUMO day!
We’ll be answering questions in the support forum and helping each other in #sumo on IRC from 9am to 5pm PST (UTC -8).

Join us, create an account and then take some time today to help with unanswered questions. Additional tips for getting started are on the etherpad. Our goal is to respond to every new question posted Thursday, so please try to answer as many questions as you can throughout the day.

Last time, we managed to reach 91% of questions answered! Can we reach 100% ?

Do not forget:

Happy SUMO Day!

QMO: Bug Verification Day – every Monday

Manuela Muntean — Thu, 23 May 2013 07:35:14 +0000

Greetings Firefox friends,

Every Monday we are holding our weekly Bug Verification Day and we would like to invite you to join us. We are happy to let you know that we use the #testday channel now, and not #qa as before.

There is no need for experience with verifying bugs. Feel free to ask any question on the #testday channel and someone will be there to offer you guidance. More details are available in the new etherpad we set up for you.

If you want to get involved, but you’re unable to join these meetings, you can verify bugs on your own time and add them to the new provided etherpad.

Many thanks to Tiziana, mga, MarioMi, Tom (:Tad) , Mitzabmm , and to everyone else participating!

Best regards! See you every Monday!

When: May 27, 2013.

QMO: Unconfirmed Bugs Triage Day – every Tuesday

Manuela Muntean — Thu, 23 May 2013 07:25:02 +0000

Greetings Mozilla contributors!

Every Tuesday we are holding our weekly Unconfirmed Bugs Triage day. The event is held on the #testday irc channel (instead of #qa) and is addressed to all of you willing to contribute in making Firefox better.

You can find information in the etherpad. You don’t need to have any previous testing experience. Feel free to ask your questions on #testday. Someone will be available to offer you guidance.

If you’re unable to attend these meetings and still want to get involved, you can triage bugs on your own time and just add them to the etherpad.

Many thanks to Aleksej, lizzard, mga, Aish, Mitzabmm, Johan, Phoenix, edwardb, MarioMi, and to everyone else participating!

Best regards! See you every Tuesday!

When: May 28, 2013.

Firefox Flicks: Firefox Flicks 2013 Staff Pick - Lizz

Thu, 23 May 2013 03:26:16 +0000

The Flicks team gets to see every entry that comes in for the contest. While there’s still a few months left in the contest we thought we’d share some of our favorites. Being featured as a staff pick has no bearing on the Firefox Flicks voting process. It’s just Flicks we’ve seen come in that we think are really interesting and wanted to share them with Flicks fans. We hope you find them inspiring.

“Hey Flicksters, I’m Lizz, part of the Firefox Flicks team. I write for the Flicks blog, coordinate our film festival sponsorships, work on film school outreach in North America and manage gear and print materials for Flicks 2013. For my staff pick, I chose the film “From Dream to Reality” from Ian in the UK.

There are several reasons “From Dream to Reality” stood out to me. Most obviously, it’s adorable and I have a soft spot for cute things. But more than its cuteness, I love that it has dry humor at the end, when the raccoon says, “How are you holding that without thumbs?”, to which the fox replies, “Magic.”

I also think the ‘dreams’ that the raccoon has of a meaningful mobile experience is spot on with what we’re trying to do with Firefox OS. More than anything though, I love the animation style. The line drawing feels kind of old school and I like that it’s not flashy, just simple and well-done.

Having seen all or most of the Flicks entries thus far, I’m really impressed by the enthusiasm and vision I’ve been seeing from a lot of the filmmakers. It seems like a lot of these videos really speak to our goals for the mobile web, which is so exciting because it means we’re not the only ones who envision a more connected and accessible world.”

The Bugzilla Update: Bugzilla 4.4 and 4.2.6 released

Dave Miller — Thu, 23 May 2013 03:05:10 +0000

(cross-posted from LpSolit’s Blog)

We released Bugzilla 4.4 and 4.2.6 today. Bugzilla 4.2.6 is a bugfix release, and contains no security fixes. It adds support for MySQL 5.6 and fixes a crash with Oracle.

Bugzilla 4.4 contains many new features:

The searching system has been improved: it allows multiple search criteria to match one field; it has improved support for flags; it has better performance, especially with complex queries.
The tagging system has been redesigned: the old tagging fields in the page footer are gone in favor of a Tags field in the bug itself. Tags remain private and are only visible by you. They can also be used in queries as any other field.
Bugzilla can now correctly identify uploaded attachments which have a MIME type of application/octet-stream.
You can now save tabular and graphical reports as you already do with saved searches. Previously, you had to bookmark them in your web browser.
You can customize columns displayed in whinemails.
As usual, the WebServices have been improved with several new methods.
The security has been improved, such as using HMAC SHA-256 to generate tokens instead of MD5.
etc ….

This release also means the End Of Life (EOL) of Bugzilla 3.6, which was the last series for Bugzilla 3.x. This branch is no longer supported, and any new security bug found on this branch will remain unfixed. Installations still running Bugzilla 2.x or 3.x are urged to upgrade to Bugzilla 4.4 or 4.2.6.

So, what’s next? Well, the main focus for Bugzilla 5.0 will be usability and user experience. Bugzilla sometimes (often?) looks old-fashioned because we wanted to support old browsers and browsers with JavaScript disabled. But we decided to move to a more interactive interface where JavaScript will help accomplish some tasks with less page reloads, such as submitting changes to a bug or adding an attachment. We also plan to add a new skin to Bugzilla which should look like this. Some pages will also be entirely redesigned, such as the Group Controls page to administrate access to bugs which was considered too complex for the average admin. More information will come with the release of development snapshots.

Meeting Notes: Mobile: 2013-05-22

Jesper Kristensen — Thu, 23 May 2013 03:00:07 +0000

Schedule

Next merge: 2013-06-24
Next release: 2013-06-25

Major Topics for This Week

About Home Work: Work has been landing on “fig”. More changes should be ready to test by end of week.

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs.

Jamie Hewland fixed bug 849072 – Improve tab flushing and syncing behavior (first patch!)

Stand ups

Suggested format:

What did you do last week?
What are working on this week?
Anything blocking you?

Please keep your update to under 2 minutes!

Kats

Previously:
- bug 866184 – use gfx::Point instead of individual floats in some functions
- bug 867685 – Make GeckoLayerClient.setIsRTL hold the GLC lock when updating viewport
- bug 867582 – Fix some jittery behaviour at page edges in APZC
- PTO
- bug 860898 – add a verbose option to mach build options
Now:
- Catching up on bugmail, reviews, etc.
- start looking at async subframe scrolling (bug alias multi-apzc + dependencies)

GBrown

Last week:
- Mostly PTO
Now:
- bug 869030 Robocop testDoorHanger and testSystemPages cause future reboots on pandas
- bug 867360 Watcher dies sometimes on Pandas
- bug 870553 A blocklist/whitelist for Shumway

Chris Lord (cwiiis)

Done
- bug 869696 – Gralloc is really slow on the Geeksphone Peak (and other Adreno 205 devices?) – requires follow-up

Doing
- bug 803299 – Use 24-bit colour on 24-bit screens (patches r+’d but backed out due to reftest failures)
- bug 869156 and bug 866772 – Dynamic toolbar stuff
- bug 870055 – Page continues moving while finger is on screen (b2g browser)
- bug 870311 – Touch events are wonky on high dpi devices (b2g)

Chris Peterson

Help our new intern Shane Tully get up to speed on hg and Bugzilla
bug 776223 – NullPointerException: at android.content.ClipboardManager.setPrimaryClip(ClipboardManager.java)
bug 863103 – Add BackgroundService runIntentInService() and WakeLock
bug 872076 – Catch “missing CONTROL_LOCATION_UPDATES permission” exceptions

GCP

Last week:
- bug 862808 Local Video is upside down on Android when in portrait mode
- bug 873812 Trying to establish a call from an Android device to a Windows machine fails to render the remote video streams
- bug 859430 Add Bluetooth headset functionality to WebRTC calls
Next week:
- bug 874572 getUserMedia – Browser holding lock on device camera despite browser activity in the background and paused
- bug 874546 getUserMedia – Video playback does not resume when browser returns to being the foreground activity

Brian N

Done
- Bug 869411 – About:home is cut off beneath title bar
- Bug 872556 – Add-ons section can go missing in about:home
- Bug 779497 – The Add-ons Manager entries are multiplied if a search engine is added from context menu
In progress
- Session restore test cases
Next
- Ouya

Sriram

Add a PagerTabStrip for new about:home – bug 872762
Quick share from Android – bug 869123
Hide existing about:home page – bug 873579
New bookmarks page – bug 862796
- cl.ly/image/0z0U0c0n0c2m
Dynamic responsive tabs header – bug 874014
- cl.ly/image/3M1z1c1k2n1M – variable size header + icons

WesJ

Bug 874689 – Make FilePicker use Async prompt service
Bug 870062 – Provide asynchronous option in PromptServic
Looking at moving other prompt service usage to async
Bug 853844 – Investigate removing the pageload throbber – Have eiditicker access. Looking to run some tests with a variety of apk’s to see if we can improve pageload.

liuche

bug 872543 – Dismissing notification in JellyBean
bug 871978 – SwitchPreference crash
bug 871970 – Rename datareporting_crashreporter_title
bug 862116 – Strings for Android system notification + notification icons
Next/Finish:
- finish bug 873230 – split xml files into xml/ and xml-v11
- bug 870169 – TelemetryReporter interface for more reporter probes
- second pass for bug 872329 – Settings uplift
- bug 865371 – Settings UI Changes

LucasR

Last week
- Google I/O + PTO on Monday
- Launched The Layout: http://thelayout.cc
- Catching up with patch reviews
- Prep work for the Summit Planning Assembly
Next week
- bug 867608 – Gap between forward button and favicon after backing out of reader mode
- bug 844502 – In landscape orientation, tab menu overlays content, page stuck resizing and shifting around
- New about:home stuff

Margaret

Done
- bug 872737 – Support distribution bookmarks from a /system location
- bug 873429 – Form assistant suggestions is not dismissed while entering different letters
- bug 872005 – Reader Mode: Able to add pages to reading list on devices incapable of accessing Reader Mode
- bug 872965 – Exit Reader Mode icon takes user back, but not necessarily to original article
- bug 872962 – Reader Mode text formatting pop-up is incorrectly positioned on device rotation
- bug 873146 – about: page favicons are not displayed in the “Your tabs from last time” section of about:home screen
- (fig) bug 871639 – Incorrect title when leaving editing mode while on about:home
- (fig) bug 872834 – Finish adding editing mode to browser toolbar
- Interviews

In Progress
- (fig) bug 871645 – Consolidate names of browser toolbar’s element

Next
- Investigate some reader mode regressions caused by dynamic toolbar – bug 872961, bug 872956
- More new about:home stuff

BLassey

PTO end of last week
bug 866957 – Collect and report cell tower info
bug 872139 – Slow down zoom animation for reflow on zoom
bug 867517 – Gecko-based WebView

MFinkle

Recruiting
Planning around WebRT and Marketplace
Pitching in ideas for the PR Tour happening over the next two weeks
Misc manager stuff

Ian Barlow

In SF this week

Work in progress
- Mixed Content blocking
- FHR – about:healthreport (Arun)
- OUYA design refinement / future TV concepts (Zhenshuo)
- Future tablet browsing concepts (Yuan)
- Updated Settings UI

rnewman

FHR.
FHR.
Roadmappy kinds of things.

Feature Focus

Firefox 22

Features

[ON TRACK] Added locale: Slovak
State of good repair:
- [ON TRACK] ANR Reporter – Not user facing
- [ON TRACK] Refining Tab UI
- [ON TRACK] Performance improvements – Including WebGL, texture streaming, async canvas updates

Firefox 23

Features

[AT RISK] Firefox Health Report
[AT RISK] Added locale: Turkish
[AT RISK] Added locale: Hungarian
[ON TRACK] Dynamic URL bar
[ON TRACK] NFC bump for tab sharing
[ON TRACK] WebRTC platform support, confirmed: preffed OFF
[ON TRACK] L10N foundation improvements
[ON TRACK] UI for changing search engine default
[ON TRACK] RSS/Atom feed handling
[ON TRACK] API: Payments
[ON TRACK] Other toolbar/awesomescreen improvements:
Switch to Tab (Awesomescreen shows already open tabs), Domain autocomplete in Awesomescreen, Show URL instead of Title in Toolbar, highlight domain in toolbar when showing URL

Firefox 24

Features

[ON TRACK] Reader Improvements
[PLANNED] Packaged apps support
[PLANNED] Web Audio API
[PLANNED] API: Push notifications
[PLANNED] SkiaGL improvements
[PLANNED] Set Top Box optimization
[PLANNED] Directional game console navigation
[PLANNED] Quickshare
[PROPOSED] Shumway: generic video player
- Will create new project page with Mobile-specific work to be done when known
[PROPOSED] bug 850984- Request for set Baidu search engine as default for zh-CN Version of Firefox for Android
Need someone to take on: bug 861164 – use different search URLs for tablet vs. non-tablet

Firefox 25

Features

[PROPOSED] Privileged apps support
[PROPOSED] Shumway – v2 branded players
- Will create a project page for Mobile-specific work when known
[PROPOSED] API: Cloud
[PROPOSED] Solid developer environment
[PROPOSED] API: Alarm
[PLANNED] API: Web activities
[PLANNED] API: Contacts
[PLANNED] Dynamic Snippets
[PROPOSED] About:home redesign

Round Table

QA

Beta – regression – gfx crasher – bug 867058
Vivante device ordered heading to Toronto – bug 863307
Competitive analysis work for Product
Continuing to hammer on WebRTC

User Advocacy

We now have auto updating Feedback tools from the metrics team. If anyone would like access to these tools please let Tyler know.

Details

Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
Dial-in: conference# 99998
- US/International: +1 650 903 0800 x92 Conf# 99998
- US toll free: +1 800 707 2533 (pin 369) Conf# 99998
- Canada: +1 416 848 3114 x92 Conf# 99998
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
irc.mozilla.org #mobile for backchannel
Mobile Vidyo Room

Retrieved from “?title=Mobile/Notes/22-May-2013&oldid=659380“

Meeting Notes: Firefox/Gecko Delivery Planning: 2013-05-22

Jesper Kristensen — Thu, 23 May 2013 03:00:06 +0000

Schedule & Progress onUpcoming Releases

Firefox Desktop

Current Releases

FF21.0 looks like it’ll stick, congrats!

Beta (22)

https://www.mozilla.org/en-US/firefox/22.0beta/releasenotes/
- Desktop WebRTC
- Windows HiDPI
English Stub Installer on Beta
- https://bugzilla.mozilla.org/show_bug.cgi?id=857199
- https://www.mozilla.org/en-US/firefox/beta/ for Stub Installer
- https://www.mozilla.org/en-US/firefox/all-beta.html for Full Installer

Aurora (23)

https://www.mozilla.org/en-US/firefox/23.0a2/auroranotes/

Nightly (24)

FF24 is also planned as ESR24
- New scheme: planned dot releases of the ESR will be 24.1, 24.2, etc. For sanity the major+minor version will add up to the corresponding non-ESR release. 24.2 ==> 24 + 2 ==> released with Firefox 26
- “Chemspill” releases will use a third digit, e.g. 24.2.1

Firefox Metro

Read Only

Metro Team completed Work Week in Vancouver – View Results
Iteration #7 ends this Thursday on May 23.
- Team has completed 68 points (48%) of total story work.
- Majority of the remaining work will carry over to Iteration #8.
Iteration #7 Review and Planning meeting happens on Friday May 24.
Iteration #8 runs from Tuesday May 28 – Monday June 10.
On PTO from Friday May 31 – June 12: Asa will be assuming my Metro responsibilities while I’m gone.

ID	Summary	Priority	Status
831909	Story – Text selection in Firefox app bar (touch)	P1	ASSIGNED
831910	Story – Use the Auto-Complete Screen	P1	ASSIGNED
831915	Story – Implement Tile Widget and Groups – Part I	P1	ASSIGNED
831905	Story – Secure site indicators in the Firefox app bar	P1	ASSIGNED
857437	Defect – On-screen keyboard (OSK) overlapping app bars and find bar	P2	ASSIGNED
850737	Story – Smoothly scroll the Firefox Start screen – Part I	P2	ASSIGNED
867641	Defect: Context Bar covers some text when using previous and next buttons in Find in Page	P2	ASSIGNED
781002	Story – Apply metro styling to the context menu	P2	ASSIGNED
831913	Story – Use the Firefox app bar in snapped view	P2	REOPENED
833131	Story – Sync bookmarks	P2	REOPENED
860899	Story – Fixup all failing mochitest-metro-chrome tests in automation	P1	RESOLVED
855147	Defect: Settings do not persist when closing Firefox from desktop application bar	P1	RESOLVED
835623	Story – Combine page contextual items (URL bar, bookmark star, etc.) into single app bar	P2	RESOLVED
867515	Defect – Junior Style “Back” & “New Tab” buttons not displayed when opening links via “New Tab”	P2	RESOLVED
833130	Story – Sync passwords	P2	RESOLVED
833132	Story – Sync history	P2	RESOLVED
849312	[tracking] Backlog – Various sync issues	P2	RESOLVED
868217	Change – Adjust Sync UI for better information mapping	P2	RESOLVED
833182	Story – Updating Metro Firefox	P2	RESOLVED
849395	Story – Allow updates via about flyout	P2	RESOLVED
856049	Defect – Lower border of “Pair a device” input box is missing	P1	VERIFIED
867121	Defect – Snapped view: Favicons too close to text in awesome screen	P1	VERIFIED
867115	Defect – Context menu in snapped view shows the tab bar for an instant	P1	VERIFIED
867616	Story – Contextual app bar should replace standard/page app bar choices	P1	VERIFIED
867163	Defect – Restore tile button doesn’t work when context app bar is visible on a second time	P1	VERIFIED
872243	Change – Remove the “rainbow” gradients from the start screen	P1	VERIFIED
866065	Defect – ms-windows-store:// links should not need to be opened with an application	P1	VERIFIED
858598	Defect – Select popups near the bottom of the screen are unusable	P1	VERIFIED
856267	Defect – Context Menu overlapping with the Tab App Bar when visible	P1	VERIFIED
833133	Story – Sync tabs	P2	VERIFIED
869237	Change – Move “Paste” after “Select, Select All” in text selection context menu	P2	VERIFIED
855663	Defect – On first display, Findbar briefly displays at the top of the screen	P2	VERIFIED
872159	Defect – Flyout panels have a different border than permissions flyout	P2	VERIFIED
859625	Defect – remove obsoleted nsISidebar functions	P4	VERIFIED

Firefox Mobile

Beta (22)

Handy Dandy Tracking Page for Fx22: https://wiki.mozilla.org/Mobile/Roadmap/Tracking_Fx22

Confirmed for beta 2

bug 857459 – some about:home content is not displayed at first start-up
The multilocale build contains Slovak!
Beta 1 looks stable at less than 3 crashes per 100 ADU
4.3 stars and we’re still trending to positive comments

Aurora (23)

[AT RISK] Dynamic URL bar <=== We are converging
[AT RISK] Firefox Health Report
[AT RISK] Added locale: Turkish
[AT RISK] Added locale: Hungarian
[ON TRACK] NFC bump for tab sharing
[ON TRACK] WebRTC platform support, confirmed: preffed OFF
[ON TRACK] L10N foundation improvements
[ON TRACK] UI for changing search engine default
[ON TRACK] RSS/Atom feed handling
[ON TRACK] API: Payments

Nightly (24)

bug 862763 – nsLayoutUtils::FontSizeInflationEnabled shows up in profiles, but shouldn’t <== Looks like this change resulted in a ~14% Tp4 (no chrome) improvement for Android
Working to get WebRTC to state where we can pref it on – this is a goal, need to enumerate the plan
Also working to converge on Reflow on zoom, slowing down zoom animation is in progress: bug 872139 – Slow down zoom animation for reflow on zoom
[PROPOSED] Privileged apps support
[PROPOSED] Shumway – v2 branded players
- Will create a project page for Mobile-specific work when known
[PROPOSED] API: Alarm
[PLANNED] API: Web activities
[PLANNED] API: Contacts
[PLANNED] Dynamic Snippets
[PROPOSED] About:home redesign

Developer Tools

landing refinements for netmonitor, sourcemaps etc in 24
Jetpack UX work is increasingly linked to Australis, working to coordinate with Dolske’s team to assess scope.
Jetpack has a beta bug, currently investigated and Mossop will arrange patching as need be.

Feedback Summary

Desktop

21 seems quite stable at this point. No urgent issues to report. One small issue to report around UI changes.

Menu Item Change - We are seeing user confusion around moving the “clear recent history” button. Feedback is low at this point, but could increase as more users update. We suggest an educational push similar to the Private Browsing changes.

Scrolling is laggy Comments around scrolling being laggy/mouse only?. May be related to perf problems we saw during the beta.

Untrusted connections (from last week) - Spike died down May 15th/16th.

Updates not completing (from last week) - Only seems to have been May 13th, otherwise, still seeing comments but at a more normal level.

Mobile

21 is a very smooth and stable release. YAY!

We now have automated feedback tools, please ping Tyler if you want access.

UX & User Research

Fuller update to come (will update the wiki). For now, some highlights:

[Metro] – Design iterations and refinements:
- Updated Start Screen Tiles — http://cl.ly/image/0j3m1B0W1U2S
- Downloads Bar — http://cl.ly/image/3W3B2I2J0A1T
- Awesome Bar Results — http://cl.ly/image/0R1Q3s073e3u/o
- “Finalizing” Main Toolbar Specs — http://cl.ly/image/1J2c3b0J2J0D

[Australis]
- Customization Mode Updates on UX Branch — http://cl.ly/image/3i1C0Q27023D
- Updated OS X Design Specs — http://people.mozilla.com/~shorlander/files/australis-design-specs/australis-design-specs-osx.html

Market Insights from the Product Marketing Strategy Team

Mobile

The first Jolla phone was revealed and made available for pre – oder for 399 Euros. A device with a dual – core processor and a 4.5 – inch display, it will be able to run Android apps with the help of Open Mobile’s Application Compatibility Layer. It will not support the Google Play Store, though, so applications will need to be loaded through other venues. Besides Android, it will support Qt and HTML5 apps. The value proposition is branded “The Other Half” and speaks to the device’s ability to adapt its design, settings and apps as the user applies different hardware elements (like a cover) to it, as it acts through her day. Jolla will be providing a few of them, but it invites collaborators to create those accessories. The device will ship before the end of 2013.

http://www.geek.com/mobile/jollas-first-phone-running-sailfish-os-now-available-to-pre-order-1555742/

Opera launched the stable version of its Webkit – based Android browser. Based on Chromium 26, the app will likely switch to Blink once Google has integrated it into Chromium. It holds most of Opera’s signature features, such as the proxy – mode, Speed Dial home page, and Discover panel, which lets the user browse through the day’s top news. Available for Android 2.3 or newer, this version does not support tablets yet and has a 4.4 star rating.

https://play.google.com/store/apps/details?id=com.opera.browser

Samsung has acquired a 10% stake in Pantech, the 3rd largest Korean smartphone manufacturer. While significant in the country, the device maker has had little success outside of it, where is sells in the low – end in some of the emerging markets. Another stakeholder in Pantech is Qualcomm with 11.96%.

http://thenextweb.com/asia/2013/05/22/samsung-buys-10-stake-in-korean-handset-maker-pantech-for-48-million/

The 2012 Kaspersky Security Bulletin Board claims that 99% of the newly discovered mobile malicious apps target Android. The rate of discovery is going up, from 8 new unique programs in January 2011 to 8 times that amount at the end of 2012. There are 3 main types of malware: SMS Trojans, that send messages to premium-rate numbers, backdoors which provide unauthorized access and allow the installation of other malicious programs, and spyware as the 3rd category. These 3 types account for 51% of the newly discovered malware.

http://www.kaspersky.com/about/news/virus/2013/99_of_all_mobile_threats_target_Android_devices

Telefonica has announced a deal with Samsung to integrate its carrier billing backend into Samsung’s mobile services. Using the BlueVia payment APIs, Telefonica’s 316 million users who use Samsung’s app portals and services would be able to charge content directly to their phone bill. The rolle-out will be gradual, starting with Germany.

http://techcrunch.com/2013/05/16/telefonica-adds-samsung-as-a-carrier-billing-oem-for-apps-games-music-and-more/

ZTE has announced that is will begin selling phones in India with 5 devices priced between $105 and $270. The smartphones will be available in major cities starting with October and could be followed later by tablets. Important because ZTE is one of the top 5 worldwide phone manufacturers and India a country with a great deal of potential in the long – term and staggering growth in smartphones sales of 75% Year – over – Year.

http://thenextweb.com/in/2013/05/20/zte-targets-india-as-it-reveals-plans-to-launch-five-new-smartphones-in-the-country/

Marketing, Press & Public Reaction

Firefox 23 Lands In Aurora Channel: Kills Blink Element, Introduces Slew Of New Dev Tools

Planning Meeting Details

Wednesdays – 11:00am PT, 18:00 UTC
Mountain View Offices: Warp Core Conference Room
Toronto Offices: Finch Conference Room
irc.mozilla.org #planning for backchannel
(the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

650-903-0800 or 650-215-1282 x92 Conf# 99696 (US/INTL)
1-800-707-2533 (pin 369) Conf# 99696 (US)
Vidyo Room: ProductCoordination
Vidyo Guest URL

Retrieved from “?title=Firefox/Planning/2013-05-22&oldid=659436“

WoMoz: WoMoz Meeting Notes (May 15th)

Delphine — Thu, 23 May 2013 01:11:55 +0000

Meeting Agenda and Notes can be found here: https://womoz.etherpad.mozilla.org/15-05-13

Our next meeting will be on Tuesday MAY 28TH AT 20:00 UTC, irc channel #womoz

Project Highlights:

Some WoMoz members to attend AdaCamp, in San Francisco! The conference takes place during two days, from 8-9th of June. As Mozilla women community members, we are very proud to be able to participate in this event. Thank you Reps program for helping us bring women from far away so they can participate.
We are now 6 WoMoz committee members. More update about this to come soon.
Welcome Elvia who will help us out with the website!
Major website redesign and update on the works
Upcoming WoMoz local events:
- WoMoz Kick-off event in the Philippines on May 25th organized by Faye Tandog
- Webmaker contest in disabled children’s school by Mermi in Tunisia (see here and here for her previous updates about this)
- WoMoz presentation in Senegal organized by Gniele NIANG

The Bugzilla Update: Release of Bugzilla 3.2.7, 3.4.7, 3.6.1, and 3.7.1

Max Kanat-Alexander — Thu, 23 May 2013 00:26:41 +0000

(Translation available: Belorussian provided by PC)

So, today we had a bunch of releases. They are good. They fix stuff! Fixed stuff is good.

Now, I could pretty much end the blog post there, but there is one…tiny…extra…thing to talk about. If you were paying attention, you might have noticed that the 3.7.1 release says that it’s leading up to Bugzilla 4.0! Yes, that’s right, the next major release of Bugzilla will be 4.0, and here’s a bit about it:

Why 4.0?

So what is it that makes this release worthy of being called 4.0? Well, the biggest thing is that there have been major UI improvements. The biggest one is that the Advanced Search page has been fully redesigned. You can see it at our test site. It’s going to get better than that, too. Also, if you review a lot of patches, you will probably appreciate the new attachment details UI (log in to see the full feature set).

Bugzilla 4.0 will also have cross-domain WebServices support, via JSONP. As a part of that, the JSON-RPC WebServices interface can also now be accessed using HTTP GET and a simple query string in the URL, instead of having to POST a JSON object.

Also in the area of WebServices, we’re planning to have our most-requested WebService function implemented, Bug.update, so that you can update all the attributes of a Bug via the WebServices. There may be other good WebServices improvements which make 4.0, too.

Also, a great feature for installations that get a lot of bugs is the new Automatic Duplicate Detection. To try it out, go to file a bug on our test installation, type a few (real) words in to the Summary field, and then click out of it.

We are also planning on changing the default statuses, based on our 12 years of experience since Bugzilla was first open-sourced. The current status workflow is simple and broadly applicable, but it is ambiguous or less-than-useful in some ways: for example, a NEW bug may not actually be NEW–it’s just not being worked on. And then what does ASSIGNED really mean? Does it mean that somebody is working on the bug, or just that it’s been assigned to somebody (which you can already tell from the Assigned To field)? So, to resolve these issues, the new workflow will be even simpler: UNCONFIRMED -> CONFIRMED -> IN_PROGRESS -> RESOLVED -> VERIFIED. Installations that are upgrading will keep the old workflow by default, although there will be a script included to convert them to the new workflow, if they want.

Features Already In 3.7.1

3.7.1 already has the new Search UI and the new Attachment Details UI, although further improvements to the Search UI are coming in later development releases. 3.7.1 also has automatic duplicate detection and JSONP support for the JSON-RPC WebService.

Some of the other new features and changes in 3.7.1 are:

There is AJAX auto-completion of usernames in the CC, Assignee, and QA Contact boxes.
The First/Last/Next/Prev and the “Show my last search results” links at the top of a bug now work with multiple searches, so doing a new search won’t “clobber” your old list.
Bug ID custom fields can now represent relationships, much like “Blocks/Depends On” do now.
You can now add Hours Worked to a bug without having to comment.
There are now calendar widgets on every date field in the UI.
The Voting system and the Bug Moving system have been moved into being extensions, and at some point will be maintained separately from the main Bugzilla codebase (though they still ship with Bugzilla, for now).
email_in.pl now takes command-line arguments that allow you to specify defaults for field values, or override the field values specified in the incoming email.
Multi-select custom fields can now be columns on bug lists.
There is a new user preference for whether the “Additional Comment” box should show up before or after the existing comments.
In the code, there is a new function $bug->set_all, which takes a bunch of arguments and updates a bug doing all the updates in the proper order, making it extremely easy for custom code to update bugs.
The Bugzilla/Search.pm file (which implements the searching logic in Bugzilla) has been majorly refactored to be much simpler to understand and customize.
When you do a quicksearch, the quicksearch boxes in the header and footer will contain your last search.
You can now restrict the values and visibility of custom fields by the value of the Component field.
Custom fields can now be marked as mandatory (that is, they must have a value).
The “fields.html” page now contains help for every single bug field in Bugzilla, and the fields display the help when you hover over their names, on enter_bug.cgi.
There are a lot of great new code hooks, including ones for adding new columns and validators to objects, and another for modifying bug field permissions (so you can make certain fields read-only for certain users, using a hook).
Bugzilla can now be installed using Strawberry Perl, on Windows.
Comments are no longer manually word-wrapped at 80 columns before being sent to the browser–they are just word-wrapped in the browser.
Any time checksetup.pl throws an error, it will make it red to make it clearer.
YUI has been updated to 2.8.1, and Bugzilla now contains almost all of YUI, so all YUI features are available to customizers.

Do remember, though, that this is an unstable release. It may have bugs. They might be really bad bugs. We have no idea, because we haven’t tested this release at all. If it pokes your best friend in the face when you file a new bug, don’t blame us–we warned you.

The Plan

Right now we expect the 4.0 release to happen some time around the end of this year. To make this target, we’ll definitely need help with QA, so if you want to help out with Bugzilla, see if you can find/fix some bugs in 3.7.1, and also if you want, you can help out the QA Team write automated tests for 4.0!

-Max

The Bugzilla Update: Release of Bugzilla 3.2.10, 3.4.10, 3.6.4, and 4.0rc2

Max Kanat-Alexander — Thu, 23 May 2013 00:26:36 +0000

We just released Bugzilla 3.2.10, 3.4.10, 3.6.4, and 4.0rc2. Mostly, these contain a lot of very important security fixes. One of the fixes in particular took over 100 hours of work from the Bugzilla team as a whole and a host of external contributors, and we’ll be blogging about that in more detail in the coming days or weeks. Right now, what’s important to know is that these issues are pretty serious and you should update as soon as possible.

Older versions of Bugzilla are also affected, even though they haven’t been patched because they have reached End Of Life. If you are running a version of Bugzilla earlier than 3.2, it is now very important that you upgrade so that you can remain secure.

Most of the issues that were fixed today were discovered as a result of Mozilla expanding their security bug bounty program to include web applications. We’d like to thank Mozilla for funding this initiative and helping us significantly improve the security of Bugzilla in various areas.

Progress Toward Bugzilla 4.0

With the release of Bugzilla 4.0rc2, we’re that much closer to Bugzilla 4.0! This second Release Candidate has a fully-tested Bug.update WebService method, so we don’t expect its API to change any more (although it has changed quite a bit since 4.0rc1 thanks to testing and bug fixes). The other new WebService methods may still change before the final release of 4.0, as we haven’t tested all of them yet.

4.0rc2 also contains a lot of bug fixes over rc1, and should be relatively stable. Now is the time to start trying out deployments of it to see if everything is okay in your environment. Our current plan is to release Bugzilla 4.0 on Tuesday, February 15, 2011 if everything goes well with this release.

-Max

The Bugzilla Update: Bugzilla 4.0 Released!

Max Kanat-Alexander — Thu, 23 May 2013 00:26:31 +0000

So, last week we released Bugzilla 4.0, which was pretty exciting. It had some awesome major new features, like the redesigned search page, automatic duplicate detection, autocomplete for user and keyword fields, and an enormously-enhanced WebServices interface.

In addition to all of these huge features, though, there were a lot of smaller improvements that were pretty awesome in and of themselves. The major, major features are so huge that it’s easy to miss how great some of the other changes were, so I wanted to take some time in this blog to talk about some of those “smaller” improvements that can be pretty significant for some users.

UI Improvements

In addition to the redesigned search page, one of the biggest UI improvements is the new “attachment details” page (log in to see the full functionality). If you do a lot of code review in your Bugzilla, or if you open up attachments frequently to comment on them, you’ll appreciate the new full-size comment box and the enormous textarea space available for commenting inline on text attachments.

Also, another really nice change is that when you forget to set a required field on bug entry, you’re notified before you leave the page, instead of having to submit the form and then go back to add any missing data. Bugzilla highlights the fields you missed and puts a clear message in bold red letters on the page so that you can see what you need to fill out. It even puts the page focus on the first box you need to fix, now.

On the Search page and the bug entry page, you can hover over the label of any field to get a description of what that field does. Your mouse cursor will even change to indicate the availability of help. This should be particularly useful to people who are new to Bugzilla.

When you do a “quicksearch” using the box in the header or footer, your search will still be there when you see the search results, now. This makes editing the search you just did a lot easier.

There is a “Calendar” widget for every single date/time field in Bugzilla now.

You can choose to have the “Add a new comment” box above or below the existing comments, when viewing a bug, now. (See your Preferences.)

Every command-line script of Bugzilla now prints any error in red (if this is possible in your terminal), to make it really clear that running the script did not succeed.

And of course, this is pretty obvious, but there are great new icons for the Home page, now.

Custom Fields

People have long asked for the ability to make certain custom fields “mandatory”–that is, when filing a bug, you have to fill those fields out, and after the bug is filed, those fields can never be empty. Bugzilla 4.0 now supports this–all you have to do is check a single checkbox in the Administration UI, and your custom field becomes mandatory!

You can see “Multi-Select” custom fields as a column in your search results (the bug list) now!

Almost every custom field in your system will now be available as an axis for Graphical Reports and Tabular Reports. (Actually, a whole lot of other built-in fields are now available, too!)

You can now represent relationships between bugs when using the “Bug ID” field.

You can now display custom fields only in a certain Component or only in a certain Classification.

Search

Some people make really heavy use of the “Show my last search results” link, or the “First/Previous/Next/Last” links at the top of the bug page. In past versions of Bugzilla, doing a new search would entirely replace your “last search results”, meaning that “Show my last search results” and the “First/Previous/Next/Last” links would suddenly be working with a whole new set of bugs. Now Bugzilla “remembers” the last five search results for all logged-in users and does its best to give you the right list whenever you’re trying to navigate using those links on the bug page.

You can now search for attachments with specific flags on them, when using the Boolean Charts (which are now called “Custom Search”). Just specify a criteron for an attachment and a criterion for a flag in the same Chart.

Since almost the very first version of Bugzilla, you haven’t been able to search for a Product, Component, Target Milestone, etc. if its name contained a comma. Now you can!

WebServices

You can get data from the Bugzilla JSON-RPC WebService using HTTP GET, now, which is a lot easier in many situations. Also, you can even call the JSON-RPC WebServices from another domain using JSONP, meaning that you can use data from an external Bugzilla on your webpage, straight from JavaScript!

Also, there are a ton of new WebService functions and parameters available. See the full list of WebService improvements for details. Probably the biggest one is the new Bug.update function that allows you to update existing bugs.

Miscellaneous

Loading pages in Bugzilla should now be much faster, particularly if it’s your first time visiting Bugzilla, since we have eliminated the need for the browser to download a large number of unnecessary CSS files.

If you’re using time-tracking, you don’t have to enter a comment just to enter Hours Worked anymore!

If you’re setting up the Inbound Email interface, you can set defaults for certain fields using command-line switches.

If you are using a localized version of Bugzilla and your terminal does not understand Unicode, all of Bugzilla’s command-line scripts will now attempt to output their messages in your terminal’s character set.

If you are running Bugzilla under suexec (usually meaning that you’re on shared hosting), checksetup.pl now properly sets permissions on everything, meaning that all functionality of Bugzilla should now be working (including graphs and dependency trees).

Bugzilla now optionally supports sending the Strict-Transport-Security HTTP header for improved security on HTTPS installations.

If you are writing extensions, there are a ton of new hooks. The Extensions system is now capable of implementing the vast majority of possible extensions, particularly if you know a few tricks.

Future Plans

Now that 4.0 is released, we’re working on 4.2! Actually, we’ve been working on 4.2 for quite some time, and it already has some great new features, such as HTML bugmail and a new “tags” system that we’re implementing. We also expect to have a fully-redesigned Search backend that behaves consistently and intelligently for all searches while also performing considerably better than the current system does. There are already 100 enhancements marked as FIXED for 4.2, in fact! Check out that full list for details.

Currently our plan is to freeze for 4.2 on April 20, which would put our likely release date at some point in Q4 of 2011. Of course, depending on how many contributors we get, we could possibly release even earlier than that! Finding and fixing bugs in the trunk code is the fastest way to speed up our release process, so if you want to do that, see our development process for information on how to get our code and submit patches!

-Max

The Bugzilla Update: Bugzilla 4.1.1 Development Release

Max Kanat-Alexander — Thu, 23 May 2013 00:26:28 +0000

Less than a month after our release of 4.0, we have our first development snapshot, Bugzilla 4.1.1 available for you! This is our first release towards what will eventually be 4.2, and it’s got a bunch of new features. Here’s a really quick overview of what’s new in 4.2:

Bugzilla now sends bugmail in both text and HTML.
You can disable component, milestone, and version values.
You can now create an attachment by pasting it into a text field.
If you are using a modern web browser, then after you update a bug, the URL in your web browser will be the URL to view the bug. (So, pressing refresh will simply let you see the bug, and not try to update it again. Also, if you have “session restore” in your browser, it will load the bug instead of an error page.)
Comments are no longer automatically word-wrapped by the server, but are instead word-wrapped in the browser. This means that they are no longer exactly 80 characters wide–they are now wider.
Tabular reports now look nicer and can be sorted.
There is a new link, (take) that appears next to the Assignee field and allows you to assign a bug to yourself.
Bugzilla can now run on SQLite as its database system. This is experimental and should not yet be used for production systems.
You can now say that a custom field should only appear when any of a set of values are set on another field. (So, for example, you could say that a single field appears in multiple products.)
You can now choose to optionally (as a user preference) not have Quicksearch search bug comments.
The default list of columns for search results is now more sensible.
Bugzilla now audits most changes to most things in the system, and stores this auditing information in a table in the database. There is not yet a UI into this table.
The system for deciding how and when to store attachments on the disk (instead of in the database) has been simplified.
long_list.cgi, xml.cgi, and showattachment.cgi are gone. (They were not in use since a very old version of Bugzilla.) We also removed sidebar.cgi (the sidebar) because it wasn’t in use and future versions of Firefox will not support it.
You can search for bugs based on the number of comments that they have.
Also, you can add “number of comments” as a column in your search results.
Boolean charts now work sensibly for almost all fields. For example, searching for “CC is not equal to” now finds bugs where that user is not CC’ed, instead of all bugs that have at least one CC who isn’t that user. However, some of the old “magical” boolean chart functionality (such as searching for only attachment flags if you specify both a flag criterion and an attachment criterion) is temporarily missing while we redesign the search system.
By default, searches now only return 500 results. (You can click a link to see more.) Searches may also now never return more than 10,000 results.
The “See Also” field now accepts many more types of URLs. It also accepts simple bug numbers to refer to a bug in your current Bugzilla. Adding a local bug number to the “see also” field will also cause that bug’s “See Also” to point to this bug.
If you only have the “editcomponents” privilege for one or more products, you can now manage Flags for those products.
You can now specify “limit” and “offset” as URL parameters for all searches. These work much like their similar SQL equivalents.
You can now require a certain level of password complexity for your users.
When you run checksetup.pl to create a new Bugzilla database, it will print out far less information than it used to.
Almost all of the important information that checksetup.pl prints out can now be localized.
There is now a specific directory in bz_locations (in Bugzilla::Constants) for where the pre-compiled templates are stored, that can be customized.
This release contains an initial implementation of a new tags system. The new UI for this tags system has not yet been implemented.
There is now a special group for moderating quips, so you don’t have to be an admin.
Bugzilla can now automatically detect the correct encoding for text attachments that aren’t in UTF-8.

Those are most of the major new changes that are in 4.1.1 over 4.0. We also have many other features planned for 4.2.

We hope that you enjoy testing Bugzilla 4.1.1 and we would love to hear your feedback, both on how the new features work and any bugs that you may find!

-Max

The Bugzilla Update: Release of Bugzilla 4.1.2, 4.0.1, 3.6.5, and 3.4.11

Max Kanat-Alexander — Thu, 23 May 2013 00:26:25 +0000

Hey Bugzilla users! We just released four new versions of Bugzilla. There were a lot of cool bug fixes in 3.6.5 and 4.0.1, but most importantly, if you had trouble installing Bugzilla 4.0, you should try again now with Bugzilla 4.0.1. There was a problem with the way that our install-module.pl script installed the Math::Random::Secure module–basically, it would install the module even though the module’s prerequisites failed to install. Then when you tried to run checksetup.pl, Math::Random::Secure would throw a cryptic error about “Math::Random::Secure::irand.”

Now, in 4.0.1 and 3.6.5, install-module.pl won’t install the module if installing it would break your system. Basically, following the standard installation instructions should work fine, now. Bugzilla 3.4.11 took this a step further and no longer uses Math::Random::Secure at all for this older branch (although don’t worry, Bugzilla 3.4.x is still secure).

For 4.1.2, we made this protection even more extreme–install-module.pl now completely refuses to operate if you don’t have a compiler installed somewhere on your system (because so many CPAN modules require a compiler, and CPAN throws very confusing error messages when there is no compiler available on your system).

New Features in 4.1.2

All right, with all that out of the way, let’s talk about new features in 4.1.2! Here’s a quick list of important new things:

Extensions can call a web_dir method to get the on-disk path to where web-accessible files should go for the extensions.
Work to improve Bugzilla’s accessibility (per the WAI WCAG) is ongoing.
There’s a new hook in Bugzilla::Install::Filesystem to allow extensions to create their own files, directories, etc.
Searching by relative dates (like 1d, 1w, etc.) now don’t round you off to the beginning of the time period (that is, the beginning of the day, the start of the week) unless you put the letter “s” after them (exception: searching for “0d” or “0w” still gives you the start of that the current day, week, etc.).
New WebService function: Product.create
New WebService function: Group.create
If you change the requestee of a flag that is set to “?”, the “requester” will not change.
install-module.pl now requires a compiler to be installed on the system.
Update to YUI 2.9.0.
contrib/bugzilla_ldapsync.rb has been removed (it was non-functional).
If you are using some authentication method that uses the extern_id field (like LDAP), you can now edit a user’s extern_id from the Users control panel.

The Plan For Pretty

So, as you may have read, the “Make Bugzilla Pretty” contest is over, and Jonathan Wilde has won. The current plan is for his UI to be the new official UI for Bugzilla 5.0, which will come some time after 4.2.

Basically, the way that it will work is this: After we branch for 4.2, we will create a new “pretty” branch. The Bugzilla team will work on implementing the new UI in this branch, while simultaneously doing new feature development on the normal Bugzilla trunk. Once the “pretty” branch is ready, it will be merged back into the trunk. We can do this all fairly efficiently thanks to bzr.

Now, there is a chance that the “pretty” branch won’t be ready by the time we want to do the release that follows 4.2. In this case, that release will be called 4.4 and the release after that will have the new UI. However, we very much want to release the new UI as soon as possible, so our goal is for 5.0 to be the release after 4.2.

Get Involved

As always, we love new contributors in every area. There are a lot of ways to contribute to Bugzilla–you don’t just have to be a programmer. In particular, we’d really love to have somebody to be in charge of our documentation. If you know anybody who’s a great documenter (including yourself!) who wants to help out an open-source project, please send them our way!

-Max

The Bugzilla Update: Release of Bugzilla 4.2rc2, 4.0.4, 3.6.8, and 3.4.14

Dave Miller — Thu, 23 May 2013 00:26:22 +0000

Today we are announcing the second Release Candidate for Bugzilla 4.2, in addition to one new stable release and two security-only updates for the 3.4.x and 3.6.x series.

Bugzilla 4.2rc2 is our second Release Candidate for Bugzilla 4.2. This release has received QA testing, and should be considerably more stable than the development releases before it. It is still not considered fully stable, and so you should understand that if you use it, you use it at your own risk. This will most likely be the last release candidate before 4.2 final.

Bugzilla 4.0.4 is our latest stable release. It contains various useful bug fixes and security improvements for the 4.0 branch.

Bugzilla 3.6.8 and 3.4.14 are security updates for the 3.6 branch and the 3.4 branch, respectively.

All the gory details and download links and the security advisory are available on our website.

Get Involved

The Bugzilla Update: Release of Bugzilla 4.3.2, 4.2.2, 4.0.7, and 3.6.10

Dave Miller — Thu, 23 May 2013 00:26:19 +0000

Today we have several new releases for you!

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 4.2.2 is our latest stable release. It contains various useful bug fixes and security improvements:

Download 4.2.2
Release Notes for 4.2.2

Bugzilla 4.0.7 is a security update for the 4.0 branch:

Download 4.0.7
Release Notes for 4.0.7

Bugzilla 3.6.10 is a security update for the 3.6 branch:

Download 3.6.10
Release Notes for 3.6.10

Bugzilla 4.3.2 is an unstable development release. This release has not received QA testing from the Bugzilla Project, and should not be used in production
environments. Development releases exist as previews of the features that the next major release of Bugzilla will contain. They also exist for testing purposes, to collect bug reports and feedback, so if you find
a bug in this development release (or you don’t like how some feature works) please tell us.

Download 4.3.2

The Bugzilla Update: Release of Bugzilla 4.3.3, 4.2.3, 4.0.8, and 3.6.11

Dave Miller — Thu, 23 May 2013 00:26:16 +0000

Today we have several new releases for you!

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 4.2.3 is our latest stable release. It contains various useful bug fixes and security improvements:

Download 4.2.3
Release Notes for 4.2.3

Bugzilla 4.0.8 is a security update for the 4.0 branch:

Download 4.0.8
Release Notes for 4.0.8

Bugzilla 3.6.11 is a security update for the 3.6 branch:

Download 3.6.11
Release Notes for 3.6.11

Bugzilla 4.3.3 is an unstable development release. This release has not received QA testing from the Bugzilla Project, and should not be used in production environments. Development releases exist as previews of the features that the next major release of Bugzilla will contain. They also exist for testing purposes, to collect bug reports and feedback, so if you find a bug in this development release (or you don’t like how some feature works) please tell us.

Download 4.3.3

The Bugzilla Update: Release of Bugzilla 4.4rc1, 4.2.4, 4.0.9, and 3.6.12

Dave Miller — Thu, 23 May 2013 00:26:13 +0000

Today we have several new releases for you!

All of today’s releases contain security fixes. We recommend that all Bugzilla administrators read the Security Advisory that was published along with these releases.

Bugzilla 4.4rc1 is our first Release Candidate for Bugzilla 4.4. This release has received QA testing, and should be considerably more stable than the development releases before it. It is still not considered fully stable, and so you should understand that if you use it, you use it at your own risk.

If feedback from this release candidate indicates that it is mostly stable, then Bugzilla 4.4 will be released in a few weeks. If feedback indicates that more extensive fixes are needed, there may be another release candidate after this one.

Download 4.4rc1
Release Notes for 4.4rc1

Bugzilla 4.2.4 is our latest stable release. It contains various useful bug fixes and security improvements:

Download 4.2.4
Release Notes for 4.2.4

Bugzilla 4.0.9 is a security update for the 4.0 branch:

Download 4.0.9
Release Notes for 4.0.9

Bugzilla 3.6.12 is a security update for the 3.6 branch:

Download 3.6.12
Release Notes for 3.6.12

Mozilla Add-ons Blog: A step forward in add-on install experience

Jorge Villalobos — Wed, 22 May 2013 19:53:40 +0000

We recently heard some great news from our support team that we want to share with you. Thanks to the last update in the Babylon translation software installer, support requests related to the way it customizes Firefox have dropped sharply, as much as 60% in some areas.

Like with many other software packages, Babylon’s installer includes an add-on that customizes Firefox, adding a toolbar and changing some settings like the home page. Until recently there wasn’t a Right Way of doing this, so every software vendor did it their own way. This has lead to an inconsistent and unsatisfying user experience, which has brought a great deal of work to our support staff.

To deal with add-on user experience problems, we started Project Squeaky last year. One of our first accomplishments was to establish the Add-on Guidelines, a short checklist that all add-on developers should follow. If you read the guidelines, you’ll notice that install experience and settings changes are specified to greater detail than the others, given that they are the ones we’ve identified as the most common problems users encounter.

We have been in contact with software vendors like Babylon for quite a while now, and these discussions have yielded positive results. We’re especially happy about the progress we’ve made with Babylon because their install base is particularly large, causing the support team to immediately notice the change in user sentiment after their install experience was improved.

This one positive outcome is very exciting for us, and we hope to continue moving forward in this area. There’s much planned for the rest of the year, and we hope users will greatly benefit from all that is coming.

Web FWD: Our teams kick some serious...

Wed, 22 May 2013 17:43:00 +0000

Just two weeks until our WebFWD III Cohort teams graduate on June 5!. Below are just a few highlights of how they kicked some bootie during our program; we hope you can meet them at graduation, and/or at our San Francisco mixer the day before, June 4 (note the floor change)!.

— The WebFWD Team

Anahita

All Anahita apps now available for free download.
Free “Tribe” support group is available for members to engage and help one other with technical questions.
Released Anahita 3.0 Embryo.
Started offering consulting, development, and hosting services to enterprise customers.

Appsembler.

Landed a large customer (edX).
Hired a developer and student intern.
Successfully integrated Mozilla Persona, Towtruck from Mozilla Labs and started integrating with Firefox Marketplace.
Initiated partnership discussions with Red Hat’s OpenShift, dotCloud and Transifex.

Common.ly

Selected to be a Thiel Fellow, which includes $100,000 to fund Commonly over the next 2 years.
Held the Gamedev Garage Sale which earned over $1000 in 4 days, creating a new library of public domain art and music.
Launched public beta for the Commonly Platform

Gameleon

Moved from MVP to Beta Version of the Gameleon Editor.
Reached over 16.000 game developers & enthusiasts at Pyrkon, Comic Con Bucharest, and IT Is Business.
Acquired over 620 registered users of the online editor creating over 80 maps.
Released open source virtual machine, the counterpart to the online editor.
Won Startup Camp Berlin Pitch Marathon, competing against 60 other companies.
Participated in Mini Seedcamp Belgrade and Eleven Demo Day in London.

Letters in Motion

Pivoted to founding Letters in Motion
Conducted tech review.
Built prototype

mist.io

Launched private beta
Got from 0 to 300 active users
Got from 0 to 700 machines managed through our service

Mobozi

Indexed and analyzed over 1,000 mobile web apps.
Attained over 2,000 app installs.
Acquired over 5,000 monthly active users of Mobozi Apps.

Nudge

Over 2,000 sites created using NudgePad.
The self hosted version of NudgePad has been downloaded over 400 times.
Over 25,000 people visited a NudgePad powered site in April.

hacks.mozilla.org: Compiling to JavaScript, and Debugging with Source Maps

Nick Fitzgerald — Wed, 22 May 2013 08:16:40 +0000

This is a tutorial on how to write a compiler which generates JavaScript as its target language, and maintains line and column meta-data in source maps for debugging. Storing line and column coordinates in a source map allows the end-user of the compiler to debug the source code that they wrote, rather than the ugly, generated JavaScript they are not familiar with.

In this tutorial, we will be compiling a small Reverse Polish Notation, or RPN, language to JavaScript. The language is super simple, and is nothing more than simple arithmetic with variable storage and output capabilities. We are keeping the language simple so that we can focus on integrating source maps with the compiler, rather than language implementation details.

Availability

Initial support for source maps in the debugger is available in Firefox 23 (Aurora at time of writing) with more improvements coming in Firefox 24 (Nightly at time of writing). Chrome DevTools also have support for source maps.

Overview of the Source Language

RPN uses postfix notation, meaning that the operator follows its two operands. One of the benefits of RPN is that as long as we limit ourselves to binary operators, we do not need any parentheses, and do not need to worry about operator precedence.

Here is an example program in our source language:

a 5 =;
b 3 =;
c a b + 4 * =;

This is an equivalent program written in a language which uses infix notation for its arithmetic operators:

a = 5;
b = 3;
c = (a + b) * 4;

Our language will support addition, subtraction, multiplication, division, assignment, and printing. The print operator’s first operand is the value to print, the second operand is how many times to print the value and must be greater than or equal to one:

5 1 print;
# Output:
# 5
 
3 4 print;
# Output:
# 3
# 3
# 3
# 3
 
4 print;
# Syntax error
 
n -1 =;
4 n print;
# Runtime error

Lastly, division by zero should throw an error:

5 0 /;
# Runtime error

Getting Setup

We will be writing our compiler on Node.js, using Jison to generate the parser for our language from a grammar, and using the source-map library to help generate source maps.

The first step is to download and install Node.js if you don’t already have it on your system.

After you have installed Node.js, use its package manager npm to create a new project for the compiler:

$ mkdir rpn
$ cd rpn/
$ npm init .

After the last command, npm will prompt you with a bunch of questions. Enter your name and email, answer ./lib/rpn.js for the main module/entry point, and just let npm use the defaults that it supplies for the rest of the questions.

Once you have finished answering the prompts, create the directory layout for the project:

$ mkdir lib
$ touch lib/rpn.js
$ mkdir -p lib/rpn

The public API for the compiler will reside within lib/rpn.js, while the submodules we use to implement various things such as the lexer and abstract syntax tree will live in lib/rpn/*.js.

Next, open up the package.json file and add jison and source-map to the project’s dependencies:

...
"dependencies": {
  "jison": ">=0.4.4",
  "source-map": ">=0.1.22"
},
...

Now we will install a link to our package in Node.js’s globally installed packages directory. This allows us to import our package from the Node.js shell:

$ npm link .

Make sure that everything works by opening the Node.js shell and importing our package:

$ node
> require("rpn")
{}

Writing the Lexer

A lexer (also known as a scanner or tokenizer) breaks the inputted raw source code into a stream of semantic tokens. For example in our case, we would want to break the raw input string "5 3 +;" into something like ["5", "3", "+", ";"].

Because we are using Jison, rather than writing the lexer and parser by hand, our job is much easier. All that is required is to supply a list of rules that describe the types of tokens we are expecting. The left hand side of the rules are regular expressions to match individual tokens, the right hand side are the snippets of code to execute when an instance of the corresponding token type is found. These tokens will be passed on to the parser in the next phase of the compiler.

Create the rules for lexical analysis in lib/rpn/lex.js:

exports.lex = {
  rules: [
    ["\\s+",                   "/* Skip whitespace! */"],
    ["#.*\\n",                 "/* Skip comments! */"],
    [";",                      "return 'SEMICOLON'"],
    ["\\-?[0-9]+(\\.[0-9]+)?", "return 'NUMBER';"],
    ["print",                  "return 'PRINT';"],
    ["[a-zA-Z][a-zA-Z0-9_]*",  "return 'VARIABLE';"],
    ["=",                      "return '=';"],
    ["\\+",                    "return '+';"],
    ["\\-",                    "return '-';"],
    ["\\*",                    "return '*';"],
    ["\\/",                    "return '/';"],
    ["$",                      "return 'EOF';"]
  ]
};

Writing the Parser

The parser takes the tokens from the lexer one at a time and confirms that the input is a valid program in our source language.

Once again, the task of writing the parser is much easier than it would otherwise be thanks to Jison. Rather than writing the parser ourselves, Jison will programmatically create one for us if we provide a grammar for the language.

If all we cared about was whether the input was a valid program, we would stop here. However, we are also going to compile the input to JavaScript, and to do that we need to create an abstract syntax tree. We build the AST in the code snippets next to each rule.

A typical grammar contains productions with the form:

LeftHandSide → RightHandSide1
             | RightHandSide2
             ...

However, in Jison we are a) writing in JavaScript, and b) also providing code to execute for each rule so that we can create the AST. Therefore, we use the following format:

LeftHandSide: [
  [RightHandSide1, CodeToExecute1],
  [RightHandSide2, CodeToExecute2],
  ...
]

Inside the code snippets, there are a handful of magic variables we have access to:

$$: The value of the left hand side of the production.
$1/$2/$3/etc: The value of the the nth form in the right hand side of the production.
@1/@2/@3/etc: An object containing the line and column coordinates where the nth form in the right hand side of the production was parsed.
yytext: The full text of currently matched rule.

Using this information, we can create the grammar in lib/rpn/bnf.js:

exports.bnf = {
  start: [
    ["input EOF", "return $$;"]
  ],
  input: [
    ["",           "$$ = [];"],
    ["line input", "$$ = [$1].concat($2);"]
  ],
  line: [
    ["exp SEMICOLON", "$$ = $1;"]
  ],
  exp: [
    ["NUMBER",           "$$ = new yy.Number(@1.first_line, @1.first_column, yytext);"],
    ["VARIABLE",         "$$ = new yy.Variable(@1.first_line, @1.first_column, yytext);"],
    ["exp exp operator", "$$ = new yy.Expression(@3.first_line, @3.first_column, $1, $2, $3);"]
  ],
  operator: [
    ["PRINT", "$$ = new yy.Operator(@1.first_line, @1.first_column, yytext);"],
    ["=",     "$$ = new yy.Operator(@1.first_line, @1.first_column, yytext);"],
    ["+",     "$$ = new yy.Operator(@1.first_line, @1.first_column, yytext);"],
    ["-",     "$$ = new yy.Operator(@1.first_line, @1.first_column, yytext);"],
    ["*",     "$$ = new yy.Operator(@1.first_line, @1.first_column, yytext);"],
    ["/",     "$$ = new yy.Operator(@1.first_line, @1.first_column, yytext);"]
  ]
};

Implementing the Abstract Syntax Tree

Create the definitions for the abstract syntax tree nodes in lib/rpn/ast.js.

Since we will be maintaining line and column information in all of the AST nodes, we can reuse some code by making a base prototype:

var AstNode = function (line, column) {
  this._line = line;
  this._column = column;
};

The definitions for the rest of the AST nodes are pretty straight forward. Link up the prototype chain, assign relevant attributes, and don’t forget to call AstNode‘s constructor:

exports.Number = function (line, column, numberText) {
  AstNode.call(this, line, column);
  this._value = Number(numberText);
};
exports.Number.prototype = Object.create(AstNode.prototype);
 
exports.Variable = function (line, column, variableText) {
  AstNode.call(this, line, column);
  this._name = variableText;
};
exports.Variable.prototype = Object.create(AstNode.prototype);
 
exports.Expression = function (line, column, operand1, operand2, operator) {
  AstNode.call(this, line, column);
  this._left = operand1;
  this._right = operand2;
  this._operator = operator;
};
exports.Expression.prototype = Object.create(AstNode.prototype);
 
exports.Operator = function (line, column, operatorText) {
  AstNode.call(this, line, column);
  this.symbol = operatorText;
};
exports.Operator.prototype = Object.create(AstNode.prototype);

Compilation

Generated JavaScript

Before we generate JavaScript, we need a plan. There are a couple ways we can structure the outputted JavaScript.

One strategy is to translate the RPN expressions to the equivalent human readable JavaScript expression we would create if we had been writing JavaScript all along. For example, if we were to port this RPN example:

a 8 =;
b 2 =;
c a b 1 - / =;

We might write the following JavaScript:

var a = 8;
var b = 3;
var c = a / (b - 1);

However, this means that we are completely adopting the nuances of JavaScript’s arithmetic. In an earlier example, we saw that a helpful runtime error was thrown when any number was divided by zero. Most languages throw an error when this occurs, however JavaScript does not; instead, the result is Infinity. Therefore, we can’t completely embrace JavaScript’s arithmetic system, and we must generate some code to check for divide-by-zero errors ourselves. Adding this code gets a little tricky if we want to maintain the strategy of generating human readable code.

Another option is treating the JavaScript interpreter as a stack machine of sorts and generating code that pushes and pops values to and from a stack. Furthermore, stack machines are a natural fit for evaluating RPN. In fact, it is such a good fit that RPN “was independently reinvented by F. L. Bauer and E. W. Dijkstra in the early 1960s to reduce computer memory access and utilize the stack to evaluate expressions.”

Generating JavaScript code for the same example above, but utilizing the JavaScript interpreter as a stack machine, might look something like this:

push(8);
push('a');
env[pop()] = pop();
push(2);
push('b');
env[pop()] = pop();
push('a');
push('b');
push(1);
temp = pop();
push(pop() - temp);
temp = pop();
if (temp === 0) throw new Error("Divide by zero");
push(pop() / temp);
push('c');
env[pop()] = pop();

This is the strategy we will follow. The generated code is a bit larger, and we will require a preamble to define push, pop, etc, but compilation becomes much easier. Furthermore, the fact that the generated code isn’t as human readable only highlights the benefits of using source maps!

Creating Source Maps

If we weren’t generating source maps along with our generated JavaScript, we could build the generated code via concatenating strings of code:

code += "push(" + operand1.compile() + " "
  + operator.compile() + " "
  + operand2.compile() + ");\n";

However, this doesn’t work when we are creating source maps because we need to maintain line and column information. When we concatenate strings of code, we lose that information.

The source-map library contains SourceNode for exactly this reason. If we add a new method on our base AstNode prototype, we can rewrite our example like this:

var SourceNode = require("source-map").SourceNode;
AstNode.prototype._sn = function (originalFilename, chunk) {
  return new SourceNode(this._line, this._column, originalFilename, chunk);
};
 
...
 
code = this._sn("foo.rpn", [code,
                            "push(",
                            operand1.compile(), " ",
                            operator.compile(), " ",
                            operand2.compile(), ");\n"]);

Once we have completed building the SourceNode structure for the whole input program, we can generate the compiled source and the source map by calling the SourceNode.prototype.toStringWithSourceMap method. This method returns an object with two properties: code, which is a string containing the generated JavaScript source code; and map, which is the source map.

Implementing Compilation

Now that we have a strategy for generating code, and understand how to maintain line and column information so that we can generate source maps easily, we can add the methods to compile our AST nodes to lib/rpn/ast.js.

To play nice with the global JavaScript environment, we will namespace push, pop, etc, under __rpn.

function push(val) {
  return ["__rpn.push(", val, ");\n"];
}
 
AstNode.prototype.compile = function (data) {
  throw new Error("Not Yet Implemented");
};
AstNode.prototype.compileReference = function (data) {
  return this.compile(data);
};
AstNode.prototype._sn = function (originalFilename, chunk) {
  return new SourceNode(this._line, this._column, originalFilename, chunk);
};
 
exports.Number.prototype.compile = function (data) {
  return this._sn(data.originalFilename,
                  push(this._value.toString()));
};
 
exports.Variable.prototype.compileReference = function (data) {
  return this._sn(data.originalFilename,
                  push(["'", this._name, "'"]));
};
exports.Variable.prototype.compile = function (data) {
  return this._sn(data.originalFilename,
                  push(["window.", this._name]));
};
 
exports.Expression.prototype.compile = function (data) {
  var temp = "__rpn.temp";
  var output = this._sn(data.originalFilename, "");
 
  switch (this._operator.symbol) {
  case 'print':
    return output
      .add(this._left.compile(data))
      .add(this._right.compile(data))
      .add([temp, " = __rpn.pop();\n"])
      .add(["if (", temp, " <= 0) throw new Error('argument must be greater than 0');\n"])
      .add(["if (Math.floor(", temp, ") != ", temp,
            ") throw new Error('argument must be an integer');\n"])
      .add([this._operator.compile(data), "(__rpn.pop(), ", temp, ");\n"]);
  case '=':
    return output
      .add(this._right.compile(data))
      .add(this._left.compileReference(data))
      .add(["window[__rpn.pop()] ", this._operator.compile(data), " __rpn.pop();\n"]);
  case '/':
    return output
      .add(this._left.compile(data))
      .add(this._right.compile(data))
      .add([temp, " = __rpn.pop();\n"])
      .add(["if (", temp, " === 0) throw new Error('divide by zero error');\n"])
      .add(push(["__rpn.pop() ", this._operator.compile(data), " ", temp]));
  default:
    return output
      .add(this._left.compile(data))
      .add(this._right.compile(data))
      .add([temp, " = __rpn.pop();\n"])
      .add(push(["__rpn.pop() ", this._operator.compile(data), " ", temp]));
  }
};
 
exports.Operator.prototype.compile = function (data) {
  if (this.symbol === "print") {
    return this._sn(data.originalFilename,
                    "__rpn.print");
  }
  else {
    return this._sn(data.originalFilename,
                    this.symbol);
  }
};

Gluing it Together

From here we have done all the difficult work, and we can run a victory lap by connecting the modules together with a public API, and by creating a command line script to call the compiler.

The public API resides in lib/rpn.js. It also contains the preamble, to initialize __rpn:

var jison = require("jison");
var sourceMap = require("source-map");
var lex = require("./rpn/lex").lex;
var bnf = require("./rpn/bnf").bnf;
 
var parser = new jison.Parser({
  lex: lex,
  bnf: bnf
});
 
parser.yy = require("./rpn/ast");
 
function getPreamble () {
  return new sourceMap.SourceNode(null, null, null, "")
    .add("var __rpn = {};\n")
    .add("__rpn._stack = [];\n")
    .add("__rpn.temp = 0;\n")
 
    .add("__rpn.push = function (val) {\n")
    .add("  __rpn._stack.push(val);\n")
    .add("};\n")
 
    .add("__rpn.pop = function () {\n")
    .add("  if (__rpn._stack.length > 0) {\n")
    .add("    return __rpn._stack.pop();\n")
    .add("  }\n")
    .add("  else {\n")
    .add("    throw new Error('can\\\'t pop from empty stack');\n")
    .add("  }\n")
    .add("};\n")
 
    .add("__rpn.print = function (val, repeat) {\n")
    .add("  while (repeat-- > 0) {\n")
    .add("    var el = document.createElement('div');\n")
    .add("    var txt = document.createTextNode(val);\n")
    .add("    el.appendChild(txt);\n")
    .add("    document.body.appendChild(el);\n")
    .add("  }\n")
    .add("};\n");
}
 
exports.compile = function (input, data) {
  var expressions = parser.parse(input.toString());
  var preamble = getPreamble();
 
  var result = new sourceMap.SourceNode(null, null, null, preamble);
  result.add(expressions.map(function (exp) {
    return exp.compile(data);
  }));
 
  return result;
};

Create the command line script in bin/rpn.js:

#!/usr/bin/env node
var fs = require("fs");
var rpn = require("rpn");
 
process.argv.slice(2).forEach(function (file) {
  var input = fs.readFileSync(file);
  var output = rpn.compile(input, {
    originalFilename: file
  }).toStringWithSourceMap({
    file: file.replace(/\.[\w]+$/, ".js.map")
  });
  var sourceMapFile = file.replace(/\.[\w]+$/, ".js.map");
  fs.writeFileSync(file.replace(/\.[\w]+$/, ".js"),
                   output.code + "\n//@ sourceMappingURL=" + sourceMapFile);
  fs.writeFileSync(sourceMapFile, output.map);
});

Note that our script will automatically add the //@ sourceMappingURL comment directive so that the browser’s debugger knows where to find the source map.

After you create the script, update your package.json:

...
"bin": {
  "rpn.js": "./bin/rpn.js"
},
...

And link the package again so that the script is installed on your system:

$ npm link .

Seeing Results

Here is an RPN program that we can use to test our compiler. I have saved it in examples/simple-example.rpn:

a 8 =;
b 3 =;
c a b 1 - / =;
c 1 print;

Next, compile the script:

$ cd examples/
$ rpn.js simple-example.rpn

This generates simple-example.js and simple-example.js.map. When we include the JavaScript file in a web page we should see the result of the computation printed on the page:

Great success!

However, we aren’t always so lucky, and our arithmetic might have some errors. Consider the following example, examples/with-error.rpn:

a 9 =;
b 3 =;
c a b / =;
c a b c - / =;
c 1 print;

We can compile this script and include the resulting JavaScript in a web page, but this time we won’t see any output on the page.

By opening the debugger, setting the pause on exceptions option, and reloading, we can see how daunting debugging without source maps can be:

The generated JavaScript is difficult to read, and unfamiliar to anyone who authored the original RPN script. By enabling source maps in the debugger, we can refresh and the exact line where the error ocurred in our original source will be highlighted:

The debugging experience with source maps is orders of magnitude improved, and makes compiling languages to JavaScript a serious possibility.

At the end of the day though, the debugging experience is only as good as the information encoded in the source maps by your compiler. It can be hard to judge the quality of your source maps simply by looking at the set of source location coordinates that they are mapping between, so Tobias Koppers created a tool to let you easily visualize your source maps.

Here is the visualization of one of our source maps:

Good luck writing your own compiler that targets JavaScript!

References

Meeting Notes: Firefox Status: 2013-05-21

Jesper Kristensen — Wed, 22 May 2013 03:00:06 +0000

General Topics

Status updates tool: switch to bsmedberg

Friends of the Firefox team

Give a shoutout/thanks to people for helping fix and test bugs.

Stand ups

Suggested format:

What did you do last week?
What are working on this week?
Anything blocking you?

Please keep your update to under 1 minute!

paolo

Reviews on features added to the JavaScript API for downloads
Prepared the promises patch that included code documentation
Continuing towards landing the updated implementation of promises

mak

Been at the jsday in Verona last week.
Went to visit couple of italian red pandas :)
Lots of pending bugmails and requests, still syncing up with those.

felipe

bug 853389 AddonRepository – Patches posted for review \o/ — following up with tests and seeing where I can help Irving in his part
GSoC – in-depth review of the proposals submitted to the project i’ll be mentoring (About:memory enhancements), student chosen.
bug 812573 Hotfix pushed to prod today!
Some prep work for the Summit Assembly

ttaubert

JSDay in Verona last week, Scotland.JS before that.
Landed a couple of sessionstore code cleanups.
Met with Nick Hurley to talk about speculative connect for sessionstore.
Catching up with (bug) mail.
Reviews.

adw

bug 518606 Troubleshooting Information page should have better support for copy-and-paste to plaintext.
- landed after more discussion on SUMO forum
bug 868793 Loading about:support can trip “ASSERTION: FormatStringFromName() without format parameters”
- landed
bug 856270 Update nsEditorSpellCheck to use nsIContentPrefService2
- first review pass with Ehsan, trying to figure out why test_bug366682.html is intermittent
bug 599804 Highlight all doesn’t work with non HTML documents (e.g. CSS styled XML files)
- reviewed
bug 856595 Intermittent test_wheel_default_action.html
- may know what’s wrong, trying patch on tryserver
bug 555120 Intermittent failure in browser_bug441778.js
- not sure what’s wrong, but patch to bug 856595 may fix this too
bug 873046 Intermittent browser_thumbnails_background.js
- need to investigate
follow-ups to bug 841495 background thumbnail service
- need to work on these
triage

markh

Mainly experimenting with e10s – got things (mainly) working on Windows, got html5 form validation “ported” to the new world order and currently working on form autocomplete.

dolske

Meetings on PICL and First-run
Australis UR stuff starting
pwmgr patches / review (modular/mainthread IO)
Bit of recent activity for modal http auth prompts (bug 613785)

dao

Reviews… Let me know if a patch needs priority.
Monday was a holiday in Germany, catching up on bugmail. I may miss today’s meeting.

mikedeboer

Last week:

worked on search-related bugs that are tracked for Fx 23
worked on Australis bugs that my team mates kindly assigned to me
Async Responsive workgroup meeting: I will add `add_task(Task)` API for Mochi tests bug 872229
Wrote a common JS Assert lib: bug 873126

This week:

work on search-related bugs
work on Australis bugs
work on add_task API
work on Add-ons Manager auto-complete
work on find bar improvements

gijs

Australis
- Make the navbar always visible (bug 870545, bug 752434, bug 872162, filed bug 872446)
- More work on tests (almost there now!) (bug 855683, bug 872578, bug 873449, bug 873534, bug 874028, bug 874051, bug 874070, bug 874371 ).
  - Some of these were repetitive issues where people listen for load events on the <tab> elements rather than their linked <browser>s. Don’t Do That. (I need to blog about this)
- Filed/fixed some polish issues (bug 874448, bug 872463)
- Followup about tab label fadeout (bug 658467)
- Helped divvy up most of the remaining bugs into milestones (may need to do another session?).
- Important discussions regarding the future of the add-on bar (still undecided at this point).
- Reviews

Other
- Tried to help mentor someone for bug 291534, dao said we want a different approach. Probably shouldn’t be a mentored bug in that case, any ideas how to followup here?
- Other bug fixes (bug 874040, bug 874391, bug 872455,

MattN

(travelling during meeting)

Australis
- Landed tab stroke polish
- Landed tab drag indicator positioning
- HiDPI background tabs up for review
- HiDPI foreground tabs in progress
- Tabs in Titlebar positioning for Windows
- tab close buttons
Intern phone screen

mixedpuppy

back from talkilla work week
have patches for selenium webdriver to work with social, a couple minor items left to do
have outline for fx24/25 updates needed to support webrtc providers

Details

Tuesdays – 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
Dial-in: conference# 91337
- US/International: +1 650 903 0800 x92 Conf# 91337
- US toll free: +1 800 707 2533 (pin 369) Conf# 91337
- Canada: +1 416 848 3114 x92 Conf# 91337
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 91337
irc.mozilla.org #fx-team for backchannel
“Firefox” Vidyo Room

Retrieved from “?title=Firefox/Meeting/21-May-2013&oldid=658769“

Meeting Notes: Mozilla Platform: 2013-05-21

Jesper Kristensen — Wed, 22 May 2013 03:00:03 +0000

Notices/Schedule

FF21.0 looks like it’ll stick, congrats! Unthrottling decision will come before the end of the week, checking on FHR server load before enabling full uptake
Firefox 23.0a2 and 22.0b1 were released last week
- https://www.mozilla.org/en-US/firefox/23.0a2/auroranotes/
- https://www.mozilla.org/en-US/firefox/22.0beta/releasenotes/
FF22.0b2 will be going to build before the end of the day (5 weeks from release, 4 weeks till our last change)

Firefox 24 is planned to be the next ESR – keep calm and carry on
Stability work week in late August – we’ll be asking a few engineers to join and help direct upcoming quarters for the Socorro/crash-kill teams

Unresolved Aurora 23 Trackers (non-security, not tracked for Beta)	Unresolved Beta 22 Trackers (non-security)
40 bugs (24 bugs last week)	41 bugs (38 bugs last week)

Key Issues

Mixed content blocker merged to Aurora (tanvi)

Firefox’s Mixed Content Blocker merged from Nightly to Aurora this week.

When an HTTPS page contains HTTP resources, the HTTP resources are
called Mixed Content. With the latest Aurora, Firefox will block certain
types of Mixed Content by default, protecting our users from
man-in-the-middle attackers and eavesdroppers. To learn more about this
feature, check out these links[1].

We are proactively trying to find websites that have compatibility
issues and alert web administrators. For those of you using Firefox
Nightly or Aurora, please let us know if you encounter any sites that
are broken due to the Mixed Content Blocker. You can do this by leaving
a quick comment on one of the following tracking bugs:

Mixed Content Compatibility Issues on Mozilla Affiliated Sites: bug 843977
Mixed Content Compatibility Issues on non-Mozilla Sites: bug 844556

[1]
https://blog.mozilla.org/security/2013/05/16/mixed-content-blocking-in-firefox-aurora/
https://blog.mozilla.org/tanvi/2013/04/10/mixed-content-blocking-enabled-in-firefox-23/

Threads

dev-platform
- Advance warning – Session Restore is changing, will break add-ons (yoric)
- pymake required to build on Windows (gps)
- RFC – Modules for workers (yoric)
- Visual C++ PGO linker memory usage (ted)
dev-webapps
- app: URI scheme (marcos)
mobile-firefox-dev
- Builds break if you update to Android SDK r22 (kbrosnan)

Products/Projects

Firefox Desktop

Australis status updates: https://etherpad.mozilla.org/weekly-australis-checkpoint
Patches for bug 853389 are up for review.

Firefox Mobile

Blog Shout Out: http://lucasr.org/2013/05/17/introducing-the-layout/

Performance, Usability, Features

Landed in Nightly (Fx24): bug 871390 – Leaking Shmem with NoSwap canvas update
bug 862763 – nsLayoutUtils::FontSizeInflationEnabled shows up in profiles, but shouldn’t <== Looks like this change resulted in a ~14% Tp4 (no chrome) improvement for Android
Push API: Blocked waiting for desktop Push API to land; implementing Java background service in the meantime bug 863103
Fixed: bug 828563 – m.here.com GPS not finding correct location on Galaxy Nexus

Stability Wins

bug 866501 – android.content.res.Resources$NotFoundException: Resource is not a ColorStateList (color or path): TypedValue{t=0×2/d=0×1010350 a=<n>}: at android.content.res.Resources.loadColorStateList(Resources.java) mainly on HTC devices running Gingerbread
Another ANR squashed bug 860879 – ANR @ org.mozilla.gecko.PromptService.finishDialog(PromptService.java:470)

Stability

Desktop

bug 869027 Appears to be bouncing between JS and DOM. (Aurora/Nightly)

Mobile

Nom for Aurora?
- bug 866501 – android.content.res.Resources$NotFoundException: Resource is not a ColorStateList (color or path): TypedValue{t=0×2/d=0×1010350 a=<n>}: at android.content.res.Resources.loadColorStateList(Resources.java) mainly on HTC devices running Gingerbread

Beta crashers:
- bug 867058 – java.lang.IllegalArgumentException: bytes.length 0 must be a positive number at org.mozilla.gecko.gfx.BitmapUtils.decodeByteArray(BitmapUtils.java)
  - currently investigated by Dev

release:
- under 2 crashes per ADU! ( ~ 1.5%); next milestone under 1? Can we do it?
- Beyond Flash crashes, database crashers are starting to take the majority of top crash issues :

Android database issues bug 778935 and bug 752828 are still the most serious unsolved issues present on release. Is there additional data we need, or can we at least make the user experience better by catching the errors and presenting a message to the user?

OrangeFactor

Past week’s OrangeFactor: 6.88 and trending downward (Previous Week: 8.66).
Good news, everybody!
- Joel Maher found a workaround for the Android NSS crash (bug 761987). Efforts to find and fix the underlying cause continue in bug 871575.
- Mike Habicher fixed a bug in the AOSP code used by the B2G emulator that fixed nearly all B2G test crashes in bug 867996.
- Bobby Holley landed a patch which fixed one of the most frequent mochitest asserts we were hitting in bug 860941.
bug 856027 (Un-hide WindowsXP opt xpcshell tests when the failure rate isn’t unacceptably high) needs an owner or the tests should be disabled. All logging patches have landed.
New Windows iX test slaves were brought online. Tracking a few new failures, primarily in media code – bug 872748, bug 872760, bug 872788, bug 872996. All are currently unowned.
22 intermittent failures fixed in the last week – List – Thanks!.

Platform Meeting Details

Tuesday 2013-05-21 – 11:00 am Pacific
Dial-in: conference# 98411
- US/International: +1 650 903 0800 x92 Conf# 98411
- US toll free: +1 800 707 2533 (pin 369) Conf# 98411
- Canada: +1 416 848 3114 x92 Conf# 98411
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 98411
Engineering Vidyo Room / Warp Core / SFO-Boardroom / Tor Commons
join irc.mozilla.org #planning for back channel

Retrieved from “?title=Platform/2013-05-21&oldid=658800“

hacks.mozilla.org: Introducing AWSBOX, the DiY PaaS for Node.JS – A Node.js holiday season, part 12

Lloyd Hilaiel — Tue, 21 May 2013 19:44:47 +0000

This is episode 12, out of a total 12, in the A Node.JS Holiday Season series from Mozilla’s Identity team. It’s the last part, and covers awsbox.

Once you’ve written a server in Node.js, how do you deploy it?
Instead of using a pre-existing “Platform as a Service” (PaaS) provider, the Identity team at Mozilla chose to build custom infrastructure atop Amazon EC2, and we’d like to tell you more about it.

Meet awsbox, a minimalist PaaS layer for Node.js applications that’s currently handling nearly two dozen of the non-critical services that we support.
Awsbox was designed to deliver simple, PaaS-style deployment without sacrificing the flexibility of custom infrastructure.

Using awsbox

In order to deploy a Node.JS project with awsbox, you must make some tiny changes to your application, provide your amazon credentials in the environment, and then you can deploy via the command line.

In terms of app changes, you must:

Create an .awsbox.json file that specifies how to start the server.
add awsbox as a dependency in your package.json
ensure your server binds to the port specified in the PORT environment variable

To provide your amazon credentials, you must set AWS_ID and AWS_SECRET in your environment, two values which you can obtain through the amazon management console.

With the initial application configuration complete, you can npm install which will install awsbox, and you’re ready to create your first server:

$ node_modules/.bin/awsbox create -n MyFirstAWSBOX
reading .awsbox.json
attempting to set up VM "MyFirstAWSBOX"
   ... VM launched, waiting for startup (should take about 20s)
   ... Instance ready, setting human readable name in aws
   ... name set, waiting for ssh access and configuring
   ... public url will be: http://<IP ADDRESS>
   ... nope.  not yet.  retrying.
   ... victory!  server is accessible and configured
   ... applying system updates
   ... and your git remote is all set up
   ... configuring SSL behavior (enable)
 
Yay! You have your very own deployment. Here are the basics:
 
  1. deploy your code:  git push MyFirstAWSBOX HEAD:master
  2. visit your server on the web: http://<IP ADDRESS>
  3. ssh in with sudo: ssh ec2-user@<IP ADDRESS>
  4. ssh as the deployment user: ssh app@<IP ADDRESS>

The final step to deploy your application is to git push:

$ git push MyFirstAWSBOX HEAD:master

And now your Node.JS application is hosted and running on an EC2 instance. At this point, you’ve spent about twenty minutes with awsbox. You’ve made minimal changes to your application. You’ve deployed a new server and gotten your application up and running in EC2. Finally, you’ve got an easy way to push changes that fits within your existing workflow (you just git push to a remote).

Now that you have a feel for how you use awsbox and the basic features it provides, let’s take a step back and look at what it actually is and how it works.

awsbox is … A Minimalistic Contract

Any hosting environment has certain expectations of the application that it will be running, the contract. For awsbox this contract includes the following:

What process(es) should be run are specified by the app in .awsbox.json. At its simplest, the file may look like this:

{
  "processes": [ "path/to/myprocess.js" ]
}

What software must be installed is specified by the app in package.json.

Which port to contact the server is delivered to the app via the PORT environment variable.

In building awsbox, a main goal was minimal invention, to make it easy to “port” an existing application.

awsbox is … A Machine Image

During the process of creating an instance, awsbox creates a machine instance from an “Amazon Machine Image”, which results in a running server that’s ready to accept your node.js application, install its dependencies, and run it. The image is built from the Amazon Linux AMI which is a custom linux distribution provided by amazon, and has access to popular rpm-based package repositories via yum. The ID of awsbox AMI is referenced in the awsbox javascript library.

This image is pre-configured with multiple user accounts. ec2-user is an account that has sudo access to the machine. proxy is an account that hosts an HTTP reverse proxy that with a few steps can serve as an SSL terminator to let you support HTTPS without modifying your application. Finally, the app user is the account that hosts all of your application code, your server logs, the server based git repository that you push to, and the git post-commit hook responsible for installing dependencies and starting your server after you push.

awsbox is … Command Line Tools and Libraries

At the time you npm install awsbox, a collection of javascript libraries and a command line tool are installed locally. The command line tool gives you a much faster way to deploy servers than available through Amazon’s web console, and handles most of the complexity of creating an instance in EC2 that is ssh and web accessible.

The awsbox command line tool also provides many command line verbs to perform basic administration of your awsbox, which can be listed with node_modules/.bin/awsbox -h.

The most interesting verb is create, which actually creates a virtual machine.

awsbox is … A Pile Of Features and Hooks

Finally, any non-trivial server requires more than just a Node.JS service. To support the unknown awsbox allows you to specify yum packages that should be installed at instance creation time. For more custom configuration you have two options:

SSH in and do whatever you need to: The goal of awsbox is to let you move as fast as possible, and sometimes the most expedient way to get a new instance of a service up is to perform required steps manually and write a README. But a more repeatable solution is available…

Write scripts to automatically configure software for you: Awsbox has the notion of hooks, which occur at various stages of instance creation or deployment. Using these hooks, it’s possible to configure mysql, install redis manually, or do whatever you need to in order to get your service running.

Is awsbox for Me?

Having a single consistent mechanism of deploying non-critical services has been an incredible efficiency benefit for our team. Collaboration is easier when you have a simple and well defined contract between application and environment. Diagnosis of issues is faster when you have a consistent set of deployment conventions. Finally, moving from experiment to production environment is less costly when an application has all of its dependencies explicitly expressed.

If you are looking for a deployment solution for your own experimental Node.JS services, give the ideas and design of awsbox a careful look.

Previous articles in the series

This was part twelve in a series with a total of 12 posts about Node.js. The previous ones are:

Mozilla Web Development: Firefox Marketplace: May 3rd – May 16th

Andy McKay — Tue, 21 May 2013 19:11:10 +0000

This is a regular post focusing on the status of the Firefox Marketplace.

Total bugs open: 552
Total bugs opened: 298
Total bugs closed: 218

Some specific changes of note:

APIs added for payment status and users permissions (868030 and 868252)
API to allow the setup of payments for apps (869572)
Allow a submission flow that checks app permissions (858306)
Enable the German and Polish translations (868888 and 868594)
Signing in after logging out fixed (869664)
Submitting reviews multiple times fixed (871871)
Webfighter demo gained payments (858289)
Forced issuers for payments re-enabled (850085)
Payments hooked up for the mMrketplace (867729)
Senior Themes reviewer group created (868053)
Move from pyes to pyelasticsearch (857156)
Scroll positions preserved between tabs in the marketplace (868249)
Stop Marketplace reverting to US after a phone reboot (865132)

The new Marketplace consumer user interface was pushed. The Marketplace is now a packaged app that uses the REST API to populate the app. This was a huge change and makes the site faster and more awesome. To checkout the packaged app see the Fireplace app on github.

The Marketplace was also moved out of Aurora status.

hacks.mozilla.org: Firefox Developer Tool Features for Firefox 23

Rob Campbell — Tue, 21 May 2013 09:07:15 +0000

Another uplift has left the building and it’s time to take a look at what’s in Firefox Developer Tools in Firefox 23 currently Aurora, our pre-beta channel. You can download it from the Aurora Download page today. Firefox 23 is currently scheduled to hit the release channel on Tuesday August 6th, 2013.

Episode XXIII is a barn-storming, hair-raising spectacle of incredible epicness that is sure to delight and amuse. If you want a sneak peak at features under active development, give Nightly a try.

Network Monitor

There’s a new tool in the toolbox: The Network Monitor. It’s a classic waterfall timeline view of network activity on a site. This data’s been available since Firefox 4 via the Web Console, albeit in a less visually pleasing way.

Please file bugs under the Developer Tools: Netmonitor component in Bugzilla.

Remote Style Editor

In Firefox 23, you can now edit styles via a Remote Connection on a suitably-enabled device. This should be great help for App Developers interested in testing and debugging styles on a mobile device over the remote protocol in real time.

As of the time of this writing, the Remote Style Editor should be compatible with Firefox for Android version 23, also scheduled for uplift to Aurora. We are working on incorporating the Style Editor Actors for the remote protocol into the Firefox OS Simulator and investigating what it will take to backport them to Firefox OS release.

Options Panel

We’ve added a Gear menu to the Toolbar containing an Options panel for turning tools on or off. As we add more stuff, this is going to be a popular place to manage preferences related to the Developer Tools.

Currently, there are options to turn on the Light or Dark theme for the tools and enable Chrome Debugging.

Initial SourceMap Support for Debugger Protocol

The first pieces of SourceMap support for the Debugger have landed and we are now able to serve up SourceMapped JS files for your debugging pleasure. Soon to follow will be column support for breakpoints allowing you to debug minified JS with a SourceMap.

Watch for the upcoming blog post by Nick Fitzgerald on Hacks explaining the magic.

Variables View Everywhere

Our Variables View is an improved Object Inspector and an integral part of our Debugger. Naturally, we wanted to put it in Everything. So now the Web Console and Scratchpad have a Variables View. Use the ESC key to close it.

Browser Console

If you have Chrome Debugging turned on, check out the Browser Console. It’s a replacement for the ancient Error Console and gives you a Chrome-context command line for executing JavaScript against the browser. It’s nice and should be enabled by default in Firefox 24.

GCLI Appcache Command

We finally have a little something for developers trying to use App Cache to store offline data. A new appcache command for the Graphical Command Line. You can read about it in Mike Ratcliffe’s The Application Cache is no longer a Douchebag.

Web Console in Debugger Frame

The Web Console is now fully-remoted (and has been since version 18). It now makes use of the Debugger’s current Frame if paused on a breakpoint.

Multiple Paused Debuggers

You can now debug multiple tabs at the same time using the Script Debugger. Previously, when attempting to use the debugger on two separate tabs, you’d be given a notification to resume the debugger in the other tab. Now you can debug as many tabs as you like.

There is one caveat to this awesome power, however. Due to the nested event loops each Debugger creates, you have to resume each tab in the order in which they were paused. Debug carefully and always carry a big stack.

You can see a comprehensive list of bugfixes in table form in Firefox 23 Developer Tools Fixes.

Meeting Notes: Mozilla Project: 2013-05-20

Jesper Kristensen — Tue, 21 May 2013 03:00:02 +0000

All-hands Status Meeting Agenda

Items in this section will be shared during the live all-hand status meeting.

Friends of the Tree

The 20+ Firefox OS App Developers who came, built & demo’ed their work at the Bogota Apps Workshop, despite a severe shortage of Geeksphones (awesome photos here): http://cogswells.tumblr.com/

Upcoming Events

Monday, 20 May

WebRTC meetup at the Hacker Dojo in Mountain View, CA at 6:30pm – 8:30pm
- Learn how to build your very first WebRTC web application!
- Feel free to bring a laptop to follow along with the WebRTC application we will build in the presentation

Saturday, 25 May

Firefox OS Camp Cartagena

Next Week

MDN sprint: Friday May 31 and Saturday June 1 in the San Francisco and Paris offices. Bay Area and Paris staff: please join us any time on Friday (or Saturday) to work on code examples or developer docs for your Mozilla product or area of the Mozilla project. More details in the wiki or contact Janet Swisher (jswisher@ or jms in IRC). Volunteers and remote participants are also welcome! See you in #devmo.

WebFWD Applications due June 5! Details and application at http://webfwd.org/apply.

Product Status Updates (voice updates)

Grow Mozilla

Speaker Location: San Francisco

Help us build a history of Mozilla told by Mozillians. Please share your memories about this Mozilla milestone:

July 15, 2003: The Mozilla Foundation is born with start-up support from America Online and Mitch Kapor

Speakers

Presenter	Title	Topic	Location	Share?	Media	More Details
Who Are You?	What Do You Do?	What are you going to talk about?	Where are you presenting from? (Moz Space, your house, space)	Will you be sharing your screen? (yes/no, other info)	Links to slides or images you want displayed on screen	Link to where audience can find out more information
Anika and Dia	Members of the People team	People team IRC channel	irc://irc.mozilla.org#peoplepeople
Kate	Firefox OS Camp Cartagena	IRC: #fxoscamp	wiki: https://wiki.mozilla.org/FirefoxOSLaunchCamp/LatAm2013

Introducing New Hires

New Hire	Introduced by	Speaker location	New Hire location	Will be working on
Peiying Mo	Chris Hofmann	Mountain View	Mountain View	Senior Localization Program Manager
Francesco Lodolo	Chris Hofmann	Mountain View	Brescia, Italy	Localization Engineer
Liza Fox	Shezmeen Prasad	Mountain View	Brighton, UK	Brand Events Team
Simone Sapin	Jet Villegas	Taipei	UK	Software Engineer Platform
Ryan Feeley	Bryan Clark	Mountain View	Toronto	UX Designer
Marc Feeley	Azita Rashed	Mountain View	Mountain View	Research Engineer

Introducing New Interns

New Intern	Introduced by	Speaker location	New Hire location	Will be working on
Ben Brittain	Tim Terriberry	MV	MV	Platform
Brandon S. Kase	Bill Walker	MV	MV	Labs
Eric Atkinson	Dave Herman	MV	MV	Research
Evan Shapiro	Dylan Oliver	MV	MV	FFX OS
Ivan Alagenchev	Tanvi Vyas	MV	MV	Security Eng
Michael Vitousek	Luke Wagner	MV	MV	Research
Shu Hao Wu	Mike Cooper	MV	MV	Web Dev
Tim Kuehn	Dave Herman	MV	MV	Research
Varunkumar Manohar	Anurag Phadke	MV	MV	Metrics
Jack Montgomery	Zhenshuo Fang	SF	SF	UX Design
Ryan Seys	Ben Adida	MV	SF	Identity
Shane Tully	Brad Lassey/Chris Peterson	SF	SF	Platform
Timothy Gaweco	Laura Forrest	SF	SF	Product Marketing, Desktop
Vlad Filippov	Ben Adida/Chris Karlof	SF	SF	Identity

<meta>

Notes and non-voice status updates that aren’t part of the live meeting go here.

Status Updates By Team (non-voice updates)

QA

WebQA

B2G/Gaia testing:
- 3 Inari nodes set up by Stephen and Raymond – thanks
- Gaia-ui-tests v1.0.1 branch tuned by Bob Silverberg and Askeing Yen, now providing automated builds coverage on Jenkins
- Some v1.0.1 bugs found already via the automation suite
- DeviceStorage API change knocked out v1-train testing for 24hrs but back online now after quick response from Mr Hylands https://bugzilla.mozilla.org/show_bug.cgi?id=871956
- Attempted a v1.0.1 automation run against Hamachi but ran into a WiFi bug: https://bugzilla.mozilla.org/show_bug.cgi?id=872510
Firefox Health Report
- Successful Firefox 21 release
- we also fixed a sec bug
- Working with the dev team on hooks for exploratory testing as well as automating the smoke tests – https://bugzilla.mozilla.org/show_bug.cgi?id=872094
Mozillians
- Release slated for this week – https://wiki.mozilla.org/Mozillians/Releases/2013-05-16
- UX redesign is up on dev – stop by and take a look – mozillians-dev.allizom.org/

Dial-in: conference# 8600
- US/International: +1 650 903 0800 x92 Conf# 8600
- US toll free: +1 800 707 2533 (pin 369) Conf# 8600
- Canada: +1 416 848 3114 x92 Conf# 8600
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 8600

Retrieved from “?title=WeeklyUpdates/2013-05-20&oldid=658307“

about:community: How to tell a Mozillian you love them.

mdouglass — Mon, 20 May 2013 23:51:24 +0000

Last week I visited the beautiful city of my birth, Toronto, Ontario, Canada. The purpose of my trip was to visit three potential Summit sites, including a large convention space (because two of the hotels we had our eye one did not have actual event space).

Our first stop was the convention space. It’s was an old building inside of the Exhibition grounds where I spent many summers. The space was huge and sterile and certainly not for us. I could tell right away it just wasn’t right.

And, neither were two of the hotels.

And, then we got to the Sheraton and here’s what was waiting for us:

A lot of foxes, everywhere, all over, as we toured the hotel. Not only was the space amazing, but these guys just got it. In every way. Plus, this hotel is a few blocks from our amazing Toronto space! I was very happy with the experience and am certain the folks who travel to Toronto for the Summit will be in for a treat.

Instantbird: Instantbird 1.4 Released!

clokep — Mon, 20 May 2013 18:19:44 +0000

Log Viewer showing dates in a tree

Get your copy of Instantbird 1.4, hot off the presses! We’ve made a lot of improvements (for full details, see the release notes):

Twitter:

The character counter should now be correct when tweeting links.
Twitter now uses the v1.1 API, this will allow Twitter to continue working past June 11th, 2013 (when the v1.0 API is disabled).

Invalid/self-signed/out-of-date SSL certificates can now be easily overridden for IRC accounts.
Logs are now organized by the date they were created, and smartly folded to easily find recent chats.

As we stated during the Instantbird 1.3 release, this version now requires Mac OS X 10.6 (Snow Leopard). Instantbird 1.4 is based off Mozilla 20 and libpurple 2.10.7, the newest versions available.

You might be asking “What’s next?” for Instantbird; we will be participating in Google Summer of Code 2013 (again through Mozilla). Through this and our other volunteers, we’ll continue improving Instantbird to make it a chat program you love to use. Hopefully we can integrate some cool new features from this year’s Google Summer of Code and finish integrating the Account Import Wizard from Google Summer of Code 2012! As always, if you see any issues, please file bugs!

Mozilla Add-ons Blog: Become a Marketplace App Reviewer!

Amy Tsay — Mon, 20 May 2013 17:08:24 +0000

This post originally appeared on the Apps blog, and we’re re-posting it for the AMO community in case anyone here is interested!

***

A majority of add-ons on AMO are reviewed by volunteer contributors, and they are a big reason why addons.mozilla.org is a safe, thriving place for submitting and downloading add-ons. With the launch of Firefox Marketplace, contributors will again play an important role in helping to shape and nurture a new community.

App reviewers ensure apps submitted to the Firefox Marketplace adhere to security and privacy policies, and meet quality and user experience standards. In return, reviewers enjoy perks such as invitations to special Mozilla events around the world, fast-tracked reviews of their own apps, and cool gear from the incentives program.

You’ll have front-row seats to the apps arriving in the Marketplace, and as one of the first reviewers, you’ll have an opportunity to mentor new reviewers, and have a voice in how the community evolves.

Did we pique your interest? Learn more about the program here, or apply today!

about:community: Milestone: The Mozilla Foundation is born

dboswell — Mon, 20 May 2013 14:42:26 +0000

July 15, 2003: The Mozilla Foundation is born with start-up support from America Online and Mitch Kapor

Share in the comments any memories you have of this event, photos of any t-shirts from this period or any other interesting pieces from this time in Mozilla’s history. The information shared here will help us visually create the history of Mozilla as a community.

Mozilla L10N: Teach yourself L20n at L20n.org

Jeff Beatty — Fri, 17 May 2013 21:40:16 +0000

Language can be very difficult to capture within software localization. Each natural language in the world evolves at its own pace and in its own unique way, creating vibrant and rich means of expression. Sadly, simple static string translation is often ill-equipped to properly accommodate gender, conjugation, plural, or case changes required within the language by changing string variables and other run-time string composition issues. This is why we created L20n.

We’re super happy to announce that we’ve released an amazing tool to help localizers, engineers, and localization tool developers learn and practice L20n themselves! l20n.org contains a real-time text editor that allows you to edit L20n code and visually see how it impacts localization. The real-time editor is part of the “Learn” section of l20n.org dedicated to walk you through what L20n has to offer, feature by feature, and give you a chance to try these features out in real-time.

L20n is a localization framework (comprised of a pseudo-programming language) meant to transfer the ability to localize software using the fullness of any language from the developer to the localizer. L20n empowers localizers to be more independent of source language developers and have more control and flexibility in localizing software according to their native language’s demands.

l20n.org is live and running now! Go give it a try! Not only is it live, but its hosted on github for you to fork and contribute to. Enjoy testing out L20n!

Firebug Blog: Firebug 1.12 alpha 6

Honza — Fri, 17 May 2013 15:22:00 +0000

getfirebug.com has Firebug 1.12 alpha 6

Firebug 1.12a6 fixes 11 issues
Firebug 1.12a6 is compatible with Firefox 20-23

Couple of highlights from this release

Use in Command Line (issue 6422)

This feature allows referring various objects from the command line using new $p variable.

See also detailed description of this feature.

Precision for Console API %f log pattern (issue 6439)

Floats can be rounded by using the %.xf pattern inside the first console.log() argument. Here x denotes the number of decimal places the number should be rounded to.

console.log("amount: %.2f", 4.3852)
will output
amount: 4.39

You may want to get to know about the other patterns available inside the Console API.

Please post feedback in the newsgroup, thanks

Jan ‘Honza’ Odvarko

QMO: Firefox 22.0 Beta 2 Testday, May 24th

Alexandra Lucinet — Fri, 17 May 2013 13:25:29 +0000

Greetings Mozilla contributors,

On Friday, May 24th we are organizing Firefox 22.0 beta 2 testday. We will focus on testing the overall functionality of the browser, with main focus on plugins.

We’ve set up an etherpad with all the details about the event.

No previous testday or testing experience is needed, so feel free to join us on the #testday IRC channel where our moderators will provide guidelines for you and answer your questions.

See you on Friday!

When: May 24, 2013.

BlueGriffon: BlueGriffon EPUB Edition 1.7

BlueGriffon — Fri, 17 May 2013 07:47:00 +0000

I just released BlueGriffon EPUB v1.7 for all platforms. Purchasers of older versions can safely download and install it over their existing install, it will not reset profile or license credentials.

Note to Windows users: you may have to install the MSVC10 Redistributable Package since we moved to VC10. See the download page.

Mozilla Security: Mixed Content Blocking in Firefox Aurora

Tanvi — Fri, 17 May 2013 05:26:49 +0000

Firefox 23 moved from Nightly to Aurora this week, bundled with a new browser security feature. The Mixed Content Blocker is enabled by default in Firefox 23 and protects our users from man-in-the-middle attacks and eavesdroppers on HTTPS pages.

When an HTTPS page contains HTTP resources, the HTTP resources are called Mixed Content. With the latest Aurora, Firefox will block certain types of Mixed Content by default, providing a per-page option for users to “Disable Protection” and override the blocking.

What types of Mixed Content are blocked by default and what types are not? The browser security community has divided mixed content into two categories: Mixed Active Content (like scripts) and Mixed Passive Content (like images). Mixed Active Content is considered more dangerous than Mixed Passive Content because the former can alter the behavior of an HTTPS page and potentially steal sensitive data from users. Firefox 23+ will block Mixed Active Content by default, but allows Mixed Passive Content on HTTPS pages. For more information on the differences between Mixed Active and Mixed Passive Content, see here.

Mixed Content Blocker UI
Designing UI for security is always tricky. How do you inform the user about a potential security threat without annoying them and interrupting their task?

Larissa Co (@lyco1) from Mozilla’s User Experience team aimed to solve this problem. She created a Security UX Framework with a set of core principles that drove the UX design for the Mixed Content Blocker.

When a user visits an HTTPS page with blocked Mixed Active Content, they will see a shield icon in the location bar:

Clicking on the shield, the user will see options to “Learn More”, “Keep Blocking”, or “Disable Protection on This Page”:

If a user decides to “Keep Blocking”, the notification in the location bar will disappear:

On the other hand, if a user decides to “Disable Protection on This Page”, all mixed content will load and the lock icon will be replaced with a yellow warning sign:

When a user visits an HTTPS page with Mixed Passive Content, Firefox will not block the passive content by default. But since the page is not fully encrypted, the user will not see the lock icon in the location bar:

Compatibility
We have a master tracking bug for websites that break when Mixed Active Content is blocked in Firefox 23+. In addition to websites that our users have been reporting to us, we are running automated tests on the Top Alexa websites looking for pages with Mixed Active Content. If you run into a compatibility issue with a website involving mixed content, please let us know in the master bug, or take a step further and contact the website to let them know. Chances are, their website is also broken on Chrome and/or Internet Explorer. Chrome and Internet Explorer also have Mixed Content Blockers, but their definitions of Mixed Active and Mixed Passive Content differ from slightly from Firefox’s definition.

Want to learn more?
Still curious and want to learn more details about the Mixed Content Blocker in Firefox? Check out this more detailed blog post or feel free to ask us questions on mozilla.dev.security.

Software Carpentry: Wrapping Up at UC Davis

Greg Wilson — Fri, 17 May 2013 00:00:00 +0000

Jenna Lang has posted a great wrap-up on the boot camp at UC Davis — with Python cookies!

Software Carpentry: Experiences with the Oxford DTCs

Mike Jackson — Fri, 17 May 2013 00:00:00 +0000

Mario Antonioletti has posted his experiences on being a first-time instructor at our boot camp for the Oxford doctoral training centres, our second in Oxford, last week.

Mozilla IT: RFO: DNSSEC Resolution failures (mozilla.org) 20130515@1800 PDT [872818]

mrz — Thu, 16 May 2013 22:27:47 +0000

On May 15 at 1800 PDT Nagios alerted the start of sporadic DNS resolution failures. This post summarizes the events, the impact and specific steps Mozilla IT is taking to avoid future disruptions of this nature.

This post is intended to be technical in nature. DNSSEC is fairly technical and DNSSEC failures tend to be similarly technical. As we’ve done before, we hope to share the failures we encounter in production so you don’t have to experience the same.

SUMMARY

An SOA mismatch between SVN and the nameservers was caused by the DNSSEC signer refusing to sign with an expired ZSK. This was misdiagnosed as a KSK issue, leading to a DNS outage for DNSSEC-verifying resolvers.

DETAILS

In the afternoon of May 15, the nameservers refused to load SOA update 2013051500 for the mozilla.org DNSSEC-signed zone.

Investigation found that the DNSSEC signer was refusing to sign the zone, providing only the error “fatal: cannot find SOA RRSIGs“. In hindsight, this undocumented error indicates that the zone’s ZSK has expired.

Mozilla’s domain registrar publishes DS records for the mozilla.org KSK. When the expired key was found at 16:44, it was misunderstood to be a KSK, rather than a ZSK. A new KSK was generated and its DS record added to Mozilla’s domain registrar.

The new KSK did not resolve the signing errors. Mozilla’s domain registrar was found to rate-limit DS record changes, preventing the new KSK from being reverted. DNS lookups began showing invalid DS records from Mozilla’s domain registrar, but this was later found to be internal DNS only.

After examining the keys (both current and expired) more closely, the expired key was found to be a ZSK, rather than a KSK. Renewing the ZSK fixed the DNSSEC signer. The mozilla.org SOA 2013051500 was signed by both KSKs and the new ZSK, and then published.

Comcast users began reporting DNS resolution issues of mozilla.org, complicating access to various Mozilla properties. DNSSEC validation tools showed unexpected issues with the signed mozilla.org zone.

The DS records were confirmed to be correct externally, so the mozilla.org zone was re-signed without the old KSK, leaving only the new KSK and new ZSK. This resolved the validation issues for reasons unknown, and Comcast users reported DNS working correctly again.

Bugs have been filed to document the KSK/ZSK renewal process, to monitor the expiration times of those keys, and to monitor that the zones validate.

BUGS

872818: mozilla.org SOA mismatch, DNSSEC signer refusing to sign
872831: alarm when DNSSEC signing keys are expiring soon
872884: document ZSK and KSK renewal/rollover process
872832: regenerate mozilla.org DNSSEC ZSK (resolved)
872885: regenerate mozilla.org DNSSEC KSK (resolved)
872927: monitoring: add full validation of DNSSEC zones

TIMELINE (PST8PDT, UTC -0700)

15:32 – SOA mismatch detected between nameservers 2013051402 and svn 2013051500.
16:03 – Found DNSSEC signer refusing to sign mozilla.org 2013051500
16:44 – Found expired key preventing signing of mozilla.org
16:52 – Added new KSK to Mozilla’s domain registrar alongside existing KSK to renew expired key
17:06 – Found that expired key was ZSK, not KSK as previously thought.
17:27 – Signed mozilla.org with both KSKs and new ZSK
17:45 - Mozilla’s domain registrar publishing incorrect hash for new KSK (misleadingly, for internal lookups only)
18:00 – Comcast users reporting sporadic DNS resolution failures
18:20 – Validation issue found with signed zones
18:25 – Signed mozilla.org with new KSK and new ZSK
18:30 – Comcast users reporting DNS resolving successfully
18:35 – Validation issue confirmed resolved

NOTES

ZSK and KSK are “zone signing key” and “key signing key” for mozilla.org. DNSSEC permits multiple KSKs and autoselects the latest ZSK. We sign with a single KSK, outside of 17:30-18:25 above.
There is no filesystem difference between ZSKs and KSKs. The distinction is the word “zone” or “key” in the comment in the first line of the keyfile.

hacks.mozilla.org: Building a Notes App with IndexedDB, Redis and Node.js

Jennifer Fong-Adwent — Thu, 16 May 2013 21:03:33 +0000

In this post, I’ll be talking about how to create a basic note-taking app that syncs local and remote content if you are online and defaults to saving locally if offline.

Using Redis on the server-side

When adding records in Redis, we aren’t working with a relational database like in MySQL or PostgreSQL. We are working with a structure like IndexedDB where there are keys and values. So what do we need when we only have keys and values to work with for a notes app? We need unique ids to reference each note and a hash of the note metadata. The metadata in this example, consists of the new unique id, a creation timestamp and the text.

Below is a way of creating an id with Redis in Node and then saving the note’s metadata.

// Let's create a unique id for the new note.
client.incr('notes:counter', function (err, id) {
 
...
 
    // All note ids are referenced by the user's email and id.
    var keyName = 'notes:' + req.session.email + ':' + id;
    var timestamp = req.body.timestamp || Math.round(Date.now() / 1000);
 
    // Add the new id to the user's list of note ids.
    client.lpush('notes:' + req.session.email, keyName);
 
    // Add the new note to a hash.
    client.hmset(keyName, {
      id: id,
      timestamp: timestamp,
      text: finalText
    });
 
...
 
});

This gives us the following key pattern for all notes on the server-side:

notes:counter contains all unique ids starting at 1.
notes:<email> contains all the note ids that are owned by the user. This is a list that we reference when we want to loop through all the user’s notes to retrieve the metadata.
notes:<email>:<note id> contains the note metadata. The user’s email address is used as a way to reference this note to the correct owner. When a user deletes a note, we want to verify that it matches the same email that they are logged in with, so you don’t have someone deleting a note that they don’t own.

Adding IndexedDB on the client-side

Working with IndexedDB requires more code than localStorage. But because it is asynchronous, it makes it a better option for this app. The main reason for why it is a better option is two-fold:

You don’t want to wait around for all your notes to process before the page renders all elements. Imagine having thousands of notes and having to wait for all of them to loop through before anything on the page appears.
You can’t save note objects as objects – you have to convert them to strings first, which means you will have to convert them back to objects before they are rendered. So something like { id: 1, text: 'my note text', timestamp: 1367847727 } would have to be stringified in localStorage and then parsed back after the fact. Now imagine doing this for a lot of notes.

Both do not equate to an ideal experience for the user – but what if we want to have the ease of localStorage’s API with the asynchronous features of IndexedDB? We can use Gaia’s async_storage.js file to help merge the two worlds.

If we’re offline, we need to do two things similar to the server-side:

Save a unique id for the note and apply it in an array of ids. Since we can’t reference a server-side id created by Redis, we’ll use a timestamp.
Save a local version of the note metadata.

var data = {
  content: rendered,
  timestamp: id,
  text: content
};
 
asyncStorage.setItem(LOCAL_IDS, this.localIds, function () {
  asyncStorage.setItem(LOCAL_NOTE + id, data, function () {
    ...
  });
});

The structure of the IndexedDB keys are very similar to the Redis ones. The pattern is as follows:

All local ids are saved in a localNoteIds array
All local note objects are saved in note:local:<id>
All remote/synced ids are saved in a noteIds array
All remote/synced note objects are saved in note:<id>
Local notes use a timestamp for their unique id and this is converted to a valid server id once Redis saves the data

Once we’re online, we can upload the local notes, save the remote ones on the client-side and then delete the local ones.

Triggering note.js on the client-side

Whenever we refresh the page, we need to attempt a sync with the server. If we are offline, let’s flag that and only grab what we have locally.

/**
 * Get all local and remote notes.
 * If online, sync local and server notes; otherwise load whatever
 * IndexedDB has.
 */
asyncStorage.getItem('noteIds', function (rNoteIds) {
  note.remoteIds = rNoteIds || [];
 
  asyncStorage.getItem('localNoteIds', function (noteIds) {
    note.localIds = noteIds || [];
 
    $.get('/notes', function (data) {
      note.syncLocal();
      note.syncServer(data);
 
    }).fail(function (data) {
      note.offline = true;
      note.load('localNoteIds', 'note:local:');
      note.load('noteIds', 'note:');
    });
  });
});

Almost done!

The code above provides the basics for a CRD notes app with support for local and remote syncing. But we’re not done yet.

On Safari, IndexedDB is not supported as they still use WebSQL. This means none of our IndexedDB code will work. To make this cross-browser compatible, we need to include a polyfill for browsers that only support WebSQL. Include this before the rest of the code and IndexedDB support should work.

The Final Product

You can try out the app at http://notes.generalgoods.net

The Source Code

To view the code for this app feel free to browse the repository on Github.

Firefox Flicks: Firefox Flicks 2013 Staff Pick - Tobi

Thu, 16 May 2013 15:24:10 +0000

“I’m Tobi, part of the Firefox Flicks team. I work on the project in general and I help the community with their activities around Flicks 2013. I chose Scooter from the USA as my pick.

The idea seems a bit odd first of all. But I like it. The video is nicely produced as well. It gives a quite different perspective on things. I respect it a lot when people from older generations are still exploring new technologies. Actually it looks like he has a jailbroken iPhone running FirefoxOS. That’s bad ass. I can understand that when you get older you might not always want to go with the latest “trends” anymore. You might be tired of that. It’s a pitty. Mobile computing is really something that can make everyones’ life a little easier, no matter if you’re young or old. This man is doing everything right.

Having seen all the Flicks entries so far, I think we can be really happy about having such an engaged community. It takes a lot of effort to create a submission, so I already wanted to say thanks to everyone who contributed to far!”

Mozilla User Research: Herding UX: How to Plan a Workshop for a Diverse Creative Team

Larissa — Thu, 16 May 2013 05:12:27 +0000

A few weeks ago, the entire User Experience Team came together for our UX Summit to reflect on our work and our organization. As part of the week’s activities, I planned and led a day-long workshop around the goal of creating and shipping products that our users love.

Running a successful workshop for a large group of designers, researchers, prototypers, and UX managers who work on different products in Mozilla can be quite a challenge. This is my reflection on how I tried to help a diverse group such as ours discuss common challenges and begin creating a shared process.

Plan activities that are relevant to each person’s work

This suggestion seems obvious, but it’s often overlooked in many workshops, especially ones led by those who don’t know the participants well. It’s not uncommon to learn new skills in a great workshop then realize later on that you have no clue how to integrate that learning into your own product process.

I wanted to make sure that my colleagues would walk away feeling like they had something tangible to take back to the product teams they work with. Thus, many of my activities began with individual (or small team) reflections where I asked everyone to apply a framework or process I put together to their own product experiences. This approach provided us with some common tools and language to evaluate our impact as a UX team, while allowing each person to introspect on his or her own work.

Individual worksheets help our diverse team reflect on specific projects while discussing informally

Not everyone has to speak up to be an active participant

I’ve never liked workshops where each participant is forced to share, one after another. I understand the reasons for doing so (such as allowing each person to be heard, not just the majority voice), but it’s hard to scale this approach, introverts hate being required to speak up, and everyone’s answers tend to be verbose variations on the same theme. Besides, with a diverse organization such as ours, things that are meaningful to one product team can be irrelevant to another.

I still had a large group discussion at the end of each activity, but rather than asking everyone to report out, I made sure that it was only one of multiple ways that people could voice their thoughts and observations to the rest of the team. During the individual reflection portion of an exercise, participants had worksheets that they could fill out alone or talk to others about as they saw fit. This task gave people the opportunity to reflect specifically about the issues they cared about. Afterwards, I also asked each person to contribute their thoughts (on post-its or name tags) to a large group visualization. These maps gave everyone a chance to share their point-of-view and quickly see the bigger organizational picture from everyone else’s contributions.

In the end, I think the balance between reflecting on individual team needs and visualizing patterns within the larger UX organization created a richer discussion about issues that were relevant to the entire group.

About 40 participants share their ideas quickly through a group map

Scaffold difficult tasks (don’t shy away from them)

Not every activity in a workshop is going to be easy to explain or easy to do. Some activities are hard because they tap into uncomfortable/sensitive team issues. Others require complex thinking that cannot be compressed into the time you have for the workshop.

For my workshop, I wanted to do a particular activity that I knew was challenging but useful in the long run. So I tried to break it down into smaller tasks that were easier to understand. I also provided written instructions, examples, and worksheets to help my colleagues get started. Despite my preparation, people were still fairly confused in the beginning, but I persisted in explaining the task and why the activity was important, until eventually everyone tried it out. Later on, some participants told me that this challenging activity was one of the most useful components of my workshop for them.

Don’t shy away from activities that challenge the team; they often lead to the most meaningful changes. Instead, acknowledge the difficulty of what you’re asking people to do, give them enough time to do it, and (as cheesy as it sounds) have faith in your team’s ability to figure it out.

Practical Tip: I scheduled my hardest activity about an hour before lunch so that everyone had time to wake up but weren’t sluggish from having eaten or exhausted from thinking. I think the promise of a lunch break encouraged people to power through the challenging task. (Just don’t end late for lunch, or else you will have some very unhappy participants!)

C’est La Vie

I’m a planner so I spend a lot of time preparing for the workshops I lead. Planning the right activities and making sure they run smoothly ensure that a workshop meets its goals and isn’t just a waste of time for everyone involved.

But it’s also important to remember that a successful workshop isn’t one where you hit every bullet point in your agenda; it’s one where the participants get something valuable out of the time they spend with you. As a facilitator, you have to be responsive to the needs of the group as the workshop progresses. Let the discussion go longer if everyone’s energy seems to be there. Cut the activity short if people look like they’ve checked out. If it seems like the group isn’t getting to insights, modify the activity on the fly so that they do.

During breaks and individual activities, I like to get the temperature of the room by talking to individuals and seeing whether they still find the exercises relevant for their particular group. As much as I try to plan beforehand, my activities can still be slightly biased towards an interaction designer’s perspective. It’s important that I check my own assumptions about what other disciplines within the UX team need.

During breaks, people wandered over to the group maps and shared their insights informally

As a parting thought, remember that your workshop isn’t and shouldn’t be the only opportunity you have to accomplish whatever goals you set. Instead, it’s a starting point for later conversations and activities with individuals and smaller teams. The art of facilitating the workshop is in figuring out where to focus the group’s energy so that you build that great starting point for change to ripple through your organization.

Software Carpentry: Stanford Bootcamp Recap

Ariel Rokem — Thu, 16 May 2013 00:00:00 +0000

On May 6th-7th, we hosted a bootcamp at Stanford University. Participants were students, post-docs and staff affiliated with the Center for Neurobiological and Cognitive Imaging and the Neuroscience Graduate Program and both units provided support for the workshop. Bob Dougherty, the research director at the CNI, helped raise a substantial portion of the funds to support the boot-camp (coffee!) and Prof. Miriam Goodman, from the Department of Molecular and Cellular Physiology, helped to get the neuroscience program on board and to secure additional funding from that program. Prof. Goodman was a participant in a SWC boot-camp at Berkeley last year and was eager to get SWC to Stanford. Instructors were Paul Ivanov, Bernhard Konrad and myself.

Considering that the students were a rather homegenous group in terms of their scientific interests (the brain!), there were a variety of backgrounds in terms of their knowledge about computers. Matching instruction to the level of knowledge (based on a pre-workshop questionnaire) was a challenge. As were installation issues that plagued the first day. A large majority of participants failed to follow the instructions provided by the Anaconda Python distribution to configure their bash shell environment. I guess that just goes to show that they needed the workshop.

The instruction followed the standard boot-camp plan for most of the two days: unix shell, version control with git, python programming, and so forth. In the last two-hour session of the work-shop we conducted a little experiment. Adapting a lesson plan from Justin Kitzes' recent UC Berkeley bootcamp, we taught a session aimed at teaching the students how to combine all the components of the previous parts (shell, git and programming) to create a reproducible research project. To make things more interesting, we used a publically available neuroscience data set. We demonstrated how one would load the data from the files comprising this data-set into an IPython notebook and performed a rather basic calculation on it, visualizing various quantities as we went along.

Demonstrating one possible work-flow, we started by working interactively in the notebook, exploring the data as we went along. We demonstrated how bits of an exploratory data analysis session can turn into function definitions. Then, we showed how you would write modules based on these function, tests for the modules, commit them as a git repo and start putting together a push-button analysis. We reached the end of all this a little bit out-of-breath and it is not obvious that everyone managed to follow through every step of the session, but I do believe that the most important point came across: reproducible research is important and, with the help of the tools we teach, eminently possible.

We used this etherpad to comminucate with students througout the workshop and to gather feedback at the end of each half-day. You can see a list of the participants at the top and the feedback strewn throughout. At the very end of the workshop, we asked them to write down their feedback for the entire workshop. Many took the time to write some thoughtful comments (for which we are grateful!). I have selected a couple of interesting points from the feedback we got. This one is quite encouraging:

great workshop. i appreciated the backround and theory as well as the more practical examples. i think you did a nice job presenting this information to students of various levels. might be helpful to make it clear what level this class is for - some people had no coding backround, others were quite experienced. maybe a quick survey in the beginning and maybe some work in groups to accodmidate the different levels. i really appreciated your humor and positive attitude:)

On the other hand, this one is a bit discouraging:

I'm very grateful that you all volunteer your time to do this. But, I think you can/should be paid for it. There's money around for such things, many of our PIs would be happy to fork up a few hundred bucks, and in general I think the culture of doing good work for free in academia is deleterious to our collective financial well-bring.+4

The '+4' at the end of that comment represents the fact that four additional people expressed their support to that point. I wonder whether this notion is due to the local hyper-capitalistic culture surrounding Stanford, and I am curious to hear what other instructors think about this. My personal response, also in line with some other aspects of the local culture, is that Software Carpentry is just one more way to create more value than we capture.

When the workshop was over, Paul, Bernhard and I took a long walk. Prof. Goodman had kindly invited us to her house in Menlo Park for post-workshop pizza and socializing. On the way over, we took the opportunity to go over the sessions one-by-one and reflect on them. For each session, each one of us in turn said what they think worked and what didn't work. It was very useuful to get feedback from the other instructors, to rehash the mistakes and the successes and to be able to imagine what we would do differently in future workshops. One of the main sentiments in the air was that we were not sure whether we had really managed to "seal the deal", to get students to actually start using the things we had shown them in their day-to-day life. Fortunately, I have the email addresses of participants. In a couple of months, I will circle back and ask them to fill another set of evaluations and (assuming anyone responds) see whether they have adopted any of it into their day-to-day research life.

Software Carpentry: Announcing Hack4ac

Greg Wilson — Thu, 16 May 2013 00:00:00 +0000

Hack4ac is a one-day hackathon in London, England, on July 6. Its goals are:

Demonstrate the value of the CC-BY licence within academia. We are interested in supporting innovations around and on top of the literature.
Reach out to academics who are keen to learn or improve their programming skills to better their research. We're especially interested in academics who have never coded before.

It looks like fun—if you're in the area and interested in getting involved, they'd be happy to have you there.

Mozilla Add-ons Blog: Add-ons Update – Week of 2013/05/15

Jorge Villalobos — Wed, 15 May 2013 21:22:51 +0000

I post these updates every 3 weeks to inform add-on developers about the status of the review queues, add-on compatibility, and other happenings in the add-ons world.

The Review Queues

Most nominations for full review are taking less than 3 weeks to review.
Most updates are being reviewed within 1 week.
Most preliminary reviews are being reviewed within 1 week.

These stats are taken from the last queue report:

88 nominations in the queue awaiting review.
59 updates in the queue awaiting review.
57 preliminary review submissions in the queue awaiting review.

If you’re an add-on developer and would like to see add-ons reviewed faster, please consider joining us. Add-on reviewers get invited to Mozilla events and earn cool gear with their work. Visit our wiki page for more information.

Firefox 21 Compatibility

The compatibility blog post for Firefox 21 is up, and the the compatibility bump for AMO add-ons was run last week. Firefox 21 was released yesterday, so all compatibility updates should be uploaded to AMO as soon as possible, if they haven’t been already.

As usual we recommend using the Aurora and Beta branches to test your add-ons ahead of time.

ESR Compatibility

There are a couple of compatibility issues that are related to the ESR and other business deployments that are worth mentioning:

In Firefox 21, certain folders in the Firefox install directory where moved under browser/. You can read more about it on this bug. This affects installers that drop add-ons or other customizations in the install directory.
We’re planning on changing the version number scheme for ESR releases. The idea is that, if we have ESR 24, ESR version 24.1 would be the security upgrade that corresponds to Firefox 25. This way it is easier to associate an ESR version with its mainline equivalent in security patches. For add-ons, this means that maxVersions should always be in the form 24.*, rather than 24.0.*. This is especially important for add-ons with binary components, which don’t have default compatibility.

Hive Learning Network NYC: Webmaking as Connected Learning

ldecoursy — Wed, 15 May 2013 19:29:56 +0000

This is re-posted from Matt Thompson’s blog. Connected Learning wants to revolutionize the way people learn. How can Webmaker be a part of that movement? These new resources on Connected Learning are highly recommended reading for anyone interested in the … Continue reading →

about:community: Letting go to make room for what’s next- New thoughts on Knowledge Share

Dia Bondi — Wed, 15 May 2013 19:20:50 +0000

Change. For some it’s a bad word. For some it’s exciting. Lately I’ve been stuck, and now I see that change was the next step to stuck. I had to get stuck in order to change. Change will take some letting go.

So what’ the change? Capture Mozilla is Air.Mozilla too. Duh you say? Sounds simple! Simple yes, easy no. Capture Mozilla was a brain child of mine born from the need to scale knowledge and know how, not in the form of formal training, but in the voice of the Mozillians who are sharing. Here are some things I’m learning that lead to a (change) wider view of knowledge share:

1) Ownership matters.

When we build a video, either really scrappy or really produced, we want some ownership. Maybe we don’t want to hand it over to the Capture Mozilla project. Maybe we want to share it, but curate it from a place that is our own, that we have ownership in.

2) It’s hard to know what’s C-Mo.

There are 4 distinct channels for Capture Mozilla. Well, what if YOUR knowledge share doesn’t fit? Do we cram you into the C-Mo box? Do we shape your share into the C-Mo mold? No. We follow you. Like Mozillians ourselves, there are many variations of video knowledge share and putting us in a box is limiting.

3) Making your own box makes sense.

Maybe your knowledge share fits into a C-Mo box. Maybe you and your group or initiative, or subject deserves it’s own box. And that box comes in the form of channels. Checkout Air.Mozilla channels and see what I mean. They are in their infancy and can only grow with your participation. Someone’s got to go first, it could be you.

Notice all the “maybe’s” in my post? That’s because I’m still thinking. Less stuck, at the beginning of change and thinking of all the “what’s possible” and “maybe’s”. What I do know now is that Capture Mozilla is a project, not a place. Making implicit knowledge explicit though video storytelling can and does happen in channels too. By the way, changing the thrust of my work takes some letting go. And that hurts a little. Change, there’s that work again.

And so now I see that the first iteration of Capture Mozilla was the baby version. The version that said all short videos live here. The idea of Capture Mozilla is growing up and it’s next stage is the freedom of channels.

It’s a project, an intention, not a place. Whew.

“So, in a given time frame, plan to achieve something worthwhile in half the time, throw it away, then rebuild what has to be a better version, given the advantages of hindsight.” – from an essay in the MythicalManMonth

about:community: Grow Mozilla discussion this Thursday

dboswell — Wed, 15 May 2013 16:30:45 +0000

If you’re interested in helping people get involved with Mozilla, join us tomorrow to discuss community building at Mozilla.

Time: Thursday, May 15 at 10:00 AM Pacific / 17:00 UTC
Agenda: Identifying core contributors, community building functionality priorities and more
Video: David Boswell’s vidyo room (link for guest access is on agenda)
Audio (if vidyo doesn’t work): 1-800-707-2533, pin: 369, conf: 9634#
Room: Get to da Choppa in Mountain View 3rd floor and Transamerica Pyramid in San Francisco 3rd floor
Backchannel: irc.mozilla.org#mozillians

Firefox Flicks: What Can You Win? — Firefox Flicks 2013 Prizes

Wed, 15 May 2013 15:54:28 +0000

You’ve spent days and nights planning the perfect flick. You’ve called in all your personal favors and created a winner. But what does winning Firefox Flicks actually get you? Fame, (a modest) fortune and opportunities to work with film industry luminaries — all this and more. We’re really excited to give you more details on the fantastic prizes you can win this year.

Just for participating, you’ll receive an exclusive, limited edition Firefox Flicks sticker sheet that was designed for the 2013 competition. That’s a little thank you from us. Keep reading for all the details.

People’s Choice Awards

People’s Choice is a new award category this year and will include flicks chosen by the public. The three People’s Choice winners will receive a limited edition Flicks 2013 prize package and have their videos promoted on our channels. They’ll also be featured in the Flicks gallery on Givit and on MovingArt channels.

Early Entry Awards

This year, we’re choosing three Early Entry Award winners. Each winning team will receive $1000 USD and have their flick promoted on our channels. They’ll also get a special edition 2013 prize pack and will automatically qualify for one of the 40 finalist spots.

The 40 Firefox Flicks finalists will have their films evaluated by our panel of judges and all finalists will receive SnagIt and Camtasia software licences from TechSmith (one per person).

Finalists

From the 40 finalists, the judges will choose four regional runners-up, four regional winners and a Grand Prize winner.

Regional Winners

The four regional runner-up teams will each receive $2500 USD, a one-year Shooting People membership for each team member, a special edition Flicks 2013 prize package and have their flick promoted on our channels.

The four regional winner teams will each receive $5000 USD, a one-year Shooting People membership for each team member, a limited edition Flicks 2013 prize pack and have their flick promoted on our channels. Their videos will also be featured in the Flicks gallery on Givit and on MovingArt channels. Additionally, the four regional winners will be flown to Toronto, Canada, for the 2013 Toronto International Film Festival for the award ceremony and celebration.

Grand Prize Winner

Finally, there is the Grand Prize winner. Make sure you’ve got your passport ready, because the Grand Prize winning team will fly to Los Angeles to work with Flicks judges Couper Samuelson (Producer) and Franklin Leonard (Founder, Black List), as well as representatives from Panavision, to professionally produce their winning entry using a comprehensive Panavision digital camera package. If timing allows, the winning team will also get a two-day training session at the Dolby Institute in LA, as well as an invitation to a movie premiere and after-party at the Dolby Theater.

The Grand Prize winner will also receive a one-year Shooting People membership for each team member, a limited edition Flicks 2013 prize pack and have their flick promoted on our channels. Their videos will also be featured in the Flicks gallery on Givit and on MovingArt channels. Additionally, the Grand Prize winner will be flown to Toronto, Canada, for the 2013 Toronto International Film Festival for the award ceremony and celebration.

Sound amazing? Want to win? You still have a few weeks to get your flick in for the next round of Early Entry Awards and before the contest closes on July 31, 2013.

The Den: Spring Theme for Firefox

ccollins — Wed, 15 May 2013 09:54:06 +0000

In the Northern Hemisphere, spring has sprung! People are basking in longer days, excited to be able to spend more time outside and taking time to smell the blooming flowers.

Speaking of flowers, there’s a featured Firefox theme that will be sure to make your browser bloom — it’s called Fine Fractal Flower. Even if it’s not spring where you are, this nature-inspired theme is sure to make you smile.

Here’s what the theme looks like:

And what it looks like once installed:

If this theme isn’t for you, there are thousands more available!

Meeting Notes: Firefox Status: 2013-05-14

Jesper Kristensen — Wed, 15 May 2013 03:00:12 +0000

General Topics

Work week agenda

Friends of the Firefox team

Give a shoutout/thanks to people for helping fix and test bugs.

mconley giving a shoutout to ge3k0s (Guillaume C.) for keeping us on our toes in Australis land. He’s doing great work filing bugs and catching regressions.

Stand ups

Suggested format:

What did you do last week?
What are working on this week?
Anything blocking you?

Please keep your update to under 1 minute!

gavin

reviews
work week organization
new hire stuff

next week

actually followup on test pilot
more work week/hiring

felipe

AddonRepository bug 853389: feedback from Blair implemented and going through tests now, met with Irving to discuss file writing stuff and with Irving and Mossop to discuss downgrade concerns
Fixed intermittent bug343515.js orange (bug 765192)
Reviewed all 31 GSoC applications once and two-pass reviews on the project I’m gonna mentor

markh

Landed a couple of “panel” features and patches to make Social use them.
Landed the async form history patch after fixing an orange which caused it to be backed out.
Getting my head around the e10s work and made a start on moving the form observer and autocomplete to an out-of-process message-based model.

mconley

Jamun branch is dead – Australis work is happening solely on UX branch now.
As per UX request, I’ve moved the star button back into the URL bar for now while I work on the new bookmark widget for Australis. Merged this change into UX.
Fixed strange appearance of popups on OSX
Been tackling randomly failing tests under browser/base/content/test. Very frustrating.
Laid out a rough roadmap for the rest of the Australis work – viewable from line 330 onwards here.
Started conversations with ZER0 from the Jetpack team about Australis impacts to the SDK
Lots of reviews

mikedeboer

Last week:

Findbar related bugs: bug 257061, bug 869543, bug 565552
- bug 776708 thoroughly reviewed by Dao… thank you sir!
Consolidating Search related bugs: bug 862401, bug 860560, bug 867742
Tried to take as many Australis related bugs as Mike-ingly possible
Async/ Testing tracking bugs: bug 870774 and bug 867742

This week:

take as many Australis related bugs as…
Async perf meeting

gijs

Last week:

One public holiday
Australis
- bug 855683 (JP tests) and bug 869939 (migrate stuff from addon bar to navbar) – blocked on decisions regarding addon-bar removal, talked with jetpack folks and mconley, posted to fx-dev, waiting on finalizing discussion there + ux feedback
- landed bug 853083 (tabs left margin on windows without the app button)
- lots of stuff about bug 853415 (weird overflow bug), seems we’re now going to able to fix it by never hiding the navbar
- Started work on never hiding the navbar in bug 870545 and bug 752434.
- behind the scenes stuff about bug 658467 (tab label fadeout rather than ellipsis), looking hard to make work in a performant manner
Other
- landed bug 865316 (polish for OS X menubuttons)
- still waiting for reviews on Fx reset tab restoring, and UX response from Limi on whether we care enough about tab groups

This week:

More Australis customization stuff (navbar, tab scrollbar fixes after that’s done)
Want to tackle UX orange/red and get it just as green as the trees outside my window.

MattN

Last week:

all Australis, all the time
- bug 858089 = Tab stroke polish is very close. Little issues keep popping up.
- Australis OS X LWT landed
- Bug triage
Intern phone screen

Finish bug 858089 = Tab stroke polish
Fix bug 864608 – Tab drag placeholder
bug 857886 – HiDPI OS X tabs
More Australis follow-ups
Review Gijs’ clip-path patch

jaws

This past week:

Gave a presentation at Mobile Monday Detroit
- Should have a video of the presentation uploaded to YouTube and blogged about
The UI for customization mode is near-finalized for Windows, OS X, and Linux. Some minor bugs here and there.
The location bar and search container now have a minimum width (on UX)

This week:

Look at GSoC proposals
Work on toolbar overflow for Australis
Lots of smaller but nice wins for Australis to work on (bug 870865, bug 870866, bug 870869)
Add some more functionality to the History widget (Clear recent history…, etc)

UX Updates

lco

Back from vacation, trying to catch up!
How many sites is Mixed Content actually breaking?
- short answer: not that many
- investigation here: https://bugzilla.mozilla.org/show_bug.cgi?id=844556
- Mostly sites with CSS are breaking, a couple of big notable ones– can we reach out to them in some way?

Details

Tuesdays – 10:00am Pacific, 1:00pm Eastern, 17:00 UTC
Dial-in: conference# 91337
- US/International: +1 650 903 0800 x92 Conf# 91337
- US toll free: +1 800 707 2533 (pin 369) Conf# 91337
- Canada: +1 416 848 3114 x92 Conf# 91337
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 91337
irc.mozilla.org #fx-team for backchannel
“Firefox” Vidyo Room

Retrieved from “?title=Firefox/Meeting/14-May-2013&oldid=655845“

Meeting Notes: SeaMonkey: 2013-05-14

Jesper Kristensen — Wed, 15 May 2013 03:00:05 +0000

Agenda

Who’s taking minutes? -> Ratty
Nominees for Friends of the Fish Tank TBA

Action Items

(who needs to do what that hasn’t been recorded in a bug) We should assign people to the open items.

NEW

OPEN

Need to reward the nominees of the friends of the fish tank from this year!

CLOSED

Status of the SeaMonkey Buildbot Master and Tree

No Windows langpacks since 8th April on trunk. Needs investigating.
- Comment from mcsmurf on this: Not clear what is meant by this, please clarify. xpi/win32/ folders on FTP server look fine. Also file a bug if something needs to be investigated/fixed.
The Java on Linux bug has been tracked down to being due to our (SM’s) build config. Basically our RelEng team needs to check whether we can switch to linking libstdc++ dynamically, like FF and TB do. See: bug 754622 Oracle/Sun Java jre1.7.0_04 and later does not work in SeaMonkey.
- In the mean time, InvisibleSmiley has added the workaround to the 2.17 and 2.18 release notes.
Tinderbox is going to be EOLed. We need to move the SeaMonkey tinderboxpushlog off.
- Mostly done now, just a few loose ends.
- Callek has gotten up and running a newer version of TBPL (that doesn’t depend on tinderbox) for testing. This will be deployed eventually to replace the current TBPL code we are running.
- Mcsmurf needs to talk to Callek to see if tbpl can get more memory (some PHP(?) setting?) as sometimes fetching a log fails due to not enough memory (See bug 845844).
Intermittent issue with Mac OSX64 Debug Leak log comprehension. Issue tracked in bug 774844. Also see possibly related Thunderbird bug 806492.
Two remaining machines on Parallels are the buildmaster (cb-seamonkey-linuxmaster-01) and Linux64 (cb-seamonkey-linux64-01). ~~These need to be migrated to ESX~~. Specifically:
- sea-vm-linux64-1 will replace cb-seamonkey-linux64-01 (and running jobs now).
- sea-master1 will replace the current buildmaster.
- Both our buildmaster and cb-seamonkey-linux64-01 are down due to hardware failure. This means no builds and no releases until they are replaced. After two days of help from DCOps, Callek has decided to cease all recovery operations and concentrate on setting up the puppetmaster to get the ball rolling on getting our new buildmaster out. Therefore, our 2.18b5 and our 2.18 release are cancelled. instead will go directly to the 2.19 series of betas.
bug 740633 set up seamonkey HPs in scl3. Hardware installed and iLO configured. CentOS 6.3 installed.
- Awaiting puppetmaster fully prepared to instantiate as Linux Mock-Based slaves
sea-puppet (one of said hp machines) is ready to be configured as a puppet master (bug 827079), needs audit of the manifests and settings creation.
comm-* will be building out of mozilla-* eventually. Jcrammer is working on this.
release.mozilla.org does not track the SeaMonkey project anymore (bug 850339) [WONTFIX]. Instead SeaMonkey URLs pointing to releases.mozilla.org have been redirected to ftp.mozilla.org bug 871120.
bug 865976 Cannot build SeaMonkey on Linux since Bug 842927 (Implement DOM3 KeyboardEvent.key only for non-printable key, first)
- Callek has checked in a temporary hack to allow SeaMonkey to continue building but Masayuki Nakano needs to patch widget/gtk2/compat/gdk/gdkkeysyms.h for a proper fix.

Release Train

SeaMonkey 2.18b4 shipped May 3.
Due to hardware failure, SeaMonkey 2.18b5 and SeaMonkey 2.18 are cancelled.
Instead will go directly to 2.19 series of betas and by the 24th June, the 2.19 final. This means that users of 2.17.1 will be going directly to 2.19.
If Firefox decides to do a dot release, we might go for a 2.18 later.

Extensions Compatibility Tracking

See Basics page. Please only list current changes here.
Addon Compatibility Listings
There are now Lightning versions for both SM 2.17.x (Lightning 2.2b1) and SM 2.18 betas (Lightning 2.3b1) available on AMO.
- Might need to point out in release notes that users needs to install the Lightning beta versions for the SeaMonkey releases (as Lightning follows Thunderbird 17.0.x release schedule)
Shipped extensions (DOMI, CZ, Venkman) compatibility:
- Extensions are now compatible by default thus mitigating the issue. Although some people still disable c-b-d and run into issues.
- SeaMonkey 2.18 will ship ChatZilla 0.9.90
Our build team needs to automate DOMI branch selection rather than having to tweak the client.py every 6 weeks. bug 763506
- Meanwhile Callek made some changes to the tags that SM pulls (CZ, Venkman, DOMI) for comm-central. See comm-central changeset 347b255c4810.
Nightly Tester Tools is being actively developed by xabolcs (coder) and whimboo (reviewer) to make it more compatible with comm-central in general and SeaMonkey in particular. See Issues · mozilla/nightlytt · GitHub.
- Alpha build of new Nightly Tester Tools available at http://users.skynet.be/antoine.mechelynck/nightlytt-3.6pre-201304281100-1e1b71fd0875.xpi
  Update: on 1 May uploaded a version with titlebar customization working in SeaMonkey (in addition to an ability to customize the “Build ID” paste string with both c-c and m-c changesets) as http://users.skynet.be/antoine.mechelynck/other/nightlytt-3.6pre-fx+tb+sm+tk.xpi ; this is still not yet ready for prime time, the customization dialog works, but needs to be checked. See also the “Settings” and “Variables” sections on the Nightly Tester Tools wiki page. Tonymec 08:40, 1 May 2013 (PDT).

2.x (Last, Current, Next)

[From a previous meeting:] There is a problem with the metrics server, so no current data is available
See Basics page for the usual reminders.

2.17

open tracking (0)
tracking requests (1)
targeted (0)
fixed (10)

SeaMonkey 2.17 Release Notes

2.Next

Current breakages:
- Nothing significant at the moment.
Mozilla-central bugs that affect us:
- Note: Please file bugs if you notice any landing on mozilla-central that might break us. Please don’t depend on Ratty noticing such landings.
- bug 769764 move proxy resolution to separate thread and remove sync api. Tracked in:
  - MailNews bug 791645 Rewrite calls to synchronous nsIProtocolProxyService::DeprecatedBlockingResolve with Async code before DeprecatedBlockingResolve disappears as well.
- bug 737615 Remove use of synchronous cache API from unit tests. Tracked in:
  - bug 804972 Remove synchronous calls to nsICacheSession::openCacheEntry in SeaMonkey tests.
  - Mcsmurf says this is almost fixed but there was a test failure. He will close this bug and open a new one for the failure.
- bug 793634 Force builds to be compatible with gtk 2.18/glib 2.22. Tracked in:
  - bug 795354 Migrate SeaMonkey Linux builders to CentOS 6.
  - bug 794772 Port |Bug 713802 – Build with GIO support (and drop GnomeVFS)|. This is dependent on bug 795354.
- bug 795144 default –disable-gnomeui icon theme support
  - porting bug needed for the two configure.in changesets? Changes could be folded into bug 794772 above. *** IanN and Ewong are looking into this..
- bug 839034 move markPageAsXXX methods to nsINavHistoryService. Tracked in:
  - bug 845895 Fix markPageAsXXX usage in Seamonkey.

Feature List, Planning

Private Browsing is now mostly complete and uplifted to 2.18. Most things should work but some edge cases have probably been missed. Hopefully any remaining bugs will be found before its release.

Testing would be appreciated! Please file bugs as blocking the meta bug 460895.
We need to figure out if we want a new about:privatebrowsing page which someone will have to write (bug 842439). We also don’t have any help content yet.

Bug statistics for the last two (full) weeks: 35 new, 14 fixed, 14 triaged.

Low-Medium triaging effort.

Open reviews/flags:
23 review
7 super-review
2 ui-review
6 feedback

bug 847546 Support Retina Display (HiDPI) on SeaMokney on MacOS X.
- Ratty thinks we will need 2x PNGs as well as other changes. See Core Tracking bug 785330 for supporting HiDPI mode (Retina Display) on Mac OS X.
See Feature List page for major wanted/needed features.
- Ratty suggests featuring one or more bugs from that page at each meeting.
Featured helpwanted bugs:
- bug 449728 Drag tabs between windows.

Good First Bugs

Note: The GFB list is open to all including our regular contributors.
Ratty is working on an updated GFB list, suggestions welcome.
New GFBs recently added:
Currently there are 24 GFBs open, 2 are being actively worked on. bug 735333 needs some help getting this running on the try-server. Mcsmurf is assisting.
List of Open mentored bugs.
- Ratty notes that there are 23 bugs that are GFBs but without the mentor keyword. These need to be audited to see if they are really suitable as GFBs.
Mentors of stalled bugs should try to communicate with the assignees and if they can’t work on them any more to unassign/free up those bugs.

Roundtable – Personal Status Updates

Status Updates from developers – what are you working on, what’s the progress, any other comments? (feel free to add yourself to the list if your name is missing and you have interesting status).

Callek

Fixed:

bug 867870 Add SeaMonkey 2.18 Beta 4 to bouncer.

Working on:

bug 870191 Add SeaMonkey 2.18 Beta 5 to bouncer.

To Do:

bug 740633 set up seamonkey HPs in scl3.
bug 817383 SeaMonkey needs new (public) GPG key, in order to support signing releases properly.
bug 827079 Setup SeaMonkey PuppetMaster.
bug 827178 Update stage.m.o cron to match recent changes with ffxbld cron.
bug 845844 Deploy updated tbpl to tbpl.drapostles.org.

ewong

Fixed:

Review:
- bug 739056 – Port |Bug 715099 – Convert nsProfileMigrator to JS so we can use JS modules on migration| to SeaMonkey

Working On:
- bug 633937 – Port bug 562048 to suite.
- bug 796994 – Use filepicker’s open() instead of the obsolete show() in /suite/*
- bug 834690 – Port |Bug 569342 – Find bar should not be enabled in about:addons| to SeaMonkey
- bug 834691 – Port |Bug 632233| to SeaMonkey (XULBrowserWindow.onLocationChange looks for a “disablefastfind” attribute in all content documents before ruling them out)
- bug 837649 – [Tracking Bug] Stop OSX 10.5 support for SeaMonkey project
- bug 837650 – Stop support for OSX 10.5 in suite/ tree

To Do:

IanN

Some testing, reviewing and commenting.
Fixed:
Checked in pending review:
- bug 864130 Update en-GB for Gecko 22
Waiting for feedback/review:
- bug 808835 Add l10n.ini file for Chatzilla
- bug 837408 Add en-GB locale to gaia
Fixing review comments before checkin:
- bug 757230 When using add button for permissions in Data Manager set a displayHost
- bug 798147 Switch to correct pref pane if pref window already open
- bug 778534 Use image instead of html:img in instant messaging
Working on:
- Various SM Council documents.
- bug 606683 Allow customization of toolbar in Composer and MailNews Composition
- bug 639690 [META] Re-arrange code between editor and editorOverlay
- bug 773979 [META] Switch to new drag and drop api in SeaMonkey
- bug 657234 Move pasteQuote and pasteNoFormatting into contentAreaContextOverlay
- File/Folder selection in windows.
To Do:
- bug 639395 Get cmd_fontSize to reflect current state of selected content / content at caret.
- Prefs-in-a-tab.
- Create FAQ for Friends of the Fish Tank.
- Help get composer standalone builds working with –enable-tests.

mcsmurf

Fixed bug 867008 Remove previous calls to PlacesUtils.backups and move them to PlacesBackups (SeaMonkey)
Fixed bug 864271 Permanent orange: TEST-UNEXPECTED-FAIL | browser_dataman_basics.js | Test timed out
Fixed bug 863426 Port test fixes from |Bug 854467 – can’t un-set the clicktoplay flag on an nsIPluginTag| to SeaMonkey
Fixed bug 863672 Port configure.in changes to comm-aurora
Worked on bug 840474 Clicking on new mail notifcation opens two MailNews windows when no MailNews window is open (new feature disabled for SeaMonkey 2.18 due to this bug)
Filed bug 868205 Click-to-play pref (plugins.click_to_play) broken in SeaMonkey}}
Filed bug 869965 New: Background url bar color when vitising a SSL page does not cover the whole url bar
Filed bug&created patch bug 870290 [SeaMonkey] (perma-orange) TEST-UNEXPECTED-FAIL test_hang_submit.xul | Test timed out. (Broken plugin crash reporter submit link)
Filed bug&created patch bug 871291 Replace CSS selector -moz-locale-dir with chromedir selector inside pluginProblem.css
Created patch for bug 867068 Switch SeaMonkey to new Places async API
Created patch for bug 798278 Implement multiple plugin doorhanger UI (Port Bug 797677 and Bug 754472)

Ratty

Waiting for check-in on CLOSED TREE:

bug 870728 The Geolocation prompt should not offer action in PB mode if the action remembers permission for more than a session.
- Landed on comm-beta (2.18b) a=CLOSED TREE.
bug 871536 Mitigate clickjacking of about:certerror.
bug 871541 Remove updateIcon from tabbrowser since it has only one consumer.
bug 871548 Query params sent when reporting a phishing site could contain sensitive info.

Working on:

bug 870413 Implement permission prompt for desktop notifications in SeaMonkey.

Other stuff:

Did some reviews.
Bug triage and Bug discussions.
Usual end user support and PR in newsgroups and Mozillazine.

rsx11m

Fixed on trunk:

bug 867210 Put “Display emoticons as graphics” in a new line.

Fixed on comm-beta:

bug 849359 Print button is misaligned in the Composer and Message Composition toolbars with the Modern theme.

Working on:

bug 868419 Update Help for Mail & News Message Display preference pane.

Filed:

bug 868486 Session restore logic appears broken in Browser preference pane.
bug 868495 Browser main preference pane cut off in Windows 7 with hardware acceleration.

Follow-up discussions:

bug 861471 Update the SSL preference pane after bug 733642 changed preference names and semantics.

Other:

Bug triage, testing, and commenting for SeaMonkey and MailNews Core.
End-user information and discussion on MozillaZine

Any other business?

SeaMonkey Meeting Details

Time: 14 May, 2013, 12:00 UTC
- (8am Eastern, 1pm UK, 2pm Central Europe, 8pm Hong Kong)
Location: #seamonkey IRC channel
Further Read: Basics

Retrieved from “?title=SeaMonkey/StatusMeetings/2013-05-14&oldid=655694“

Meeting Notes: Mozilla Platform: 2013-05-14

Jesper Kristensen — Wed, 15 May 2013 03:00:03 +0000

Actions

jst and lmandel to find owner for Orange Factor bug 858948

Notices/Schedule

FF 21.0 for Desktop and mobile was shipped this morning
- Mobile push includes push to Google play store and Yandex store
- Desktop Release notes : http://www.mozilla.org/en-US/firefox/21.0/releasenotes/
- Mobile Release notes : http://www.mozilla.org/en-US/mobile/21.0/releasenotes/
22.0b1 is targeted fot go-to-build today and will be shipped before end of week
Aurora updates are disabled – will enable on Friday to update to Aurora 23

Unresolved Aurora 23 Trackers (non-security, not tracked for Beta)	Unresolved Beta 22 Trackers (non-security)
24 bugs (?? bugs last week)	38 bugs (32 bugs last week)

Key Issues

Threads

dev-platform
- converting CPPSRCS to moz.build (mshal)
- Follow-up on the Windows PGO issue (ehsan)
- Dropped support for MSVC 2005 and 2008 (ehsan)
firefox-dev
- Speculative pre-connections control preference

Products/Projects

Firefox Desktop

Social API
- Shane Caraveo landed the “Share panel” (bug 818675), which significantly improves the social API’s “share” capabilities

Form history/autocomplete back-end changes
- Mark Hammond chased down the last few test failures blocking back-end refactor of autocomplete/form history (bug 566746, bug 697377)

Australis
- Work continues. Star button changes were reverted, several changes to the toolbar and find bar behaviors landing now.

XUL Panel improvements
- Mark Hammond landed some improvements to XUL panel positioning (bug 812943, bug 798226)

Firefox Mobile

Usability, Responsiveness, and New Features

Lots of WebRTC patches landed last week
- bug 862883 Enable webrtc mochitest automation for FxAndroid
- bug 866093 application crashed [@ webrtc::VoEExternalMediaImpl::SetExternalRecordingStatus(bool)]
- bug 869477 WebRTC UI permissions no longer shown
Reflow on Zoom on double-tap only patch has been r+’d, Scott is working through some breakage in the vkbOverlap test before landing bug 847872.
ANR Reporter is ready for privacy review: bug 863777 – Teach ANR reporter to use the profiler to get a native stack
Implementing WebSockets for bug 834033 – Implement Push Notifications for Android

Stability Wins

bug 778459 – java.lang.OutOfMemoryError: at org.mozilla.gecko.AwesomeBarTabs.updateFavicon()
bug 827248 – java.lang.OutOfMemoryError: at org.mozilla.gecko.AboutHomeContent.getTopSitesThumbnails()

Stability

Benjamin Smedberg’s patch from bug 831768, which reduced Flash crashes and hangs by a quarter on beta, is shipping on release today with Firefox 21.
Jan de Mooij deduced a testcase for #4 topcrash bug 851934 (outlook.com) from full dumps within 24h of being assigned there, and realized he had already fixed this for 22 in bug 867482! Unfortunately too late for 21.
Is there anything more we can do about : bug 752828 – android.database.sqlite.SQLiteDatabaseLockedException: database is locked at android.database.sqlite.SQLiteStatement.native_executeSql(Native Method) on ICS ?
- it’s one of the top bugs for all channels for FFX for Android.

OrangeFactor

Past week’s OrangeFactor: 8.66 (Previous Week: 7.63).
No significant changes from last week.
bug 861176 – “Intermittent cppunittests TEST-UNEXPECTED-FAIL | TestSTSParser.exe | test failed with return code 4294967295 | Couldn’t get the profile directory.” Affects all branches. Needs an owner from RelEng.
Suggestions for moving OF downward?
17 intermittent failures fixed in the last week – List – Thanks!.

Roundtable

Get the most out of Mercurial. Upgrade to 2.5 or 2.6 and read gps’s blog posts at http://gregoryszorc.com/blog/2013/05/12/thoughts-on-mercurial-%28and-git%29/ and http://gregoryszorc.com/blog/2013/05/13/the-state-of-mercurial-at-mozilla/.
Clang 3.3 will be released during the 24 release cycle and we’ll likely upgrade shortly after it comes out (froydnj)

Platform Meeting Details

Tuesday 2013-05-14 – 11:00 am Pacific
Dial-in: conference# 98411
- US/International: +1 650 903 0800 x92 Conf# 98411
- US toll free: +1 800 707 2533 (pin 369) Conf# 98411
- Canada: +1 416 848 3114 x92 Conf# 98411
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 98411
Engineering Vidyo Room / Warp Core / SFO-Boardroom / Tor Commons
join irc.mozilla.org #planning for back channel

Retrieved from “?title=Platform/2013-05-14&oldid=655889“

Burning Edge - Firefox: Firefox Nightly 23, weeks 1-6

Jesse Ruderman — Wed, 15 May 2013 02:25:25 +0000

Speed & memory:

Fixed: 805241 - JS: Merge the new baseline compiler.
Fixed: 804676 - JS: Remove dependence of Ion compilation on ScriptAnalysis::analyzeTypes.
Fixed: 825928 - Graphics: Layers refactoring.
Fixed: 865546 - Graphics: Large scaled images in SVG's cause choppy scrolling.
Fixed: 854803 - Graphics: Images on slow network continously use 1 full core.
Fixed: 600307 - Rewrite and cleanup DOMStorage code.
Fixed: 566746 - Form history should use asynchronous storage API.
Fixed: 697377 - Form Autocomplete should use asynchronous storage API.

For more, read Taras's Snappy blog and MemShrink blog posts.

New web technologies:

Fixed: 765780 - Enable plugins and JavaScript in designMode.

For more, read Firefox 23 for developers.

Security & privacy:

Fixed: 838692 - Don't allow navigating named targets from sandboxed iframes.
Fixed: 549697 - Add click-to-play plugin UI to the addon manager.
Fixed: 834836 - Turn on pref to block mixed active content.

Other notable fixes:

Fixed: 858538 - Download-attribute kills WebSocket connections.
Fixed: 560072 - Object.getOwnPropertyDescriptor throws for many DOM objects.
Fixed: 485149 - Using box-shadow on a <fieldset> with <legend> does not follow box shape.
Fixed: 857820 - Drop only blink effect from text-decoration: blink; and completely remove <blink> element.
Fixed: 369180 - Proxy Authentication required while typing Search String.
Fixed: 649216 - Remove unnecessary delay when clicking tab close buttons sequentially.
Fixed: 636564 - [Mac] Lion-style floating scrollbars.

Sources:

Mozilla Add-ons Blog: Jetpack Project: weekly update for May 14, 2013

Jeff Griffiths — Tue, 14 May 2013 20:26:01 +0000

WE SHIPPED!!

Unless you’re hiding under a rock, you are probably aware that the Mozilla Project has released Firefox 21 today. Additionally, unless you’ve been completely ignoring my recent posts on this blog, you might also realize that Firefox 21 signals a new chapter in the life of the Jetpack project, as we ship the SDK’s module loader and APIs in Firefox 21.

To me this is a big deal, for add-on developers, for Firefox developers, for the entire project. I’d like to thank everyone involved for all the hard work, but in particular there are a few people who deserve special mention:

Atul Varma & Aza Raskin started Jetpack in 2009 in Mozilla Labs, then rebooted it in 2010, ushering in the modern era of content scripts, CommonJS modules the command-line cfx tool and Add-on Builder.
Dietrich Ayala, David Mason, Myk Melez & Brian Warner who guided the project through the ‘re-boot’ phase, always with an eye to landing Jetpack’s capabilities in Firefox and revolutionizing how Firefox features are made.
Dave Townsend, Irakli Gozalishvili and the rest of the current Jetpack team who have done a ton of work coordinating a series of important changes to make the SDK fit nicely into mozilla-central.
Various Mozilla Labs engineers including Shane Caraveo, Anant Narayanan, Andrew Sutherland & David Ascher who kicked the tires and built prototyped their own crazy ideas based on our shaky prototypes and beta releases.
Our fantastic contributors who keep showing up with great code for new features and bug fixes.

Now that we ship with Firefox I have decided to dial back the frequency of these posts to every 6 weeks on uplift and instead highlight for developers the new features and bug fixes that have landed in the recent Nightly cycle. As always if you have questions, feedback or want to get involved you can find us on the wiki, on the email list and of course in #jetpack on irc.mozilla.org.

Quick Stats

Total open bugs: 505
Bugs created last week: 15
Bugs fixed last week: 13
Total SDK-based Add-ons on AMO: 1,809
Open pull requests on Github: 54

Note: the stats above are based on the queries I linked to for each item. If you have suggestions on how these queries might be made more accurate,please comment below. Stats generated at 2013-05-14 10:39:08 PDT

hacks.mozilla.org: Pushing Firefox OS Apps to the Geeksphone

Jason Weathersby — Tue, 14 May 2013 19:38:51 +0000

A push to device feature was added in the 3.0 release of the Firefox OS Simulator. This feature allows web apps to be pushed to a connected device by clicking one button in the Simulator Dashboard. Availability of the Developer Preview Phone from Geeksphone has raised interest in the feature, so this post will detail how to configure your Geeksphone and the computer running the Simulator to make use of it.

Setting Up the Geeksphone Device

To push apps to the Geeksphone Firefox OS Developer Preview phone, you first need to enable Remote debugging. This can be done from the Settings app by selecting Device information > More Information > Developer -> Remote debugging. Now we are ready to configure the computer running the Simulator.

Windows

The team at Geeksphone recently released a set of drivers for Windows to support USB communication with their phones. The drivers are available at Geeksphone’s Web Site (direct ZIP link).

To install them, first download and extract the zip file to a known location on your system. Next, connect the phone to your machine using the provided USB cable. Click on the Start Button and enter “Device Manager” in the Search programs and files text entry field and press enter. This will launch the Windows Device Manager. Alternatively, you can launch the Device Manager from the icon located in the Windows Control Panel.

The connected phone will be listed under the Other Devices category. Right click on the Android label and select Update Driver Software….

In the Update Driver Software dialog, choose Browse my computer for driver software.

Locate the usb_driver folder from the Geeksphone download and make sure the Include subfolders checkbox is checked. Click on the Next button.

You will most likely receive a Windows Security alert. Select the Install this driver software anyway entry.

This will install the proper USB drivers and list the phone as Geeksphone Device in the Device Manager.

Launch the Firefox OS Simulator. The Dashboard should now contain a Push button and a Device connected message, and you should be able to add your Firefox OS app to the Simulator and push it to the phone.

Linux

If you are running the Simulator on a Linux machine, you will need to create or modify a udev rules file for the device. This process is described in “Setting up a Device for Development” (Steps 3.a and 3.b). The Geeksphone Firefox OS Developer Preview phone idVendor attribute is “05c6”, so your android.rules file should contain an entry similar to:

SUBSYSTEM==”usb”, ATTR{idVendor}==”05c6”, MODE=”0666”, GROUP=”plugdev”

After making the above changes, either reboot the system or restart the udev service:

sudo service udev restart

If you make these changes and the push to device button does not show up in the Simulator Dashboard, please see this workaround.

Mac

If you are running the Simulator on a Mac, no additional configuration is required to enable push to device.

Reference

Additional information about setting up and using the Firefox OS Simulator, including installing, adding apps, debugging and using the push to device capability can be found on the MDN page for the Firefox OS Simulator.

SUMO Blog: What’s up with SUMO – May 13

Verdi — Tue, 14 May 2013 17:04:54 +0000

Big things this week

Notes and video from this SUMO meeting.
Check out the designs for the new topic and subtopic pages and give us feedback.
Locales can assign reviewer rights (coming in this sprint).
Firefox 21 is out Tuesday – we’re tracking status and issues here.
Current SUMO development sprint – 2013.10
Next SUMO meeting is June 3rd at 9:00 am PST (call in details & meeting notes). Please add your comments, questions and updates to the wiki. You can also participate in #sumo during the meeting. We’re going to record and post a video of the meeting.

The Mozilla Blog: Firefox for Android Includes Open Source Fonts and HTML5 improvements

Mozilla — Tue, 14 May 2013 15:33:03 +0000

Firefox for Android comes with the custom, open source fonts Charis and Open Sans to make the Web more beautiful and easier to read on your small screen. The Web is made up almost entirely of text and sometimes reading text can be difficult on small phone and tablet screens. These new fonts will replace the three available Android default fonts to enable a more visually appealing and clear reading experience on the Web. The difference is subtle, but beautiful.

Firefox for Android includes HTML5 compatibility improvements as tested on HTML5test.com, the leading industry HTML5 compliance test. Firefox Firefox scores 421 and 14 bonus points (out of a total of 500).

Thanks to the hard work of the many Mozillians who contribute to building the best mobile browser, Firefox for Android now has an average rating of 4.5 stars in the Google Play Store. Whoo-hoo!

For more information:

Download Firefox for Android
Firefox for Android Release Notes

The Mozilla Blog: Stay Social with Firefox

Mozilla — Tue, 14 May 2013 15:32:47 +0000

Social sites are a key part of online life and with Firefox we want to make it easier to use the Web the way you want. Mozilla developed the Social API to enable social providers to integrate directly into Firefox to make your browsing experience more social, customizable and personal. The Social API makes it easy for your favorite social providers to add a sidebar with your content to Firefox or notification buttons directly on the Firefox toolbar.

Last year we launched with Facebook as the first social integration partner in Firefox. Today, we are adding multiple new social providers Cliqz, Mixi and msnNOW to Firefox, in addition to Facebook Messenger for Firefox, to help you stay connected to your social networks, no matter where you go on the Web.

The new social providers in Firefox make it even easier for you to keep up with friends, family, news and events while you surf the Web. You can get real time updates about news activity, entertainment or your personal network while you browse the Web.

New providers you can now add to your Firefox include:

Cliqz:

Cliqz delivers a real-time stream of the most relevant articles, stories, and videos based on your interests directly to Firefox. In the upper left of the sidebar, you can personalize your news feed by selecting categories, keywords, websites, and specific people you want to follow. Share links across your social networks or by email; preview Twitter commentary; and save articles for later without ever leaving Firefox.

To activate, visit the Cliqz activation page and click “Activate Cliqz.”

Mixi:

The Mixi sidebar let’s you easily stay in touch with your friends on the Mixi social network in Japan. It provides a real-time activity stream of all comments and photo shares from your personal social network directly to your Firefox browser. Mixi for Firefox is only available to users in Japan.

msnNOW:

msnNOW makes it easy to stay up to date on the things people are talking about, searching for and sharing the most on Web. MSN scours the most interesting trends from real-time sources like Facebook, Twitter, Bing, and BreakingNews.com, so you’ll always know what’s happening and get the jump on what everyone is talking about. You can customize the activity stream to watch for particular types of trending content from the sidebar dropdown menu.

To activate, go to the msnNOW page and click “Turn it On.”

The Social API has endless potential for integrating social networks, e-mail, finance, music, cloud possibilities, services, to-do lists, sports, news and other applications into your Firefox experience. We designed the Social API to make it easier and more convenient to use the Web the way you want. Soon we’ll add even more ways to integrate your favorite Web services into your Firefox Web experience.

For more information:

Download Firefox for Windows, Mac and Linux
Firefox for Windows, Mac and Linux Release Notes
More information on Firefox Health Report

BlueGriffon: BlueGriffon 1.7

BlueGriffon — Tue, 14 May 2013 11:07:00 +0000

I just released BlueGriffon 1.7 for Windows (XP, 7, 8), OS X (10.6 to 10.8) and Ubuntu (12.04 and 13.04, 32 and 64 bits). You can find it here.

about:community: Jean-Claude Van Damme loves Mozilla

mdouglass — Tue, 14 May 2013 04:17:45 +0000

I’m making that up of course.

Brussels is home to Tintin (image on the right), a chocolate museum (Mozilla tour please), and Fosdem, giant Open Source event.) It’s the capital of the European Union and the likely host of the Mozilla Summit 2013 (it’s also the birth place of Jean-Claude!)

Yes, after an amazing search for just the right spot for the third Summit location, we are focusing our attention to Brussels, Belgium. The event venue we have our eye on is called The Square. Check it out, seems spot on for Mozilla (creative, colorful, fun.) We will have about 5 hotels (rather than one large one like we’ll have in Toronto and in Santa Clara.) Here’s a map of where they all sit relative to the event space — each walking distance from it. Think Olympic Village. And, the best news is that Brussels is 1.5 hours from Paris, 2 from London and close to many others by train.

Next up, invitations. Volunteers who have been selected to attend the 2013 Summit will receive email notification on May 20th. The email will be linked to a list of assigned venues by person. There will also be an option to participate in a lottery to attend an alternative Summit location (somewhere other than where you were assigned.) We will select about 10% of the group (~90 people) to attend an alternative site by the end of May.

As for staff, we will kick off the site-selection process the last week in May. Most of Mozilla’s staff will know where they are headed prior to the Planning Assembly (June 14th).

We are aiming for official registration to kick off in early July after which time we’ll start booking travel and hotels and kicking off any immigration proceedings that need to be proceeded.

As always, if you need anything or have questions, please ping me on IRC #summit2013.

Meeting Notes: Mozilla Project: 2013-05-13

Jesper Kristensen — Tue, 14 May 2013 03:00:03 +0000

All-hands Status Meeting Agenda

Items in this section will be shared during the live all-hand status meeting.

Friends of the Tree

Thanks to all of the new contributors who helped with Firefox 21 and thanks to Josh and Seif for creating the report on activities for the release.
Anthony Hughes would like to thank (hopefully I don’t forget anyone) Simona Badau, Bhavana Bajaj, Juan Becerra, Carsten Book, Ioana Budnar, Raymond Etornam, Mike Hommey, Cornel Ionce, Michael Kaply, Alexandra Lucinet, Manuela Muntean, Phil Ringnalda, Gavin Sharp, Paul Silaghi, Hong Tang, Nick Thomas, Mihaela Velimiroviciu, Justin Wood, and Hector Zhao for working hard over the weekend to ensure we ship a top-quality Firefox 21 to all of our users on Tuesday.

Upcoming Events

This Week

JavaScript team work week in Santa Cruz – AGENDA

Monday, 13 May

13:00 SecReview:Add –marionette CLI to enable Marionette on all Firefox builds

5:30-7:30 PM Mozilla SF / 6:00-7:00 PM on AirMozilla: SF Book Salon & Wine Reception for Susan Crawford. A decade ago, the US led the world in fast, cheap Internet. What happened? Signed books for those who arrive early.

Tuesday, 14 May

13:00 Security Champions
- “MTV-2J JK”; “SFO-7B The Warfield”; “TOR-5N Spadina”
- Vidyo: 2J
- Dial-in Info (phone):
  - In office or soft phone: extension 92
  - US/INTL: 650-903-0800 or 650-215-1282 then extension 92
  - Toronto: 416-848-3114 then extension 92
  - Toll-free: 800-707-2533 then password 369
  - Conference num 95227
  - IRC Backchannel: #security

Wednesday, 15 May

Google I/O at Moscone Center

Thursday, 16 May

Google I/O at Moscone Center

Grow Mozilla discussion at 10 AM pacific — a forum for discussing community building at Mozilla
- Agenda and dial-in information (feel free to add items to the agenda)

Friday, 17 May

Google I/O at Moscone Center

Product Status Updates (voice updates)

Firefox Desktop/Mobile

Speaker Location: Vancouver (johnath)

Release week!
- Thanks for the last minute push, everyone

Webmaker

Speaker Location: Ryan Merkley, Toronto

This week: a sneak peek at Collusion 1.0. Releasing in June 2013. demo from Dethe Elza coming up in today’s Lightning Presentation section. Watch a Popcorn version of his sneak peek demo here.
Other ways to get involved with Webmaker this week:
- check out our new Webmaker blog
- the Webmaker community’s 10 most awesome things on the web this week
- 12 ways to get involved with Webmaker
- Also: check out this photo of Mark Surman from the White House Science Fair Apr 22:

Firefox OS

Speaker Location: No Audio. Yo.

1.0.1
- In IOT phase still: in-country testing of builds on devices in the target markets.
1.1
- Chipset vendor commercialization testing ending this week (except MMS).
- MMS: Merging back to master branch today, uplift to 1.1 at end of week. (Best tweet to describe this feature came from Robin Berjon, one of the W3C editors of HTML and DAP specs.)
ZDNet: “Firefox OS puts a good $50 smartphone within reach”

Grow Mozilla

Speaker Location: San Francisco

Help us build a history of Mozilla told by Mozillians. Please share your memories about this Mozilla milestone:

September 23, 2002: Phoenix 0.1 is released, the first version of a browser that will be renamed to Firebird and then Firefox

60 Seconds with Mozilla IT

Speaker Location: mrz in SF

Mozilla IT made some changes last week.

Speakers

Presenter	Title	Topic	Location	Share?	Media	More Details
Who Are You?	What Do You Do?	What are you going to talk about?	Where are you presenting from? (Moz Space, your house, space)	Will you be sharing your screen? (yes/no, other info)	Links to slides or images you want displayed on screen	Link to where audience can find out more information
Diane Bisgeier	Program Manager, WebFWD	Help us recruit the next cohort for WebFWD – deadline is June 5! http://webfwd.org	Mozilla San Francisco	No screen share – just showing off the schwag you can get if you refer a team to our next class.	Here’s the messenger bag :) > https://www.facebook.com/photo.php?fbid=361822707265407&set=pb.218655251582154.-2207520000.1367814592.&type=3&theater	Details on WebFWD at http://webfwd.org
Dethe Elza	Lead Developer, Collusion	Sneak peek at Collusion 1.0	Pre-recorded demo video	Yes, playing video from Toronto	Popcorn demo video version	learn more about Collusion
Dia Bondi (IRC thejudge)	Head of Knowledge Cultivation	Capture Mozilla is Air.Mozilla too! + Badges	San Francisco	No	https://air.mozilla.org/channels/culture_and_context/ https://badges.mozilla.org/en-US/ https://air.mozilla.org/channels/

Introducing New Hires

New Hire	Introduced by	Speaker location	New Hire location	Will be working on
Travis Choma	Bill Walker	Mountain View	San Francisco	Software Architect, Apps
Peiying Mo	Chris Hofmann	Mountain View	Mountain View	Senior Localization Program Manager
Sole Penades	Frederic Wenzel	Mountain View	London, UK	Senior Web Developer, Developer Ecosystem
Candice Serran	Sheila Mooney	Mountain View	San Francisco	FirefoxOS

Introducing New Interns

New Intern	Introduced by	Speaker location	New Hire location	Will be working on
David Zbarsky	Fabrice	MV	MV	FFX OS
Mohammed Almeshekah	Camilo Viecco	MV	MV	Security Engineering
Subhadeep Paul	David Zeber	SF	SF	Metrics

<meta>

Notes and non-voice status updates that aren’t part of the live meeting go here.

Status Updates By Team (non-voice updates)

QA

Test Execution

Driving hard to qualify Firefox 21 release candidates ahead of this week’s release [testplan]

WebQA

B2G/Gaia testing:
- Have our Inari commercial-RIL build up and running in Jenkins
  - we were waiting for the fix from https://bugzilla.mozilla.org/show_bug.cgi?id=840612 – Marionette turns off NetworkManager’s control of offline state too aggressively, to land on 1.0.1
    - …and looks like we’re hitting a commercial-RIL issue: https://bugzilla.mozilla.org/show_bug.cgi?id=869066
- Will soon branch and port tests over to 1.0.1
- Unfurling Marketplace/Payments blockers as we work through automation
- Standing the BIRT reports up
Engagement Projects
- Flicks: new promos, blog posts, partners and copy
- Reps: More of the new voting system has been implemented
FHR
- Release scheduled for Tuesday, 2013-05-14 @ 6am
- https://etherpad.mozilla.org/FHRMeeting
- Working w/ the devs to get automation in place
Firefox Marketplace
- http://mzl.la/10bLndx shipped Thursday
- Fireplace is being tested and is scheduled to go live this week
Mozilla.org
- pushed to prod pushed https://github.com/mozilla/bedrock/compare/1f1154a75630c2b7987951c6890e5fc17e1a6839…master
Mozillians
- UI redesign work is beginning – https://wiki.mozilla.org/Mozillians/Milestones/Phase3
- mozillians-dev.allizom.org is currently tracking the homepageredux developer branch
- The mozillians.dev job has been disabled in Jenkins
- A new Jenkins job called mozillians.homepageredux.dev has been created
- homepageredux branch created on https://github.com/mozilla/mozillians-tests to track new UX feature work
Socorro
- Milestone 46 slated to release today – https://bugzilla.mozilla.org/buglist.cgi?query_format=advanced&target_milestone=45&product=Socorro&list_id=6493476

Automation & Tools

New tracking-flags extension (bug 750742) and native REST API (bug 866927) are in the review phase.
Orange Factor is finally making the switch to the IT ElasticSearch cluster – bug 870559
Eideticker for b2g is now live
Working on making b2g automation engine (aka Marionette) more stable and more available in user/nightly builds. More information soon on this.
For now, the rest of the news is here

Dial-in: conference# 8600
- US/International: +1 650 903 0800 x92 Conf# 8600
- US toll free: +1 800 707 2533 (pin 369) Conf# 8600
- Canada: +1 416 848 3114 x92 Conf# 8600
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 8600

Retrieved from “?title=WeeklyUpdates/2013-05-13&oldid=655402“

Software Carpentry: A Mention in Science Careers

Greg Wilson — Tue, 14 May 2013 00:00:00 +0000

Vijee Venkatraman has written a good article for Science Careers titled "When All Science Becomes Data Science", which mentions Software Carpentry.

hacks.mozilla.org: Speed Up App Development with X-Tag and Web Components

Daniel Buchner — Mon, 13 May 2013 20:27:11 +0000

In the last few years we’ve witnessed an evolution in what ‘app’ means to both developers and consumers. The word app evokes the idea of a rich, task-oriented user experience with highly optimized user interface that responds to its environment and can be used on an array of common devices. In order to make development of rich app experiences easier, native platforms have generated many of their own controls and components that Just Work™.

For other native technology stacks, extensible components are all but assumed – not so much for the web. Soon, that all changes. We are on the verge of a declarative renaissance that will dramatically advance app development for the web platform, and Web Components will drive it.

X-Tag and Web Components offer features that obliterate the status quo for layout, UI, and widget development – here’s a few notable Web Component features:

Create real custom elements the browser understands
Stop the instantiation madness: ~~$$(‘button.super’).initSuperButton()~~
Remove unmanageable HTML widget guts from your app’s view files
Work with sharable components, based on standard technologies

Meet the Web Components Family

Web Components is a group of W3C specifications, quickly moving toward standardization, that provide a robust HTML component model. You should not assume the following specs are implemented in your browser of choice. While these specifications are in various stages of implementation across browsers, you can use X-Tag (with either Mozilla or Google’s prollyfill) today to create custom elements that work well in recent version of Firefox, Chrome, Safari, and stock mobile browsers. X-Tag is a powerful sugar library primarily focused on wrapping and enhancing one of the draft-state Web Component specs: Custom Elements (document.register). We’ll get to X-Tag shortly – but for now, let’s quickly review the key features of each spec:

Custom Elements

Custom Elements provides you a way to create new elements for use in your environment. There are two ways to declare a new custom element, the imperative DOM API – document.register(), and the declarative HTML tag – (whose DOM constructor is HTMLElementElement). After declaration, new custom elements can be created in the same ways native elements are, such as document.createElement, presences in original source (the markup of a page), and innerHTML, etc.

Here’s an example of what a custom element registration looks like in both the declarative and imperative styles:

document.register('x-foo', {
  prototype: Object.create(HTMLElement.prototype, {
    readyCallback: { 
      value: function(){
        // do stuff here when your element is created
        this.innerHTML = '<div>Barrrr me matey!</div>';
      }        
    },
    bar: {
      get: function() { return 'bar'; },
    },
    // add more properties to your custom prototype
    // ...
  })
});

<element name="x-foo">
  <script>
    if (this !== window) {
      this.register({
        prototype: {
          readyCallback: { 
            value: function(){
              // do stuff here when your element is created
              this.innerHTML = '<div>Barrrr me matey!</div>';
            }        
          },
          bar: {
            get: function() { return 'bar'; },
          }
        }
      });
    }
  </script>
</element>

Shadow DOM

The Shadow DOM allows you to encapsulate structural and supporting elements within components. Elements within nodes remain visible for purposes of display UI (depending on the type of element and your styles), but are hidden from the rest of your application code, unless you explicitly cross the shadow boundary.

HTML Templates

HTML Templates bring simple DOM templating and markup reuse to the web platform – which are often shimmed today using the HTMLScriptElement + DocumentFragment hack-pattern.

HTML Imports

HTML Imports are external HTML documents that contain declarative component definitions. HTML component documents can by imported using the link element with the rel attribute value import. Imported resources may themselves contain additional sub-imports, which the browser then retrieves and performs automatic dependency resolution upon.

Web Components + X-Tag = WINNING

Mozilla’s X-Tag library enhances the imperative (JavaScript) route for creating custom elements. X-Tag’s primary interface is the xtag.register() method – it wraps the soon-to-be standard document.register() DOM API with features and functionality that make development of amazing custom elements effortless.

Creating a Custom Element

Here’s a quick example of what registering a custom element looks like using X-Tag:

xtag.register('x-pirate', {
  lifecycle: {
    ready: function(){
      this.innerHTML = '<blockquote>' +
                         '<img src="pirate-1.png"/>Barrr me matey!' +
                       '</blockquote>';
    }
  },
  accessors: {
    src: {
      // X-Tag's attribute sugar relays any value passed to the src 
      // setter on to the src attribute of our <x-pirate> and its
      // <img> element (specified by CSS selector), and vice versa.
      attribute: { selector: 'img' },
      set: function(){
        // When a <x-pirate>'s src attribute/setter is changed, we 
        // stop everything to announce the arrival of a new pirate.
        // Ex: doc.querySelector('x-pirate').src = 'pirate-2.png';
        alert("There's a new captain on deck ye scurvy dogs!");
      }
    }
  },
  events: {
    // This is an example of X-Tag's event and pseudo systems. The
    // "tap" custom event handles the dance between click and touch,
    // the ":delegate(img)" pseudo ensures our function is only 
    // called when tapping the <img> inside our <x-pirate>.
    'tap:delegate(blockquote > img)': function(){
      alert("A pirate's life for me!");
    }
  }
});

To the Democave Batman!

We’re actively working on a custom element UI toolkit and style pack that will make development of app interfaces a breeze. It’s still in very early stages, but we have a few demos for you.

Get the Code

Head over to X-Tags.org and grab the code to develop custom elements of your own. After you get the hang of things, start contributing to our open source effort!

QMO: Contributor Spotlight: Glenn Howard

rbillings — Mon, 13 May 2013 18:15:03 +0000

This month WebQA would like to extend thanks to Glenn Howard, and to highlight some of his work for our team. Glenn is an automation engineer who has made a big impact on our wiki-tests repository! You can see the projects he’s helped out with on Github:

https://github.com/glennhoward

Glenn has been contributing for a year and a half so far. He manages to fit it in on top of his job- and we really appreciate the time and effort he puts in! He puts in a few hours per week, whenever he has spare time. This kind of regular contribution makes a big impact. Any contributor who can help out, even for short bursts of time, makes all of the difference in our projects. Our volunteers make it possible to extend both the depth and breadth of our testing!

“As busy as he undoubtedly is, Glenn still finds time to contribute more than just the great tests for our critical wiki.mozilla.org site — he contributes ideas and exudes enthusiasm for Web testing (and not just Mozilla’s) in a lot of different aspects; we’re always grateful to have him participate in our meetings and mailing-list discussions!” – Stephen Donner

Glenn currently resides in Dublin, Ireland where he works as a full time Automation QA Engineer with Gilt. While Mozilla headquarters is located in California, our contributors and employees cover the globe. We have people helping out in many different timezones. While our IRC channel definitely has prime times for being busy, you can always try connecting with us there. If you’d like to contribute and have questions about the info on our team page, you can try clicking this link to get into our IRC channel. IRC is where our community comes together to find work, ask questions, and to get to know one another.

We always like to ask our primary contributors how they found us, and what got them started contributing to our team. Here is what Glenn had to say:

I was looking for some Selenium/WebDriver examples and came across Dave Hunt’s blog, from this I found the mozwebqa team. I had used Firefox for quite some time and when I discovered that I could help give back, as well as learn some python, I couldn’t wait to help out and it went from there.

My favourite type of issue to work on is one that lets me contribute with others and that really gets me thinking. Being able to work with others on tough issues is great as it pushes you and well as lets you learn from others.

When asked what he’d tell a newcomer who was thinking of contributing:

Do it! Not only will you get a chance to work/contribute with some really amazing and passionate people, you’ll also get a chance to expand your own knowledge in the process. I’ve met some really great like-minded people which makes it fun to contribute and help out.

This is an important part of contributing- the ability to network with others. You get the chance to contribute work, but you also meet new folks and learn a lot in the process. Our contributors help knit the fabric of our community and play an important part in getting new folks started.

Glenn has been an incredible addition to our community. His passion for Mozilla’s mission is apparent as he fluently works on projects, helping identify coverage gaps and creating test automation. I’ve enjoyed spying on him and watching as he helps on-board new community members, helping untangle the Mozilla fire-hose of information overload and sharing his infectious excitement with new community members. ~ Matt Brandt

Glenn’s contributions span far beyond his github pull requests! We value all of the people who make the time to become a regular part of our community. Particular thanks go to Glenn for all of his help, the whole QA team appreciates your work!

about:community: Milestone: Phoenix 0.1 released, first version of Firefox

dboswell — Mon, 13 May 2013 16:04:53 +0000

September 23, 2002: Phoenix 0.1 is released, the first version of a browser that will be renamed to Firebird and then Firefox

Firebug Blog: Firebug 1.11.3

Honza — Mon, 13 May 2013 06:55:47 +0000

Firebug 1.11.3 has been released (archive).

Firebug 1.11.3 fixes 15 issues
Firebug 1.11.3 is compatible with Firefox 17-22

All users subscribed to AMO beta channel should be already updated to version 1.11.3 beta 1 which is exactly the same as 1.11.3.

One little problem related to browser page context-menu slipped into this release. If you experience the menu being unexpectedly long, just restart your browser.

Please post feedback in the newsgroup, thanks!

Jan ‘Honza’ Odvarko

The Mozilla Blog: Personalization with Respect

jsullivan — Fri, 10 May 2013 23:36:56 +0000

Mozilla’s mission compels us to provide people with an Internet experience that puts them in control of their online lives and that treats them with respect. Respecting someone includes respecting their privacy. We aspire to a “no surprises” principle: the idea that when information is gathered about a person, it is done with their knowledge and is used in ways that benefit that person. People should be made aware of how information is collected and used. Each individual should also be able to decide whether the exchange of personal data for the services received in return feels fair. This can be challenging to achieve, especially when balanced against convenience and ease of use: people expect a fast, streamlined user experience without excessive prompts and confusing choices. But we are always striving toward this ideal.

Mozilla is an active participant in the ecosystem of today’s Web economics. Much of the content and information that people enjoy and benefit from is funded by digital marketing and sponsorship. This is a valid business model. We simply believe that when personal data is collected to deliver these services, the collection should be done respectfully and with the consent of the consumer. Commerce works best when users understand the transactions they engage in. The best long-term customer relationships are built on trust.

Mozilla aspires to enable personalization — the customization of ads, content, recommendations, offers and more — that doesn’t rely on the user being in the dark about who has access to that information, and with whom that information is shared. As a major Web browser provider and, now, OS developer, Mozilla’s role is to experiment and innovate toward that aspiration. As an open source project, where contributions are welcomed by all, we encourage all in the industry to help, by constructively proposing approaches and collaborating with us in the open.

Here are a just a few examples of the work Mozilla is doing to explore personalization with respect:

Persona is an identity system for the Web. It gives people control over their Web logins. People choose what identity to present to a given service. In particular, people can keep their work, personal, and other facets of their lives distinct.
Do Not Track allows you to tell a website that you would like to opt-out of third-party tracking for purposes including behavioral advertising. It lets users express how they would like information about themselves to be handled. It has many benefits. People who use Firefox must actively enable Do Not Track, making it very clear that the user has made an explicit choice Also, Do Not Track is independent of any particular technology, providing resilience in the face of technology evolution. We continue to work with a broad range of interested parties to see the Web adopt Do Not Track.
Third party cookie policies are being evaluated to strike a better balance between personalized ads and the tracking of users across the Web without their consent. For example, an experimental version of Firefox allows cookies to be set by first parties and by third parties where Firefox has stored a cookie for the party’s domain, but to block by default third-party cookies whose domain is not known from Firefox’s cookie store. We’ve been evaluating that approach, as well as others, working with stakeholders from across the industry.

It should be possible to delight users (and yes, the right offer at the right time can be a delight), while treating them with respect. We continue to experiment with and evaluate new ways to put users in control of their Web experience and encourage you to join us in building toward this vision. We will share more updates soon.

Mozilla Websites: A few UX changes. A single page. Millions of new downloads.

hhabstritt — Fri, 10 May 2013 16:24:16 +0000

We recently designed, tested, and released a new version of our our primary download page for Firefox for Desktop. In our tests, we improved the download conversion rate of the top 3 non-Firefox browsers by over 12%! This alone results in millions of additional downloads annually.

Focusing on the entire funnel leading up to a product download and not just the product itself, is as important as the efforts taken to improve retention of a product. This is one of the approaches that the Websites team at Mozilla is taking to improve and support our products.

What is the /new page on Mozilla.org?

This is where the majority of our desktop browser downloads are initiated. For instance, if the user searches for “Firefox”, “Mozilla Firefox”, or “download Firefox” from a desktop browser, the /new URL is the top search result.

What did we change?

Though a relatively simple page, we were able to make number of changes across visual design, interaction, technical improvements and overall user experience that had substantial results. How did we do this?

reduced the number of steps to download
simplified number of actions displayed on page and reduced distractions to funnel user directly to download (ie: no link to Fx for Android or other products displayed)
focus on our product – the last page design did not display visuals that focused on the product, but focused more on Mozilla community.
significantly faster page load time
updated style to our responsive Mozilla style guide
inline page interaction that responds immediately to the user’s request for download, resulting in no page refresh for confirmation and installation instructions.

Old Experience – includes page refresh:

New Experience – inline interaction, no page refresh:

* To experience the inline page interaction yourself, visit the Firefox for Desktop download page.

Design Decisions & Testing

We could infer that the outcome of changes such as updating this page to a consistent style as our other Mozilla.org pages and improving page load time alone would have a positive result. However, some of the other changes were more subjective and required testing and validation before releasing to 100% of our users.

Based on common interaction patterns, what we know about how users respond to pages that “feel” responsive to their actions, as well as minimizing distraction, we were able to make many initial design decisions. To validate the more subjective changes, such as button placement, button style, and animations, we ran A/B tests using Google Analytics Content Experiments.

An important part of testing is not just validating our work, but exposing interesting facts about our users and issues that may need further attention. For instance, we learned that large percentage of users downloading Firefox already have Firefox for Desktop. This could mean that the user is not aware that we run silent updates, that they are not aware that their version of Firefox is already up to date, that they wanted a fresh copy of the browser, or a number of other possibilities. This is just one of the interesting things we learned that we are looking into for further improvements.

Given the success of these tests, we were very confident in releasing the new experience to all of our users. Our initial improvements to the /new page and download funnel are just the beginning. We will also continue to test improvement possibilities, such as the style of the download button, to learn more about our users and improve the performance of the download funnel.

A few stats:

Across the top 3 browsers, we saw a 14% download conversion improvement.

Across all browsers and operating systems, we saw an average of a 4% improvement.

Considerable improvements to page load time:

Time to be able to interact: 46% decrease
Time to load page content: 71% decrease
Time to execute JavaScript: 35% decrease

Next Steps:

Testing download button styles and placement, translate page for non-english languages, add logic and conditional messaging for all platforms to move towards a unified Firefox download page, improve other touch points within the onboarding funnel by using a similar process of testing and validating with real users.

Software Carpentry: Git vs. Subversion and Feedback in General

Greg Wilson — Fri, 10 May 2013 00:00:00 +0000

Software Carpentry's mission is to help scientists teach other scientists how to be better programmers. If we want to do that successfully, we need to be scientists ourselves. In particular, we need to base what we teach on evidence, not anecdotes or personal preferences.

For example: we taught Git at the Toronto boot camp last week, and once again I think our learners would have absorbed more if we'd taught Subversion. Why? Well, take a look at this diagram by Oliver Steele (which I found on this page written by Nick Quaranto):

Four locations are in play, and eight different commands are used to move information around or compare what's in one place to another. Now look at the corresponding diagram for Subversion:

There are only three locations for people to keep track of, and the basic workflow involves only four commands. If you believe complexity is partially multiplicative (because people have to keep track of the interactions between things, as well as the things themselves), Git is at least twice as complex for people to understand. Slicing it another way, there are more opportunities for people to do the wrong thing with Git, and more they have to understand to undo it. And that's before we introduce branches...

But that's just my point of view, and the fact that I can wrap a plausible story around it doesn't make it true. Matt Davis and others believe they've been successful with Git in front of the same kinds of people. We need to find out who's right, so our major goal for the next three months is to poll and interview boot camp attendees to find out who was taught what, who tried what, who's still using what, and why. Caitlyn Pickens will be leading this effort, and many of you will get email from her in the next few weeks. When it arrives, please take a few minutes to tell us what you're actually doing, even if it's not what we told you to do—especially if it's not, because that'll tell us what we need to fix.

about:community: Firefox 21 New Contributors

dboswell — Thu, 09 May 2013 15:59:08 +0000

We are pleased to reveal that Firefox 21 is brought to you through the hard work of 326 developers. Of these, we welcome the 41 who contributed their first code change to Firefox in this release, 34 of whom were brand new volunteers! Please join us in thanking each of these diligent and enthusiastic individuals, and take a look at their contributions (thanks to Seif Lotfy for collecting this data):

Andreas Wagner: 550175

Benedict Singer: 787134, 795360, 803677, 794180

Catalin Iordache: 813019, 821269, 821396, 821901

ChangZhuo Chen: 778053

David Guo: 747835

Dustin L. Howett: 812647

Ian Patterson: 712748

Jan-Ivar Bruaroey: 794240, 817429, 817430, 816112, 824955, 800538

Jonathan Kamens: 823042

Jorge Luis Mendez: 820117, 820285

Julien Levesy: 811753

Julien Wajsberg: 824695, 825237

Lawrence Mandel: 819732

Marius Gedminas: 364845

Matej Cepl: 800557

Michal Jaskurzynski: 424712

Mohit Gahlot: 818106

Nikolay Bryskin: 650935

Peter Retzer: 784297

Rafael Gieschke: 791419

Ravisankar Sivasubramaniam: 803078

Rik Cabanier: 748433, 809927

Sergiu Dumitriu: 826563

Soumya Deb: 818660, 821968, 821969, 821971

Sriram: 715736

Stefan Arentz: 807659

Stephen Pohl: 813322

Steve Singer: 817356

Thomas Zimmermann: 758103, 809367, 817730

Ting-Yuan Huang: 815473

Tobias Netzel: 812932, 817045, 818004

Usurelu Catalin: 820197

Virgil Dupras: 801450

Walter Chen: 816514

Yura Zenevich: 803067

alex: 815131

groodt: 686228, 813946

ithinc: 656222, 819907, 822068, 822914, 824480

rfw2nd: 553917

zeyu: 813801

zmgmoz: 804845

hacks.mozilla.org: Phones for Apps for Firefox OS

Havi Hoffman — Thu, 09 May 2013 14:38:13 +0000

Update: Today, Monday, May 13 at 11:00am PDT, we closed the submission form for the Phones for Apps program. Thanks so much to all of you for your interest and enthusiasm. Your response has been overwhelming! We’ve received thousands of applications, more than we’re equipped to review in a timely fashion.

We’ve started reviewing your proposals, and in the next few weeks we plan to notify application builders and porters who’ve been selected. We regret we can’t respond to the thousands of you with great ideas for apps for Firefox OS. There will be other opportunities to get access to the the Developer Preview device. Please keep working on your apps. We can’t wait to see them in Firefox Marketplace.

Hello HTML5 app developers, the open mobile web is calling.

We know you’re out there, chomping at the bit, coding, testing, reading documentation, downloading and running the Firefox Simulator. And you’re ready to ‘Send to Device.’ You just need to get your hands on a device.

Today we’re announcing a new program with you in mind. We call it: Phones for Apps for Firefox OS.

Firefox Marketplace on the Geeksphone Keon

Maybe you’ve built apps in the past for Chrome, webOS, Blackberry WebWorks, or the PhoneGap store. Maybe you’ve created beautiful web apps for a desktop environment and now you want to port them to mobile. Maybe you’re a student about to start a summer break. We know you may not live anywhere near Bogota, Colombia or Warsaw, Poland, locations of upcoming App Workshops.

Wherever you are

Wherever you are, if you can show you’ve got a great app idea and the skill to build it, we’d love to see your apps in the Marketplace when the Firefox OS launch begins later this summer. And to sweeten the deal, we’ll send a Firefox OS Developer Preview device for you to work with now.

When Firefox OS phones become available to consumers in select locales this summer, you’ll have an opportunity that only comes around once—a first-mover advantage in Firefox Marketplace. End users in Latin America, Eastern Europe and other launch locations will be on the lookout for playful and practical apps to install: games, tools, and utilities as well as locally relevant news, sports, travel, entertainment, review apps, and social sharing experiences. And you can build and submit them now!

Apply now

Tell us about the Firefox App you’d like to build or port. If your proposal is accepted, we’ll send you a Geeksphone Keon. Our device inventory is limited and our launch dates are approaching fast, so act now. This program will close at the end of May or when our limited supply of Geeksphones runs out. There’s a limit of one phone per app proposal. We can’t wait to see what you’re working on. There’s never been a better time to get started.

Apply here.

Mozilla IT: 60 Seconds with Mozilla IT – May 6

mrz — Thu, 09 May 2013 03:15:25 +0000

From the May 6 weekly Project Meeting:

Sometimes Mozilla IT shows a different side and brings Mozilla to the classroom.

Meeting Notes: Mobile: 2013-05-08

Jesper Kristensen — Thu, 09 May 2013 03:00:08 +0000

Schedule

Next merge: 2013-05-13 (3 BUSINESS DAYS!)
Next release: 2013-05-14

Friends of the Mobile Team

Give a shoutout/thanks to people for helping fix and test bugs.

Chen Dai contributed patches to
- bug 866487 – MOZ_UPDATER always set to true in AppConstants.java
- bug 869322 – Screen can’t read the text in input box
Abir Viqar landed his first patch! (bonus points for an r+ on first attempt)
- bug 839434 – Private browsing page opens the pop-ups in normal browsing
Tetsuharu OHZEKI continued to file and fix multiple bugs
- bug 865250 – Clean up BrowserApp.get/setPreferences()
- bug 867875 – Add the pref to switch reader mode
- bug 868936 – Use strict equality operator in JSDOMParser.js

Stand ups

Suggested format:

What did you do last week?
What are working on this week?
Anything blocking you?

Please keep your update to under 2 minutes!

GBrown

Last week:
- Investigated bug 867626 Expose Shumway in navigator.plugins
- bug 865944 Use foreground activity to determine if browser has terminated
- –> Panda failure rates much better this week
- bug 868681 Offline apps doorhanger not shown
- bug 868767 Unable to uninstall org.mozilla.fennec_aurora/firefox_beta and reboot
Working on:
- bug 867626 Expose Shumway in navigator.plugins
- Follow-up on bug 865944 Use foreground activity…
- bug 869030 Robocop testDoorHanger causes future reboots on pandas
- bug 867360 Watcher dies sometimes on Pandas

Chris Lord (cwiiis)

Done
- Wrote a timer webapp over the weekend: http://chrislord.net/index.php/2013/05/04/writing-and-deploying-a-small-firefox-os-application/
- Spent some time tracking down B2G issues
- Bank holiday

Doing
- bug 866461 – Bing.com constantly resizing with the dynamic toolbar
- bug 803299 – Use 24-bit colour on 24-bit screens (patches r+’d but backed out due to reftest failures)

Chris Peterson

Done
- Fixed bug 778459 – java.lang.OutOfMemoryError: at org.mozilla.gecko.AwesomeBarTabs.updateFavicon()
- Fixed bug 827248 – java.lang.OutOfMemoryError: at org.mozilla.gecko.AboutHomeContent.getTopSitesThumbnails()
- Fixed bug 868604 – JavaScript Warning “test for equality (==) mistyped as assignment (=)?” in “chrome://browser/content/downloads.js”
- Fixed bug 868673 – Fix -Wtype-limits “comparison of unsigned expression >= 0 is always true” warning in XPFE
- Implementing WebSockets for bug 834033 – Push API for Android

Next
- Implement System Messages for bug 834033 – Push API for Android

JChen

Past week
- Finished bug 863777 – Teach ANR reporter to use the profiler to get a native stack
  - Doing privacy review now
- Worked on bug 860879 – ANR @ org.mozilla.gecko.PromptService.finishDialog
  - Have patches for review
  - Going to file follow up bugs
- Worked on bug 847983 – IME in designmode doesn’t seem to work very well
Next
- Finish bugs from above
- bug 868566 – Cannot create a new paragraph in a text box on Motorola Support Forums
- bug 868569 – Cursor selection buttons in Swype don’t work
- bug 846660 – java.lang.InstantiationException: cant instantiate class char
- PTO starting next Wed

GCP

This week:
- WebRTC
- bug 862883 Enable webrtc mochitest automation for FxAndroid
- bug 866093 application crashed [@ webrtc::VoEExternalMediaImpl::SetExternalRecordingStatus(bool)]
- bug 863290 crash in webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices
- bug 869477 WebRTC UI permissions no longer shown
Next week:
- bug 863290 crash in webrtc::videocapturemodule::DeviceInfoAndroid::NumberOfDevices
- bug 867185 Camera names should percolate upwards to the UI
- bug 862808 Local Video is upside down on Android when in portrait mode

Brian N

Done
- Ouya bugs
  - Bug 849847 – Make about:home scrollable with the analog stick
  - Bug 868230 – Map gamepad X button to show/hide tabs tray
In progress
- Bug 868553 – Make about:home use a ViewPager
Next
- Other about:home rewrite work
- Ouya bugs

Sriram

Back from vacation
- More coffee, more sleep, more cricket
Exploring quick share menu.

WesJ

Vacation
Bug 813756 – Payments frontend for Android – Landed! yay!
Bug 757481 – Tests for prompt service – have some new wip up
Bug 798358 – Hardcoded add-ons on about:home links to author’s desktop site with desktop add-on installs – Landing now
Bug 826325 – Decide where window.open should open content – Still trying to find the right solution here
Bug 808636 – Update visual style of mobile error pages – http://people.mozilla.com/~wjohnston/netError/index.html

LucasR

Last week
- Bank holiday
- bug 869166 – Add space between URL bar and tab curve
- bug 869022 – Fade tabs button and menu away when tabs panel is open
- bug 868460 – Tidy up animation bits
- bug 867554 – New sidebar animation on tablets
- bug 860121 – Animating the landscape tab menu on tablets yield a white gap between the sidebar and the tab count button
- bug 866466 – Opening a remote-tab from tab-menu overlays view onto the regular and private tabs menu
- bug 867141 – Unable to close regular tabs after closing last private tab
- bug 865228 – Misc improvements in the browser toolbar animations
- (In progress) bug 869494 – Add editing mode to browser toolbar
Next week
- bug 869494 – Add editing mode to browser toolbar
- bug 867608 – Gap between forward button and favicon after backing out of reader mode
- Pre-assembly interviews for the Mozilla Summit meeting in Paris
- Google I/O
  - Android Design lab: https://developers.google.com/events/io/sessions/383307141

Margaret

Done
- bug 867249 – Improve BitmapUtils.getDominantColor to avoid returning gray-ish colors
- bug 867627 – Dominant color favicon backgrounds are really slow to update
- bug 867650 – Search list still shown on Awesomescreen when clearing search string
- bug 867125 – Unpinning a site from about:home removes it from about:home regardless of the number of visits
- bug 867059 – “Set as Default” option still available in context menu after disabling a search engine
- Helped interview devtools candidates

In Progress
- Crash in BrowserToolbar.setTitle – bug 868342
- Blog post about dominant color favicons

Next
- Update empty favicon style – bug 869634
- Use better default thumbnails on about:home when we don’t have a screenshot – bug 837392

Scott (jwir3)

Last Week:

bug 847872: Reflow zoom on double tap only (r+, but I’m having some difficulty with tests – specifically testVkbOverlap on Android and I’m kind of blocked on this before I can land).
Looked into bug 864595: Assertion failure in caretPositionFromPoint. I have a solution, but it’s not quite ready for review.
bug 862763: Performance of nsLayoutUtils::FontSizeInflationEnabled needs some work (in review).

This Week:

Land reflow-on-zoom on double-tap only.
Land HResize performance enhancement for reflow-on-zoom.
Finish implementation of last solution for bug 836565 that queues one event for each document to be reflown in nsDocumentViewer, for responsiveness (this might not be necessary).
bug 766599: Reframe to prevent crash in nsFontInflationData (this will allow us to dynamically change font inflation prefs without a reload).

BLassey

bug 867517 – Gecko based web view
bug 833795 – Content jitters when URL bar hidden (B2G)

MFinkle

Done:

bug 869477 – WebRTC UI permissions no longer shown
Looking into bug 862377 – Android WebRTC permissions UI will only respect first doorhanger

Next:

Metro work week in Vancouver

Ian Barlow

Designs ready to go
- bug 869123 NEW: Quick Share — shortcut to most frequently used sharing service
  - https://bug869123.bugzilla.mozilla.org/attachment.cgi?id=745998
- bug 867371 Updated Settings UI in progress
  - https://etherpad.mozilla.org/settings-reorg
- bug 853844 New progress indicator
  - https://bugzilla.mozilla.org/show_bug.cgi?id=853844#c16
- bug 867633 Consolidate lock icon and forward button animations in toolbar
  - https://bugzilla.mozilla.org/show_bug.cgi?id=867633#c1
- bug 847435 Updated look for back session history menu
  - https://bug847435.bugzilla.mozilla.org/attachment.cgi?id=746397
- bug 868998 Reveal title bar by scrolling a certain distance

Work in progress
- bug 864958 Some subtle adjustments to the PB chrome
- bug 808636 Reviewing work in progress on mobile error pages
- Some discussion around WebRTC doorhanger permissions
- Continuing work with Product on some UX prerequisites for Mozilla Apps on Android
- Standing by for any and all questions about Multipage About:home
- Usability testing plan for Multipage about:home
- TV design concepts
- New tablet concepts

WebRT

There is a meeting on Friday (11a PT) to discuss the “synthesizing APK” approach to delivering Apps on Android.

PiCL

Work week in Vancouver this week.

Feature Focus

Fx21

[ON TRACK] bug 834681 – Add support for basic distribution modifications
[ON TRACK] bug 831354 – Ship fonts for content in Firefox for Android
[ON TRACK] Amazon Search URL
[PLANNED]bug 867604 – [Meta] HTML5 Compat
- Note: thanks for the uplifts last week!

Fx22

[AT RISK] Reflow on zoom (double tap) by default
[PROPOSED] New tab UI

Pet bug: Bug 862996 – Put text headings back in the tab menu

[PROPOSED] ANR

Fx23

NFC bump for tab sharing
WebRTC platform support, preffed off
[ON TRACK] READER: Serif/Sans Serif font toggle, Add to reading list from long tap, add to reading list from context menu
[ON TRACK] bug 730445 – Add UI to specify a default search engine
[AT RISK] Firefox Health Report
[PLANNED] RSS/Atom feed handling
[PLANNED] Set Top Box optimization
[PLANNED] Directional game console navigation <== same set of bugs as above?
[PLANNED] Dynamic Snippets
[PROPOSED] Addition of search engines
[PROPOSED] Changing default search engines by locale
[AT RISK] bug 716403 – (dynamic-toolbar) Request to hide the navigation bar when scrolling down content

Fx24

Tradeoffs: Finishing the last 3 Reader Improvements and moving About:Home Redesign
Need to create a project plan for Shumway and Dynamic Snippets

[PLANNED] Packaged apps support
[PLANNED] Web Audio API
[PLANNED] API: Push notifications
[PLANNED] API: Web activities
[PLANNED] API: Contacts
[PLANNED] SkiaGL improvement
[PROPOSED] API: Payments
[PROPOSED] API: Alarm
[PROPOSED] Location-based search engines
[PROPOSED] Shumway: generic video player
[PROPOSED] About:home redesign
[PROPOSED] Reader improvements
[PROPOSED] Profile support for alternate browser configurations
[PROPOSED] API: Cloud
[PROPOSED] Change default search engine for zh-CN

Round Table

SUMO

Meeting this week to plan a strategy around replying to 1-star reviews on Google Play.

Thought we had a small spike in crash feedback but it turned out to be nothing.

Getting ready for Firefox 21.

QA

bug 853522 regressed h.264 videos on JB devices. need to uplift fix to all channels
working on a test matrix to cover release coordinate on multiple stores:
bug 856445 – Lg optimus black crash confirmed, over to mfinkle
bug 845729 – SGS2 blocklist confirmed, awaiting beta uplift to retest

Details

Wednesdays – 9:30am Pacific, 12:30pm Eastern, 16:30 UTC
Dial-in: conference# 99998
- US/International: +1 650 903 0800 x92 Conf# 99998
- US toll free: +1 800 707 2533 (pin 369) Conf# 99998
- Canada: +1 416 848 3114 x92 Conf# 99998
- FR/Paris: +33 1 44 79 34 80, x92 Conf# 99998
irc.mozilla.org #mobile for backchannel
Mobile Vidyo Room

Retrieved from “?title=Mobile/Notes/08-May-2013&oldid=653497“

Meeting Notes: Firefox/Gecko Delivery Planning: 2013-05-08

Jesper Kristensen — Thu, 09 May 2013 03:00:06 +0000

Schedule & Progress onUpcoming Releases

Firefox Desktop

Beta (21)

- FF21.0b7 Desktop is ready to go
- FF21.0b7 Mobile was shipped yesterday
- FF21.0 final RC build’s have gone to build and are with QA

Firefox Metro

Iteration #7: May 02 – May 23
- 14% of the iteration work (20 points across 10 stories) has been completed to date (see table below).
- 35% of the total project work has been completed to date.
- We will be releasing figures on the project’s quality performance and defect levels at the conclusion of Iteration #7.
- Product Manager is reviewing release build to determine which ‘out of scope’ legacy features to turn off in V1.
- Team on Work Week from May 13 – May 17.
Iteration #6: Finished on April 30
- Team completed 74 story points across 20 features.
- Team achieved a new average velocity of 51 story points per iteration which was an 8% improvment from the previous iteration.
- Overall performance gain has resulted in a new expected production release forecast of November 19, 2013 – a reduction of 2 iterations from the previous status update.
- Production Release Forecast now includes Best Case and Worst Case scenarios – View Release Forecast

ID	Summary	Priority	Status
862209	Defect: Unloaded websites reloading after closing them while using “tabs from last time”	P1	ASSIGNED
867115	Defect – Context menu in snapped view shows the tab bar for an instant	P1	ASSIGNED
831909	Story – Text selection in Firefox app bar (touch)	P1	ASSIGNED
866065	Defect – ms-windows-store:// links should not need to be opened with an application	P1	ASSIGNED
860899	Story – Fixup all failing mochitest-metro-chrome tests in automation	P1	ASSIGNED
831915	Story – Implement Tile Widget and Groups – Part I	P1	ASSIGNED
831905	Story – Secure site indicators in the Firefox app bar	P1	ASSIGNED
855147	Defect: Settings do not persist when closing Firefox from desktop application bar	P1	ASSIGNED
835623	Story – Combine page contextual items (URL bar, bookmark star, etc.) into single app bar	P2	ASSIGNED
850737	Story – Smoothly scroll the Firefox Start screen – Part I	P2	ASSIGNED
833182	Story – Updating Metro Firefox	P2	ASSIGNED
849395	Story – Allow updates via about flyout	P2	ASSIGNED
855297	Story – Provide a consistent OSK experience for when users have no keyboard and mouse	P2	ASSIGNED
781002	Story – Apply metro styling to the context menu	P2	ASSIGNED
831913	Story – Use the Firefox app bar in snapped view	P2	REOPENED
867163	Defect – Restore tile button doesn’t work when context app bar is visible on a second time	P1	RESOLVED
833130	Story – Sync passwords	P2	RESOLVED
833131	Story – Sync bookmarks	P2	RESOLVED
833132	Story – Sync history	P2	RESOLVED
833133	Story – Sync tabs	P2	RESOLVED
849312	[tracking] Backlog – Various sync issues	P2	RESOLVED
856049	Defect – Lower border of “Pair a device” input box is missing	P1	VERIFIED
867121	Defect – Snapped view: Favicons too close to text in awesome screen	P1	VERIFIED
858598	Defect – Select popups near the bottom of the screen are unusable	P1	VERIFIED
856267	Defect – Context Menu overlapping with the Tab App Bar when visible	P1	VERIFIED

Firefox Mobile

Current Releases

Google Star rating is *visual* 4.5 stars. We are tracking 4.25 for GA in actuality but the visual tipping point is a result of lot’s of hard work: https://medium.com/what-i-learned-building/f4488e366b91

Beta (21)

We are backing out the fix for this crash because it blocks too many JB devices. We are considering doing a final beta to increase our confidence prior to GA: bug 853522 – crash in mozilla::MediaPluginHost::DestroyDecoder @ libstagefright.so@0xd… on Samsung Galaxy Tab 2 with espresso & espresso10 hw running JB
Otherwise, we just signed off on Fx21, this will include a push to the Yandex Store

Aurora (22)

The Dynamic URL bar (a.k.a Toolbar) has been deferred from Fx22. It remains enabled in Fx23 for testing and convergence
Slovak will replace Turkish as the next locale to add support for and it is slated for Fx22
Otherwise, double tap reflow-on-zoom, New Tab UI, ANR reporter, Async Canvas Playback

Nightly (23)

Lot’s of good work, namely, last-minute fixes prior to uplift to be sure we’re ready for Aurora
Here is the feature page which is being updated, some of these features our out of scope and we’re identifying incremental progress: https://wiki.mozilla.org/Mobile/Roadmap#Firefox_23:_Real_Media

Services

Firefox Health Report

On track to ship in desktop with Fx21
Will hit Android for either 23 or 24
Dashboards are still coming, but we can get useful data for Nightly/Aurora/Beta, ask mconnor+gps if you have questions.

Product Announcements

No updates.

Feedback Summary

Desktop

USR 20 should be available later this week.

Flash – We are still seeing as much (or more) negative feedback about flash stutter or generally causing a poor experience. Crashkill team reports that Flash crashes are down on beta but it seems to just result in more jerkiness complaints on beta, not sure it’s actually improved the feedback.
Popups – We are seeing a significantly increased amount of popup reports in both Release and Beta. Assuming it is new malware.

Mobile

Meeting this week to plan a strategy around replying to 1-star reviews on Google Play.

Getting ready for Firefox 21.

User Experience (Design and Research)

[desktop]
- [General]
  - Downloads Panel Revisions — Goals: tighter spacing, more information, less button-in-button (Shorlander)
    - Circle Progress — http://cl.ly/image/2L03120N460J
    - Custom Progress Bar — http://cl.ly/image/2V0I1B3G0s0o
- [Australis] (Zhenshuo, Stephen)
  - Supporting implementation; working doc
  - final refinements to visual design – Windows 7 variant (click on the menu button at far right), mac version – not interactive
  - Also see Firstrun section, below
- [Firstrun] (Zhenshuo, Holly)
  - Implementing & testing phase 1(Web only first run)
    - bug 853872, bug 853875
    - Design example: http://cl.ly/image/0m120s3C2i3Z/o
  - Designing & implementing phase 2 (In-chrome first run)
    - bug 862998
    - Design Example: http://cl.ly/image/0h150z1L4526
  - Phase 3: Australis Update
    - Starting next round of design based on http://people.mozilla.com/~zfang/Customization/Australis_UpdateExperience.pdf

[WebRTC] Ramping up! (Boriss)

[Sync, PiCL] Gathering feedback and iterating on Design http://people.mozilla.com/~zfang/FirefoxAccount/PiCL0425.pdf (Zhenshuo)

[metro] (yuan)
- Sync UI adjustments:
  - Confirm before destroying a sync connection bug 868094, mockup
  - Go over sync flyout and signup language bug 868099
  - Adjust Sync UI for better information mapping bug 868217, mockup
- Solution for Auto-complete page: mockup.
- Notification for adding a bookmark: video
- Solution for a new Metro & desktop update preference bug 866229

[android] (ibarlow)
- Blog post from Ian about the outcomes of the UI hackathon: https://blog.mozilla.org/ux/2013/05/polish-all-the-things1/
- Designs ready to go
  - bug 869123 NEW: Quick Share — shortcut to most frequently used sharing service
    - https://bug869123.bugzilla.mozilla.org/attachment.cgi?id=745998
  - bug 867371 Updated Settings UI in progress
    - https://etherpad.mozilla.org/settings-reorg
  - bug 853844 New progress indicator
    - https://bugzilla.mozilla.org/show_bug.cgi?id=853844#c16
  - bug 867633 Consolidate lock icon and forward button animations in toolbar
    - https://bugzilla.mozilla.org/show_bug.cgi?id=867633#c1
  - bug 847435 Updated look for back session history menu
    - https://bug847435.bugzilla.mozilla.org/attachment.cgi?id=746397
  - bug 868998 Reveal title bar by scrolling a certain distance
- Work in progress
  - bug 864958 Some subtle adjustments to the PB chrome
  - bug 808636 Reviewing work in progress on mobile error pages
  - Some discussion around WebRTC door hanger permissions
  - Continuing work with Product on some UX prerequisites for Mozilla Apps on Android
  - Standing by for any and all questions about Multipage About:home
  - Usability testing plan for Multipage about:home
  - TV design concepts (Zhenshuo)
    - Overall Design thinking http://people.mozilla.com/~zfang/TV/FirefoxonTV.pdf
    - Initial UI Sketches http://people.mozilla.com/~zfang/TV/FirefoxTV_Sketches0506.pdf
  - New tablet concepts (Yuan)

Market Insights from the Product Marketing Strategy Team

Desktop / Platform

Google

On iOS, Google has now enabled app developers to integrate Chrome within their mobile applications.
Chrome Beta on Windows and Mac now supports the Chrome Office Viewer, an extension which provides seamless viewing of Microsoft Office files in the browser.
Google Translate added Bosnian, Cebuano, Hmong, Javanese and Marathi, bringing the total number of languages supported to more than 70

Microsoft

Microsoft, in a carefully-worded blog post, said that 100 million Windows 8 licenses had been sold.
Industry analysts complained that poor Windows 8 sales were were partly due to poor retailing practices
Another zero-day vulnerability was found in Internet Explorer 8.

Tizen

Another video of recent Tizen builds is available.

WebKit

WebKit released SunSpider 1.0, an updated version of the Javascript benchmark. Among other improvements, delays between tests have been eliminated so it runs up to twice as fast.

Mobile

2013 is the first year that people will buy more tablets than PCs. There will be 256 million tablets sold and 183 million PCs this year. By 2017 the number of tablets shipped will reach half a billion. This is part of a larger trend of sustaining big growth for tablets, at the rate of 67% year – over – year and a decline in PC shipments, by 10% a year.

New Android version distribution numbers put Gingerbread at 38.5%, Jelly Bean at 28.4% and Ice Cream Sandwich at 27.5%.

Shipments of smartphones in 8 major developed markets and China put Android ahead with 64.2% on average and 68.8% across the EU, 45.8% in Japan, 61.7% in Australia and 49.3% in the US. iOS is shipped on between 19.4% of devices in the EU to 49.2% of them in Japan. Top device models in the surveyed countries are the iPhone 5, the Samsung Galaxy S III, the iPhone 4S, the Galaxy S III Mini, the Galaxy Ace, iPhone 4, LG Nexus 4, Galaxy Ace 2, Galaxy s II and the Blackberry Curve.

Developer builds of Chrome OS feature a touch – screen keyboard. Important because it could mean plans to deploy the OS on tablets.

Google has hired a Chief Game Designer. Gaming is one of the top app categories downloaded through the Play Store

The first two Tizen phones will be in the mid – end to high – end range and code – named Redwood and Melius.

Opera partnered with 7 Indian phone and tablet manufacturers such as Celkon, Karbonn, Lava, Intex, Fly, Zen and HCL ME to have Opera Mini pre – installed on their Android devices.

Marketing, Press & Public Reaction

Firefox 21 highlights from the consumer and industry perspective

Firefox for Android supports extensions: here are some to get you started

Three essential security add-ons for Firefox, Chrome, and IE

Questions, Comments, FYI

No surprises [johnath]

Planning Meeting Details

Wednesdays – 11:00am PT, 18:00 UTC
Mountain View Offices: Warp Core Conference Room
Toronto Offices: Finch Conference Room
irc.mozilla.org #planning for backchannel
(the developer meeting takes place on Tuesdays)

Video/Teleconference Details – NEW

650-903-0800 or 650-215-1282 x92 Conf# 99696 (US/INTL)
1-800-707-2533 (pin 369) Conf# 99696 (US)
Vidyo Room: ProductCoordination
Vidyo Guest URL

Retrieved from “?title=Firefox/Planning/2013-05-08&oldid=653547“