mozilla

Mozilla Nederland LogoDe Nederlandse
Mozilla-gemeenschap

Tantek Çelik: #XOXOFest 2016: Ten Overviews & Personal Perspectives

Mozilla planet - wo, 14/09/2016 - 08:45

I braindumped my rough, incomplete, and barely personal impressions from XOXO 2016 last night: #XOXOfest 2016: Independent Creatives Inspired, Shared, Connected. I encourage you to read the following well-written XOXO overview posts and personal perspectives. In rough order of publication (or when I read them):

(Maybe open Ben Darlow’s XOXO 2016 Flickr Set to provide some visual context while you read these posts.)

  1. Casey Newton (The Verge): In praise of the internet's best festival, which is going away (posted before mine, but I deliberately didn’t read it til after I wrote my own first XOXO 2016 post).
  2. Sasha Laundy: xoxo from XOXO
  3. Nabil “Nadreck” Maynard: XOXO, XOXO
  4. Matt Haughey: Starving artists / Memories of XOXO 2016
  5. Courtney Patubo Kranzke: XOXO Festival Thoughts
  6. Zoe Landon: Hugs and Kisses / A Year of XOXO
  7. Clint Bush: Andy & Andy: The XOXO legacy
  8. Erin Mickelson: XOXO
  9. Dylan Wilbanks: Eight short-ish thoughts about XOXO 2016
  10. Doug Hanke: Obligatory XOXO retrospective

There’s plenty of common themes across these posts, and lots I can personally relate to. For now I’ll leave you with just the list, no additional commentary. Go read these and see how they make you feel about XOXO. If you had the privilege of participating in XOXO this year, consider posting your thoughts as well.

Categorieën: Mozilla-nl planet

Mozilla Addons Blog: WebExtensions and parity with Chrome

Mozilla planet - wo, 14/09/2016 - 00:14

A core strength of Firefox is its extensibility. You can do more to customize your browsing experience with add-ons than in any other browser. It’s important to us, and our move to WebExtensions doesn’t change that. One of the first goals of implementing WebExtensions, however, is reaching parity with Chrome’s extension APIs.

Parity allows developers to write add-ons that work in browsers that support the same core APIs with minimum fuss. It doesn’t mean the APIs are identical, and I wanted to clarify the reasons why there are implementation differences between browsers.

Different browsers

Firefox and Chrome are different browsers, so some APIs from Chrome do not translate directly.

One example is tab highlight. Chrome has this API because it has the concept of highlighted tabs, which Firefox does not. So instead of browser.tabs.onHighlighted, we fire this event on the active tab as documented on MDN. It’s not the same functionality as Chrome, but that response makes the most sense for Firefox.

Another more complicated example is private browsing mode. The equivalent in Chrome is called incognito mode and extensions can support multiple modes: spanning, split or not_allowed. Currently we throw an error if we see a manifest that is not spanning as that is the mode that Firefox currently supports. We do this to alert extension authors testing out their extension that it won’t operate the way they expect.

Less popular APIs

Some APIs are more popular than others. With limited people and time we’ve had to focus on the APIs that we thought were the most important. At the beginning of this year we downloaded 10,000 publicly available versions of extensions off the Chrome store and examined the APIs called in those extensions. It’s not a perfect sample, but it gave us a good idea.

What we found was that there are some really popular APIs, like tabs, windows, and runtime, and there are some APIs that are less popular. One example is fontSettings.get, which is used in 7 out of the 10,000 (0.07%) add-ons. Compare that to tabs.create, which is used in 4,125 out of 10,000 (41.25%) add-ons.

We haven’t prioritized the development of the least-used APIs, but as always we welcome contributions from our community. To contribute to WebExtensions, check out our contribution page.

Deprecated APIs

There are some really popular APIs in extensions that are deprecated. It doesn’t make sense for us to implement APIs that are already deprecated and are going to be removed. In these cases, developers will need to update their extensions to use the new APIs. When they do, they will work in the supported browsers.

Some examples are in the extension API, which are mostly replaced by the runtime API. For example, use runtime.sendMessage instead of extension.sendMessage; use runtime.onMessage instead of extension.onRequest and so on.

W3C

WebExtensions APIs will never completely mirror Chrome’s extension APIs, for the reasons outlined above. We are, however, already reaching a point where the majority of Chrome extensions work in Firefox.

To make writing extensions for multiple browsers as easy as possible, Mozilla has been participating in a W3C community group for extension compatibility. Also participating in that group are representatives of Opera and Microsoft. We’ll be sending a representative to TPAC this month to take part in discussions about this community group so that we can work towards a common browser standard for browser extensions.

Update: please check the MDN page on incompatibilities.

Categorieën: Mozilla-nl planet

Armen Zambrano: Increasing test coverage

