Mozilla Nederland Logo De Nederlandse Mozilla gemeenschap

Kumar McMillan: Ramblings

Mozilla planet - wo, 09/04/2014 - 05:15

Oh, hey! I almost forgot I have a blog. Well, the colors are annoying to me and my comment system sucks but, meh. I wanted to write a quick note about where you can find stuff I write.

Categorieën: Mozilla-nl planet

Carla Casilli: Open Badges, wicked problems, and that thing called hope

Mozilla planet - wo, 09/04/2014 - 00:37
"feather bad weather" by Erik bij de Vaate

“feather bad weather” ©2008 Erik bij de Vaate, used under CC-BY-SA

Open badges: they are so tantalizing to so many people, so full of possibility. They appear to offer so many solutions to so many different problems. They encourage us to look at old problems with new eyes. And precisely because of their dynamism, their precious novelty, we occasionally find ourselves overwhelmed with the hope that they’ll solve all of the problems. Everything.

This, my friends, this is precisely what’s at issue with introducing badges to our current social structure: recognizing that there are problems with existing acknowledgement and recognition systems. Problems that have not been adequately addressed. We need to crack that nut wide open as we begin to figure out how badges might change the game. We need to figure out what works and what’s worth saving in this new badge world. We need to look hard at the wicked problems that they might at least influence.

The issues most often raised about badges—accessibility, injustice, value, meaning, and rigor—are not necessarily about badges themselves but instead are rooted in wicked problems, the larger systemic social, political, and economic issues that surround learning and recognition. When viewed from this perspective, it’s obvious that badges are not a panacea. So, let’s be realistic in our discussions about the ability of badges to solve all issues of access, fairness, and equity: nothing so far has solved those issues and badges alone won’t do it, either. This is a known known; let’s not waste time arguing this point. Instead, let’s wrestle mightily with the all-too-familiar feeling of impotence when discussing any possible inroad to wicked problems. Because discuss them we must.

On the plus side of this discussion, here’s a tiny sample of what badges can do. They can provide markers of social and professional possibilities, they can acknowledge varying degrees of expertise in social skills, they can indicate job skills compatibility, they can evidence a variety of important learning experiences including capturing prior learning, they can demonstrate continued professional engagement, they can represent vastly different company and brand values, and perhaps most importantly, they can provide important and meaningful personal insight.

So for now, while we’re building this ecosystem together, let’s hold tight to that thing with feathers—our sense of hope, our sense of possibility—for when seeking change, particularly systemic change, odd though it may feel and sound to outsiders, optimism is a feature not a bug.


If you’re reading this and nodding your head, you might also appreciate this related post from Badge Alliance Executive Director, Erin Knight: More Beefs

Much more soon. carla [at] badgealliance [dot] org


Tagged: badges, identity, learning, mozilla, Open badges, openbadges, politics, tools, wicked problems
Categorieën: Mozilla-nl planet

Sylvestre Ledru: Changes Firefox 29 beta5 to beta6

Mozilla planet - di, 08/04/2014 - 22:52

The number of changeset has decreased (23 for beta6 compared to 43 for beta5). This is a good sign as we approach from the release date of 29. In this release, some top crashes have been fixed and some last bugs for Australis has been address.

  • 23 changesets
  • 55 files changed
  • 435 insertions
  • 704 deletions

By extensions:

ExtensionOccurrences cpp12 js10 css8 h7 ini6 html4 mm2 xul1 xml1 json1 jsm1 inc1

By modules:

ModuleOccurrences browser19 js13 dom6 widget5 content5 toolkit2 gfx2 modules1 layout1

List of changesets:

