mozilla

Mozilla Nederland Logo De Nederlandse Mozilla gemeenschap

Gervase Markham: Your Ire Is Misdirected

Mozilla planet - za, 05/04/2014 - 08:56

Hi. My name is Gervase Markham. I’m a supporter of traditional marriage, and I work for Mozilla. In fact, as far as being on the record goes, I believe I’m now the only one.

Many people who agree with me on this issue are very upset about what happened to Brendan Eich, our co-founder and, for two weeks, CEO of the Mozilla Corporation. Brendan was appointed and then, after 10 days under the Internet’s lens of anger based on his donation in opposition to the redefinition of marriage, stepped down and stepped away from Mozilla – to our great loss.

I am assured by sources I trust that Brendan decided to leave of his own accord – he was not forced out. My understanding is that the senior management of Mozilla (many of whom disagree with him on this issue) worked very hard to support him, even if I would not agree with all the actions they took in doing so. However, he eventually felt that it was impossible for him to focus on leading if he was spending all of his time dealing with the continued, relentless news and social media storm surrounding the donation he made. In other words, he wasn’t forced out from the inside – he was dragged out from the outside.

So, here’s my plea: please don’t be angry with Mozilla. Mozilla and what it does and stands for is too important to the future of the free web to allow this to do it damage. It was us who brough innovation back to the web browser market and started the process which led to the awesome web you use today. And now, we’re trying to do the same with the closed smartphone market. I believe that connecting billions of people in the developing world to the web at minimal cost and with full fidelity will lead to the next great advance in human flourishing, as people can use the information they discover to make their own lives better. That’s our goal.

If you can’t find it in your heart to forgive them (the course I would recommend), then your anger is best directed at those outside Mozilla who made his position untenable. The press that twist and sensationalize without investigation, social media which magnifies and over-simplifies without consideration, and those who rush to judgement without understanding. I’m not going to name names or organizations. But as far as Mozilla itself goes, please, please continue to support us.

I am determined to work to make all Mozillians of whatever beliefs – and whatever actions they take outside of Mozilla in support of those beliefs – confident that, if they can work with other Mozillians as Brendan did so well for 15 years, Mozilla is a place for them. How successful we’ll be at that depends on how our community deals with what just happened – but it also depends on you. If you jump to paint Mozilla in the colours of ‘the opposition’, that will become a self-fulfilling prophecy. And the world will be poorer for it.

Mozilla is caught in the middle of a worldview war. Let’s not make the free web a casualty.

Categorieën: Mozilla-nl planet

Nick Cameron: Some thoughts on data structures in Rust

Mozilla planet - za, 05/04/2014 - 03:45
One thing I'm not so keen on in Rust (more of an itch, than a pain) is that there are a lot of data structures. C++ has classes and structs (which are basically the same thing), enums, and unions. Java has classes and enums (unless its gained some recently). Scripting and functional languages tend to have more (lists, tuples, dictionaries/maps, and so forth). (I'm ignoring arrays, lists, and other sequences for this post). Rust has:
  •     structs
  •     tuples
  •     tuple structs
  •     unit structs
  •     enums
  •     unit variants
  •     'tuple' variants
  •     struct variants
This seems like a lot, and I think it is a bit confusing. But there is good motivation for all of them. Still I think it is a little bit of an ad-hoc collection.

We've been thinking recently about how to support structures like the DOM, and there have been a bunch of different proposals. One of mine (https://github.com/rust-lang/rfcs/pull/24) suggests using a kind of unification of structs and enums to support Java style inheritance. I think that idea probably won't work. But I have a lot of thoughts which I would like to preserve for posterity. I'm not proposing any changes to Rust here, just trying to put into order the data structures a bit, and maybe provide a design for a core calculus or something. Basically intellectual masturbation, but perhaps it is interesting.

Classifying data structures

I think it is useful to classify the data structure along several axes:
  1. Are there many variants or just one (enums  - many, everything else - just one);
  2. Do the data structures give types (yes, except for the variants of enums);
  3. Does the data structure introduce a name, and thus nominal typing (tuples don't, everything else does);
  4. Are the fields of the structure named (enums and unit structs/variants - NA, tuples and tuple variants - no, everything else - yes);
  5. Can the data structure be instantiated (enums - no, everything else - yes);
  6. Can the data structure be a variant of another (variants - yes, everything else - no).
Do these categories uniquely identify each data structure? Yes.

Are there combinations of categories which are empty? Also, yes. Some of these are not interesting - there are no instantiable data structure which don't introduce a type. Some are just kind of holes - why is there no anonymous record type (i.e., a structure with named fields, but which can't be named itself)? Some are design decisions - why can't variants be used as types (maybe they will in the future)? Finally, some are really interesting questions - why don't we have variants which are themselves enums? Why don't enums have fields (named or not)? What would it mean to instantiate an enum? Could we have un-named variants?

What would a minimal set of data structures look like

In RFC PR 24, I proposed nesting enums and unifying enums and structs. I would like to go even further and try and think about a minimal set of data structures with the same expressivity as Rust data structures (more, in fact).

