mozilla

Mozilla Nederland LogoDe Nederlandse
Mozilla-gemeenschap

Mozilla Firefox Adds Browser Based Virtual Reality Feature - ProgrammableWeb

Nieuws verzameld via Google - wo, 28/01/2015 - 20:54

ChristianToday

Mozilla Firefox Adds Browser Based Virtual Reality Feature
ProgrammableWeb
Mozilla has added core virtual reality support to its Firefox Nightly builds. Mozilla has long desired to bring VR functionality to the mainstream Web. Adding VR capability to Firefox's development version takes Mozilla one step closer to making its ...
Mozilla looking to add a virtual reality feature to its Firefox browserChristianToday
Experience Virtual Reality on Your Browser With Firefox Nightly BuildsWCCFtech
Easily Make Old Extensions Work With Current Version of FirefoxThe Epoch Times

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

Air Mozilla: Product Coordination Meeting

Mozilla planet - wo, 28/01/2015 - 20:00

Product Coordination Meeting Weekly coordination meeting for Firefox Desktop & Android product planning between Marketing/PR, Engineering, Release Scheduling, and Support.

Categorieën: Mozilla-nl planet

Search Google without being tracked on Mozilla Firefox with Abine Private ... - Techworm

Nieuws verzameld via Google - wo, 28/01/2015 - 19:48

Techworm

Search Google without being tracked on Mozilla Firefox with Abine Private ...
Techworm
Blur is available for all the major browsers but the Google Private Search is available only for Mozilla Firefox as a add-on. To use Blur with the Google Private Search, you are required to sign on for Abine Blur. Blur settings give you options to ...
Blur lets you search privately on GoogleGhacks Technology News

alle 8 nieuwsartikelen »Google Nieuws
Categorieën: Mozilla-nl planet

Yunier José Sosa Vázquez: 6 años llevando la voz de Mozilla a la Intranet cubana

Mozilla planet - wo, 28/01/2015 - 19:00

Hace 6 años y coincidiendo con la natalicio de nuestro Héroe Nacional José Martí, un grupo de interactivos estudiantes lidereados por Erick realizaron un hito en nuestra universidad, fundaban Firefoxmanía, en aquellos tiempos, la comunidad Firefox de la UCI.

Foto Comunidad

Hoy, somos la Comunidad Mozilla de Cuba, un nombre que nos hemos ganado gracias a todos los que nos visitan, participan en los eventos y nos siguen en el país. Se dice fácil, pero la verdad es que tenemos la tarea de dar lo mejor y nuestro mayor esfuerzo.

En todo este tiempo, se han realizado disímiles eventos en los que hemos disfrutado compartir los mismo intereses, actividades en las que nos relacionamos más y crecemos juntos. ¿Quién olvidará el logo gigante pintado entre la plaza Mella, el docente 1 y el 3, o el logo en la yerba al lado del docente 1? También se han publicado más de 950 noticias y 450 complementos, la instalación de complementos supera el medio millar y las descargas las 200 mil.

Estos años han servido para conocer nuevas personas con las que he intercambiado, algunas ya no están pero se les extraña y los tenemos presentes, el Robert, mi tocayo Yunier, Manuel y sus complementos, Gustavo, Jesús, Lachy y sus temas, entre otros muchos más.

También reconocer a los activos, quienes seguimos hacia adelante, inventando cosas nuevas y geniales para la comunidad. Agradecer a Erick -el impulsor, el Pochy, la bella Ody, Nilmar, Abraham, Eliecer, Artillero por mantenerse activos y espero que por muchos años más.

A la verdad, no me veo sin Firefoxmanía, estos 5 años en ella me han hecho sentir como en familia y gracias a ella he aprendido muchas cosas que me han ayudado a superarme como un ingeniero que seré.

