mozilla

Mozilla Nederland LogoDe Nederlandse
Mozilla gemeenschap

Will Kahn-Greene: Input status: August 19th, 2014

Mozilla planet - di, 19/08/2014 - 16:11
Development

High-level summary:

It's been a slower two weeks than normal, but we still accomplished some interesting things:

  • L Guruprasad finished cleaning up the Getting Started guide--that work helps all future contributors. He did a really great job with it. Thank you!
  • Landed a minor rewrite to rate-limiting/throttling.
  • Redid the Elasticsearch indexing admin page.
  • Fixed some Heartbeat-related things.

Landed and deployed:

  • cf2e0e2 [bug 948954] Redo index admin
  • f917d41 Update Getting Started guide to remove submodule init (L. Guruprasad)
  • 5eb6d6d Merge pull request #329 from lgp171188/peepify_submodule_not_required_docs
  • c168a5b Update peep from v1.2 to v1.3
  • adf7361 [bug 1045623] Overhaul rate limiting and update limits
  • 7647053 Fix response view
  • f867a2d Fix rulename
  • 8f0c36e [bug 1051214] Clean up DRF rate limiting code
  • 0f0b738 [bug 987209] Add django-waffle (v0.10)
  • b52362a Make peep script executable
  • 461c503 Improvie Heartbeat API docs
  • 8f0ccd3 [bug 1052460] Add heartbeat view
  • d1604f0 [bug 1052460] Add missing template

Landed, but not deployed:

  • ed2923f [bug 1015788] Cosmetic: flake8 fixes (analytics)
  • afdfc6a [bug 1015788] Cosmetic: flake8 fixes (base)
  • 05e0a33 [bug 1015788] Cosmetic: flake8 fixes (feedback)
  • 2d9bc26 [bug 1015788] Cosmetic: flake8 fixes (heartbeat)
  • dc6e990 Add anonymize script

Current head: dc6e990