Tim NguyenBug 989449 - fix menu-button dropmarker corners to have border-radii on Windows 7, Vista and XP. r=mikedeboer, a=sylvestre. - bc6c34299b03 Tim NguyenBug 980339 - Remove border-radius from add-on manager on Windows 8. r=mikedeboer, sr=Unfocused, a=sylvestre. - cb7f81834560 Mike de BoerBug 991072: fix zoom percentage label to be centered in any toolbar. r=mconley, a=sylvestre. - 3e69377c027a Gijs KruitboschBug 946595 - High contrast themes on Windows 8 shouldn't be considered the default theme in CSS, r=jimm, a=sylvestre. - 250d63775815 Boris ZbarskyBug 976920 - Mostly back out Bug 932322 for now; only define the unforgeable properties on the window object itself. r=jst, a=sledru - aecbb562466a Robert StrongBug 982448 - Some fxmetro pref's still being left behind with values without --enable-metro in the mozconfig. r=bbondy, a=sledru - 6f0ad6b259ca Jan de MooijBug 983709 - Simple branch patch for uplift. r=hv1989, a=sledru - 81285325c7db Jon CoppeardBug 986864. r=sfink, a=sledru - e6b88dfe88cd Phil RingnaldaBug 986760 (with a dash of 989101 added in) - disable browser_UITour3.js on Linux for excessive failures and lack of action taken toward fixing them. a=test-only - 6c1da25749a0 Matthew NoorenbergheBug 990384 - Define tabToolbarNavbarOverlap to reduce magic numbers in CSS for the overlap between the tabs and nav-bar. r=mconley a=sylvestre - a2fccb7d55f7 Matthew NoorenbergheBug 878436 - Update Lion Fullscreen window styling offsets to avoid themes shifting position. r=timdream a=sylvestre - 4d27870d3fdc Matthew NoorenbergheBug 990387 - Toolbar buttons on the TabsToolbar appear below the nav-bar border with a theme. r=dao a=sylvestre - 81075b35ee13 Matthew NoorenbergheBug 973855 - [Australis] Include browser-bottombox in the customization mode padding. r=jaws a=sylvestre - 75c7e2c98e0c Jan BeichBug 948946 - Use private-browsing indicator with GTK theme on non-Linux as well. r=MattN a=sylvestre - f7faeaf19dfa John DaggettBug 975460 - disable async font loader on OSX 10.6 (beta/aurora). r=smichaud,mkato a=sylvestre - 79c61c6f632d Joel MaherBug 987892 - Clear up oranges for deBug mochitest-browser-chrome jobs on Mozilla-Beta. r=armenzg a=test-only - 13bf6fe8df1f Benjamin BouvierBug 969203 - Take out non strictly commutative Float32 functions. r=sstangl, a=sledru - 7e9b33204db9 Bobby HolleyBug 980537 - Only store FakeBackstagePass instances in mThisObjects. r=khuey, a=sledru - 9933fa36efa5 Mike KaplyBacking out Bug 889085 (dddfd63f1414, f8c14bd80676) due to regression Bug 987783. r=roc, a=sledru - 51e5b0ec21b3 Garrett RobinsonBug 971341 - Fix infinite tab loading due to missing characters in CSP's path regexes. r=sstamm, a=lsblakk - fe5d67aa5366 Shane CaraveoBug 992398 - Fix domain for cdn deployment of directory site. r=gavin, a=sledru - ea5b3027bb42 Karl TomlinsonBug 990794 - Crash on ovrfl in SharedBuffer::Create(). r=roc, a=sledru - 51a84afe085d Karl TomlinsonBug 990794 - Crash on ovrfl in AllocateAudioBlock. r=roc, a=sledru - 004a7c15d761

r= means reviewed by
a= means uplift approved by

Previous changelogs:

Original post blogged on b2evolution.

Categorieën: Mozilla-nl planet

Joel Maher: polishing browser-chrome – coming to a branch near you soon

Mozilla planet - di, 08/04/2014 - 21:54

The last 2 weeks I have gone head first into a world of resolving some issues with our mochitest browser-chrome tests with RyanVM, Armen, and the help of Gavin and many developers who are fixing problems left and right.

There are 3 projects I have been focusing on:

1) Moving our Linux debug browser chrome tests off our old fedora slaves in a datacenter and running them on ec2 slave instances, in bug 987892.

These are live and green on all Firefox 29, 30, and 31 trees!  More work is needed for Firefox-28 and ESR-24 which should be wrapped up this week.  Next week we can stop running all linux unittests on fedora slaves.

2) Splitting all the developer tools tests out of the browser-chrome suite into their own suite in bug 984930.

browser-chrome tests have been a thorn in the side of the sheriff team for many months.  More and more the rapidly growing features and tests of developer tools have been causing the entire browser-chrome suite to fail, in cases of debug to run for hours.  Splitting this out gives us a small shield of isolation.  In fact, we have this running well on Cedar, we are pushing hard to have this rolled out to our production and development branches by the end of this week!

3) Splitting the remaining browser chrome tests into 3 chunks, in bug 819963.

Just like the developer tools, we have been running browser-chrome in 3 chunks on Cedar.  With just 7 tests disabled, we are very green and consistently green. 



While there are a lot of other changes going on under the hood, what will be seen by next week on your favorite branch of Firefox will be:

  • ‘dt’ jobs for opt, and ‘dt1′, ‘dt2′, ‘dt3′ jobs for debug
  • ‘bc’ job will turn into ‘bc1′, ‘bc2′, ‘bc3′
  • much faster turnaround times on bc tests (62 minutes is the slowest right now, the rest are averaging ~20 minutes/job)
  • less random orange cluttering up results