Hoy también se celebra el Día de la Privacidad y Mozilla lanzó una campaña que busca concienciar a las personas acerca de la importancia de la privacidad de los datos en Internet. En este sitio podrás conocer herramientas y recibir consejos de cómo tomar el control de tu privacidad en la red. Comparte con tus amigos la página y todos podrán cuidar mejor sus datos.

Algunas fotos de estos 6 años.

hpim2579 hpim2606 img_7174  Erick, Yunier J, Antonio, Yunier, Roberto y Pedro Yaisel DSCN0138_2 todos Los ganadores del concurso junto a nosotros 20130427_130510 mhworkweek Todos juntos listos para picar los cake al lado del poster Todos juntos listos para picar los cake IMG_20141110_152332

Categorieën: Mozilla-nl planet

How to Customise Mozilla Firefox for Maximum Privacy in 7 Simple Steps - Lifehacker UK

Nieuws verzameld via Google - wo, 28/01/2015 - 18:33

Lifehacker UK

How to Customise Mozilla Firefox for Maximum Privacy in 7 Simple Steps
Lifehacker UK
Do you trust that your right to privacy is respected online? According to research conducted by Harris Poll, commissioned by Mozilla, almost half of the people who are online in the UK (42 percent) do not. With the majority of us relying on the power ...
7 Ways To Increase Your Privacy By Customising FirefoxTechWeekEurope UK

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

Ben Hearsum: Signing Software at Scale

Mozilla planet - wo, 28/01/2015 - 17:45

Mozilla produces a lot of builds. We build Firefox for somewhere between 5 to 10 platforms (depending how you count). We release Nightly and Aurora every single day, Beta twice a week, and Release and ESR every 6 weeks (at least). Each release contains an en-US build and nearly a hundred localized repacks. In the past the only builds we signed were Betas (which were once a week at the time), Releases, and ESRs. We had a pretty well established manual for it, but due to being manual it was still error prone and impractical to use for Nightly and Aurora. Signing of Nightly and Aurora became an important issue when background updates were implemented because one of the new security requirements with background updates was signed installers and MARs.

Enter: Signing Server

At this point it was clear that the only practical way to sign all the builds that we need to is to automate it. It sounded crazy to me at first. How can you automate something that depends on secret keys, passphrases, and very unfriendly tools? Well, there's some tricks you need to know, and throughout the development and improvement of our "signing server", we've learned a lot. In the post I'll talk about those tricks and show you how can use them (or even our entire signing server!) to make your signing process faster and easier.

Credit where credit is due: Chris AtLee wrote the core of the signing server and support for some of the signature types. Over time Erick Dransch, Justin Wood, Dustin Mitchell, and I have made some improvements and added support for additional types of signatures.

Tip #1: Collect passphrases at startup

This should be obvious to most, but it's very important not to store the passphrases to your private keys unencrypted. However, because they're needed to unlock the private keys when doing any signing the server needs to have access to them somehow. We've dealt with this by asking for them when launching a signing server instance:

$ bin/python tools/release/signing/signing-server.py signing.ini gpg passphrase: signcode passphrase: mar passphrase:

Because instances are started manually by someone in the small set of people with access to passphrases we're able to ensure that keys are never left unencrypted at rest.

Tip #2: Don't let just any machine request signed files

One of the first problems you run into when you have an API for signing files is how to make sure you don't accidentally sign malicious files. We've dealt with this in a few ways:

  • You need a special token in order to request any type of signing. These tokens are time limited and only a small subset of segregated machines may request them (on behalf of the build machines). Since build jobs can only be created if you're able to push to hg.mozilla.org, random people are unable to submit anything for signing.
  • Only our build machines are allowed to make signing requests. Even if you managed to get hold of a valid signing token, you wouldn't be able to do anything with it without also having access to a build machine. This is a layer of security that helps us protect against a situation where an evil doer may gain access to a loaner machine or other less restricted part of our infrastructure.

We have other layers of security built in too (HTTPS, firewalls, access control, etc.), but these are the key ones built into the signing server itself.

Tip #3: Use input redirection and other tricks to work around unfriendly command line tools