Rough plan for the next two weeks
  1. Working on Dashboards-for-everyone bits. Documenting the GET API. Making it a bit more functional. Writing up some more examples. (https://wiki.mozilla.org/Firefox/Input/Dashboards_for_Everyone)
  2. Update Input to ElasticUtils v0.10 (bug 1055520)
  3. Land all the data retention policy work (bug 946456)
  4. Gradients (https://wiki.mozilla.org/Firefox/Input/Gradient_Sentiment)
  5. Product administration views (bug 965796)

Most of that is in some state of half-done, so we're going to spend the next couple of weeks focusing on finishing things.

What I need help with
  1. (django) Update to django-rest-framework 2.3.14 (bug 934979) -- I think this is straight-forward. We'll know if it isn't if the tests fail.
  2. (django, cookies, debugging) API response shouldn't create anoncsrf cookie (bug 910691) -- I have no idea what's going on here because I haven't looked into it much.
  3. (html) Fixing the date picker in Chrome (bug 1012965) -- The issue is identified. Someone just needs to do the fixing.

For details, see our GetInolved page:

https://wiki.mozilla.org/Webdev/GetInvolved/input.mozilla.org

If you're interested in helping, let me know! We hang out on #input on irc.mozilla.org and there's the input-dev mailing list.

Additional thoughts

We're in the process of doing a Personally Identifiable Information audit on Input, the systems it's running on and the processes that touch and move data around. This covers things like "what data are we storing?", "where is the data stored?", "who/what has access to that data?", "does that data get copied/moved anywhere?", "who/what has access to where the data gets copied/moved to?", etc.

I think we're doing pretty well. However, during the course of the audit, we identified a few things we should be doing better. Some of them already have bugs, one of them is being worked on already and the otehrs need to be written up.

Some time this week, I'll turn that into a project and write up missing bugs.

That's about it!

Categorieën: Mozilla-nl planet

Firefox gets Chromecast, but no Mozilla TV hardware yet - PC Pro

Nieuws verzameld via Google - di, 19/08/2014 - 15:13

Android Headlines - Android News

Firefox gets Chromecast, but no Mozilla TV hardware yet
PC Pro
Mozilla UI engineer Lucas Rocha announced yesterday that the new feature has been incorporated into the "Nightly" build of Firefox for Android. Nightly is the first of three channels used in the development of the browser, testing new features before ...
Firefox gains Chromecast support as partner readies Chromecast competitor ...Gigaom
Firefox for Android nightly builds gain Chromecast support9 to 5 Google
Firefox For Android Gains Chromecast Support, Starting With Nightly BuildsAndroid Police
Android Headlines - Android News
alle 6 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Firefox for Android krijgt Chromecast-ondersteuning - Tweakers

Nieuws verzameld via Google - di, 19/08/2014 - 13:51

Firefox for Android krijgt Chromecast-ondersteuning
Tweakers
Via zijn Google+-feed laat Mozilla ui-engineer Lucas Rocha weten dat de laatste testbuild van Firefox for Android deze mogelijkheid nu ook bevat. Op termijn wordt deze optie in de normale mobiele Firefox-releases opgenomen. Dan moeten ook de meeste ...

Categorieën: Mozilla-nl planet

Adam Lofting: Trendlines and Stacking Logs

Mozilla planet - di, 19/08/2014 - 13:49
TL;DR
  • Our MoFo dashboards now have trendlines based on known activity to date
  • The recent uptick in activity is partly new contributors, and partly new recognition of existing contributors (all of which is good, but some of which is misleading for the trendline in the short term)
  • Below is a rambling analogy for thinking about our contributor goals and how we answer the question ‘are we on track for 2014?’
  • + if you haven’t seen it, OpenMatt has crisply summarized a tonne of the data and insights that we’ve unpicked during Maker Party
Stacking Logs

I was stacking logs over the weekend, and wondering if I had enough for winter, when it struck me that this might be a useful analogy for a post I was planning to write. So bear with me, I hope this works…

To be clear, this is an analogy about predicting and planning, not a metaphor for contributors* :D

So the trendline looks good, but…

Screen Shot 2014-08-19 at 11.47.27

Trendlines can be misleading.

What if our task was gathering and splitting logs?

Vedstapel, Johannes Jansson (1)

We’re halfway through the year, and the log store is half full. The important questions is, ‘will it be full when the snow starts falling?

Well, it depends.

It depends how quickly we add new logs to the store, and it depends how many get used.

So let’s push this analogy a bit.

Firewood in the snow

Before this year, we had scattered stacks of logs here and there, in teams and projects. Some we knew about, some we didn’t. Some we thought were big stacks of logs but were actually stacked on top of something else.

Vedstapel, Johannes Jansson

Setting a target was like building a log store and deciding to fill it. We built ours to hold 10,000 logs. There was a bit of guesswork in that.

It took a while to gather up our existing logs (build our databases and counting tools). But the good news is, we had more logs than we thought.

Now we need to start finding and splitting more logs*.

Switching from analogy to reality for a minute…

This week we added trendlines to our dashboard. These are two linear regression lines. One based on all activity for the year to-date, and one based on the most recent 4 weeks. It gives a quick feedback mechanism on whether recent actions are helping us towards to our targets and whether we’re improving over the year to-date.

These are interesting, but can be misleading given our current working practices. The trendline implies some form of destiny. You do a load of work recruiting new contributors, see the trendline is on target, and relax. But relaxing isn’t an option because of the way we’re currently recruiting contributors.

Switching back to the analogy…

We’re mostly splitting logs by hand.

Špalek na štípání.jpg

Things happen because we go out and make them happen.

Hard work is the reason we have 1,800 Maker Party events on the map this year and we’re only half-way through the campaign.

There’s a lot to be said for this way of making things happen, and I think there’s enough time left in the year to fill the log store this way.

But this is not mathematical or automated, which makes trendlines based on this activity a bit misleading.

In this mode of working, the answer to ‘Are we on track for 2014?‘ is: ‘the log store will be filled… if we fill it‘.

Scaling

Holzspalter 2

As we move forward, and think about scale… say a hundred-thousand logs (or even better, a Million Mozillians). We need to think about log splitting machines (or ‘systems’).

Systems can be tested, tuned, modified and multiplied. In a world of ‘systems’ we can apply trendlines to our graphs that are much better predictors of future growth.

We should be experimenting with systems now (and we are a little bit). But we don’t yet know what the contributor growth system looks like that works as well as the analogous log splitting machines of the forestry industry. These are things to be invented, tested and iterated on, but I wouldn’t bet on them as the solution for 2014 as this could take a while to solve.

I should also state explicitly that systems are not necessarily software (or hardware). Technology is a relatively small part of the systems of movement building. For an interesting but time consuming distraction, this talk on Social Machines from last week’s Wikimania conference is worth a ponder:

Predicting 2014 today?

Even if you’re splitting logs by hand, you can schedule time to do it. Plan each month, check in on targets and spend more or less time as required to stay on track for the year.

This boils down to a planning exercise, with a little bit of guess work to get started.

In simple terms, you list all the things you plan to do this year that could recruit contributors, and how many contributors you think each will recruit. As you complete some of these activities you reflect on your predictions, and modify the plans and update estimates for the rest of the year.

Geoffrey has put together a training workshop for this, along with a spreadsheet structure to make this simple for teams to implement. It’s not scary, and it helps you get a grip on the future.

From there, we can start to feed our planned activity and forecast recruitment numbers into our dashboard as a trendline rather than relying solely on past activity.

The manual nature of the splitting-wood-like-activity means what we plan to do is a much more important predictor of the future than extrapolating what we have done in the past, and that changing the future is something you can go out and do.

*Contributors are not logs. Do not swing axes at them, and do not under any circumstances put them in your fireplace or wood burning stove.

Categorieën: Mozilla-nl planet

Rumbling Edge - Thunderbird: 2014-08-18 Calendar builds

Thunderbird - di, 19/08/2014 - 07:14

Common (excluding Website bugs)-specific: (17)

  • Fixed: 344561 – Day/Week view: Header boxes are misaligned if scrollbars are shown
  • Fixed: 680203 – Make Lightning tests work with packaged-tests
  • Fixed: 682109 – Today pane: Today’s date not automatically updated
  • Fixed: 998281 – Default status new event is available, should be busy
  • Fixed: 1000535 – Lightning frequently prompts for access to Google Calendar
  • Fixed: 1002024 – Sending separate invitations to attendees onlys send email for first invited person
  • Fixed: 1007040 – Autocomplete for event invitations: Use uppercase and lowercase of name like in addressbook card
  • Fixed: 1018120 – GMT Timezone with timezone information is assumed to be UTC / events move forward by 1 hour
  • Fixed: 1022113 – Today-pane: too many calls to the function “setCurrentEvent” when updating the attribute “current”
  • Fixed: 1022129 – In the calendar views the day marked as Today doesn’t update at midnight
  • Fixed: 1026623 – Set em:strictCompatibility to ensure the right Lightning version is used.
  • Fixed: 1031715 – Converting email to event shouldn’t fail when Thunderbird Conversations is installed
  • Fixed: 1041566 – Lightning 3.5 broken with 2014-07-21 update
  • Fixed: 1042125 – Make the CalDAV provider async safe
  • Fixed: 1042741 – No buttons on invitations or response to invitations [incompatibility between Thunderbird Conversations and Lightning]
  • Fixed: 1042849 – Remove Serbian [sr] from /calendar/locales/shipped-locales
  • Fixed: 1049201 – Nighly builds broken due to incorrect manifest paths

Sunbird will no longer be actively developed by the Calendar team.

Windows builds Official Windows

Linux builds Official Linux (i686), Official Linux (x86_64)

Mac builds No binaries since July 23, 2014.

Categorieën: Mozilla-nl planet

Rumbling Edge - Thunderbird: 2014-08-18 Thunderbird comm-central builds

Thunderbird - di, 19/08/2014 - 07:11

Thunderbird-specific: (30)

  • Fixed: 273884 – Enclosing double quotes are shown in recipient column, messes up sorting of name/address
  • Fixed: 934875 – Thunderbird: No status bar accessible
  • Fixed: 964377 – Intermittent test-attachment-reminder.js | test-attachment-reminder.js::test_manual_automatic_attachment_reminder_interaction
  • Fixed: 967583 – Tooltip for ‘Get Mail for’ button says ‘nobody’ for Local Folders, Feed and News accounts, sometimes ends with comma
  • Fixed: 985641 – random orange: test-session-store.js | test-session-store.js::test_restore_single_3pane_persistence + test-session-store.js::test_restore_single_3pane_persistence_again + test-session-store.js::test_message_pane_height_persistence + test-session-store.j
  • Fixed: 1009469 – For recipient autocomplete matches other than {Name beginsWith}, [tab] no longer confirms suggested recipient (“foo >> somefoo <mail@asdf.com>” is retained as recipient). Suggestion becomes stale/unresponsive when TB loses focus.
  • Fixed: 1018241 – Customize option in Search Messages continues to be wonky
  • Fixed: 1018960 – Severe bug with empty junk can cause deletion of inbox (If selected folder at Folder Pane is changed while folder context menu of Junk is shown, “Empty Junk” clears wrong folder)
  • Fixed: 1020339 – Add UI for disabling and clearing Visited Link/Browsing History
  • Fixed: 1021684 – Update box.com Filelink implementation to new APIs
  • Fixed: 1024017 – Add ability to choose info shown in the desktop chat notifications
  • Fixed: 1024130 – Address book sorting not sticky
  • Fixed: 1024600 – Enable test-attachment-reminder.js mozmill tests on Windows again
  • Fixed: 1026608 – Delete button on main toolbar doesn’t always change to “Undelete” when toggled from keyboard or header pane
  • Fixed: 1034732 – comm-central build for win64 is not updated after 2014-06-13
  • Fixed: 1034818 – No gap between on toolbarbuttons icon and text in Icons beside Text mode
  • Fixed: 1035650 – Remove public destructors of NS_*_INLINE_* refcounted classes, Remove NS_HIDDEN, Fix dangerous public destructors. in mail/ and mailnews/
  • Fixed: 1037751 – Use white graphics for the phishing icon
  • Fixed: 1037795 – Port Bug 1034360 to TB – remove OCSP preference UI (or at least remove the unnecessary dialog window)
  • Fixed: 1038029 – Undefined symbols during |making ./libprldap60.dylib|
  • Fixed: 1038323 – Clear Recent History menuitem doesn’t have a keyboard shortcut
  • Fixed: 1038588 – DebuggerServer’s closeListener has been changed to closeAllListeners()
  • Fixed: 1038647 – perma orange: TEST-UNEXPECTED-FAIL | mozmill/utils/test-iteratorUtils.js | test-iteratorUtils.js::test_toArray_custom_content_iterator
  • Fixed: 1038745 – No builds for latest nightly localization of Thunderbird for win32
  • Fixed: 1038909 – Disable what’s new page for now
  • Fixed: 1039798 – perma-orange: test-message-header.js::test_address_book_switch_disabled_on_contact_in_mailing_list
  • Fixed: 1040831 – Daily 33.0a1 gives “Couldn’t load XPCOM” error and startup fails since updating this morning
  • Fixed: 1041475 – TEST-UNEXPECTED-FAIL | mozmill/content-tabs/test-install-xpi.js | test-install-xpi.js::test_install_corrupt_xpi + test-install-xpi.js::test_install_xpi_offer + test-install-xpi.js::test_xpinstall_disabled + test-install-xpi.js::test_xpinstall_actually_i
  • Fixed: 1045026 – Cannot use “thunderbird” as PROGRAM name, because it is already used in mail/components/search/mdimporter
  • Fixed: 1050363 – Thunderbird fails to compile nsldif32v60.dll: LINK : fatal error LNK1104: cannot open file ‘mozcrt.lib’

MailNews Core-specific: (34)

  • Fixed: 367011 – “Remove All Tags” does not do so for custom tags
  • Fixed: 553757 – SMTP server pref dialog: “Password, transmitted insecurely” doesn’t fit after switching from SSL to non-SSL
  • Fixed: 662907 – web site from RSS feed not rendered correctly (due to noscript tags)
  • Fixed: 960854 – Port |Bug 920353 – pymake native commands can’t easily use e.g. mozbuild modules| to c-c
  • Fixed: 966053 – Recipient area mishandles display names with commas in them (e.g. “LastName, FirstName”), during autocomplete creates dysfunctional extra “LastName” recipients without email address
  • Fixed: 992879 – Folders created with a colon (:) or star (*) in Tb24 on linux are duplicated with hash names on startup with Tb trunk or earlier, such local folders/feeds do no longer work
  • Fixed: 1013123 – Increase width of ‘Enter a tag prefix’ textbox for prefix of autotagged category names of feed articles
  • Fixed: 1015774 – errUtils.js::logException shows the same exception to Error console twice
  • Fixed: 1024053 – Modify test_quarantineFilterMove.js to use Promises
  • Fixed: 1024908 – If the focus is returned to filter action list and the previously focused item is no longer there, an exception is shown
  • Fixed: 1025548 – Preliminary perf/code org tweaks for Bug 257037
  • Fixed: 1033963 – Add mailnews.message_warning_size to prefs.
  • Fixed: 1034231 – Modify test_offlineCopy.js to use Promises.
  • Fixed: 1036619 – Implement 1035394 – Add dangerous public destructor detection to _INHERITED refcounting macros in comm-central
  • Fixed: 1037479 – Move LOCAL_INCLUDES to moz.build in c-c
  • Fixed: 1037482 – Move TESTING_JS_MODULES to moz.build in c-c
  • Fixed: 1037775 – Port |bug 1036864 – Remove EXPORT_LIBRARY| to MailNews
  • Fixed: 1037947 – Fix test_movemailDownload.js to work with maildir
  • Fixed: 1042294 – crash NS_ProxyRelease(nsIEventTarget*, nsISupports*, bool), typically during import
  • Fixed: 1043019 – Port |Bug 1036894 – Move in-tree library linkage information to moz.build| and |Bug 1041936 – Allow static library definitions to depend on shared libraries| to comm-central
  • Fixed: 1043040 – Port |Bug 1036694 – merge nsIMarkupDocumentViewer into nsIContentViewer| to comm-central
  • Fixed: 1044460 – Port relevant changes from Bug 1043344 for moving libraries and programs build to the compile tier
  • Fixed: 1044999 – No L10n builds for Thunderbird for aurora/central due to client.py not allowing –skip-venkman
  • Fixed: 1046638 – Port |Bug 1044162 – make install locations for EXTRA_{PP_,}JS_MODULES better| to comm-central
  • Fixed: 1046826 – Use m-c’s config/makefiles/debugmake.mk in c-c’s rules.mk
  • Fixed: 1048042 – Port |Bug 780159 – Remove obsolete REGCHROME| and |Bug 935387 – Remove non recursed install targets| to comm-central
  • Fixed: 1048561 – Fix up after landing of Bug 1043041 – Replace use of NSPR’s PRTime with a safer type in mozilla::pkix
  • Fixed: 1049935 – Port |Bug 1045783 – move OS_LIBS += $(call EXPAND_LIBNAME,…) calls to moz.build| to comm-central
  • Fixed: 1049936 – Port |Bug 1046784 – move -DNOMINMAX definitions to moz.build| to comm-central
  • Fixed: 1050086 – C-c needs a “port” of bug 1047267
  • Fixed: 1050708 – buildid no longer being set on Thunderbird comm-central builds (make upload and graph server posts fail)
  • Fixed: 1051619 – Port |Bug 914274 – Remove MODULE_NAME| to comm-central
  • Fixed: 1052602 – Fix various xpcshell issues in gloda land and others
  • Fixed: 1052985 – Fix windows manifest build issues

Windows builds Official Windows, Official Windows installer

Linux builds Official Linux (i686), Official Linux (x86_64)

Mac builds No binaries since July 23, 2014.

Categorieën: Mozilla-nl planet

Firefox OS'lu Mozilla Flame satışa çıktı - Hürriyet

Nieuws verzameld via Google - di, 19/08/2014 - 05:21

Hürriyet

Firefox OS'lu Mozilla Flame satışa çıktı
Hürriyet
Kimden mi bahsediyoruz: Tabii ki Mozilla! Aradan geçen zaman içerisinde Firefox OS'u geliştiren Mozilla, uzun zamandır beklenen ve bu işletim sistemi ile çalışan telefonunu nihayet piyasaya sürdü! Firma tarafından yapılan açıklamaya göre Flame isimli ...
Mozilla'nın İlk Telefonu Flame Satışta!ShiftDelete
Mozilla ilk telefonunu satışa sunduTimeturk

alle 17 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Laurent Jouanneau: Release of SlimerJS 0.9.2

Mozilla planet - ma, 18/08/2014 - 22:24

Few days ago, I released a minor version of SlimerJS, my scriptable browser based on XulRunner: SlimerJS 0.9.2.

If you discover my project: this is a browser which is controlled by a script, not by a human. So it has no user interface. In fact this is a browser like PhantomJS, which proposes the same API as PhantomJS. But it is based on Gecko, not on Webkit. See my previous post about the start of the project.

This new version fixes some bugs and is now compatible with Gecko/Firefox/Xulrunner 31.

Next big work on SlimerJS:

  • fix last issues that prevent GhostDriver to work well with SlimerJS
  • support Marionette(https://developer.mozilla.org/en-US/docs/Mozilla/QA/Marionette)
  • try to implement remote debugging, to allow to debug your script from Firefox Dev Tools
  • try to have a true headless browser (so to have a browser without visible windows)

Help is welcomed, See you on Github ;-)

Categorieën: Mozilla-nl planet

Christian Heilmann: Makethumbnails.com – drop images into the browser, get a zip of thumbnails

Mozilla planet - ma, 18/08/2014 - 20:53

About 2½ years ago I wrote a demo for Mozilla Hacks how to use Canvas to create thumbnails. Now I felt the itch to update this a bit and add more useful functionality. The result is:

http://makethumbnails.com

It is very easy to use: Drop images onto the square and the browser creates thumbnails for them and sends them to you as a zip.

homepage

Thumbnail settings page

You can set the size of the thumbnails, if you want them centered on a coloured background of your choice or cropped to their real size and you can set the quality. All of this has a live preview.

If you resize the browser to a very small size (or click the pin icon on the site and open a popup) you can use it as neat extra functionality for Finder:

resize to simple mode

All of your settings are stored locally, which means everything will be ready for you when you return.

As there is no server involved, you can also download the app and use it offline.

The source, of course, of course is available on GitHub.

To see it in action, you can also watch the a quick walkthrough of Makethumbnails on YouTube

Happy thumbing!

Chris

Categorieën: Mozilla-nl planet

Rizky Ariestiyansyah: Webmaker with SMK ITACO

Mozilla planet - ma, 18/08/2014 - 20:08

August 18, 2014 we will carry out the webmaker event we’ve scheduled previously, the event held at SMK ITACO Bekasi, this is a vocational school for children who are less economic conditions. We only...

The post Webmaker with SMK ITACO appeared first on oonlab.

Categorieën: Mozilla-nl planet

Doug Belshaw: Facebook and Twitter: beyond the like/favorite binary?

Mozilla planet - ma, 18/08/2014 - 18:09

There’s been a couple of developments with the social networks Facebook and Twitter that fit together quite nicely this week. The first is the news that Facebook likes make a huge difference in terms of what you see while browsing your news feed:

Wired writer Mat Honan found out what happens when you like every single thing that shows up in your Facebook feed. The results were dramatic: Instead of his friends’ updates, he saw more and more updates from brands and publishers. And, based on what he had liked most recently, Facebook’s algorithm made striking judgements about his political leanings, giving him huge numbers extremely right-wing or extremely left-wing posts. What’s more, all that liking made Honan’s own posts show up far more in his friends’ feeds — distorting their view of the world, too.

But Medium writer Elan Morgan tried the opposite experiment: Not liking anything on Facebook. Instead of pressing like, she wrote a few thoughtful words whenever she felt the need to express appreciation: “What a gorgeous shock of hair” or “Remember how we hid from your grandmother in the gazebo and smoked cigarettes?” The result, as you might guess, is just the opposite of Honan’s experience: Brand messages dwindled away and Facebook became a more relaxed, conversational place for Morgan.

The second piece of news is that Twitter is experimenting with changes to the way that ‘Favorites’ work:

Favorites have also been pseudo-private; while you can view a list of favorited tweets from an account’s profile page or on a tweet’s detail page, typically only the “favoriter” and the “favoritee” ever know about it. If Twitter starts surfacing favorited tweets in timelines, they’ve suddenly become far more public. The change — and the backlash — is somewhat similar to Facebook’s attempts to share just about everything “friends” did with Open Graph.

[…]

For those who have used Twitter for years, the change is so shocking it can seem like the company is completely ignorant to how its customers use the service. But even seasoned Twitter veterans should admit that the service’s core functionality is fairly arcane — it’s far from accessible to new users, and that’s a problem for Twitter.

What I find interesting is that most sites allow you to ‘love’, ‘like’, ‘favourite’, ‘+1’ or otherwise show your appreciation towards content. You can do this with Mozilla Webmaker too, when browsing the gallery. The trouble is that this is extremely limiting when it comes to data mining. If it’s used in conjunction with an algorithm to serve up content (not currently the case with Webmaker) then it’s a fairly blunt instrument.

There are some sites that have attempted to go beyond this. I’m thinking specifically of Bit.ly for Feelings, which allows you to share content that you don’t agree with. But there’s not a lot of great examples.

The trouble is, I guess, is that human emotions are complex, changeable and along three-dimensional analogue spectrum. Digital technologies, on the other hand - and particularly like/favorite buttons - are binary.

Update: after posting this I found that Yahoo! are planning to scan photos you publish on Tumblr to gauge brand sentiment. I’m not sure if that’s better or worse, to be honest!

Questions? Comments? I’m @dajbelshaw on Twitter, or you can email me at doug@mozillafoundation.org

Categorieën: Mozilla-nl planet

Nigel Babu: Arrrgh! Tracebacks and Exceptions

Mozilla planet - ma, 18/08/2014 - 17:45

My colleague asked me to take a look at a logging issue on a server last week. He noticed that the error logs had way too little information about exceptions. In this particular instance, we had switched to Nginx + gunicorn instead of our usual Nginx + Apache + mod_wsgi (yeah, we’re weird). I took a quick look this morning and everything looked exactly like they should. I’ve read up more gunicorn docs today than I’ve ever done, I think.

Eventually, I asked my colleague Tryggvi for help. I needed a third person to tell me if I was making an obvious mistake. He asked me if I tried running gunicorn without supervisor, which I hadn’t. I tried that locally first, and it worked! I was all set to blame supervisor for my woes and tried it on production. Nope. No luck. As any good sysadmin would do, I checked if the versions matched and they did. CKAN itself has it’s dependencies frozen, this lead to more confusion in my brain. It didn’t make sense.

I started looking at the Exception in more detail, there was a note about email not working and the actual traceback. Well, since I didn’t actually have a mail server on my local machine, I commented those configs out, and now I just had the right Traceback. A few minutes later, it dawned on me. It’s a Pylons “feature”. The full traceback is printed to stdout if and only if there’s no email handling. Our default configs have an email configured and our servers have postfix installed on them and all the errors go to an email alias that’s way too noisy to be useful (Sentry. Soon). I went and commented out the relevant bits of configuration and voilà, it works!

Palm Face

Image source: Unknown, but provided by Tryggvi :)

Categorieën: Mozilla-nl planet

J. Ryan Stinnett: WebIDE enabled in Nightly

Mozilla planet - ma, 18/08/2014 - 17:44

I am excited to announce that WebIDE is now enabled by default in Nightly (Firefox 34)! Everyone on the App Tools team has been working hard to polish this new tool that we originally announced back in June.

Features

While the previous App Manager tool was great, that tool's UX held us back when trying support more complex workflows. With the redesign into WebIDE, we've already been able to add:

  • Project Editing
    • Great for getting started without worrying about an external editor
  • Project Templates
    • Easy to focus on content from the start by using a template
  • Improved DevTools Toolbox integration
    • Many UX issues arose from the non-standard way that App Manager used the DevTools
  • Monitor
    • Live memory graphs help diagnose performance issues

Transition

All projects you may have created previously in the App Manager are also available in WebIDE.

While the App Manager is now hidden, it's accessible for now at about:app-manager. We do intend to remove it entirely in the future, so it's best to start using WebIDE today. If you find any issues, please file bugs!

What's Next

Looking ahead, we have many more exciting things planned for WebIDE, such as:

  • Command line integration
  • Improved support for app frameworks like Cordova
  • Validation that matches the Firefox Marketplace

If there are features you'd like to see added, file bugs or contact the team via various channels.

Categorieën: Mozilla-nl planet

Gregory Szorc: Mercurial hooks move and testing Mercurial

Mozilla planet - ma, 18/08/2014 - 17:10

Mozilla has a number of source repositories under https://hg.mozilla.org/hgcustom/ that cumulatively define how version control works at Mozilla.

Back in February, I launched an effort to establish a unified Mercurial repository for all this code. That repository is version-control-tools and it has slowly grown.

The latest addition to this repository is the import of the hghooks repository. This now-defunct repository contained all the server-side Mercurial hooks that Mozilla has deployed on hg.mozilla.org.

Soon after that repository was imported into version-control-tools, we started executing the hooks tests as part of the existing test suite in version-control-tools. This means we get continuous integration, code coverage, and the ability to run tests against multiple versions of Mercurial (2.5.4 through 3.1) in one go.

This is new for Mozilla and is a big deal. For the first time, we have a somewhat robust testing environment for Mercurial that is testing things we run in production.

But we still have a long way to go. The ultimate goal is to get everything rolled into the version-control-tools repository and to write tests for everything people rely on. We also want the test environment to look as much like our production environment as possible. Once that's in place, most of the fear and uncertainty around upgrading or changing the server goes away. This will allow Mozilla to move faster and issues like our recent server problems can be diagnosed more quickly (Mercurial has added better logging in newer versions).

If you want to contribute to this effort, please write tests for behavior you rely on. We're now relying on Mercurial's test harness and test types rather than low-level unit tests. This means our tests are now running a Mercurial server and running actual Mercurial commands. The tests thus explicitly verify that client-seen behavior is exactly as you intend. For an example, see the WebIDL hook test.

So what are you waiting for? Find some gaps in code coverage and write some tests today!

Categorieën: Mozilla-nl planet

Matt Thompson: Webmaker: what is the latest data telling us?

Mozilla planet - ma, 18/08/2014 - 17:00

What are we learning? This post highlights new metrics and some early analysis from Adam, Amira, Geoff, Hannah and many others. The goal: turn our various sources of raw data into some high-level narrative headlines we can learn from.

Getting to 10K

Current contributor count: 5,529 (Aug 15)

  • Are we on track to hit 10K? No, not yet. The statistical increase we’re seeing is based on good work to record past contribution. But our current growth-rate isn’t enough.
  • Why is the 4-week trend-line up? Because of Maker Party + bulk capturing historical activity (especially Hive + MVP contribution badges).
  • What can we do to grow faster? Short term, we can focus on (amongst other things):

    • 1) Maker Party partners. Convert more partner commitments into action, through a streamlined on-boarding process.
    • 2) Webmaker users. Try to convert more users into contributors. Ask them to do something more directly.
    • 3) Training. Net Neutrality teach-ins, train the trainer events, MozCamps, etc.
      • + …what else?