Categorieën: Mozilla-nl planet

The Gay Rights Battle Moves to the Boardroom - U.S. News & World Report

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

The Gay Rights Battle Moves to the Boardroom
U.S. News & World Report
Now the boardroom is becoming the next battleground as two major – but very different – private institutions, World Vision U.S. and Mozilla, have had to answer for internal decisions that had repercussions for the gay community. Trouble is brewing for ...

Google Nieuws
Categorieën: Mozilla-nl planet

Staś Małolepszy: Refactored l10n.js landed in Gaia

Mozilla planet - di, 08/04/2014 - 20:33

Today Zibi and I landed the refactored code of shared/js/l10n.js in Gaia master. A culmination of months of hard work, the refactor is also a first step of a larger initiative to innovate in the area of mobile localization and eventually, to implement L20n in Gaia.

Firefox OS faces a number of challenges related to localization. Growing the locale coverage beyond 20 supported locales; adapting to multiple screen sizes and form factors; ensuring the performance and memory consumption is good when the DOM is localized on the fly. In order to respond to these needs and many more that we will encounter in the future, we need a flexible and modular codebase, with a thought-out API designed to perform well in asynchronous scenarios.

We decided to re-write Gaia's l10n.js drawing from our experiences from developing L20n. The underlying concepts are similar: the code is organized into useful abstractions like the localization Context managing the fallback chain of Locale objects, or the Entity class which represents a single translation unit.

It's not L20n just yet. The library still uses the .properties file format.
There are no custom macros or arbitrary dicts which allow localizers greater flexibility in creating translations. The language fallback is limited to two locales. It still is a good first step towards empowering developers and localizers alike.

To minimize the risk of regressions, the refactored code was almost a drop-in replacement for the old l10n.js library. We decided to keep the exact same API of the navigator.mozL10n object. Everything should just work as it did before. We feel that there's room for improvement in the API design, and we'll soon start suggesting changes to it (e.g. bug 993188 has made many developers implement workarounds in their apps, which would break if we fixed it right away in our refactored drop-in patch).

Notable changes
  • Modular code which encapsulates main concepts of localization with a clean OOP approach.

  • Better security thanks to the lazy compilation step.

  • Better error reporting, especially on build time:

    /build_stage/browser/index.html: [l10n] [ar]: 3 missing in the visible DOM: enter-search-or-address, top-sites-startPage, browserBrandShortName /build_stage/browser/index.html: [l10n] [ar]: 10 missing compared to en-US: brandShortName, browserBrandShortName, browserBrandFullName, enter-search-or-address, top-sites-startPage, top-sites-tab, search-engines, default-search-engine, edit-bookmark, edit-bookmark-header
  • The internal API (currently hidden behind the navigator.mozL10n wrapper) is ready to fully support asynchronous parsing, compilation and fetching of translations, which we think will be important when implementing language packages for Firefox OS.

  • You can now freely nest placeables, meaning that this will work:

    foo = Foo foobar = {{ foo }} Bar foobarbaz = {{ foobar }} Baz
  • Good test coverage, both in our source repo and as part of the Gallery app test suite.

Feedback and bugs

The top priority fot this refactor was to be 100% compatible with the old l10n.js library. We made sure all tests pass on Travis and on TBPL and put a lot of effort into writing additional tests. We will be monitoring the tree for any regressions. If you notice something weird going on with your device or your app, for instance related to language switching, please let us know.
File bugs in the newly created Gaia::L10n component in Bugzilla or find us in #gaia and #l20n.

Next steps

The list of tasks on our to-do list is long, but we couldn't be more exited about them. Ranging from UX improvements to developer-friendly APIs, to giving localizes more control over their translations, next months are going to be great for localization and Firefox OS. A sneak peek, in no particular order:

  • Revisit the build time optimizations currently used in production Firefox OS builds, which we suspect cripple the performance of builds with more than 20 locales installed.

  • Implement responsive localization tools, such as the @formFactor macro which makes it possible to define different translations for tablets and phones.

  • Clean up the app startup API; implement mozL10n.ready() and mozL10n.once() as separate methods (bug 993188) and move away from listening to the 'localized' events.

  • Improve app launch performance by delaying localization when possible.

  • Research the use of Mutation Observers to automatically localize new DOM nodes when they are inserted into the existing DOM.

  • Research langpacks, possibly using the DataStores API.

  • Implement better language negotiation and language fallback via the ECMAScript Internationalization API and the navigator.languages API.

Categorieën: Mozilla-nl planet