One of the trickiest parts about automating signing is getting all the necessary command line tools to accept input that's not coming from a console. Some of them are relative easy and accept passphrases via stdin:

proc = Popen(command, stdout=stdout, stderr=STDOUT, stdin=PIPE) proc.stdin.write(passphrase) proc.stdin.close()

Others, like OpenSSL, are fussier and require the use of pexpect:

proc = pexpect.spawn("openssl", args) proc.logfile_read = stdout proc.expect('Enter pass phrase') proc.sendline(passphrase)

And it's no surprise at all that OS X is the fussiest of them all. In order to sign you have to unlock the keychain by hand, run the signing command, and relock the keychain yourself:

child = pexpect.spawn("security unlock-keychain" + keychain) child.expect('password to unlock .*') child.sendline(passphrase) check_call(sign_command + [f], cwd=dir_, stdout=stdout, stderr=STDOUT) check_call(["security", "lock-keychain", keychain])

Although the code is simple in the end, a lot of trial, error, and frustration was necessary to arrive at it.

Tip #4: Sign everything you can on Linux (including Windows binaries!)

As fussy as automating tools like openssl can be on Linux, it pales in comparison to trying to automate anything on Windows. In the days before the signing server we had a scripted signing method that ran on Windows. Instead of providing the passphrase directly to the signing tool, it had to typed into a modal window. It was "automated" with an AutoIt script that typed in the password whenever the window popped up. This was hacky, and sometimes lead to issues if someone moved the mouse or pressed a key at the wrong time and changed window focus.

Thankfully there's tools available for Linux that are capable of signing Windows binaries. We started off by using Mono's signcode - a more or less drop in replacement for Microsoft's:

$ signcode -spc MozAuthenticode.spc -v MozAuthenticode.pvk -t http://timestamp.verisign.com/scripts/timestamp.dll -i http://www.mozilla.com -a sha1 -tr 5 -tw 60 /tmp/test.exe Mono SignCode - version 2.4.3.1 Sign assemblies and PE files using Authenticode(tm). Copyright 2002, 2003 Motus Technologies. Copyright 2004-2008 Novell. BSD licensed. Enter password for MozAuthenticode.pvk: Success

This works great for 32-bit binaries - we've been shipping binaries signed with it for years. For some reason that we haven't figured out though, it doesn't sign 64-bit binaries properly. For those we're using "osslsigncode", which is an OpenSSL based tool to do Authenticode signing:

$ osslsigncode -certs MozAuthenticode.spc -key MozAuthenticode.pvk -i http://www.mozilla.com -h sha1 -in /tmp/test64.exe -out /tmp/test64-signed.exe Enter PEM pass phrase: Succeeded $ osslsigncode verify /tmp/test64-signed.exe Signature verification: ok Number of signers: 1 Signer #0: Subject: /C=US/ST=CA/L=Mountain View/O=Mozilla Corporation/CN=Mozilla Corporation Issuer : /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Code Signing CA-1 Number of certificates: 3 Cert #0: Subject: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Root CA Issuer : /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Root CA Cert #1: Subject: /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Code Signing CA-1 Issuer : /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Root CA Cert #2: Subject: /C=US/ST=CA/L=Mountain View/O=Mozilla Corporation/CN=Mozilla Corporation Issuer : /C=US/O=DigiCert Inc/OU=www.digicert.com/CN=DigiCert Assured ID Code Signing CA-1

In addition to Authenticode signing we also do GPG, APK, and couple of Mozilla-specific types of signing (MAR, EME Voucher) on Linux. We also sign our Mac builds with the signing server. Unfortunately, the tools needed for that are only available on OS X, so we have to run separate signing servers for these.