Webmaker users

Highlights:

  • We now have about 120K Webmaker users. We’re seeing big recent increases, mostly thanks to the snippet.
  • About 2% of those users are currently contributors.
  • ~50% of users have published something.
    • Most of that publishing happens on the user’s first day. (Users who don’t make something on their first day tend not to make anything at all.)
    • There’s very little overlap between tools. Users tend to make with a single tool. (e.g., of the ~46K people who have made something, only 2K have made something with both Thimble and Popcorn.)
    • About 20% have opted in to receive email updates from us. (e.g., via BSD)

Owned media
  • Snippet
    • Our top snippet performer: “The Web is your playground! See what you can build with Mozilla Webmaker and our global Maker Party.” (+ animated pug icon)
      • CTR = 0.58%. (Other MP variations: 0.15% – 0.49%)
      • The icon and animation have a big influence on CTR. Fun icons and playfulness are the hook.
      • “Teach and learn” language generally performs as well as more playful language.

  • Landing pages
    • A “survey-based approach” is our top performer. Asking people *why* they’re interested in Webmaker. (vs straight email sign-up ask) (+4.7% conversion rate)
    • 80 / 20 split for learning vs. teaching. About 78% of survey respondents express interest in making / learning, with 22% wanting to teach / mentor.
  • Language focused on teaching, learning and education performs well.
    • e.g., “Welcome to Webmaker, Mozilla’s open source education project, where you can teach and learn the web through making.” (+17%)
    • vs. “We believe anyone can be a tinkerer, creator, builder of the Web. Including you.”

  • Mozilla.org referral traffic
    • “Webmaker” out-performs “Maker Party.” Our conversion rate dropped to half when we shifted from from “Learn the web” to “Join our Maker Party.”