First a few observations. If fields are not named, then order is important, otherwise it isn't. That means mixing named and un-named fields doesn't really work. If a structure is named then it is nominally typed, otherwise, it is structurally typed. A unit structure is the same as a structure with n fields (named or not), where n = 0.

Lets start with records - we want named and un-named records with named and un-named fields. That gives us structs and tuples, both with and without names (as opposed to Rust which is missing un-named structs). Here is a Rust-like syntax (I use `[]` to mean a comma-separated sequence):S ::= 'struct' id '{' ([id:T] | [T]) '}'
T ::= id | '{' ([id:T] | [T]) '}'
e ::= id? '{' ([id:e] | [e]) '}'The next thing we need are enums and variants. Lets follow my unification proposal and just add variants to structs. The next question is what the variants should be - lets just use the existing data structures. And then we have the question of should an enum be instantiable - rather than following my RFC and using enum vs struct to differentiate, lets just add a keyword - abstract. Now we have:S ::= 'abstract'? 'struct' id '{' ([id:T] | [T]), [S] '}'
T ::= ... | id | '{' ([id:T] | [T]) '}'
e ::= ... | id? '{' [[id:e] | [e]] '}'Note that the initialiser syntax has changed to be a sequence of sequences of possibly named expressions. That is because I imagine the fields of outer data structures being inherited by inner ones. We have to accommodate un-named fields (where order is important) and named fields (where order is not, at least within the sub-sequence).

I believe this emulates all Rust data structures and adds anonymous records. Enums are abstract structs with no fields, structs are structs with named fields and no variants. Unit, tuple, and struct variants are nullary structs, structs with un-named fields, and structs with named fields - each nested inside an abstract struct with no fields. And so forth. One difference is that our encoding of variants introduce types, but that is an increase in expressivity.

With reference to my earlier classification, the obviously missing structures are un-named structures with variants and un-named variants - I don't believe either are practically useful; neither are present in Rust.

We have also added expressivity in the form of inheritance of variants from their enclosing structures. In terms of data, we can therefore emulate Java-style classes (we need to add virtual functions to emulate their behaviour, see the RFC for details of that).

To make the syntax more friendly we would add unit variants and structs. Then eliminate the struct keyword. We could use different kinds of brackets. Continuing we could end up back at Rust. I hope the little syntax snippet gives a glimpse of an elegant foundation for all these data structures.

A practical matter

I said above that my RFC/proposal wouldn't actually work, and this thought experiment has the same problem - how to implement enums? As with any value we must know the size of the value at compile time. In a language like Java where everything is a pointer, that is easy - the size is always one word. In Rust we want to really pass values by value. Since each enum variant could be a different size, that is a problem.

The current Rust implementation is to use the maximum size of the variants as the static size for an enum value. Then pad any variant values which are smaller than that. That is fine if we don't have too many enum objects or all enum variants are similar sizes. That is mostly the case.

However, under the scheme sketched above, we might expect both those constraints to be false. If we think about the DOM for instance, each object could be wildly different in size and we would have lots of objects, so there would be a lot of wasted memory.

One solution might be to represent enum values as a tag and a pointer to a bunch of fields, rather than as a tag and a bunch of fields. That would work, although you would have to do be careful to copy the pointed-to fields and not just the pointer when passing by value. However, it adds the cost of a dereference to every access and it is often convenient to really have a value. Rust is a systems language in the C-spirit and so there should not be this kind of magic.

In the context of virtual structs, we have previously discussed treating struct objects as dynamically sized types. We could then allocate precisely sized instances and refer to them via pointer which gives subtyping. However, such values must have restricted uses and so this would be incompatible with the current use of enum values. A solution suggested by bill-myers on GitHub is to use some keyword or attribute (`unsized`, say) which indicates that instances should be dynamically sized and mostly passed by reference. Omitting the keyword would give the current semantics and it is up to the programmer to ensure there is not too much memory wasted by padding.
Categorieën: Mozilla-nl planet

Personality and Change Inflamed Mozilla Crisis - New York Times

Nieuws verzameld via Google - za, 05/04/2014 - 03:28

Washington Post (blog)

Personality and Change Inflamed Mozilla Crisis
New York Times
Monday morning “town halls” at Mozilla are open to the public and anyone can look at the code that powers Mozilla's popular Firefox web browser. The company's employees are encouraged to speak their minds and even criticize the boss on Twitter.
Brendan Eich, Mozilla, and the right to be wrongWashington Post (blog)
Mozilla's Gay-Marriage Litmus Test Violates Liberal ValuesThe Atlantic
The racism behind firing Mozilla CEO Brendan EichDigiNews
TheStreet.com -Business Insurance
alle 593 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Jim Chen: Let's not protest protesters

Mozilla planet - za, 05/04/2014 - 00:03

Jon Foreman (of the band Switchfoot) recently wrote a post called ”Why I Refuse To Protest Protestors”. In it, he talked about his experience dealing with protests at his band's concerts. A few sentences he wrote struck me the most,