Ron Piovesan: Quality content rules the Facebook news feed

Mozilla planet - di, 08/04/2014 - 20:09

With over 1 billion users worldwide coupled with deep local reach and engagement, Facebook is a key social platform for financial services professionals to reach out and connect with customers.

Everyday, millions of agents and advisers use their Facebook Business Page to share content, post updates on their business, and provide useful insights into what is happening in the market.

But it is a simple truth that as more people engage on Facebook Business Pages, the more crowded a user’s news feed will be. At best, a user can review dozens or maybe a hundred updates a day.

To reduce noise and keep a user’s news feed as relevant as possible, Facebook uses over 1000 filters to determine which posts should get highlighted.

In a recent TechCrunch article,  Facebook News Feed Director of Product Management Will Cathcart highlighted the main filters:

  • How popular (Liked, commented on, shared, clicked) are the post creator’s past posts with everyone
  • How popular is this post with everyone who has already seen it
  • How popular have the post creator’s past posts been with the viewer
  • Doe the type of post (status update, photo, video, link) match what types have been popular with the viewer in the past
  • How recently was the post published

As an agent or adviser, you’ve worked hard to build a loyal and active following on your Facebook Business Page. Make sure you keep those followers engaged and up-to-date by posting timely, relevant content.

Focusing on consistency and quality of content will help determine how prominently your post will appear in your follower’s news feed.

Categorieën: Mozilla-nl planet

David Rajchenbach Teller: Recent changes to OS.File

Mozilla planet - di, 08/04/2014 - 16:02

A quick post to summarize some of the recent improvements to OS.File.


To write a string, you can now pass the string directly to writeAtomic:

OS.File.writeAtomic(path, "Here is a string", { encoding: "utf-8"})

Similarly, you can now read strings from read:, { encoding: "utf-8" } ); // Resolves to a string.

Doing this is at least as fast as calling TextEncoder/TextDecoder yourself (see below).

Native implementation has been reimplemented in C++. The main consequence is that this function can now be used safely during startup, without having to wait for the underlying OS.File ChromeWorker to start. Also, decoding (see above) is performed off the main thread, which makes it much faster.

According to my benchmarks, using to read strings is about 2-5x faster than NetUtil.asyncFetch on large files and doesn’t block the main thread for more than 5ms, while asyncFetch performs string decoding on the main thread. Also, it doesn’t perform any main thread I/O by opposition to NetUtil.asyncFetch.


When using writeAtomic, it is now possible to request existing files to be backed up almost atomically. In many cases, this is a good strategy to ensure that data is safely written to disk, without having to use a flush, which would be expensive for the whole system.