“The further away we get from the Mozilla brand, the more work there is to get someone on board.” — Adam

Maker Party
  • 1,796 events currently entered (Aug 15)
    • That means we’ve already surpassed last year’s total! 1,694 total Maker Party events last year, vs. same number in our first month this year.
    • But: we’ll still need a big event push in second half to hit our contributor target.
  • Key takeaways:
    • Tracking partner activity. Automated tracking has been hard — we’re relying instead on one-to-one calls.
    • We’re gathering great data from those calls. e.g.,
      • Unreported success. Partners are participating in ways that aren’t showing up in our system. Manual badging is filling that gap.
      • Occasional confusion about the ask. Some think “Maker Party” is a “MozFest-level” commitment. They don’t realize the ask is simpler than that.
      • They need easier ways to get started. More simplification and hand-holding. Working on a simplified “Event Wizard” experience now.
      • Some partners see more value in Maker Party than others. Orgs with offerings similar to our own may perceive less value than those in adjacent spaces.
    • We haven’t cracked the earned media nut. Not much coverage. And little evidence of impact from the coverage we got.
    • We don’t have a good way for measuring participation from active Mozillians.
    • Second half. We should gear up for a second “back to school” wave to maximize contributors.

“There’s the ‘summer wave’ and ‘back to school’ waves. We need to have strategies and actions towards both.” –Hannah