Mozilla planet - ti, 13/09/2016 - 23:27
Last quarter I spent some time increasing mozci's test coverage. Here are some notes I took to help me remember in the future how to do it.

Here's some of what I did:
  • Read Python's page about increasing test coverage
    • I wanted to learn what core Python recommends
    • Tthey recommend is using coverage.py
  • Quick start with coverage.py
    • "coverage run --source=mozci -m py.test test" to gather data
    • "coverage html" to generate an html report
    • "/path/to/firefox firefox htmlcov/index.html" to see the report
  • NOTE: We have coverage reports from automation in coveralls.io
    • If you find code that needs to be ignored, read this.
      • Use "# pragma: no cover" in specific lines
      • You can also create rules of exclusion
    • Once you get closer to 100% you might want to consider to increase branch coverage instead of line coverage
    • Once you pick a module to increase coverage
      • Keep making changes until you run "coverage run" and "coverage html".
      • Reload the html page to see the new results
      After some work on this, I realized that my preferred place to improve tests is focusing on the simplest unit tests. I say this since integration tests do require proper work and thinking how to properly test them rather than *just* increasing coverage for the sake of it.
      Creative Commons License
      This work by Zambrano Gasparnian, Armen is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 Unported License.
      Categorieën: Mozilla-nl planet

      Mozilla: overheden moeten met techbedrijven samenwerken - Security.nl

      Nieuws verzameld via Google - ti, 13/09/2016 - 17:08

      Mozilla: overheden moeten met techbedrijven samenwerken
      Security.nl
      Mozilla richt zich vooral op overheden die encryptie proberen te verzwakken. "Maar encryptie is niet optioneel en het aanbrengen van backdoors voor overheden, zelfs voor onderzoek, brengt de veiligheid van alle internetgebruikers in gevaar", zegt ...

      Categorieën: Mozilla-nl planet

      Mozilla: overheden moeten met techbedrijven samenwerken - Security.nl

      Nieuws verzameld via Google - ti, 13/09/2016 - 17:01

      Mozilla: overheden moeten met techbedrijven samenwerken
      Security.nl
      Mozilla richt zich vooral op overheden die encryptie proberen te verzwakken. "Maar encryptie is niet optioneel en het aanbrengen van backdoors voor overheden, zelfs voor onderzoek, brengt de veiligheid van alle internetgebruikers in gevaar", zegt ...

      Categorieën: Mozilla-nl planet

      The Mozilla Blog: Cybersecurity is a Shared Responsibility

      Mozilla planet - ti, 13/09/2016 - 16:23

      There have been far too many “incidents” recently that demonstrate the Internet is not as secure as it needs to be. Just in the past few weeks, we’ve seen countless headlines about online security breaches. From the alleged hack of the National Security Agency’s “cyberweapons” to the hack of the Democratic National Committee emails, and even recent iPhone security vulnerabilities, these stories reinforce how crucial it is to focus on security.

      Internet security is like a long chain and each link needs to be tested and re-tested to ensure its strength. When the chain is broken, bad things happen: a website that holds user credentials (e.g., email addresses and passwords) is compromised because of weak security; user credentials are stolen; and, those stolen credentials are then used to attack other websites to gain access to even more valuable information about the user.

      One weak link can break the chain of security and put Internet users at risk. The chain only remains strong if technology companies, governments, and users work together to keep the Internet as safe as it can be.

      Technology companies must focus on security.

      Technology companies need to develop proactive, pro-user cybersecurity technology solutions.

      We must invest in creating a secure platform. That means supporting things like adopting and standardizing secure protocols, building features that improve security, and empowering users with education and better tools for their security.

      At Mozilla, we have security features like phishing and malware protection built into Firefox. We started one of the first Bug Bounty programs in 2004 because we want to be informed about any vulnerabilities found in our software so we can fix them quickly. We also support the security of the broader open source ecosystem (not just Mozilla developed products). We launched the Secure Open Source (SOS) Fund as part of the Mozilla Open Source Support program to support security audits and the development of patches for widely used open source technologies.

      Still, there is always room for improvement. The recent headlines show that the threat to user safety online is real, and it’s increasing. We can all do better, and do more.

      Governments must work with technology companies.  

      Cybersecurity is a shared responsibility and governments need to do their part. Governments need to help by supporting security solutions that no individual company can tackle, instead of advancing policies that just create weak links in the chain.

      Encryption, something we rely on to keep people’s information secure online everyday, is under attack by governments because of concerns that it inadvertently protects the bad guys. Some governments have proposed actions that weaken encryption, like in the case between Apple and the FBI earlier this year. But encryption is not optional – and creating backdoors for governments, even for investigations, compromises the security of all Internet users.

      The Obama Administration just appointed the first Federal Chief Information Security officer as part of the Cybersecurity National Action Plan. I’m looking forward to seeing how this role and other efforts underway can help government and technology companies work better together, especially in the area of security vulnerabilities. Right now, there’s not a clear process for how governments disclose security vulnerabilities they discover to affected companies.

      While lawful hacking by a government might offer a way to catch the bad guys, stockpiling vulnerabilities for long periods of time can further weaken that security chain. For example, the recent alleged attack and auction of the NSA’s “cyberweapons” resulted in the public release of code, files, and “zero day” vulnerabilities that gave companies like Cisco and Fortinet just that- zero days to develop fixes before they were possibly exploited by hackers. There aren’t transparent and accountable policies in place that ensure the government is handling vulnerabilities appropriately and disclosing them to affected companies. We need to make this a priority to protect user security online.

      Users can take easy and simple steps to strengthen the security chain.   

      Governments and companies can’t do this without you. Users should always update their software to benefit from new security features and fixes, create strong passwords to guard your private information, and use available resources to become educated digital citizens. These steps don’t just protect people who care about their own security, they help create a more secure system and go a long way in making it harder to break the chain.

      Working together is the only way to protect the security of the Internet for the billions of people online. We’re dedicated to this as part of our mission and we will continue our work to advance these issues.

      Categorieën: Mozilla-nl planet

      Cybersecurity is a Shared Responsibility

      Mozilla Blog - ti, 13/09/2016 - 16:23

      There have been far too many “incidents” recently that demonstrate the Internet is not as secure as it needs to be. Just in the past few weeks, we’ve seen countless headlines about online security breaches. From the alleged hack of the National Security Agency’s “cyberweapons” to the hack of the Democratic National Committee emails, and even recent iPhone security vulnerabilities, these stories reinforce how crucial it is to focus on security.

      Internet security is like a long chain and each link needs to be tested and re-tested to ensure its strength. When the chain is broken, bad things happen: a website that holds user credentials (e.g., email addresses and passwords) is compromised because of weak security; user credentials are stolen; and, those stolen credentials are then used to attack other websites to gain access to even more valuable information about the user.

      One weak link can break the chain of security and put Internet users at risk. The chain only remains strong if technology companies, governments, and users work together to keep the Internet as safe as it can be.

      Technology companies must focus on security.

      Technology companies need to develop proactive, pro-user cybersecurity technology solutions.

      We must invest in creating a secure platform. That means supporting things like adopting and standardizing secure protocols, building features that improve security, and empowering users with education and better tools for their security.

      At Mozilla, we have security features like phishing and malware protection built into Firefox. We started one of the first Bug Bounty programs in 2004 because we want to be informed about any vulnerabilities found in our software so we can fix them quickly. We also support the security of the broader open source ecosystem (not just Mozilla developed products). We launched the Secure Open Source (SOS) Fund as part of the Mozilla Open Source Support program to support security audits and the development of patches for widely used open source technologies.

      Still, there is always room for improvement. The recent headlines show that the threat to user safety online is real, and it’s increasing. We can all do better, and do more.

      Governments must work with technology companies.  

      Cybersecurity is a shared responsibility and governments need to do their part. Governments need to help by supporting security solutions that no individual company can tackle, instead of advancing policies that just create weak links in the chain.

      Encryption, something we rely on to keep people’s information secure online everyday, is under attack by governments because of concerns that it inadvertently protects the bad guys. Some governments have proposed actions that weaken encryption, like in the case between Apple and the FBI earlier this year. But encryption is not optional – and creating backdoors for governments, even for investigations, compromises the security of all Internet users.

      The Obama Administration just appointed the first Federal Chief Information Security officer as part of the Cybersecurity National Action Plan. I’m looking forward to seeing how this role and other efforts underway can help government and technology companies work better together, especially in the area of security vulnerabilities. Right now, there’s not a clear process for how governments disclose security vulnerabilities they discover to affected companies.

      While lawful hacking by a government might offer a way to catch the bad guys, stockpiling vulnerabilities for long periods of time can further weaken that security chain. For example, the recent alleged attack and auction of the NSA’s “cyberweapons” resulted in the public release of code, files, and “zero day” vulnerabilities that gave companies like Cisco and Fortinet just that- zero days to develop fixes before they were possibly exploited by hackers. There aren’t transparent and accountable policies in place that ensure the government is handling vulnerabilities appropriately and disclosing them to affected companies. We need to make this a priority to protect user security online.

      Users can take easy and simple steps to strengthen the security chain.   

      Governments and companies can’t do this without you. Users should always update their software to benefit from new security features and fixes, create strong passwords to guard your private information, and use available resources to become educated digital citizens. These steps don’t just protect people who care about their own security, they help create a more secure system and go a long way in making it harder to break the chain.

      Working together is the only way to protect the security of the Internet for the billions of people online. We’re dedicated to this as part of our mission and we will continue our work to advance these issues.

      Categorieën: Mozilla-nl planet

      Software-update: Pale Moon 26.4.1 - Tweakers

      Nieuws verzameld via Google - ti, 13/09/2016 - 13:37

      Tweakers

      Software-update: Pale Moon 26.4.1
      Tweakers
      Pale Moon logo (75 pix) Versie 26.4.0 van Pale Moon is uitgekomen. Deze webbrowser maakt gebruik van de broncode van Mozilla Firefox, maar is geoptimaliseerd voor moderne hardware. De Windows-versie van Mozilla Firefox wordt namelijk ontwikkeld ...

      Categorieën: Mozilla-nl planet

      Mozilla Release Management Team: Firefox 49 delayed

      Mozilla planet - ti, 13/09/2016 - 12:57

      The original 2016 Firefox release schedule had the release of Firefox 49 shipping on September 13, 2016. During our release qualification period for Firefox 49, we discovered a bug in the release that causes some desktop and Android users to see a slow script dialog more often than we deem acceptable. In order to allow time to address this issue, we have rescheduled the release of Firefox 49 to September 20, 2016.

      In order to accommodate this change, we will shorten the following development cycle by a week. No other scheduled release dates are impacted by this change.

      In parallel, Firefox ESR 45.4.0 is also delayed by a week.

      Categorieën: Mozilla-nl planet

      Tantek Çelik: #XOXOfest 2016: Independent Creatives Inspired, Shared, Connected

      Mozilla planet - ti, 13/09/2016 - 07:20

      Inspired, once again. This was the fifth XOXO Conference & Festival (my fourth, having missed last year).

      There’s too much about XOXO 2016 to fit into one "XOXO 2016" blog post. So much that there’s no way I’d finish if I tried.

      Outdoors on the last day of XOXO Festival 2016

      4-ish days of:

      Independent creatives giving moving, inspiring, vulnerable talks, showing their films with subsequent Q&A, performing live podcast shows (with audience participation!).

      Games, board games, video games, VR demos. And then everything person-to-person interactive. All the running into friends from past XOXOs (or dConstructs, or classic SXSWi), meetups putting IRL faces to Slack aliases.

      Friends connecting friends, making new friends, instantly bonding over particular creative passions, Slack channel inside jokes, rare future optimists, or morning rooftop yoga under a cloud-spotted blue sky.

      The walks between SE Portland venues. The wildly varying daily temperatures, sunny days hotter than predicted highs, cool windy nights colder than predicted lows. The attempts to be kind and minimally intrusive to local homeless.

      More conversations about challenging and vulnerable topics than small talk. Relating on shared losses. Tears. Hugs, lots of hugs.

      Something different happens when you put that many independent creatives in the same place, and curate & iterate for five years. New connections, between people, between ideas, the energy and exhaustion from both. A sense of a safer place.

      I have so many learnings from all the above, and emergent patterns of which swimming in my head that I’m having trouble sifting and untangling. Strengths of creative partners and partnerships. Uncountable struggles. The disconnects between attention, popularity, money. The hope, support, and understanding instead of judgment.

      I'm hoping to write at least a few single-ish topic posts just to get something(s) posted before the energies fade and memories start to blur.

      Categorieën: Mozilla-nl planet

      This Week In Rust: This Week in Rust 147

      Mozilla planet - ti, 13/09/2016 - 06:00

      Hello and welcome to another issue of This Week in Rust! Rust is a systems language pursuing the trifecta: safety, concurrency, and speed. This is a weekly summary of its progress and community. Want something mentioned? Tweet us at @ThisWeekInRust or send us a pull request. Want to get involved? We love contributions.

      This Week in Rust is openly developed on GitHub. If you find any errors in this week's issue, please submit a PR.

      Updates from Rust Community News & Blog Posts New Crates & Project Updates Crate of the Week

      This week's crate of the week is tokio, a high-level asynchronous IO library based on futures. Thanks to notriddle for the suggestion.

      Submit your suggestions and votes for next week!

      Call for Participation

      Always wanted to contribute to open-source projects but didn't know where to start? Every week we highlight some tasks from the Rust community for you to pick and get started!

      Some of these tasks may also have mentors available, visit the task page for more information.

      If you are a Rust project owner and are looking for contributors, please submit tasks here.

      Updates from Rust Core

      84 pull requests were merged in the last two weeks.

      New Contributors
      • Cobrand
      • Jake Goldsborough
      • John Firebaugh
      • Justin LeFebvre
      • Kylo Ginsberg
      • Nicholas Nethercote
      • orbea
      • Richard Janis Goldschmidt
      • Ulrich Weigand
      Approved RFCs

      Changes to Rust follow the Rust RFC (request for comments) process. These are the RFCs that were approved for implementation this week:

      Final Comment Period

      Every week the team announces the 'final comment period' for RFCs and key PRs which are reaching a decision. Express your opinions now. This week's FCPs are:

      New RFCs Upcoming Events

      If you are running a Rust event please add it to the calendar to get it mentioned here. Email Erick Tryzelaar or Brian Anderson for access.

      fn work(on: RustProject) -> Money

      Tweet us at @ThisWeekInRust to get your job offers listed here!

      Quote of the Week

      No quote was selected for QotW.

      Submit your quotes for next week!

      This Week in Rust is edited by: nasa42, llogiq, and brson.

      Categorieën: Mozilla-nl planet

      Cameron Kaiser: Sierraspoof is here

      Mozilla planet - ti, 13/09/2016 - 01:41
      Sierraspoof is here for TenFourFox 45.4 (which is now live). And it's even a week early.
      Categorieën: Mozilla-nl planet

      Firefox 50: Mozilla behebt Twitter-Cookie-Problem - soeren-hentzschel.at

      Nieuws verzameld via Google - mo, 12/09/2016 - 23:44

      Firefox 50: Mozilla behebt Twitter-Cookie-Problem
      soeren-hentzschel.at
      Mozilla hat in Firefox 50 ein nerviges Problem behoben, welches dafür sorgte, dass man auf Twitter häufig nach Browser-Neustarts abgemeldet war. Firefox-Nutzer mussten sich häufig nach jedem Browser-Neustart neu auf Twitter anmelden. Das Problem ist ...

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

      Mozilla Open Design Blog: The Conversation About Design Has Changed

      Mozilla planet - mo, 12/09/2016 - 22:30

      Like many of us in the design community, I’ve followed along in recent years as seemingly countless companies have undertaken the exciting and often fraught challenge of redesigning their visual identities. A quick glance at the Before/After section of Brand New, the well-known design blog dedicated to the critique of such things, shows 216 projects chronicled year-to-date.

      Some redesigns have been well received like Google’s, while others have drawn an enormous amount of criticism from both the design community and the general public, such as Uber’s. These are interesting times for design as the critique of our work has moved from something those of us in the trade might discuss with colleagues over dinner, to something that anyone with an @handle and opinion can weigh in publicly over social media. On several occasions, this public discourse has taken such an extreme tone that Andrew Beck has described it as design crit as bloodsport.

      Designing in the Open

      Earlier this year I began consulting with non-profit Mozilla to tee up a logo redesign initiative. During that time, Mozilla’s Creative Director Tim Murray proposed the idea of designing in the open. His vision was to build off of the open source principles that are bedrock to Mozilla by applying them to the end-to-end process of an identity redesign. The idea was to be as transparent as possible with the process, the initial concepts, the refinement and the outcome, and to have an open, public dialog with many people as possible along the way. He would engage the typical stakeholders one would expect, such as Mozilla’s senior leadership, as well as Mozilla’s 10,000+ strong volunteer community. But Tim also wanted to reach beyond Mozillians. He invited not only the design community into the discussion, but anyone for whom the Mozilla mission – to keep the internet healthy, open and safe for all – resonates.

      Initially, his proposal made me slightly uncomfortable. I felt a mix of caution and curiosity and I had to ask myself: why?

      A Mix of Caution and Curiosity

      I was concerned that opening up earlier stages of the design process to that kind of public commentary (think stakeholders at scale) would negatively affect the work. And my hesitancy was also rooted in a lack of understanding as to what Mozilla was asking from the design community. I questioned how we as designers could meaningfully participate in a public dialog about design work. After all, by submitting a professional opinion on everything from initial thinking, to design exploration through concept and execution, weren’t we engaging in a kind of spec work?

      As for my curiosity, it was piqued by the opportunity to re-examine the methodology by which design outcomes are generated. Would a larger and more diverse conversation upfront in fact lead to a better outcome? And as design crit has gone mainstream and instantaneous thanks to social media, how can we show up in public conversations about design deliverables without compromising our point of view against spec work?

      Where Things Stand Now

      The identity redesign is now well underway. johnson banks was selected as the agency partner and Mozilla has indeed undertaken a fully transparent, moderated, and public design process. The first round creative concepts were shared a week ago and met with hundreds if not thousands of responses and a full news cycle in the design press.

      While the end result of this unconventional approach remains uncertain, we do know that Tim and team created a process that is true to Mozilla’s open source beliefs and the manifesto that guides the company’s conduct. And we know they are willing to withstand the outcome even if it rises to the level of bloodsport. For that, they should be commended.

      As for the questions raised about spec work and the Mozilla initiative, if you’re aligned with Mozilla’s mission and choose to provide critique then your participation as a practicing professional is an act of volunteerism. In their words…

      “What we’re seeking is input on work that’s in process. We welcome your feedback in a form that suits you best, be it words, napkin sketches, or Morse Code. We simply want to incorporate as many perspectives and voices into this open design process as possible. We don’t take any single contribution lightly. We hope you’ll agree that by helping Mozilla communicate its purpose better through design, you’ll be helping improve the future Internet.”

      As for the larger questions raised by increasing public dialog about design, it’s up to each of us personally to determine how we participate and when. But all industries experience change, design is no exception. By at least trying to understand Mozilla’s approach to this project and how it fits within a broader narrative, designers can use this as an opportunity to challenge long-held methodologies, and perhaps pave the way for new ones.

      aigasf_logo

      Republished with permission from AIGA SF / The Professional Association for Design

       

      Photo credit: Wikimedia Commons “And Phoebus’ Tresses Stream Athwart the Glade”

      Categorieën: Mozilla-nl planet

      Air Mozilla: Mozilla Weekly Project Meeting, 12 Sep 2016

      Mozilla planet - mo, 12/09/2016 - 20:00

      Mozilla Weekly Project Meeting The Monday Project Meeting

      Categorieën: Mozilla-nl planet

      Luis Villa: Copyleft and data: database law as (poor) platform

      Mozilla planet - mo, 12/09/2016 - 19:22

      tl;dr: Databases are a very poor fit for any licensing scheme, like copyleft, that (1) is intended to encourage use by the entire world but also (2) wants to place requirements on that use. This is because of broken legal systems and the way data is used. Projects considering copyleft, or even mere attribution, for data, should consider other approaches instead.

      Hollerith Census Machine Dials, by Marcin Wichary, under CC BY 2.0
      The original database: Hollerith Census Machine Dials, by Marcin Wichary, under CC BY 2.0.

      I’ve been a user of copyleft/share-alike licenses for a long time, and even helped draft several of them, but I’ve come around to the point of view that copyleft is a poor fit for data. Unfortunately, I’ve been explaining this a lot lately, so I want to explain why in writing. This first post will focus on how the legal system around databases is broken. Later posts will focus on how databases are hard to license, and what we might do about it.

      FOSS licensing, and particularly copyleft, relies on legal features database rights lack

      Defenders of copyleft often have to point out that copyleft isn’t necessarily anti-copyright, because copyleft depends on copyright. This is true, of course, but the more I think about databases and open licensing, the more I think “copyleft depends on copyright” almost understates the case – global copyleft depends not just on “copyright”, but on very specific features of the international copyright system which database law lacks.

      To put it in software terms, the underlying legal platform lacks the features necessary to reliably implement copyleft.

      Consider some differences between the copyright system and database law:

      • Maturity: Copyright has had 100 or so years as an international system to work out kinks like “what is a work” or “how do joint authors share rights?” Even software copyright law has existed for about 40 years. In contrast, database law in practice has existed for less  than 20 years, pretty much all of that in Europe, and I can count all the high court rulings on it on my fingers and toes. So key terms, like “substantial”, are pretty hard to define-courts and legislatures simply haven’t defined, or refined, the key concepts. This makes it very hard to write a general-purpose public license whose outcomes are predictable.

      • Stability: Related to the previous point, copyright tends to change incrementally, as long-standing concepts are slowly adapted to new circumstances. (The gradual broadening of fair use in the Google era is a good example of this.) In contrast, since there are so few decisions, basically every decision about database law leads to upheaval. Open Source licenses tend to have a shelf-life of about ten years; good luck writing a database license that means the same thing in ten years as it does today!

      • Global nature: Want to share copyrighted works with the entire world? Copyright (through the Berne Convention) has you covered. Want to share a database? Well, you can easily give it away to the whole world (probably!), but want to reliably put any conditions on that sharing? Good luck! You’ve now got to write a single contract that is enforceable in every jurisdiction, plus a license that works in the EU, Japan, South Korea, and Mexico. As an example again, “substantial” – used in both ODbL and CC 4.0 – is a term from the EU’s Database Directive, so good luck figuring out what it means in a contract in the US or within the context of Japan’s database law.

      • Default rights: Eben Moglen has often pointed out that anyone who attacks the GPL is at a disadvantage, because if they somehow show that the license is legally invalid, then they get copyright’s “default”: which is to say, they don’t get anything. So they are forced to fight about the specific terms, rather than the validity of the license as a whole. In contrast, in much of the world (and certainly in the US), if you show that a database license is legally invalid, then you get database’s default: which is to say, you get everything. So someone who doesn’t want to follow the copyleft has very, very strong incentives to demolish your license altogether. (Unless, of course, the entire system shifts from underneath you to create a stronger default – like it may have in the EU with the Ryanair case.)

      With all these differences, what starts off as hard (“write a general-purpose, public-facing license that requires sharing”) becomes insanely difficult in the database context. Key goals of a general-purpose, public license – global, predictable, reliable – are very hard to do.

      In  upcoming posts, I’ll try to explain why, even if it were possible to write such a license from a legal perspective, it might not be a good idea because of how databases are used.

      Categorieën: Mozilla-nl planet

      Jared Wein: Rethinking themes in Firefox

      Mozilla planet - mo, 12/09/2016 - 17:30

      04b11051730953b648e852e9f9a91623A couple of weeks ago Mike de Boer and I started work on a project to rethink themes in Firefox. At present day, Firefox offers two ways for users to theme their browser: XUL themes (also known as “complete themes”) and lightweight themes (also known as “themes”). We want to create something that gives more power than lightweight themes while also being easier to create and maintain than XUL themes.

      Last week we published a survey asking theme authors and users what they like about themes and what they would change. To date, we have received over 250 detailed responses. We will be keeping the survey open and monitoring it for anybody that has not had a chance to reply yet. Here’s what we’ve learned:

      Have you made a lightweight theme before?
      21.8% yes

      What do you like about lightweight themes?
      A strong majority (70%) of lightweight theme authors said that they liked how lightweight themes were simple and easy to make. The next group, at 6%, said that they liked how lightweight themes always remain compatible after Firefox updates. 4% of users also liked that they were easy to install with no restart required. A couple people complained that they were too simple and there was too much spam in the themes section of the Add-ons website.

      What do you feel was difficult to do or missing from lightweight themes?
      A little less than (42%) half of responses would have liked to do more than just a couple of images with lightweight themes. They would like to apply background images to other parts of the browser, change icons, buttons, and the size-of and location of browser components. The next group of responses (10%) wanted more support for scaling, repetition, animation, and position of background images. Improved documentation (8%) and a lack of a development environment such as an in-browser editor followed (6%). The last two groups of responses wanted the ability for themes to change based on external factors (2%) and separate images for the tabs and tab toolbar (2%).

      Have you made a XUL theme before?
      23% yes

      What do you like about XUL themes?
      A strong majority of the respondents agreed firmly with 71.2% that XUL themes are awesome in allowing to touch and customize all the things. The second largest group of respondents seek out XUL themes because they offer more nuts and bolts to tinker with than lightweight themes at 11.5%, while the familiarity with the CSS styling language is the main reason to like them for 7.7% of the respondents. Two other notable groups are people who like dark themes, which are apparently only really available as XUL themes, and ones who feel that XUL themes are the easiest thing to make on this planet, each at 3.9%.

      What do you feel was difficult to do or missing from XUL themes?
      The largest amount of responses (29.8%) said that it is a real pain to keep these themes up-to-date and working, with the current fast release cycle of Firefox and the fast pace of development. 28.1% of the respondents rightfully complained that they need to use exotic, undocumented technologies and unknown CSS selectors in order to create a working XUL theme. Whilst 15.8% claimed there is nothing wrong with XUL themes and we should keep it as-is, another 12.3% is sad about the lack of documentation or any kind of manual to get started. Packaging and delivery of XUL themes is not considered optimal by 10.5% of respondents and that ultimately very few of these themes can be configured after installation (3.5%).

      Why do you install themes?
      About half (47%) of the survey responses want to personalize Firefox. These people said that they want to make Firefox “their own” and have fun showing it off. They enjoy having full control over the user interface through XUL themes and like the ability to set arbitrary CSS. The next set of responses (16%) asked for a “dark” Firefox, making it easier on the eyes at night. These responses were generally focused on the toolbars and menus of the browser being dark. At 12% of responses was closer integration with the operating system followed closely by 11% of responses saying that they felt the default theme was boring and bland. The last category of responses that received multiple votes was to allow themes to undo recent changes to the user interface, as an attempt to keep things the same that they’ve been for the past months/years.

      What capabilities would you like themes to have?
      More than half (56%) of the survey responses want full control over the browser UI. They would like to move and hide items, change tab shapes, replace icons, context menus, scrollbars, and more. Following this large group, we had close to 5% of respondents who wanted to simply change basic colors and another group, also close to 5%, that wanted to make it easy for users to make simple tweaks to their browser or an installed theme through a built-in menu or tool. Native OS integration, such as using platform-specific icons and scrollbars, followed closely at 3%. Also at 3% of responses were requests from users who require larger icons and improved readability of the browser’s user interface for improved accessibility. Not far behind, and ironically next in the order of responses, were requests for a smaller browser UI (2%). These users generally want to maximize the amount of screen space that web pages can use. Both “dark themes” and “themes not breaking with future releases” got 2% of responses. In our last group of responses at or above 1% was themes that could change based on external factors (time of day, season, month, web color, or a very slow animation), restartless and easy to trial, ability to apply multiple themes to create a “mash-up”, and to lighten the tab bar.

      What parts of Firefox are most important to you to be able to change the appearance of? Why?
      Almost 20% of the respondents can not make a choice between the parts of Firefox and thus want to customize the app in its entirety. Following closely with 16% is the group of respondents that think the tabs area is the most important part for themes, while half that number choose toolbars, (toolbar)button icons and the area above the tabs, including the window decoration and window controls. Interestingly, the wish to be able to theme in-content pages is as strong as that of the Awesomebar and respective navigation controls: 6.8%. Changing the colors, palette and fonts used for the UI are the other most notable choices from the community of respondents at 6.4% and 4%, respectively.

      Are there theme-related features from other browser or apps that you would like to see incorporated into Firefox?
      An overwhelming majority of the respondents insist that we don’t need to change a thing and that other apps don’t offer grand alternatives at 36.5%, or simply can’t think of any. The Vivaldi browser came up in our preliminary research and also takes a prominent position as device of inspiration for theming features at 11.2%. A dark theme like other apps already offer in their package (5.9%), applying tints of color on SVG icons and background masks (2.9%) on UI elements – most notably the titlebar – and take Opera’s about:newtab theming capabilities (2.4%). A notable response from 2.9% of respondents was to introduce a live theme editor in Firefox with sharing capabilities, so that theme creators can take existing themes to tweak to their own liking and (re-)share with others.

      The grouping of the results and more details can be found in our meeting notes. Our full archive of meeting notes is also publicly viewable.


      Tagged: firefox, planet-mozilla, themes
      Categorieën: Mozilla-nl planet

      Mozilla Open Innovation Team: Introducing the Open Innovation Toolkit

      Mozilla planet - mo, 12/09/2016 - 17:26

      Innovation is part of our DNA at Mozilla. It’s not just about making products that support the open web, but how we make those products — with a transparent and participatory approach.

      There’s a paradox in open innovation. On one hand, the diversity of an open community demonstrably increases the quality of solutions. On the other hand, using best practices like human-centered design across a distributed team can be hard work. But in order to maintain high quality of experience, solve real user problems and ultimately create great products that people want, it must be done.

      To help address this, we’ve been developing the Open Innovation Toolkit.

      Open Innovation Toolkit Site

      It is a community-sourced set of best practices and methods that incorporate human-centered design into a open source product development process. It consists of a collection of easy-to-use, self-serve techniques that are gathered from industry best practices. They’re not ‘new to the world’ but together they create a knowledge bank of methods that we at Mozilla have found useful and that build on some of best thinking in the industry.

      We want to equip everyone in the Mozilla community — and beyond — with a set of useful and proven tools and a common vocabulary to incorporate human-centered design into their product development process.

      We’ve learned and been inspired by other similar efforts, such as the Nesta’s DIY toolkit for social innovation, which has successfully been used by many global organisations from Women in Global Democracy to Kent city planning council. The servicedesigntools.org site (which started out as a masters project) became a great venue for sharing service design projects.

      An overview of the current methods gathered from open source industry experts.

      More than anything, this toolkit is an invitation to everyone in open source product development, from developers to advocates, to use it, play with it and to give us feedback on use cases we might add.

      Check out our first examples at https://toolkit.mozilla.org and contribute your ideas!

      Introducing the Open Innovation Toolkit was originally published in Mozilla Open Innovation on Medium, where people are continuing the conversation by highlighting and responding to this story.

       

      Read the responses to this story on Medium.

      Categorieën: Mozilla-nl planet

      Air Mozilla: Meeting OpenData France 1

      Mozilla planet - mo, 12/09/2016 - 14:00

      Meeting OpenData France 1 Meeting OpenData France.

      Categorieën: Mozilla-nl planet

      La sortie de Mozilla 49 repoussée suite à deux bugs - Le Soir

      Nieuws verzameld via Google - mo, 12/09/2016 - 11:49

      Le Soir

      La sortie de Mozilla 49 repoussée suite à deux bugs
      Le Soir
      Cependant, la fondation Mozilla a décidé d'accélérer le processus et de passer de 6 à 2 semaines. C'est ainsi que la date du 13 septembre fut avancée pour Firefox 49. Cependant, deux bugs obligent la société à revoir ses plans et à différer la sortie ...
      Mozilla : deux bugs repoussent la sortie Firefox 49Clubic
      Firefox 49 : deux bugs repoussent sa mise en ligneZDNet France
      Firefox 49, le lancement est retardé en raison de deux bugs, explicationsGinjFo
      Next INpact
      alle 6 nieuwsartikelen »
      Categorieën: Mozilla-nl planet

      Pages