Tip #5: Run multiple signing servers Nobody likes a single point of failure, so we've built support our signing client to retry against multiple instances. Even if we lose part of our signing server pool, our infrastructure stays up: $ python signtool.py --cachedir cache -t token -n nonce -c host.cert -H dmgv2:mac-v2-signing1.srv.releng.scl3.mozilla.com:9120 -H dmgv2:mac-v2-signing2.srv.releng.scl3.mozilla.com:9120 -H dmgv2:mac-v2-signing3.srv.releng.scl3.mozilla.com:9120 -H dmgv2:mac-v2-signing4.srv.releng.scl3.mozilla.com:9120 --formats dmgv2 Firefox.app 2015-01-23 06:17:59,112 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: processing Firefox.app.tar.gz on https://mac-v2-signing3.srv.releng.scl3.mozilla.com:9120 2015-01-23 06:17:59,118 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: connection error; trying again soon 2015-01-23 06:18:00,119 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: processing Firefox.app.tar.gz on https://mac-v2-signing4.srv.releng.scl3.mozilla.com:9120 2015-01-23 06:18:00,141 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: uploading for signing 2015-01-23 06:18:10,748 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: processing Firefox.app.tar.gz on https://mac-v2-signing4.srv.releng.scl3.mozilla.com:9120 2015-01-23 06:19:11,848 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: processing Firefox.app.tar.gz on https://mac-v2-signing4.srv.releng.scl3.mozilla.com:9120 2015-01-23 06:19:40,480 - ed40176524e7c197f4e23f6065a64dc3c9a62e71: OK Running your own signing server

It's easy! All of the code you need to run your own signing server is in our tools repository. You'll need to set-up a virtualenv and create your own config file, but once you're ready you can attempt to start it with the following command:

python signing-server.py signing.ini

You'll be prompted for the passphrases to your private keys. If there's any problems with your config file or the passphrases the server will fail to start. Once you've got it up and running you can use try signing! get_token.py has an example of how to generate a signing token, and signtool.py will take your unsigned files and give you back signed versions. Happy signing!

Categorieën: Mozilla-nl planet

Mozilla looking to add a virtual reality feature to its Firefox browser - ChristianToday

Nieuws verzameld via Google - wo, 28/01/2015 - 16:47

ChristianToday

Mozilla looking to add a virtual reality feature to its Firefox browser
ChristianToday
In order to exceed the popularity of Google's Chrome browser, Mozilla has had to come up with some drastic changes. Those changes are focused primarily on augmenting the overall experience on the company's Firefox browser. Last summer, the company ...

Categorieën: Mozilla-nl planet

Robert Longson: New SVG/CSS Filter support in Firefox

Mozilla planet - wo, 28/01/2015 - 16:36

There’s a new specification for filters that replaces the filters module in SVG 1.1. Firefox and Chrome are both implementing new features from this specification.

Firefox 30 was the first version to support feDropShadow As well as being simpler to write, feDropShadow will be faster than the equivalent individual filters as it skips some unnecessary colour conversions that we’d otherwise perform.

Firefox 35 has support for all CSS Filters so for simple cases you no longer need any SVG markup to create a filter. We’ve examples on MDN showing how to use CSS filters.

We’ve also implemented filter chaining, this is we support multiple filter either via URLs or CSS filters on a single element.

As with earlier versions of Firefox you can apply SVG and CSS filters to both SVG and HTML elements.

As part of the rewrite to support SVG filters we’ve improved their performance by using D2D on Windows to render them thus taking advantage of any hardware acceleration possibilities on that platform and on other platforms using SIMD and SSE2 to accelerate rendering so you can now use more filters without slowing your site down.


Categorieën: Mozilla-nl planet

Pete Moore: Weekly review 2015-01-28

Mozilla planet - wo, 28/01/2015 - 16:30

Task Cluster Go Client

This week I have got the task cluster go client talking to the TaskCluster API service end points.

See: https://github.com/petemoore/taskcluster-client-go/blob/master/README.md

I also now have part of the client library auto-generating, e.g. see: https://github.com/petemoore/taskcluster-client-go/blob/master/client/generated-code.go

