Webmaker Demos January 23 2015
I managed to complete roughly five of my eleven goals for the week.
- Made progress on (but have not cracked) daily task management for the newly evolving systems
- Caught up on some email from time off, but still a chunk left to work through
- Spent more time writing code than expected
- Illness this week slowed me down
- These aren’t very good weeknotes, but perhaps better than none.
Nach Ende der Kooperation mit Mozilla: Google will Yahoo Nutzer abspenstig ... - Neue Zürcher Zeitung
Nach Ende der Kooperation mit Mozilla: Google will Yahoo Nutzer abspenstig ...
Neue Zürcher Zeitung
Und warum wirbt Google so offensiv um Nutzer? Im November wurde verkündet, dass Google und Mozilla nach zehn Jahren getrennte Wege gehen. Die Suchmaschine ist nicht mehr standardmässig in Firefox eingestellt. In den USA ist es Yahoo – mobil und ...
Nach Wechsel zu Yahoo: Google will Firefox-Nutzer zurückgewinnenGolem.de
Verlorene Marktanteile: Google will Firefox-Nutzer zurück gewinnenGoogleWatchBlog (Blog)
alle 4 nieuwsartikelen »
Google sofre com acordo entre Yahoo e Mozilla e sugere 'troca de buscador'
Usuários do Mozilla Firefox estão recebendo alertas do Google para trocarem seu mecanismo de buscas padrão no browser. As mensagens são exibidas ao acessar o site da gigante de buscas e são uma reação à adoção do Yahoo como sistema de busca ...
Google quer que usuários do Firefox voltem a usar motor de busca da empresaCanaltech
alle 5 nieuwsartikelen »Google Nieuws
The concept was for us to break apart the famed Shepard Fairey Mozilla dinosaur into quilt-like
Each member of the design team was assigned a tile or two and given a shape. This is the one I was assigned:
I turned that file into this:
We all met together in a video chat to upload our images on to the site.
Anticipation was building as we uploaded each shot one by one: But the final reveal made it worth all the effort!
Check out our new team page on dribbble. rawr!
Cassie also wrote about the exercise on her blog and discussed the opinion position for a designer to join the team.
Last Thursday we had our weekly call about the Reps program, where we talk about what’s going on in the program and what Reps have been doing during the last week.
- Dashboard QA and UI.
- Community Education.
- Feedback on reporting.
- Participation plan and Grow meeting.
- Womoz Badges.
Don’t forget to comment about this call on Discourse and we hope to see you next week!
Versión en español: “Debemos volver a pelear por la web“
It’s interesting to see how the history repeats itself and we repeat the same mistakes over and over again.
I started contributing to Mozilla in 2004, at that time Internet Explorer had the 95% of the market share. That meant that there was absolutely no way you could create a web not “adapted” to this browser and there were no way you could surf the full web with other browsers becuase a lot of sites used ActiveX and other IE-only non-standard technologies.
The web was Internet Explorer, Internet Explorer was the web, you had no choice.
We fought hard (really hard) from Mozilla and other organizations to bring user choice and open other ways to understand the web. People understood this and the web changed to an open diverse ecosystem where standards were the way to go and where everyone was able to be part of it, both users and developers.
Today everything we fought for is at risk.
— Nukeador (@nukeador) January 21, 2015
It’s not the first time we see how some sites decide to offer their content just for one browser, sometimes using technologies that are not a standard and only work there but sometimes using technologies that are standards and blocking other browsers for no reason.
Business is business.
If we don’t want a web controlled again by a few, driven by stockholders interests and not by users, we have to stand up. We have to call out sites that try to hijack user choice asking them to use one browser to access their content.
The web should run everywhere and users should be free to choose the browser they think best serve their interests/values.
I truly believe that Mozilla, as a non-profit organization, is still the only one that can provide an independent choice to users and balance the market to avoid the walled gardens some dream to build.
Don’t lower the guard, let’s not repeat the same mistakes again, let’s fight again for the web.
PD: If you want a deep analysis about the Whatsapp web fiasco, I recommend the post by my friend André: “Whatsapp doesn’t understand the web”.
The Wine project lets you run Windows programs on other operating systems, such as Linux. I spent some time recently trying to see what it would take to run Visual C++ 2013 Update 4 under Linux using Wine.
The first thing that I tried to do was to run the installer, but that unfortunately hits a bug and doesn’t work. After spending some time looking into other solutions, I came up with a relatively decent solution which seems to work very well. I put the instructions up on github if you’re interested, but the gist is that I used a Chromium depot_tools script to extract the necessary files for the toolchain and the Windows SDK, which you can copy to a Linux machine and with some DLL loading hackery you will get a working toolchain. (Note that I didn’t try to run the IDE, and I strongly suspect that will not work out of the box.)
This should be the entire toolchain that is necessary to build Firefox for Windows under Linux. I already have some local hacks which help us get past the configure script, hopefully this will enable us to experiment with using Linux to be able to build Firefox for Windows more efficiently. But there is of course a lot of work yet to be done.
Pinning for Mozharness  has been enabled for the fx-team integration tree.
Nothing should be changing. This is a no-op change.
We're still using the default mozharness repository and the "production" branch is what is being checked out. This has been enabled on Try and Ash for almost two months and all issues have been ironed out. You can know if a job is using pinning of Mozharness if you see "repostory_manifest.py" in its log.
If you notice anything odd please let me know in bug 1110286.
If by Monday we don't see anything odd happening, I would like to enable it for mozilla-central for few days before enabling it on all trunk trees.
Again, this is a no-op change, however, I want people to be aware of it.
This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
This week’s Web Literacy Map community call was fascinating. They’re usually pretty interesting, but today’s was particularly good. I’m always humbled by the brainpower that comes together and concentrates on something I spend a good chunk of my life thinking about!
I’ll post an overview of the entire call in on the Web Literacy blog tomorrow but I wanted to just quickly zoom out and focus on things that Marc Lesser and Jess Klein were discussing during the call. Others mentioned really useful stuff too, but I don’t want to turn this into an epic post!Marc
Marc reminded us of Clay Shirky’s post entitled Ontology is Overrated: Categories, Links, and Tags. It’s a great read but the point Marc wanted to extract is that pre-defined ontologies (i.e. ways of classifying things) are kind of outdated now we have the Internet:
In the Web 2.0 era (only 10 years ago!) this was called a folksonomic approach. I remembered that I actually used Shirky’s post in one of my own for DMLcentral a couple of years ago. To quote myself:
The important thing here is that we – Mozilla and the community – are creating a map of the territory. There may be others and we don’t pretend we’re not making judgements. We hope it’s “useful in the way of belief” (as William James would put it) but realise that there are other ways to understand and represent the skills and competencies required to read, write and participate on the Web.
Given that we were gently chastised at the LRA conference for having an outdated approach to representing literacies, we should probably think more about this.Jess
Meanwhile, Jess, was talking about the Web Literacy Map as an ‘API’ upon which other things could be built. I reminded her of the WebLitMapper, a prototype I suggested and Atul Varma built last year. The WebLitMapper allows users to tag resources they find around the web using competencies from the Web Literacy Map.
This, however, was only part of what Jess meant (if I understood her correctly). She was interested in multiple representations of the map, kind of like these examples she put together around learning pathways. This would allow for the kind of re-visualisations of the Web Literacy Map that came out of the MozFest Remotee Challenge:
Capturing the complexity of literacy skill acquisition and development is particularly difficult given the constraints of two dimensions. It doubly-difficult if the representation has to be static.
Finally from Jess (for the purposes of this post, at least) she reminded us of some work she’d done around matching mentors and learners:
The overwhelming feeling on the call was that we should retain the competency view of the Web Literacy Map for v1.5. It’s familiar, and helps with adoption:
However, this decision doesn’t prevent us from exploring other avenues combining learning pathways, badges, and alternative ways to representing the overall skill/competency ecosystem. Perhaps diy.org/skills can teach us a thing or two?
Google is running Summer of Code again in 2015.
Mozilla has had the pleasure of participating every year so far, and we
are hoping to participate again this year. In the next few weeks, we need
to prepare a list of suitable projects to support our application.
Can you think of a 3-month coding project you would love to guide a student through? This is your chance to get a student focusing on it for 3 months! Summer of Code is a great opportunity to introduce new people to your team and have them work on projects you care about but that aren't on the critical path to shipping your next release.
Here are the conditions for the projects:
- completing the project should take roughly 3 months of effort for a student;
- any part of the Mozilla project (Firefox, Firefox OS, Thunderbird, Instantbird, SeaMonkey, Bugzilla, L10n, NSS, IT, and many more) can submit ideas, as long as they require coding work;
- there is a clearly identified mentor who can guide the student through the project.
If you have an idea, please put it on the Brainstorming page, which is our idea development scratchpad. Please read the instructions at the top – following them vastly increases chances of your idea getting added to the formal Ideas page.
The deadline to submit project ideas and help us be selected by Google is February 20th.
Note for students: the student application period starts on March 16th, but the sooner you start discussing project ideas with potential mentors, the better.
Please feel free to discuss with me any question you may have related to Mozilla's participation in Summer of Code. Generic Summer of Code questions are likely already answered in the FAQ.
Last summer we held a short bootcamp crash course for Gecko. The talks have been posted to air.mozilla.com and collected under the TorontoBootcamp tag. The talks are about an hour each but will be very informative to some. They are aimed at people wanting a deeper understanding of Gecko.
View the talks here: https://air.mozilla.org/search/?q=tag%3A+TorontoBootcamp
In the talks you’ll find my first talk covering an overall discussion of the pipeline, what stages run when and how to skip stages for better performance. Kannan’s talk discusses Baseline, our first tier JIT. Boris’ talk discusses Restyle and Reflow. Benoit Jacob’s talk discusses the graphics stack (Rasterization + Compositing + IPC layer) but sadly the camera is off center for the first half. Jeff’s talk goes into depth into Rasterization, particularly path drawing. My second talk discusses performance analysis in Gecko using the gecko profiler where we look at real profiles of real performance problems.
I’m trying to locate two more videos about layout and graphics that were given at another session but would elaborate more the DisplayList/Layer Tree/Invalidation phase and another on Compositing.
This post is a shortened, web page version of the 2015 Mozilla Learning plan we shared back in December. Over the next few weeks, we’ll be blogging and encouraging team and community members to post their reflections and detail on specific pieces of work in 2015 and Q1. Please post your comments and questions here — or get more involved.
Within ten years, there will be five billion citizens of the web.
Mozilla wants all of these people to know what the web can do. What’s possible. We want them to have the agency, skills and know-how they need to unlock the full power of the web. We want them to use the web to make their lives better. We want them to know they are citizens of the web.
Mozilla Learning is a portfolio of products and programs that helps people learn how to read, write and participate in the digital world.
Building on Webmaker, Hive and our fellowship programs, Mozilla Learning is a portfolio of products and programs that help these citizens of the web learn the most important skills of our age: the ability to read, write and participate in the digital world. These programs also help people become mentors and leaders: people committed to teaching others and to shaping the future of the web.
Mark Surman presents the Mozilla Learning vision and plan in Portland, Dec 2015Three-year vision
By 2017, Mozilla will have established itself as the best place to learn the skills and know-how people need to use the web in their lives, careers and organizations. We will have:
- Educated and empowered users by creating tools and curriculum for learning how to read, write and participate on the web. Gone mainstream.
- Built leaders, everywhere by growing a global cadre of educators, researchers, coders, etc. who do this work with us. We’ve helped them lead and innovate.
- Established the community as the classroom by improving and explaining our experiential learning model: learn by doing and innovating with Mozilla.
At the end of these three years, we may have established something like a “Mozilla University” — a learning side of Mozilla that can sustain us for many decades. Or, we may simply have a number of successful learning programs. Either way, we’ll be having impact.
We may establish something like a “Mozilla University” — a learning side of Mozilla that can sustain us for many decades.2015 Focus
1) Learning Networks 2) Learning Products 3) Leadership Development
Our focus in 2015 will be to consolidate, improve and focus what we’ve been building for the last few years. In particular we will:
- Improve and grow our local Learning Networks (Hive, Maker Party, etc).
- Build up an engaged user base for our Webmaker Learning Products on mobile and desktop.
- Prototype a Leadership Development program, and test it with fellows and ReMo.
The short term goal is to make each of our products and programs succeed in their own right in 2015. However, we also plan to craft a bigger Mozilla Learning vision that these products and programs can feed into over time.A note on brand
Mozilla Learning is notional at this point. It’s a stake in the ground that says:
Mozilla is in the learning and empowerment business for the long haul.
In the short term, the plan is to use “Mozilla Learning” as an umbrella term for our community-driven learning and leadership development initiatives — especially those run by the Mozilla Foundation, like Webmaker and Hive. It may also grow over time to encompass other initiatives, like the Mozilla Developer Network and leadership development programs within the Mozilla Reps program. In the long term: we may want to a) build out a lasting Mozilla learning brand (“Mozilla University?”), or b) build making and learning into the Firefox brand (e.g., “Firefox for Making”). Developing a long-term Mozilla Learning plan is an explicit goal for 2015.What we’re building
Practically, the first iteration of Mozilla Learning will be a portfolio of products and programs we’ve been working on for a number of years: Webmaker, Hive, Maker Party, Fellowship programs, community labs. Pulled together, these things make up a three-layered strategy we can build more learning offerings around over time.
- The Learning Networks layer is the most developed piece of this picture, with Hives and Maker Party hosts already in 100s of cities around the world.
- The Learning Products layer involves many elements of the Webmaker.org work, but will be relaunched in 2015 to focus on a mass audience.
- The Leadership Development piece has strong foundations, but a formal training element still needs to be developed.
One of our goals with Mozilla Learning is to grow the scope and scale of Mozilla’s education and empowerment efforts. The working theory is that we will create an interconnected set of offerings that range from basic learning for large numbers of people, to deep learning for key leaders who will help shape the future of the web (and the future of Mozilla).
We want to increasing the scope and diversity of how people learn with Mozilla.
We’ll do that by building opportunities for people to get together to learn, hack and invent in cities on every corner of the planet. And also: creating communities that help people working in fields like science, news and government figure out how to tap into the technology and culture of the web in their own lives, organizations and careers. The plan is to elaborate and test out this theory in 2015 as a part of the Mozilla Learning strategy process. (Additional context on this here: http://mzl.la/depth_and_scale.)Contributing to Mozilla’s overall 2015 KPIs
How will we contribute to Mozilla’s top-line goals? In 2015, We’ll measure success through two key performance indicators: relationships and reach.
- Relationships: 250K active Webmaker users
- Reach: 500 cities with ongoing Learning Network activity
In 2015, we will continue to grow and improve the impact of our local Learning Networks.
- Build on the successful ground game we’ve established with teachers and mentors under the Webmaker, Hive and Maker Party banners.
- Evolve Maker Party into year-round activity through Webmaker Clubs.
- Establish deeper presence in new regions, including South Asia and East Africa.
- Improve the websites we use to support teachers, partners, clubs and networks.
- Sharpen and consolidate teaching tools and curriculum built in 2014. Package them on their own site, “teach.webmaker.org.”
- Roll out largescale, extensible community-building software to run Webmaker clubs.
- Empower more people to start Hive Learning Networks by improving documentation and support.
- Expand scale, rigour and usability of curriculum and materials to help people better mentor and teach.
- Expand and improve trainings online and in-person for mentors.
- Recruit more partners to increase reach and scope of networks.
Grow a base of engaged desktop and mobile users for Webmaker.
- Expand our platform to reach a broad market of learners directly.
- Mobile & Desktop: Evolve current tools into a unified Webmaker making and learning platform for desktop, Firefox OS and Android.
- Tablet: Build on our existing web property to address tablet browser users and ensure viability in classrooms.
- Firefox: Experiment with ways to integrate Webmaker directly into Firefox.
- Prioritize mobile. Few competitors here, and the key to emerging markets growth.
- Lower the bar. Build user on-boarding that gets people making / learning quickly.
- Engagement. Create sticky engagement. Build mentorship, online mentoring and social into the product.
Develop a leadership development program, building off our existing Fellows programs.
- Develop a strategy and plan. Document the opportunity, strategy and scope. Figure out how this leadership development layer could fit into a larger Mozilla Learning / Mozilla University vision.
- Build a shared definition of what it means to be a ‘fellow’ at Mozilla. Empowering emerging leaders to use Mozilla values and methods in their own work.
- Figure out the “community as labs” piece. How we innovate and create open tech along the way.
- Hire leadership. Create an executive-level role to lead the strategy process and build out the program.
- Test pilot programs. Develop a handbook / short course for new fellows.
- Test with fellows and ReMo. Consider expanding fellows programs for science, web literacy and computer science research.
- Learn more. There’s much more detail on the Learning Networks, Learning Products and Leadership Development pieces in the complete Mozilla Learning plan.
- Get involved. There’s plenty of easy ways to get involved now with Webmaker and our local Learning Networks today.
- Get more hands-on. Want to go deeper? Get hands-on with code, curriculum, planning and more through build.webmaker.org
Mozilla lanza MozVR para explorar la web en realidad virtual
El Universal / El navegador Mozilla lanzó MozVR, un nuevo sitio en realidad virtual con demos y recursos para desarrolladores, como parte de la celebración de su primera década de vida. Por ahora MozVR sólo puede ser utilizado principalmente por ...
en meer »Google Nieuws
The Grow Mozilla Community Building Forum
Mozilla Firefox: Nightly Builds ab sofort mit VR-Unterstützung
Aber auch softwareseitig passiert immer mehr: So bietet Mozilla mit seinem Firefox-Browser jetzt die Möglichkeit, Webinhalte auf VR-Brillen zu bringen. Bislang war dafür allerdings eine separate Version des Browsers nötig. Doch jetzt landet der dafür ...
Firefox bekommt Oculus-Rift-SupportPC-Welt
Virtual-Reality-Inhalte im Browser: Firefox-Alpha bringt Oculus-Support mitCHIP Online
WebVR: Oculus-Support im Firefox NightlyGolem.de
alle 5 nieuwsartikelen »
Mozilla Support for Oculus Rift a Step in Broader Plans for VR
Mozilla's recent enhanced support for the Oculus Rift headset is just one step in its plans to more fully embrace virtual reality. Mozilla has added virtual reality support to experimental builds of Firefox that lets people use the Oculus Rift headset ...
11 Biggest CEO Exits in 2014, Including Hertz, Mozilla, American Apparel
NEW YORK (TheStreet) -- Departures of CEO from U.S. companies and non-profit organizations reached a six-year high in 2014. Some 1,341 chief executives either vacated their posts or announced their upcoming departures, up 7.6% from 2013, according ...