All at once I had an epiphany: these puzzling creatures that are yelling at you are human souls – as unpredictable, perplexing and unpredictable as I am. Here's the shocker: this guy with the bullhorn could be my cousin! he could be a friend of mine! Better yet: this guy could be me! If our lives were swapped, who can say that I would be any different? I put nothing below me. Who can say what I would do if I had his reality? Compassion makes you realize what you have in common with the rest of humanity.

For me as a Mozillian, these past few days have been confusing and unsettling. First it was the protests against Brendan's appointment. For an organization you are a part of, for a pioneer you look up to, for them to be rallied against, it was hard to understand. Then it was Brendan's resignation. That was unexpected and felt like things falling apart. Now it is another wave of protests against Brendan's departure. In the midst of this whirlwind, I want to feel anguish. I want to shout. Why couldn't Brendan just recant? Why couldn't the protesters just understand? Why couldn't the media just set the story straight? Why couldn't Mozilla just handle everything a little better? I want to protest.

But that's not what Mozilla is about. Like Katharina said, Mozilla is great at not only shipping great products but also at shipping love. It was love, love for the web, that first brought Mozilla together. It is love that continues to drive our mission now. Like Jon wrote,

On my best days, I want to stand for love conquering a multitude of wrongs. I want to stand for forgiveness, for mercy, for beauty, for grace. I stand for you, sir and madame. Whether you are holding a megaphone or not. Even when you refuse to shake my hand I love you. Whether you insult me or not, drunk or sober; I honestly love you! I love your passion, your fervor, your dedication. I want to know you better. I want to find out what makes you tick. I want to know why you believe what you believe. I want to learn from you. I am for you, emphatically for you!

Let's do what we do best, at showing love. Show love to Brendan; thank him for all that he's done and wish him the best. Show love to the activists; empathize with them. Show love to people who think Mozilla is not inclusive. Show love to the journalists, to companies protesting us. Show love to the Board, to your peers, to the community. Let's show our love to Mozilla.

Categorieën: Mozilla-nl planet

Matt Thompson: How do we do better product testing in Q2?

Mozilla planet - vr, 04/04/2014 - 23:42

We’ve been trying to figure this out for Webmaker. Here’s a proposal:

  • 1) Start small. Figure out our product testing strategy *for Q2.* (Instead of “everything we need to do to get better at testing.” Which feels too overwhelming.) What are the most important things to test and learn this quarter?
    • Proposal: start with the key Engagement Ladder stuff. We’ve said those calls to action are the most important — let’s make sure they’re clear and feel good for users, and identify where they’re bailing or getting stuck. For example:
      • Sign up. Create an account.
      • Create an event.
      • Make a teaching kit.
      • Issue a mentor badge.
    • Why start here? Because we’ve said these pathways are the *most* important. In terms of reaching our 10k contributors goal. We should do usability testing to see where users are getting stuck here, and ship incremental improvements to address those.
  • 2) Focus on testing with lead users. People teaching the web. These users are signing up for Webmaker training, and will be using and offering feedback on Webmaker stuff over the next several weeks. This is a prime opportunity. What do we want to feed in there? https://wiki.mozilla.org/Webmaker/Testing
  • 3) Unstick usertesting.com. aka:

Let’s make it easy for people to test whatever the hell they want, all the time.

  • It doesn’t seem like we’re really making full use of usertesting.com as an asset.  Let’s figure out why. (e.g., not sure of process / don’t have log-in / don’t have time / need training / ?) How do we make it easy and permissionless for our devs and designers to play there?
    • For example: when Aali wants to test right-to-left in Popcorn, why can’t he just go ahead and do it? How do we make running a test on usertesting.com as easy and standard as writing a blog post?
  • 4) Optimize the process for sharing out the findings. Understanding what we’re learning from this testing. And then feeding it back into the product. That’s always the hard part. I think we win there by doing usability testing on the small number of things mentioned in (1), rather than “let’s test everything.”
  • 5) Update the Webmaker get involved page. This is where we’re sending folks now. Review and optimize.

What’s missing / wrong? Please comment here.

Categorieën: Mozilla-nl planet

Gary Kwong: Too much has happened recently in too little time.

Mozilla planet - vr, 04/04/2014 - 23:30

I know a lot of us, no matter hailing from whatever cultures, old-timer or otherwise, volunteer, employee or otherwise, will pull ourselves through.

And we’ll survive and emerge stronger.


Categorieën: Mozilla-nl planet

Planet Mozilla Interns: Willie Cheong: Release Readiness DashboardQb query Builder

Mozilla planet - vr, 04/04/2014 - 23:28

The Release Readiness Dashboard chose Elastic Search as the source of Bugzilla data because it was fast and provided a convenient means of retrieving historic information for plotting trends. However, the native queries used to request data from Elastic Search clusters are long, ugly, and horrible JSON objects.

To solve the issue of dealing with ugly Elastic Search queries, the administrator of Bugzilla’s Elastic Search cluster has set up a helpful Javascript library for web developers. It acts as a middle layer for requesting data from the Elastic Search cluster using Qb queries instead of native Elastic Search queries. The RRDashboard uses the Qb Javascript library.

Qb queries, similar to Elastic Search queries, are JSON formatted objects. One might now ask the question of what Qb queries are, and how it has an advantage over native Elastic Search queries if both are just about as obscure as the other. Qb queries for one, are much shorter than native Elastic Search queries. They are also a lot more read-able.