Shouldn’t be too far from auto-generating the entire client library soon and having it working, tested, documented and published.

Categorieën: Mozilla-nl planet

Mozilla Privacy Blog: How Mozilla Addresses the Privacy Paradox

Mozilla planet - wo, 28/01/2015 - 14:39
Earlier this month, a 20 year old NBA Clippers fan held up a sign in a crowded Washington DC arena with her phone number on it. Seasoned privacy professionals have long lamented the old adage that if you give someone … Continue reading
Categorieën: Mozilla-nl planet

Ryan Kelly: Are we Python yet?

Mozilla planet - wo, 28/01/2015 - 14:01
Categorieën: Mozilla-nl planet

Mozilla celebra il Data Privacy Day con un vademecum per la privacy online - Data manager online

Nieuws verzameld via Google - wo, 28/01/2015 - 10:46

Data manager online

Mozilla celebra il Data Privacy Day con un vademecum per la privacy online
Data manager online
Mozilla ha progettato Firefox in modo da proteggere e rispettare le informazioni private. Ecco perché è orgogliosa di essere riconosciuta dal Ponemon Institute come Most Trusted Internet Company for Privacy. I dati personali appartengono esclusivamente ...
Data Privacy Day 2015 | Mozilla | PrivacyDownload blog.it (Blog)
Una giornata di privacyApogeo Online

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

Andy McKay: Iron Workers Memorial Bridge

Mozilla planet - wo, 28/01/2015 - 09:00

I pretty much hate the Iron Workers Memorial Bridge (or Second Narrows). I have to cross it each time I cycle into work and its miserable.

Its asymmetric, the climb up from North to South is demoralising. The ride is often windy. Often wet. Usually cold. Everything that nature can throw at you, you'll encounter on the bridge.

And currently its only got one sidewalk, which means everyone has to stop and let each other pass. The east side walk is currently being renovated and will hopefully be slightly wider. This means its harder to get over and has a brutally dangerous off ramp on the north side. I'm surprised no-one has been killed on that yet.

Once the east side walk renovation gets completed, they'll start on the west side. The other part of the renovation is adding in a suicide fence. That will obstruct the view. But just occasionally the bridge gives you a stunning view... and just occasionally there's a break in the bike traffic and I get a photo like this:

Looking west to downtown and Lions Gate from the Second Narrows

I just realised that I might miss that view.

Categorieën: Mozilla-nl planet

Get Smart On International Data Privacy Day

Mozilla Blog - wo, 28/01/2015 - 07:23

Today is International Data Privacy Day. It is a day designed to raise awareness and promote best practices for privacy and data protection. It is a day that looks to the future and recognizes that we can and should do better as an industry. It reminds us that we need to focus on the importance of having the trust of our users. At Mozilla, we start from the baseline that privacy and security on the Web are fundamental and not optional. We are transparent with our users about our data practices and provide them options for choice and control. We seek to build trust so we can collectively create the Web our users want – the Web we all want. Still, we are working to do better.

The term “privacy” means different things to each of us. At Mozilla, we don’t pretend to know what it means to everyone or that we can determine the right course of action for each user. Rather, our goal is to provide options to our users so they can choose what is right for them. Our privacy principles help guide features specifically targeted at user privacy and security — such as Do Not Track and accountless communications through Hello. And, we have other initiatives that are aimed at changing the way industry interacts with users. For example, our Tiles initiative helps prove that advertising and other customized content can be displayed in a manner that respects users. Each of these features has been engineered with privacy in mind.

We are also experimenting with new privacy and security features. In November, we announced an experimental tool — a tracking protection feature — that allows a user to opt-out of cross-site tracking of their Web activities. This month, we’ve conducted user testing to iterate and improve the feature and will further simplify and optimize its operation. We also announced that we would support Tor’s efforts to provide users with a private and secure browsing experience. We’ve now launched Tor relays that allow Tor to expand its network and serve more users. Tor can now spend more time on innovation and less time on scalability. We’re learning through this experimentation and will continue to iterate until we can do better.