yield OS.File.writeAtomic(path, data, { tmpPath: path + ".tmp", backupTo: path + ".backup} } ); Compression

writeAtomic and read both now support an implementation of lz4 compression

yield OS.File.writeAtomic(path, data, { compression: "lz4"}); yield, { compression: "lz4"});

Note that this format will not be understood by any command-line tool. It is somewhat proprietary. Also note that (de)compression is performed on the ChromeWorker thread for the time being, so it doesn’t benefit from the native reimplementation mentioned above.

Creating directories recursively let dir = OS.Path.join(OS.Constants.Path.profileDir, "a", "b", "c", "d"); yield OS.File.makeDir(dir, { from: OS.Constants.Path.profileDir });
Categorieën: Mozilla-nl planet

Laura Hilliger: Training with Friends

Mozilla planet - di, 08/04/2014 - 12:42

This weekend, I’ll be leading a Webmaker Training for the National Citizens Service (NCS). NCS is an organization in the UK that provides learning opportunities for young people living in England and Northern Ireland – young people who are encouraged to lead positive change within their communities. For the first time ever, NCS has invited graduates from their programs to become Digital Champions, a group of people who will lead social action projects and spread web literacy skills in their local communities. This is the Teaching Kit we’ll be using to guide us during the event. Let me tell you why I’m SO EXCITED to be doing this: This is the first official “Webmaker Training” I run trainings all the time, but they’re always one-offs, offshoots, and truncated versions of my dream learning scenario. In 2013 we ran two prototypes – a live training for Mozilla Reps called Training Days and an online training called Teach the Web, both were hugely successful. My dream learning scenario combines these two initiatives. I think a blended-learning program that is open, inclusive, and pedagogically sound – something that helps people teach the culture, mechanics, and citizenship of the Web – is what a Mozilla professional development program should be. Why? Because open. The NCS has been great to work with// I expect the young people who participate in the NCS Community are amazing as well. The partnership started when one of our Sr Directors, the fantastic Paula Le Dieu, opened a conversation with some folks at the NCS to explain that Mozilla isn’t just a technology company, and the Web is not just a delivery mechanism for content. She talked to them about what it truly means to be part of the Open Community and our values resonated. We were asked if we could teach some of the values and skills around openness and web literacy while overlapping with NCS values around social action, personal responsibility and leadership. Spoiler Alert: Yeah, we totally can and will! I’m truly excited to share what I love about the open source community with the NCS Digital Champions, while helping them level up their social and technical skills. I’m excited to hear their ideas, push them to think bigger, and introduce them to the support networks on the web. I’m excited to learn from them. As an educator, I view the goals of this partnership (and future partnerships centered on Training) as being less about specific skills and more about big brained theories of education that say things like “You are educated when you can confidently and empathetically participate in society and the world.” The Digital Champions will help us grow Last year, the Training Days graduates and the Teach the Web participants ran hundreds and hundreds of events, spreading Webmaker and digital skills. Our community's honesty, participation and drive has made Webmaker what it is today. The 42 NCS Digital Champions are committing to running their own Maker Parties later this year. They’re also committing to spreading web literacy within their local communities and among their peers in the NCS community. We’ll be inviting them to become mentors within our online training initiatives. In May, we’ll be inviting any and every one to participate in an online learning experience that will help you teach the web and become part of the open community. I’m hoping that this weekend seeds enough interest for the NCS Digital Champions to want to play around with the new and improved Training content and discussion platform*. It's going to be fun! People who know me, know that I don't really get invested in things that don't entertain me. One of the reasons I love teaching is because I think it’s fun. It's fun to watch people learn, see what people make, share ideas and talk about stuff. I even think it’s fun to watch myself fail at relating to people. It’s fun to learn about myself, other people, the world, technology…Our agenda has random, fun activities (ahem) that are designed to get people moving, thinking and growing. I’m enthusiastic about what I do, and enthusiasm is contagious. So, yeah, it’s going to be fun for everyone involved. All of this means more people will become web literate, more people will spread openness, more people will champion the values we have. *If YOU’RE interested in helping made the online components of Webmaker Training better, help us test them! Enhanced by Zemanta
Categorieën: Mozilla-nl planet

Mozilla's Statement on the Brendan Eich Controversy, Explained - National Review Online (blog)

Nieuws verzameld via Google - di, 08/04/2014 - 10:05


Mozilla's Statement on the Brendan Eich Controversy, Explained
National Review Online (blog)
Here is the statement that Mozilla's executive chairwoman, Mitchell Baker, posted last week about the “resignation” (firing?) of CEO Brendan Eich over his personal $1,000 donation in 2008 in support of California's Proposition 8. I've added my own text ...
Mozilla CEO resignation sets off debate: #tellusatodayUSA TODAY
Mozilla's CEO Showed the Cost of Disclosure Laws by Crossing the Satan ...Forbes
Exposed: Accusations of Hypocrisy in Company's Crusade to Oust Mozilla CEO
The Guardian -Fox News -Salt Lake Tribune
alle 263 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Yunier José Sosa Vázquez: Disponible el Add-on SDK 1.16

Mozilla planet - di, 08/04/2014 - 07:40

AddonsYa se encuentra con nosotros la versión 1.15 del Add-on SDK. Descargar Add-on SDK 1.16.

Según el blog de los Add-ons de Mozilla, esta liberación menor tiene como objetivo Este lanzamiento tiene como objetivo proveer compatibilidad con Firefox 29 y el uso de las nuevas APIs que provee Australis.

Con Australis el uso de botones se ampliará y se le podrán añadir paneles, frames, barras de herramientas. Algunas de estas características no están presentes en Firefox 29 pero si en la versión 30.

También se han solucionado varios como:
  • Bug 958609 – “Add-on SDK 1.15 es incompatible con Python 2.7.6″
  • Bug 944951 – “bootstrap.js debe remover la adición del recurso: URIs al cargar”

Para conocer otros detalles, pueden leer las notas de liberación.

Antes de descargar el Add-on SDK 1.16 recuerda que puedes contribuir a la mejora de este reportando bugs, mirando el código para que contribuyas dando tus soluciones o simplemente dejar tu impresión sobre esta nueva versión.

Categorieën: Mozilla-nl planet

Rizky Ariestiyansyah: OpenX Quiz is featured on Firefox Marketplace, Awesome!

Mozilla planet - di, 08/04/2014 - 06:33
A good day to get awesome news from Mozilla, like another day I am checking my email every morning. The awesome news is my OpenX Quiz app is featured on Firefox Marketplace, this application...
Categorieën: Mozilla-nl planet

Exposed: Accusations of Hypocrisy in Company's Crusade to Oust Mozilla CEO ... -

Nieuws verzameld via Google - di, 08/04/2014 - 05:14

Exposed: Accusations of Hypocrisy in Company's Crusade to Oust Mozilla CEO ...
The online dating site OkCupid led the charge to create a firestorm of controversy over Mozilla CEO Brendan Eich's $1,000 donation to the campaign for Proposition 8 in 2008. The site went as far as to change its homepage for Mozilla Firefox users to ...

Categorieën: Mozilla-nl planet

Benjamin Kerensa: North America Mozilla Reps Meetup

Mozilla planet - di, 08/04/2014 - 03:14
DSC 0213 300x200 North America Mozilla Reps Meetup

Our group photo

This weekend, North America Mozilla Reps gathered in the not-so-sunny Portland, Oregon. We worked from the Portland Office during the weekend, where we collaborated on plans for North America for the next six month period. We also tackled a number of topics from websites and refined our priority cities which will help us be more successful in moving forward in our mission to grow contributors in North America.

We were very fortunate to have some new people participate this time round including Lukas Blakk, Janet Swisher, Larissa Shapiro, Joanna Mazgaj, Robby Sayles, Prashish Rajbhandari, Tanner Filip, Dan Gherman and Christie Koehler. It was excellent to have a larger group because this brought ideas from people who see things through different lenses.

14 1 300x221 North America Mozilla Reps Meetup

Voodoo Donuts delivered Firefox Donuts 2.0

All in all, I feel we tackled a lot more work this time than our previous meetup last year in San Francisco and we decided to have our next meetup in Portland again. One of my favorite activities during the meetup was a diversity activity that Lukas led us in that many of us hope to do with our own communities.

We closed off the meetup with a trip to the Ground Kontrol Arcade and Bar where there were many games of Pac Man and Dance Dance Revolution.

 North America Mozilla Reps Meetup
Categorieën: Mozilla-nl planet

Mozilla CEO resignation sets off debate: #tellusatoday - USA TODAY

Nieuws verzameld via Google - di, 08/04/2014 - 01:27


Mozilla CEO resignation sets off debate: #tellusatoday
Last week, Brendan Eich resigned as CEO of Mozilla under pressure after his support of California's ban on gay marriage surfaced. In 2008, he made a $1,000 contribution supporting Proposition 8. Comments from Twitter and Facebook are edited for clarity ...
Mozilla's CEO Showed the Cost of Disclosure Laws by Crossing the Satan ...Forbes
Mozilla's Statement on the Brendan Eich Controversy, ExplainedNational Review Online (blog)
Brendan Eich has the right to fight gay rights, but not to be Mozilla's CEOThe Guardian
Fox News -Salt Lake Tribune -CBS News
alle 253 nieuwsartikelen »Google Nieuws
Categorieën: Mozilla-nl planet

Mozilla's CEO Showed the Cost of Disclosure Laws by Crossing the Satan ... - Forbes

Nieuws verzameld via Google - ma, 07/04/2014 - 23:57

Mozilla's CEO Showed the Cost of Disclosure Laws by Crossing the Satan ...
The policy lesson from the case of Mozilla's Brendan Eich, who was forced out as CEO of the tech giant he co-founded as a result of his support for Proposition 8—California's ballot initiative that defined marriage as the union of a man and a woman ...

Google Nieuws
Categorieën: Mozilla-nl planet

David Rajchenbach Teller: A curse and a blessing

Mozilla planet - ma, 07/04/2014 - 23:54
The curse

When Brendan Eich stepped in as a CEO, Mozilla and him were immediately faced a storm demanding his resignation because of his political opinions. To the best of my knowledge, none of those responsible for the storm were employees of the Mozilla Corporation and only 4 or 5 of them were members of the Mozilla Community (they were part of the Mozilla Foundation, which is a different organization).

When Brendan Eich resigned from his position as an employee of Mozilla, Mozilla was immediately faced by a storm assuming that Brendan Eich had been fired, either because of his opinions or as a surrender to the first storm.

Both storms are still raging, fueled by angry (and dismayed and saddened) crowds and incompetent news reporting.

We will miss Brendan. We have suffered and we will continue suffering from these storms. But we can also salvage from them.

The blessing

Think about it. We are being criticized by angry crowds. But the individuals who form these crowds are not our enemies. Many of them care deeply about Freedom of Speech and are shocked because they believe that we are extinguishing this freedom. Others care primarily about equality, an equality that can seldom be achieved wherever there is no Freedom of Speech.

Freedom of Speech. This is one of the core values of Mozilla, one of the values for which we have been fighting all these years.

We are being criticized by some of the people who need us most. They are our users, or our potential users, and they are getting in touch with us. Through Facebook, through Twitter, through the contribute form, through the governance mailing-list, through our blogs, or in real life discussions.

Some will say that we should ignore them. Some will be tempted to answer anger with anger and criticism with superiority.

Do neither. They are our users. They deserve to be heard.

We should listen to them. We should answer their concerns, not with FAQs or with press releases, but with individual answers, because these concerns are valid. We should explain what really happened. We should show them how Mozilla is largely about defending Freedom of Speech through the Open Web.

So please join the effort to answer the angry crowds. If you can, please reach out to media and the public and get the story out there. If only one person out of a hundred angry users receives the message and decides to join the community and the fight for the open web, we will have salvaged a victory out of the storm.

Categorieën: Mozilla-nl planet

Benoit Girard: Graphics Meetup 2014Q01

Mozilla planet - ma, 07/04/2014 - 20:06

I just arrived from the Graphics Meetup in early 2014. Before the week we wrapped up the port of tiling from Fennec OpenGL specific code to the abstract Compositor API. Here a summary of the projects we discussed (from my point of view, I’m missing things that I couldn’t attend):

GFX Taipei

  • Off main thread compositing on desktop (OMTCompositing): We discussed our plan for shipping OMTCompositing to desktop and unify our compositing code. Moving compositing off the main thread is a prerequisite for the many projects that build on it such as OMTAnimation, OMTVideo, tiling and Async Pan Zoom. Matt Woodrow managed to make some sizable progress at the end of the week. Our plan is to double down on our resources to get this shipped on desktop.
  • Tiling: Bringing tiling to desktop will be important to better support 4k displays and to support Async Pan Zoom. We decided to focus on OMTCompositing before shipping tiling on desktop.
  • Async Pan Zoom: We discussed upcoming improvements to Async Pan Zoom like hit testing, scroll snap requirements. We discussed our plan to have Async Pan Zoom on the desktop. Mstange has a working prototype of APZ on mac. For now we will first focus on shipping OMTCompositing separately. Changes to the input event queue and dealing with the plugins window on Windows will be a significant problem.
  • Graphics regression test on b2g: We discussed with mchang from the b2g performance team the best way to get b2g performance regressions tests. We decided to focus on some micro benchmarks to isolate platform regressions from gaia regressions by using the Gfx Test App. Kats convinced me that FrameMetrics could be use to accurately measure ‘checkerboarding’ so we will be rolling out some tests based on that as well.
  • VSync: Vincent has been leading the effort of getting Gecko to correctly VSync. This project is very important because no matter how fast we render our animations will never be fluid if we don’t follow vsync carefully. We had a long design review and I’m fairly happy with the result. TL;DR: We will be interpolating input events and driving the refresh driver off the vsync signal.
  • Eideticker: We discussed the challenges of supporting Eideticker using an external camera instead of MHL.
  • WebGL: We reaffirmed our plans to continue to support new WebGL extensions, focus on conformance issues, update the conformance testsuite and continue to work on WebGL 2.
  • Skia: We decided to try to rebase once every 6 weeks. We will be focusing on Skia content on android and SkiaGL canvas on mac.
  • RR with graphics: Roc presented RR (blog). It really blew me away that RR already supported Firefox on Linux. We had a discussion on some of the challenges with using RR with graphics (OpenGL, X) and how it could benefit us.
  • LayerScope: LayerScope will be extended to show frame tree dumps and which display items are associated with which layer.
  • Task Tracer: Shelly presented Task Tracer. We discussed how to integrate it with the profiler and Cleopatra.
  • Ownerships: We’re looking into different approaches to add ownership of sub-modules within graphics and how it can help with improving design and reviews.
  • Designs: We discussed on how to bring better design to the graphics module. We’re going to perform design reviews in bugzilla and keep the final design in a docs folder in the graphics components. This means that design changes will be peer reviewed and versioned.

Categorieën: Mozilla-nl planet

Gervase Markham: Mozilla Voices

Mozilla planet - ma, 07/04/2014 - 18:00

I invited people to email me; here’s what they have been saying.

I fear that Mozilla showed a weakness, when we replied to that initial complaint. We showed people we care about what they had to say about Brendan, and about politics. I think we shouldn’t. …

Although technically we are still good, I fear that our community is strained right now. We need to forget all politics, and focus on the mission. Only the mission. We shouldn’t care about other things. Hopefully we will pull through…

Recent events have made me very angry, and the more I think about it, the angrier I get. …

Brendan understood that for Mozilla to be successful in its mission, participants needed to check their prejudices at the door and work together to build this great thing. And he himself compartmentalized his prejudices away from his work life.

He awarded others this tolerance, but in the end was not awarded it himself by others.

While I am myself a strong supporter of equal marriage rights, I am shocked by what was done to Brendan. It was truly vindictive and intolerant, completely unbecoming of a movement that claims to fight for tolerance.

I am not sure what you will do with the feedback you get, but if you can, in the middle of the rest, express that there exists a point of view that the leadership does not listen well enough and needs to open up lines of communication to the leadership from employees, the community and even non-community users, that idea would be worth communicating.

I feel that Brendan was unfairly persecuted for expressing his views even though it seems evident he never allowed any personal views to affect his ability to function.

People have been justifying bashing his position on the basis that equality is normally and editorially required for any position of power. Unfortunately these people are either bordering on misinformed or purely idiotic.

I am surprised at how mean people can be toward Brendan. It is a big loss for Mozilla.

I have been using Firefox since it was called Phoenix. I have installed it on many PCs. I learned Javascript on Firefox. I was loyal to Firefox during the difficult years when it had memory and speed issues. I was generally impressed with Mozilla’s stance on the Open Web. Now, I am not so impressed with Mozilla.

Somebody has been forced to resign from Mozilla because of his beliefs/ideas/opinions. That is exactly the opposite of what Mozilla states to be its “mission” …

I find it horrific that this backlash is a repeat of what you experienced two years ago. And it’s deeply affected me in my impression of how welcomed Christians are at Mozilla.

If you want your voice heard, or just want to talk in confidence (say if so), please email me.

Categorieën: Mozilla-nl planet

Tim Taubert: A ready-to-use virtual build environment for Firefox

Mozilla planet - ma, 07/04/2014 - 18:00

If you ever wondered what contributing to Firefox feels like but you never had the time to read and follow through our instructions to setup a build environment or wanted to avoid screwing around with your precious system then this might be for you.

This article will guide you through a small list of steps that in the end will leave you with a virtual machine ready to modify and build your own development version of Firefox.

I hope this will be valuable to novice programmers that do not have a full C++ development environment at hand as well as to the more experienced folks with little time and lots of curiosity.

1) Install VirtualBox