Coming from an obscure background, the problem with writing Qb queries still persists. The release management team will have significant difficulty in adopting the RRDashboard if they are unable to form Qb queries that request the same data they are currently pulling using the Bugzilla search interface. I am now ready to introduce the Qb query builder.

When the release management team builds a query using the Bugzilla search interface, a long Bugzilla URL is generated containing the query parameters. As an input to the Qb query builder, this Bugzilla URL can be directly translated into a Qb query after specifying some other required parameters like the cluster to query against. In the background, here is what actually happens.

Upon submitting the form on the Qb query builder, a big Javascript event handler is triggered. The search parameters are extracted from the submitted Bugzilla URL, then re-appended to the Bugzilla search interface’s URL. Using a CURL request, we receive an enormous HTML string containing the Bugzilla search interface’s page filled with user-specified search parameters. Scraping then occurs on each individual page element to extract the search parameters, which are then appended into a JSON object formatted as a Qb query.

The benefit of such an implementation is that this is as simple as it will ever get for an end-user to work between Bugzilla and Qb queries. Unfortunately, there are also significant limitations to this implementation.

Scraping HTML of the Bugzilla search interface implies that the Qb query tool is very dependent on how the views of Bugzilla are generated. If the HTML layout of the Bugzilla search interface changes, the Qb query builder will lose its accuracy and start missing search parameters in the output Qb queries. A possible alternative is directly parsing the Bugzilla URL without doing a CURL request to get the HTML. However, this can be a potentially complex task to handle and will require more time beyond what I current have as an intern.

Another limitation to the Qb query builder is that it can be buggy. Bugzilla’s search interface is a mature product that can handle many different combinations of search parameters. The Qb query builder, on the other hand, is new and may not be able to handle as many varieties of querying as Bugzilla can. As a result, until the Qb query builder matures enough to handle all the corner cases that Bugzilla may throw at it, users of the tool may occasionally have to modify the output Qb queries manually to get what they want.

Categorieën: Mozilla-nl planet

Matt Thompson: 5 easy ways to support Mozilla

Mozilla planet - vr, 04/04/2014 - 21:59

Mozilla Love

What’s the best way to support Mozilla right now?

5 simple suggestions:

  1. Tweet some love using #mozlove or #standwithmozilla
  2. Use the “MozLove” avatar. You can download it here: http://mzl.la/mozlove
  3. Download Firefox. Or encourage others to switch http://www.mozilla.org/firefox
  4. Make a donation. Mozilla is a non-profit community dedicated to protecting the open web. http://mozilla.org/donate
  5. Get more involved with Mozilla’s non-profit mission. http://www.mozilla.org/contribute
Categorieën: Mozilla-nl planet

Ben Hearsum: This week in Mozilla RelEng – April 4th, 2014

Mozilla planet - vr, 04/04/2014 - 21:53

Major highlights:

Completed work (resolution is ‘FIXED’):

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

Categorieën: Mozilla-nl planet

Brendan Eich alweer weg bij Mozilla na ophef over… - Blog.nl (Blog)

Nieuws verzameld via Google - vr, 04/04/2014 - 21:34

Brendan Eich alweer weg bij Mozilla na ophef over…
Blog.nl (Blog)
images Brendan Eich stapt op als CEO bij Mozilla. Al direct na zijn benoeming, eind maart, kwam hij onder vuur te liggen. In 2008 doneerde hij geld aan een campagne voor Proposition 8, een referendum in Californië die het homohuwelijk van tafel moest ...

Google Nieuws
Categorieën: Mozilla-nl planet

Sylvestre Ledru: Changes Firefox 29 beta4 to beta5

Mozilla planet - vr, 04/04/2014 - 21:30

Firefox 29 beta 5 has just been pushed to the mirrors. This release is similar to beta3 and beta4 is term of number of commits but their total size has been divided by 2. In this beta, some critical bugs fixed, various sync improvements and, obviously, Australis!

We are also providing two more statistics: by extensions and by modules (the number of files changed).

  • 43 changesets
  • 128 files changed
  • 1049 insertions
  • 425 deletions

By extensions:

ExtensionOccurrences js52 cpp26 h10 css7 html6 jsm4 xul3 json3 xhtml2 list2 ini2 in2 xml1 sh1 py1 java1 c1

By modules:

ModuleOccurrences services39 browser19 js15 content9 mobile8 dom8 layout6 docshell5 testing4 toolkit3 gfx3 netwerk1 modules1 memory1 intl1 build1

List of changesets:

Boris ZbarskyBug 988106 - No more unnecessary .wrappedJSObject in debugger. r=past, a=sledru Bobby HolleyBug 969441 - Check for recursion outside of the hairy transplant callsites. r=billm, a=sledru Nikhil MaratheBug 967005 - Report rejected promises when worker stops running. r=bent, a=sledru Sean StanglBug 616491 - Limit YARR stack size to 1MB. r=mjrosenb, a=sledru Mark HammondBug 970167 - Disable passwords engine when a master password is set. r=rnewman, a=sledru Bas SchoutenBug 984796 - Fix some small errors in path flattening code. r=jwatt, a=sledru Mark HammondBug 985212 - Check if the username looks like an email address to determine what sync to use. r=rnewman, a=sledru Henrik SkupinBug 987147 - [tps] Re-add support for old sync authentication. r=jgriffin, a=sledru Peter Van der BekenBug 988863 - Preserve Location in AddProperty. r=bholley, a=sledru Olli PettayBug 987433 - DOMTokenList should have a strong reference to its owner so that the API doesn't suddenly start returning empty string. r=khuey, a=sledru Brian NicholsonBug 988527 - Fix progress.9.png to have balanced padding. r=lucasr, a=sledru Benjamin BouvierBug 989166 - Reserve stack explicitly rather than implicitly. r=sstangl, a=sledru Margaret LeibovicBug 976680 - Remove landscape padding from home banner. r=bnicholson, a=sledru Sylvestre LedruBug 990213 - Post Beta 4: disable EARLY_BETA_OR_EARLIER a=me Marco CastelluccioBug 898647 - Move app package in the Resources directory on Mac. r=myk, a=sledru Randell JesupBug 986762 - Don't release DataChannelConnection on transient thread on readblob failure. r=smaug, a=sledru Myk MelezBug 982559 - Use intent data to start app from legacy shorcut. r=wesj, a=sledru Jared WeinBug 969963 - Grey out PanelUI-popup items when a subview is opened. r=mconley a=sledru Gijs KruitboschBug 983997 - move pulse animation into animation container, too, r=mak,a=sylvestre Chris PetersonBug 952602 - #ifdef EARLY_BETA_OR_EARLIER to disable navigator.plugins[] cloaking before GA release. r=bsmedberg a=sylvestre Nick AlexanderBug 983350 - Follow-up: Rev User-Agent string. r=rnewman, a=follow-up Mats PalmgrenBug 988453 - Make nsHyphenationManager::Shutdown() resilient against being called more than once. r=roc a=sledru Jim MathiesBug 978127 - Update various win8 specific australis customized ui tests to use new Services.metro.supported prop. r=gijs. a=tests Jon CoppeardBug 986843 - Replace AutoHoldZone with AutoCompartmentRooter r=terrence a=sylvestre Bobby HolleyBug 989183 - Check for nsXBLJSClass. r=bz, a=sledru Ehsan AkhgariBug 965362 - Do not assume that all of the contents of the HTTP channel will be available by the time we decide to read it synchronously in devtools tests. r=robcee, a=test-only Ehsan AkhgariBug 947531 - Focus the test window before starting the test. a=test-only Martyn HaighBug 970209 - Surround update logic in about:apps with synth apk specific wrapper. r=wesj, a=sledru Matt BrubeckBug 972844 - Add a Maybe Later link on about:feedback intro. r=mfinkle, a=sledru Matt WoodrowBug 973264 - If we wrap gfxImageSurface data when creating a SourceSurface, hold a reference to the original surface so the data stays alive. r=Bas, a=sledru Olli PettayBug 989210 - Consistently make cycle collector to deal with TextTrackManager's member variables. r=reyre, a=abillings Jan de MooijBug 989586 - Fix Ion correctness Bug when inlining |new Array(x)|. r=bhackett, a=sledru Robert StrongBug 982448 - some fxmetro pref's still being left behind with values without --enable-metro in the mozconfig. r=bbondy, a=sledru L. David BaronBug 989130 - Back out changeset fe119a83b1f2 (Bug 942017) while leaving the corresponding test from changeset 3c63decb4e7e. r=jfkthame approval-mozilla-beta=sylvestre Luke WagnerBug 983448 - Fix masm.convertUInt32ToFloat32 on x86. r=bbouvier, a=sledru Mike HommeyBug 984447 - Properly handle forks in mozjemalloc after Bug 694896. r=smichaud, a=sledru Ehsan AkhgariBug 919208 - Rewrite test_bug668513.html to run in its own window so that it won't be able to navigate the test runner frame back. r=bzbarsky, a=test-only Anthony LamBug 970213 - Replace icon with custom design. r=wesj, a=sledru Cameron McCormackBug 989965 - Resolve style for pseudo-elements correctly when style rules that have user action pseudo-classes on them are present. r=bzbarsky, a=sledru Myk MelezBug 968129 - Load initial tab in WebappImpl:loadStartupTab. r=mfinkle, a=sledru Ehsan AkhgariBug 990202 - Move the test page to a new window to prevent it from navigating the test runner frame back. r=bzbarsky, a=test-only Randy LinBug 912627 - Remove spurious assertion. r=cpearce, a=sledru Ryan VanderMeulenBacked out changeset cd8fed951743 (Bug 982448) for Windows mochitest-bc perma-fail.

r= means reviewed by
a= means uplift approved by

Previous changelogs:

Original post blogged on b2evolution.

Categorieën: Mozilla-nl planet

Brendan Eich, Mozilla, and the right to be wrong - Washington Post (blog)

Nieuws verzameld via Google - vr, 04/04/2014 - 20:27

Washington Post (blog)