We continue to advocate for transparency in our industry with respect to the collection and use of user data, and are committed to proving — through our own actions — that there is a better way. We are excited to begin 2015 by being recognized for the second time as the Most Trusted Internet Company for Privacy by the Ponemon Institute. We want you to help us to create the Web you want. If you have ideas about other steps we can take, please get involved. In the mean time, let’s celebrate International Data Privacy Day! Here are a few quick tips to get smart on privacy. And please join our Twitter Chat on January 28 at 11am PST hosted by @Firefox with guests (including from DuckDuckGo, McAfee, iKeepSafe, Privacy International and the Center for Democracy and Technology, among others).

Categorieën: Mozilla-nl planet

William Lachance: mozregression updates

Mozilla planet - wo, 28/01/2015 - 00:52

Lots of movement in mozregression (a tool for automatically determining when a regression was introduced in Firefox by bisecting builds on ftp.mozilla.org) in the last few months. Here’s some highlights:

  • Support for win64 nightly and inbound builds (Kapil Singh, Vaibhav Agarwal)
  • Support for using an http cache to reduce time spent downloading builds (Sam Garrett)
  • Way better logging and printing of remaining time to finish bisection (Julien Pagès)
  • Much improved performance when bisecting inbound (Julien)
  • Support for automatic determination on whether a build is good/bad via a custom script (Julien)
  • Tons of bug fixes and other robustness improvements (me, Sam, Julien, others…)

Also thanks to Julien, we have a spiffy new website which documents many of these features. If it’s been a while, be sure to update your copy of mozregression to the latest version and check out the site for documentation on how to use the new features described above!

Thanks to everyone involved (especially Julien) for all the hard work. Hopefully the payoff will be a tool that’s just that much more useful to Firefox contributors everywhere. :)

Categorieën: Mozilla-nl planet

VENEZUELA: Mozilla busca llevar la realidad virtual a Firefox - EntornoInteligente

Nieuws verzameld via Google - wo, 28/01/2015 - 00:49

EntornoInteligente