Note: The Open Virtualization Format (OVF) is supported by other Virtualization Environments such as VMWare, etc. You can use those if already installed instead of VirtualBox.

Go to the VirtualBox Downloads page and download the latest version available for your operating system. Should you already have VirtualBox installed then please ensure you are running the latest version by checking for updates before continuing.

2) Download the Firefox Build Environment

Now is the time to download the virtual machine containing our development environment ready to modify and build Firefox. You can get it here:
(sha1 = c5717af5cccdc2c42e0a236a9859abffd940df9a)

Downloading ~2.6 GB might take a while if you are on a slow connection, sorry.

3) Set up the virtual machine

Once the image has been downloaded you can double-click the .ova file and import the new virtual machine into VirtualBox. Please give it at least 2048MB of RAM (4096MB if you can) and the same number of processors that your host machine has available. Building Firefox takes up a lot of resources and you want it to build as fast as possible.

Now that your virtual machine is ready, boot it and wait for the Ubuntu desktop to be shown. A terminal will pop up automatically and do some last steps before we can get started. After a successful installation Sublime 2 should start automatically.

Note: Should you ever need root credentials, use “firefox-dev” as the password. If you want to change your Language and Keyboard settings then follow the instructions on How to change the UI Language in Ubuntu.

4) Build Firefox

Click Tools > Build to start the process. This might take a long time depending on the features of your host machine, please be patient. You can watch the build progress in the text editor’s console at the bottom. Once the build has finished you can use Tools > Run to start your custom Firefox build and check that everything works as expected.

Note: if you want to switch from an optimized to a debug build then choose Tools > Build System > Firefox (Debug) and hit Tools > Build again to start a debug build.

5) Now what?

You successfully built Firefox for the first time and wonder what’s next? How about picking a small bug for a start, contribute code and get your changes shipped to half a billion people? If that sounds compelling then take a look at Bugs Ahoy! and find something to work on that sounds interesting to you.

If you are interested in digging deeper into the build system or the version control system, or want to know more about how to create your first patch and post it to our bug tracker then take a look at our Code Firefox Lessons.

I would love to hear your feedback about the Firefox Build Environment! Please tell me what can be improved and what you would like to see in the next version. Do not hesitate to drop me a mail should you have a more detailed opinion.

Categorieën: Mozilla-nl planet