Brendan Eich, Mozilla, and the right to be wrong
Washington Post (blog)
It began badly. OkCupid posted a notice to users who were accessing it through Firefox asking them to switch browsers, pointing out that Mozilla's new chief executive was an “opponent of equal rights for gay couples. We would therefore prefer that our ...
Why Mozilla's Chief Had to ResignNew York Times (blog)
How Mozilla Lost Its CEONew Yorker (blog)
Conservatives launch boycott of Mozilla after gays press CEO to quitWashington Times
Slate Magazine (blog) -The Atlantic -Christian Broadcasting Network
alle 593 nieuwsartikelen »Google Nieuws
Categorieën: Mozilla-nl planet

David Camp: Doubt

Mozilla planet - vr, 04/04/2014 - 20:26

If you tried, I don’t think you could engineer a situation that could throw the Mozilla community so thoroughly off-center. A lot of folks at Mozilla work here because we want to do what’s right. Doing the right thing can be hard, but overall we’re comfortable with taking on hardship to do the right thing.

Now a lot of us are having a hard time figuring out what right means here. We’d love a common cause to fight for. This situation is thoroughly grey.

It hurts to see your friends and community attacked. It hurts more when you agree with the premise. We’ve seen people we respect simplified beyond their humanity by other people we respect. And we lost people that were really important to our cause.

Some are doubting their place in the community, some are doubting our leadership, some are doubting their own reaction to the situation. Did I give enough support to the people that needed it? Did the support I did give hurt someone else that needed it? Doubt is good, but it can be tough.

If you have clarity in this situation, please understand that a lot of us don’t. There are axioms floating around: “Bigotry must be shunned.” “Tolerance means tolerating personal beliefs too.” “Freedom of speech doesn’t mean freedom from consequences.” “Personal beliefs can [or cannot] be separate from the workplace.” “We shouldn’t let one righteous social cause get in the way of another one.” There’s truth in all of them. Not all of us have been able to put that together into a firm position. Maybe give us some space – repeating the axiom isn’t helping us get there.

We’ll figure it out. It may just be a resolution that doubt is OK. It may be a better understanding of shades of gray. But we hold enough in common, we do have a “right thing” that we can focus on even when the other stuff is harder to figure out. Mozillians have been coming together when it would be really easy to tear ourselves apart. The way we address this cognitive dissonance as we get back to the work of the open web will say a lot about us. I’m pretty certain it’s going to say something impressive.


Categorieën: Mozilla-nl planet

Waarom de nieuwe Mozilla-CEO na elf dagen alweer opstapte - nrc.nl

Nieuws verzameld via Google - vr, 04/04/2014 - 19:34

nrc.nl