VENEZUELA: Mozilla busca llevar la realidad virtual a Firefox
EntornoInteligente
Mientras Facebook ya adquirió Oculus VR y Microsoft se prepara para HoloLens, Mozilla (de Firefox) se suma al mundo de la realidad virtual, por lo que incorpora ahora a sus ediciones en desarrollo continuo (Nightly) y para desarrolladores (Developer ...

en meer »Google Nieuws
Categorieën: Mozilla-nl planet

Justin Wood: Release Engineering does a lot…

Mozilla planet - wo, 28/01/2015 - 00:11

Hey Everyone,

I spent a few minutes a week over the last month or two working on compiling a list of Release Engineering work areas. Included in that list is identifying which repositories we “own” and work in, as well as where these repositories are mirrored. (We have copies in hg.m.o git.m.o and github, some exclusively in their home).

While we transition to a more uniform and modern design style and philosphy.

My major takeaway here is we have A LOT of things that we do. (this list is explicitly excluding repositories that are obsolete and unused)

So without further ado, I present our page ReleaseEngineering/Repositories

repositoriesYou’ll notice a few things about this, we have a column for Mirrors, and RoR (Repository of Record), “Committable Location” was requested by Hal and is explicitly for cases where “Where we consider our important location the RoR, it may not necessarily be where we allow commits to”

The other interesting thing is we have automatic population of travis and coveralls urls/status icons. This is for free using some magic wiki templates I did.

The other piece of note here, is the table is generated by a list of pages, using “SemanticMediaWiki” so the links to the repositories can be populated with things like “where are the docs” “what applications use this repo”, “who are suitable reviewers” etc. (all those are TODO on the releng side so far).

I’m hoping to be putting together a blog post at some point about how I chose to do much of this with mediawiki, however in the meantime should any team at Mozilla find this enticing and wish to have one for themselves, much of the work I did here can be easily replicated for your team, even if you don’t need/like the multiple repo location magic of our table. I can help get you setup to add your own repos to the mix.

Remember the only fields that are necessary is a repo name, the repo location, and owner(s). The last field can even be automatically filled in by a form on your page (see the end of Release Engineerings page for an example of that form)

Reach out to me on IRC or E-mail (information is on my mozillians profile) if you desire this for your team and we can talk. If you don’t have a need for your team, you can stare at all the stuff Releng is doing and remember to thank one of us next time you see us. (or inquire about what we do, point contributors our way, we’re a friendly group, I promise.)

Categorieën: Mozilla-nl planet

Hannah Kane: A new online home for those who #teachtheweb

Mozilla planet - ti, 27/01/2015 - 23:22

We’ve recently begun work on a new website that will serve the mentors in our Webmaker community—a gathering place for anyone who is teaching the Web. They’ll find activity kits, trainings, badges, the Web Literacy Map, and more. It will also be an online clubhouse for Webmaker Clubs, and will showcase the work of Hives to the broader network.

Our vision for the site is that it will provide pathways for sustained involvement in teaching the Web. Imagine a scenario where, after hosting a Maker Party, a college student in Pune wants to build on the momentum, but doesn’t know how. Or imagine a librarian in Seattle who is looking for activities for her weekly teen drop-in hours. Or a teacher in Buenos Aires who is looking to level up his own digital literacy skills. In each of these scenarios, we hope the person will look to this new site to find what they need.

We’re in the very early stages of building out the site. One of our first challenges is to figure out the best way to organize all of the content.

Fortunately, we were able to find 14 members of the community who were willing to participate in a “virtual card-sorting” activity. We gave each of the volunteers a list of 22 content areas (e.g. “Find a Teaching Kit,” “Join a Webmaker Club,” “Participate in a community discussion”), and asked them to organize the items into groups that made sense to them.

The results were fascinating. Some grouped the content by specific programs, concepts, or offerings. Others grouped by function (e.g “Participate,” “Learn,” “Lead”). Others organized by identity (e.g. “Learner” or “Mentor”). Still others grouped by level of expertise needed.

We owe a debt of gratitude to those who participated in the research. We were able to better understand the variety of mental models, and we’re currently using those insights to build out some wireframes to test in the next heartbeat.

Once we firm up the information architecture, we’ll build and launch v1 of the site (our goal is to launch it by the end of Q1). From there, we’ll continue to iterate, adding more functionality and resources to meet the needs of our mentor community.

Future iterations will likely include:

  • Improving the way we share and discover curriculum modules
  • Enhancing our online training platform
  • Providing tools for groups to self-organize
  • Making improvements to our badging platform
  • Incorporating the next version of the Web Literacy Map

Stay tuned for more updates and opportunities to provide feedback throughout the process. We’ve also started a Discourse thread for continuing discussion of the platform.


Categorieën: Mozilla-nl planet

Mozilla releases emergency update of Firefox due crashes - myce.com

Nieuws verzameld via Google - ti, 27/01/2015 - 22:59

WCCFtech

Mozilla releases emergency update of Firefox due crashes
myce.com
Mozilla has released an unplanned emergency update with version number 35.0.1 due to all kinds of crashes and other issues. The update comes two weeks after the release of Firefox 35. The update fixes issues where the browser could crash when using ...
Experience Virtual Reality on Your Browser With Firefox Nightly BuildsWCCFtech

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

Mozilla releases Firefox emergency update due crashes - myce.com

Nieuws verzameld via Google - ti, 27/01/2015 - 22:59

Mozilla releases Firefox emergency update due crashes
myce.com
Mozilla has released an unplanned emergency update with version number 35.0.1 due to all kinds of crashes and other issues. The update comes two weeks after the release of Firefox 35. The update fixes issues where the browser could crash when using ...

en meer »Google Nieuws
Categorieën: Mozilla-nl planet

Pages