Mozilla

Mock-Ups Available for Notices (previously was EULA)

September 17th, 2008

First set of mock-ups

Second post re mock-ups

17 comments for “Mock-Ups Available for Notices (previously was EULA)”

  1. 1

    Tom said on September 17th, 2008 at 1:13 pm:

    That is just superb 😉 Even better than I exspected.

    Thanks again.

  2. 2

    Captain Canuck said on September 17th, 2008 at 1:28 pm:

    the only thing that bothers me is the l10n

    just read the last paragraph in small print on the bottom.

  3. 3

    The Open Sourcerer said on September 17th, 2008 at 1:34 pm:

    I’m no lawyer, but this is a massive improvement. Thanks for listening.

    The first of the two layout ideas is my preference and I would *really* also prefer if you, or the Ultimate Distributor, could ship with the Website Services disabled by default. So this “contract” is then only required if the user turns them on…

    But great – really great.

  4. 4

    Pingback from Firefox e l’EULA: Mozilla non farà più la preziosa. Forse. « pollycoke :)

    […] nei commenti Alessio (grazie!) ha linkato le prime bozze della nuova non-EULA di Firefox: […]

  5. 5

    Vadim P. said on September 17th, 2008 at 3:23 pm:

    I really like that style.

  6. 6

    Chip Bennett said on September 17th, 2008 at 4:09 pm:

    (Cross-posting this comment)

    I love what you have done here, with both presentation and content; that said, an end-user agreement still exists with respect to the non-free services.

    (From my perspective, I think I’m happy with this arrangement. The end-user agreement is clearly limited to use of the services – and I can either agree, and use them, or else disable them.)

    Regarding the non-free services bundled (compiled?) with Firefox (I am still quite new to FOSS, so please forgive any ignorance):

    Isn’t Firefox itself released under an open-source license (the “tri-license”)? Confusing as the “tri-license” may be, isn’t it still the same, with respect to the prohibition of encumbering the end user with use restrictions?

    If true, doesn’t the inclusion of non-free services in the Firefox build contradict the “tri-license” under which Firefox is released? I don’t know if the right term is “contradict”, “invalidate”, “contaminate”, or whatever – the point is, how are the free and non-free components compatible?

    Wouldn’t it be better to package these non-free services as an add-on for the free Firefox?

    Then, the Windows/Mac builds could have the add-on installed/enabled by default, with the EULA presented upon install – and the Linux builds could have the add-on either not installed, or else installed, but not enabled (and users presented with the EULA when the add-on is enabled).

    Else, could the Linux distros be permitted to build Firefox with the services disabled by default – without facing branding-rights revocation? If the non-free services can’t be pulled out into an add-on, perhaps this solution would satisfy all?

  7. 7

    enneite said on September 17th, 2008 at 4:28 pm:

    Great.

    Ok, now I want a “free software” label on AMO (and a pony)

  8. 8

    Anders said on September 18th, 2008 at 1:22 am:

    Yes, yes, yes! Great work. This is exactly as I had hoped. Clear, unobtrusive, friendly, good looking.

    http://lockshot.files.wordpress.com/2008/09/welcome-to-firefox.png

    http://lockshot.files.wordpress.com/2008/09/closed.png

    Congratulations.

    And great that you will work on making the service agreement even better.

    http://lockshot.wordpress.com/2008/09/18/licensing-feedback/

  9. 9

    Roy Schestowitz said on September 18th, 2008 at 2:58 am:

    That’s brilliant. Thanks, Mitchell and others.

  10. 10

    jackb said on September 18th, 2008 at 9:45 am:

    Looks great but…

    1) Ubuntu – the user does not download FireFox. Why are you thanking them

    2) The reason for this page – most all is covered else where, hence why repeat – Is the inclusion of the encumbered services inside of a floss program. You then bury that. This again is because you are shipping the services as ON. If you ship them off (or better as add-on) and helped the user understand the need and restrictions.

  11. 11

    Pingback from No Firefox EULA screen on Linux | Robert Penz Blog

    […] the Mozilla Foundation announced that here will be no EULA screen on Linux. Take a look at this post for details. It seams that our protest helped to convince them to remove that idea from the table. […]

  12. 12

    Pingback from Aktualizacja w sprawie EULI at stream of bytes

    […] tym momencie najbardziej prawdopodobne ostateczne rozwiązanie kwestii EULI w Fx będzie wyglądało […]

  13. 13

    stephantom said on September 18th, 2008 at 2:16 pm:

    This is one hell of an improvement. Hats off. Any of those mockups will be just fine. I’m even cool with the extra notice-bar.

  14. 14

    Foo Foo said on September 18th, 2008 at 9:35 pm:

    Test test

  15. 15

    Pleased as Punch said on September 19th, 2008 at 2:02 pm:

    Umm… WOW. Simple, effective, non intrusive, helpful. Great

  16. 16

    Pingback from An update on the Firefox EULA issue « I’m Just an Avatar

    […] Mitchell Baker: Mock-ups Available for Notices (previously was EULA) […]

  17. 17

    John Gilmore said on September 25th, 2008 at 7:38 pm:

    The issue is moving in the right direction. Thank you for listening.

    The trademark issue won’t go away unless you make it go away, though. Distros (and anybody else) need to be able to fix bugs in your code, without ripping all the trademarks out of it. It’s incomprehensible that you *want* your trademark to be associated with buggy code. Much bigger, more complex, more respected software like Linux and GCC get along without being trademark nazis. Almost nobody ships either Linux or GCC in the stock configuration from its originator. Yet their reputations survive and thrive. Ponder how that situation could exist for decades — then revisit your trademark policy.

    The privacy issues of your “web services” also need addressing. By default, the browser feeds search keystrokes to Google, accepts Google’s permanent cookie, and feeds every URL to Google for malware checking. One might even be led to think that Google was paying the bills over at Mozilla, given the way that Firefox’s defaults all feed reams of private information to Google without notifying the user.
    (And the way to turn off “Search suggestions” is hidden in a very odd place — nowhere near the privacy settings.)

    In a previous comment I suggested that the people responsible for the EULA idea be fired. You took offense at that, and upon reflection, you are right.

    A friend who used to work at Mozilla mentioned that most of the Moz Fdn employees really are not from the free software culture, and have little understanding of it. They’re doing marketing, or finance, or nonprofit administration, or whatever; not free software. This was a revelation that made it more obvious how the EULA error could have occurred.

    At my last company, Cygnus Support, we hired many marketing people (mostly VPs of marketing). Each of them had to be carefully watched over for a year or two, because invariably their natural reflex was shaped by a lifetime in proprietary software companies. They would automatically assume that the answer to any issue was to close down, lock out, deny, stonewall, license. The founders had to gradually teach them that the way we got customers was to have them feel really free to just download and use the software anytime they wanted, share it with all their friends, talk it up on the net, hack on it, report bugs publicly, read bug reports. Eventually the users’ company would discover that it was depending on our software, and it might want our paid services in supporting it, or improving it to fit their company’s desires even more tightly. With such a policy, we were bringing in $20M in revenues per year, before we were acquired by Red Hat. Closing the product would have cut into that revenue. After their first few years in the company, we had the marketing people and the managers and executives better trained, and we could be less watchful.

    So, I’m sure that this brouhaha has been a very salutary training session for the Moz Fdn people involved. It would be a shame to fire all that fresh expertise, and replace it with someone else whose reflexes will still be wrong, and who will not have seen WHY their reflexes are wrong for this community.

    (Cygnus was lucky to have Dan Appelman as our lawyer. Years of service to the USENIX Association and the Unix community had already knocked off any proprietary reflexes he might have had, so he never caused us this sort of trouble.)

    John

Skip past the sidebar