Next steps

Short-term focus:

  • 1) Partner conversion. This is probably our best immediate strategy for boosting contribution. Ship a simplified on-ramp for Maker Party partners. A new “Event Wizard,” simple start-up events, and user success support.
  • 2) Convert Webmaker users to contributors. We’ve seen a *big* increase in user numbers. This opens an opportunity to focus on converting those users. Ask them to do something more directly. Try new low-bar CTAs, email optimization, re-activating dormant users, etc.
  • 3) Training. Train the trainer events, MozCamps, MozFest, etc.

Longer-term questions

  • Year-long engagement. How do we more evenly distribute event creation throughout the entire year?
  • Match-making. How do we identify the teachers? How do we connect those who want to learn with those who want to teach? What are the pathways for teachers / learners?
  • Impact. How many people are learning? How much are they learning? Should we make “number of people learning” Webmaker’s KPI in 2015?
Categorieën: Mozilla-nl planet

Jess Klein: Remix + Hack the Firefox Home page. No really, we want you to!

Mozilla planet - ma, 18/08/2014 - 15:28
If you are a Firefox desktop user, you may have seen the Firefox default home page. This page contains a default engine web search and quick links to downloads, bookmarks, history, add-ons, sync and settings. Additionally, if you happen to have had tabs open the last time you used the browser,  you can restore them from the home page.  We often share important news and updates underneath the search bar.
Screen Shot 2014-08-15 at 10.18.04 AM.png
This is what I currently see at the Firefox default home page. Animated gifs FTW.