Waarom de nieuwe Mozilla-CEO na elf dagen alweer opstapte
nrc.nl
Slechts elf dagen is hij de baas bij Mozilla, de maker van onder meer browser Firefox. Maar gisteravond besloot Brendan Eich na veel publieke druk om zijn functie toch maar neer te leggen. Wat is er gebeurd? Een beknopte reconstructie (uitgebreidere ...
Homofobe directeur Mozilla na twee weken al weer vertrokkenTrouw
Nieuwe CEO Mozilla stapt alweer opSecurity.nl
Mozilla-topman nu al wegNOS
NU.nl -Volkskrant -NUtech
alle 55 nieuwsartikelen »
Categorieën: Mozilla-nl planet

Nieuwe CEO Mozilla stapt alweer op - Security.nl

Nieuws verzameld via Google - vr, 04/04/2014 - 19:27

Nieuwe CEO Mozilla stapt alweer op
Security.nl
Eich werd eind maart aangesteld als de nieuwe CEO van Mozilla, maar kwam direct in opspraak. Zijn donatie in 2008 van 1000 dollar aan een organisatie die zich verzet tegen het homohuwelijk werd breed uitgemeten. In een interview bleef hij zijn ...

Categorieën: Mozilla-nl planet

Gian-Carlo Pascutto: Only what unites us

Mozilla planet - vr, 04/04/2014 - 19:19
If anything, the last week has given us quite some things where we can have great discussions about. I'd love to do a treatise on how free speech interacts with the ability to do Internet witch burnings, or how universal truths relate to political opinions, but the nerves are tense and the knives sharpened, so attempting to do so would most likely only be preaching to the converted. Maybe another time.

Yet, when looking at the questions for the upcoming Mozillians Town Hall meeting, there is a pattern that worries me, and I would like to address.

Mozilla is a community that organizes around a mission. The mission is set out in the Manifesto. The Manifesto uses rather broad language, e.g. "must enrich the lives of individual human beings".

If we have to learn anything from the past 10 days, it is that we can only survive as a community if we interpret this mission only in its most narrow scope, where we can and should find common ground. Attempting to read the Manifesto in the widest possible manner and presuming to find that all of our fellow Mozillians have done so in the same way is the road to failure as a group and a community. Our cultural differences are immense and things which we find self-evident can be unimaginable to other. We should group among the narrow set of goals that unites us, not among what divides us.

Mission creep is death. As a result, Mozilla is pragmatic. We've thrown efforts under the bus when we believed it to be necessary to survive. It personally still pains me that we threw VP8 under the bus in favor of H264, but choices have to be made about what hurts us least.

Now, if anyone wants to make the argument that an "open, participatory and accessible" Internet obviously has a direct and inalienable relation to an already-repealed law in the state of California in the United States of America that tried to refine the legal definition of marriage, so Mozilla must fight for this cause, then fine. I am not going to argue with you. I simply want to point out that the remainder of this post is not addressed to you.

Why do I want to make this point now? I have looked at the list of questions for the Town Hall Meeting, and I could summarize a fair number of the highest up voted ones as "Why do we think it is acceptable that the personal opinion of a Mozillian influences his career prospects in our community?"

I understand this question. I've struggled with it myself. Up until yesterday, I wouldn't have believed Brendan would step down simply because of the enormous implication that has in relation to the above. When I joined Mozilla, I was encouraged by my manager (Stuart or Doug, sorry forgot which of you two!): "We expect our contributors to have an opinion and speak out on it". This obviously does not mix with what has happened this week.

The answer though, is above: it is not our fight to fight. Should a political/moral opinion and monetary support for it be grounds for a week-long internet shitstorm ending in resignation? The Fox has no opinion on this issue. The fact that we have such wildly differing opinions on it is a clear sign: this is far from the Mozilla mission, and it's outside our scope until we can find common ground. Should we fight global warming? The Fox has no opinion. Should abortion be allowed? The Fox most certainly has no opinion on that one. Should we legalize marihuana? The Fox wonders what you've been smoking that you're even asking him. Should we be able to anonymously participate on the Internet? You bet.

The "why do our private opinions affect our work" question is inappropriate for the Town Hall, because it is not Mozilla's problem. We have to choose to focus only on what unites us.
Categorieën: Mozilla-nl planet

Frédéric Harper: Don’t hurt Mozilla

Mozilla planet - vr, 04/04/2014 - 19:06
Thanks to Sean Martell for the image

Thanks to Sean Martell for the image

The storm that hit Mozilla since a couple of days makes me sad…

I’m in favor of gay marriage. I also have lesbian, gay, bisexual, and transgender friends. I would have the same opinion without them in my life. I firmly believe in freedom, and I respect people who don’t have the same opinion or vision as me. I did not know Brendan Eich enough as I only meet him once. I did not have strong opinions about his nomination as the CEO of Mozilla. I trusted the people who made the decision, and I thought that it could not hurt to have one of the founders as the new leader. CEO question apart, I’m grateful to Brendan for his contribution to the Open Web, and the creation of Mozilla. Let’s not forget the invention of JavaScript.

Why I’m sad

I’m sad because I had to start this post with justification about my personal belief, and social life. I saw so many other posts or thread gone in the wrong direction. I’m sad because the web shown his ugly face: on both sides of the story or beliefs. More important, even if I was disappointed by Brendan donation, I’m sad because he resigned. It’s not exactly about him, but more about the consequences. Last, I’m sad because Mozilla, that was probably one of the most open organization I know, changed during the last days…

Don’t hurt Mozilla

The person who did the donation was Brendan Eich. The people who nominated him were the board members. Even if they are making high level decisions as nominating a CEO, they are not Mozilla. Mozilla is thousands of people, some paid staff, and many volunteers. Mozilla is the people who fight, and work for the web: we want the web to be more open, and we want more people to have access to it. Mozilla is you! The shit storm of the last days did not only hurt Brendan: it hurt Mozilla a lot. It hurt the people who worked for days, months, years to make the web a better place to be!

Please, don’t hurt Mozilla.

P.S.: I’m not sure this post pay honor to my thoughts or if it makes sense to add to the cacophony…


--
Don’t hurt Mozilla is a post on Out of Comfort Zone from Frédéric Harper

Related posts:

  1. I’m joining Mozilla It was a bold move to leave Microsoft without knowing...
  2. Who are your rock star developers? I know; many people don’t like this rock star or...
  3. Tips and tricks for people Since a couple of days, I saw so many things...
Categorieën: Mozilla-nl planet

Alex Vincent: Think about what you do and to who you do it.

Mozilla planet - vr, 04/04/2014 - 18:53

Think, for a moment, about the kind of man you throw out of office.   We’re talking about a revolutionary here.  A man who changed the way we live and work entirely.  A man who did everything he could to promote independence, writing missives that people listened to.

Yes, he had his faults.  What man doesn’t?  But he was a leader before he was the top dog, and he did very well as a leader.  He has laid his thumbprint on history with his works.  He put his heart and soul, and his reputation, on the line, day in and day out.

You might think I’m writing the above about Brendan Eich, and I am.  But consider this:  the same could be said for the third President of the United States of America.

Congratulations.  By the same rational thinking, we the people just threw Thomas Jefferson out of office because he once owned slaves.

Categorieën: Mozilla-nl planet

Mark Surman: Mozilla is human

Mozilla planet - vr, 04/04/2014 - 18:52

A few days ago I wrote: Mozilla is messy. For better and for worse, the week’s events showed how true that is.

Looking back at the past week, this also comes to mind: Mozilla is human. In all the best and worst ways. With all the struggle and all the inspiration. Mozilla is very very human.

On the inspiration part, I need to say: Brendan Eich is one of the most inspiring humans that I have ever met. He is a true hero for many of us. He invented a programming language that is the heart and soul of the most open communications system the world has ever known. He led a band of brilliant engineers and activists who freed the internet from the grip of Microsoft. And, one-on-one, in his odd and brilliant ways, he helped and advised so many of us as we put our own hearts and souls into building Mozilla and building the web. I was truly excited to see Brendan step into the role of CEO two weeks ago. And, today, I am equally sad.

It’s important to remember that all heroes are also human. They struggle. And they often have flaws. Brendan’s biggest flaw, IMHO, was his inability to connect and empathize with people. I’ve seen and felt that over the years, finding Bredan brilliant, but distant. And you certainly saw it this past week, as many calm and reasonable people said “Brendan, I want you to lead Mozilla. But I also want you to feel my pain.” Brendan didn’t need to change his mind on Proposition 8 to get out of the crisis of the past week. He simply needed to project and communicate empathy. His failure to do so proved to be his fatal flaw as CEO.

I would argue that Mozilla is filled with heroes. Thousands of them. All of them very human, just like Brendan. In the past week, I’ve spent every waking hour with these heroes. And I have watched them struggle. I’ve watched Mitchell struggle with how to protect the soul and spirit of a global community that is filled with passion, dreams, tensions and contradictions. I’ve watched the boards struggle with how to govern something that is at once a global social movement, a valuable consumer brand and a company based in the State of California. I have watched dozens and dozens of Mozillians reflect — and sometimes lash out — as they struggle to figure out what it means to be an individual contributor or leader inside this complex organism. And I myself have struggled with how to help Mozillians sort through all this complexity and messiness. Being human is messy. That is Mozilla.

As I look at the world’s reaction to all this, I want to clarify two things:

1. Brendan Eich was not fired. He struggled to connect and empathize with people who both respect him and felt hurt. He also got beat up. We all tried to protect him and help him get around these challenges until the very last hours. But, ultimately, I think Brendan found it impossible to lead under these circumstances. It was his choice to step down. And, frankly, I don’t blame him. I would have done the same.

2. This story is actually not about Brendan Eich. Of course, the critics and the media have made this a story about Brendan and his beliefs. But, as someone intimately involved in the evens of the past week, I would say in earnest: this is a story about Mozilla finding its soul and its spirit again. Over the past three years, we’ve become better at being A Company. I would argue we’ve also become worse at being Mozilla. We’ve become worse at caring for each other. Worse at holding the space for difference. Worse at working in the open. And worse at creating the space where we all can lead. These are the things that make Mozilla Mozilla. And they are the things we did not have enough of to properly find our way out of the crisis of the past two weeks.

Before getting into this kerfuffle, we were working on the right things. We were building a phone that will truly bring the web into the hands and the pockets of the world. We were teaching the world how the web works. And we were standing up against those who want to break the web or turn into a way to watch what each of us do every day. Those are still the things we need to be doing. And we need to start doing them again on Monday.

What we also need to do is start a process of rebirth and renewal. We need to find our soul and our spirit. The good news: Mozillians know how to do this. We know how to make a phoenix rise from the ashes. That is what we must now do.


Filed under: mozilla, webmakers
Categorieën: Mozilla-nl planet

Majken Connor: Moving lines

Mozilla planet - vr, 04/04/2014 - 18:32

One of the parts that is hard about this situation for Mozilla is that we don’t know where to draw the line now. People are worried that this is now a slippery slope, or that anyone could be pushed out because of outside views. I think as a community we need to accept the truth that Brendan wasn’t a viable CEO and figure out where this leaves the lines.

I think there is an obvious set of boundaries in this case that hopefully we can restrict this kind of scrutiny to stay within. The CEO is an outward facing position. When asked about the responsibilities of CEO vs CTO, Brendan answered that the CEO does a lot of working with partners and hiring. So the CEO interacts with people currently outside the Mozilla community. People who haven’t had the chance to build trust in us, in our CEO, in our way of doing things. I think if a director of HR had made a similar donation, it would also make it hard for people who must interact with that person to feel safe and trust them, even if they leave their personal beliefs at the door.

I am worried that next we’ll be expected to thoroughly vet candidates on their political views and actions. I think the problem in this case was that we already knew about Brendan’s donation, and still asked everyone to trust him anyway. But if we don’t thoroughly vet someone, and something comes to light, will we be expected to ask them to step down as well? I have a feeling the answer is yes.

I think for me the biggest lesson here is that the world doesn’t know us, and therefore they don’t trust us. I think this is partly our fault, we have focused on trying to win with users, and not on values. If the world knew us for our values, and not for our features, maybe we’d have had more people defending us, trusting us that we wouldn’t hire a CEO that would harm our contributors. They may still have called for Brendan to step down, but they would have been much more thoughtful about separating Brendan the individual from Mozilla the organization.

Is that wishful thinking? Sure, but we’re Mozilla. We’re good at wishing things, and we’re pretty damn awesome at making sure they come true.

Categorieën: Mozilla-nl planet

Pagina's