THE OPPORTUNITYA few months back, Hive Labs, (a new project within the Hive Learning Networks designed to explore the question “how do we use design to transform edupunk ethics into great products?”), was approached by the Mozilla Foundation Engagement team to brainstorm how the space could be used in an innovative way to educate Firefox users about the Maker Party. Maker Party is Mozilla's global campaign to teach the web, uniting educators, organizations and enthusiastic web users with hands-on learning and making. While I have to admit, I have never really created something in the realm of owned media, I saw this as an interesting opportunity for Mozilla to show (vs. tell) what Maker Party is all about.  

THE CHALLENGE

The team (which included creative individuals from many different projects across the Mozilla Foundation and the Corporation) immediately identified the opportunity space and came up with a few project requirements:
  • use the space in an interactive way to introduce the website visitor to web literacy skills
  • acknowledge that the visitor may not have ever seen code before, and understand that we do not know what web literacy skills they are coming to this space with
  • create something playful


THE SOLUTION

While we tossed around a few different ideas, the solution that we came up with was to create a Webmaker Goggles - like experience that lets the visitor see under the hood of the webpage.

Screen Shot 2014-08-15 at 10.35.04 AM.png

After doing some initial sketches, we realized that we needed to define our learning objectives for the project.  While normally this is fairly easy to do - you say that the learner will come away with the ability to remix a paragraph written in HTML and understand what p tags are, or something very basic. Here, the challenge was two-fold: 1. the webpage visitor did not identify as a learner and 2. as I mentioned before, they might have no knowledge of the fact that the code is written in order to create a webpage. So, after several false starts, we came up with the the goal of having the website visitor walk away understanding that if you look under the hood of a webpage, you will see it is made from code.

Initial sketches for the snippet included replacing the Firefox logo with an image

After the learning objective was defined, we had to interpret what that meant in terms of interaction design. I believe that the most effective way to empower a user is to put the tools in their hands to allow them to directly address and grapple with the thing that they might learn by tinkering with it themselves. We tried out a few different iterations on this. Above is a sketch where the visitor might get instructed to remix the page from a video. The idea was to have a person in the video describe what to do, and then the learner would use the goggles to swap out the video for an image or video of their choosing. This idea was fun, and had a lot of potential community localization opportunities. However, there was a risk that the user would just not click on the video, and miss out on all the fun.

Ultimately, we ended up utilising what Atul Varma calls “cruise control” —that’s where we model the behavior in order to encourage the site visitor to try it out themselves. It looks like someone is typing out all of the words on the screen.  We decided to focus on revealing a little CSS, because you can use real words to represent colors and seeing those colors immediately can have a visceral impact on the site visitor. Here is a screencast of the interaction:


We’re really excited about this project, as it represents one of the first interactive uses (if not THE first) of the space of the Firefox home page. We hope that as site visitors dip their toes into understanding the craft of the Web, they’ll be inspired to learn more through Webmaker and Maker Party.  Our ultimate goal is for people to feel empowered to become creators, not just consumers, of the Web.
Categorieën: Mozilla-nl planet

Mozilla macht Firefox-OS-Referenzgerät Flame wieder verfügbar - ZDNet.de

Nieuws verzameld via Google - ma, 18/08/2014 - 13:07

Mozilla macht Firefox-OS-Referenzgerät Flame wieder verfügbar
ZDNet.de
Mozilla hat sein erstes Referenzgerät für sein Smartphone-Betriebssystem Firefox OS erneut verfügbar gemacht – und dazu ein zweites Mal eine Präsentation versandt, was einige US-Techniksites täuschte: Sie glaubten, es handle sich um eine ...
Mozilla Flame: Smartphone mit Firefox OS erhältlichChip Online
"Mozilla bietet Interessierten das Smartphone Flame mit dem Betriebssystem ...Ad-Hoc-News (Pressemitteilung)
Firefox OS Flame wird an Entwickler ausgeliefertTechNews

alle 5 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Mozilla Releases $170 Smartphone Featuring 'RAM Throttling' Capability - Yahoo News UK

Nieuws verzameld via Google - ma, 18/08/2014 - 12:36

Mozilla Releases $170 Smartphone Featuring 'RAM Throttling' Capability
Yahoo News UK
Although primarily targeted at developers who pre-ordered Mozilla Flame (when the smartphone was opened for pre-ordering in May this year), general users who have pre-ordered the smartphone can also test the device's functionality, and report issues, ...
Mozilla now shipping Flame phone to develo ...MobileSyrup.com

alle 5 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Jordan Lund: This week in Releng - Aug 11th 2014

Mozilla planet - ma, 18/08/2014 - 08:38

Completed work (resolution is 'FIXED'):


In progress work (unresolved and not assigned to nobody):

Categorieën: Mozilla-nl planet

Mozilla Releases $170 Smartphone Featuring 'RAM Throttling' Capability - International Business Times UK

Nieuws verzameld via Google - ma, 18/08/2014 - 08:13

Mozilla Releases $170 Smartphone Featuring 'RAM Throttling' Capability
International Business Times UK
Although primarily targeted at developers who pre-ordered Mozilla Flame (when the smartphone was opened for pre-ordering in May this year), general users who have pre-ordered the smartphone can also test the device's functionality, and report issues, ...
Mozilla now shipping Flame phone to develo ...MobileSyrup.com

alle 4 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Pagina's