Europas Smartphone-Markt schrumpft, Nokia und Xiaomi in den Top 5

heise online Newsticker - 14. Mai 2018 - 17:00
Gegen den allgemeinen Trend hinterlassen die Newcomer Nokia und Xiaomi ihre Duftmarke in den Statistiken der Marktforscher. Hersteller HMD Global kann auf einen richtig guten Start zurückblicken.

Bitkom-Umfrage: Deutsche wollen mehr Breitband, aber nicht mehr bezahlen

heise online Newsticker - 14. Mai 2018 - 17:00
In vielen deutschen Haushalten hat sich der Ausbau des Breitbandnetzes bereits bemerkbar gemacht, zusätzlich wünschen sich Internetnutzer aber weitere Verbesserungen ohne zusätzliche Kosten.

Drupal Association blog: Progress and Next Steps for Governance of the Drupal Community

Planet Drupal - 14. Mai 2018 - 16:39

One of the things I love the most about my new role as Community Liaison at the Drupal Association is being able to facilitate discussion amongst all the different parts of our Drupal Community. I have extraordinary privilege of access to bring people together and help work through difficult problems.

The governance of the Drupal project has evolved along with the project itself for the last 17 years. I’m determined in 2018 to help facilitate the next steps in evolving the governance for our growing, active community.

2017 - A Year of Listening

Since DrupalCon Baltimore, the Drupal Community has:

  • Held a number of in-person consultations at DrupalCon Baltimore around the general subject of project governance

  • Ran a series of online video conversations, facilitated by the Drupal Association

  • Ran a series of text-based online conversations, facilitated by members of our community across a number of time zones

  • Gathered for a Governance Round Table at DrupalCon Nashville.

This has all led to a significant amount of feedback.

Whilst I highly recommend reading the original blog post about online governance feedback sessions for a full analysis, there was clearly a need for better clarity, communications, distributing leadership, and evolving governance.

2018 - A Year of Taking Action

There are many things happening in 2018 but I want to concentrate for now on two important activities; how we continue to develop our Values and how we can continue to develop Governance of our community.

So, why am I separating “Values” and “Governance”, surely they are connected? Well, they are connected, but they are also quite different and it is clear we need to define the difference within our community.

In the context of the Drupal Community:

  • “Values” describe the culture and behaviors expected of members of the Drupal community to uphold.

  • “Governance” describes the processes and structure of interaction and decision-making that help deliver the Project’s purpose whilst upholding the Values we agree to work by.

Values What’s happened?

Quoting Dries:

Over the course of the last five months, I have tried to capture our fundamental Values & Principles. Based on more than seventeen years of leading and growing the Drupal project, I tried to articulate what I know are "fundamental truths": the culture and behaviors members of our community uphold, how we optimize technical and non-technical decision making, and the attributes shared by successful contributors and leaders in the Drupal project. 

Capturing our Values & Principles as accurately as I could was challenging work. I spent many hours writing, rewriting, and discarding them, and I consulted numerous people in the process. After a lot of consideration, I ended up with five value statements, supported by eleven detailed principles.”

The first draft of the Values & Principles was announced to the community at DrupalCon Nashville.

What’s next?

Now that we have the first release of the Values & Principles, we need a process to assist and advise Dries as he updates the Values & Principles. After hearing community feedback, Dries will charter a committee to serve this role. A forthcoming blog post will describe the committee and its charter in more detail.

Community Governance What’s happened?

At DrupalCon Nashville, many useful discussions happened on governance structure and processes.

  • A Drupal Association Board Meeting, with invited community members, met to talk with existing governance groups to find out what is working and not working. We realized that governance of the Drupal Community is large and it is difficult to understand all of the parts. We began to see here a possibility for further action.

  • The Community Conversation, “Governance Retrospective”, helped us to see that improving communications throughout the community is hugely important.

  • The Round Table Discussion, around community governance, brought together Dries, staff of the Drupal Association and Drupal Association Board, representatives of many of our current community working groups, representatives of other interested groups in the community and other community members. This group looked at both Values & Principles but also looked into how we are currently governed as a community and how can improve that.

All these things lead to one of the very best things of the DrupalCon experience; the “hallway track”. More and more throughout DrupalCon Nashville, ideas were formed and people stepped forward to communicate with each other, about how we can improve our governance. This happens all the time when we discuss the code of Drupal; I’m very excited to see it happening in other aspects of our project, too.

What’s next?

A structured approach is needed to ensure all in our community understand how decisions are being made and could have input. Speaking with a number of those involved in many of the discussions above, a consensus developed that we can start putting something into action to address the issues raised. Dries, as Project Lead, has agreed that:

  • A small Governance Task Force would be created for a fixed period of time to work on and propose the following:

    • What groups form the governance of the Drupal community right now?

    • What changes could be made to governance of the Drupal community?

    • How we could improve communication and issue escalation between groups in the community?

  • Task Force membership would be made up of a small group consisting of:

    • Adam Bergstein

    • David Hernandez

    • Megan Sanicki

    • Rachel Lawson

  • This Task Force would discuss whether or not it is beneficial to form a more permanent Governance Working Group, to handle escalated issues from other Working Groups that can be handled without escalation to the Project Lead.

  • This Task Force will propose a structure, processes needed to run this new structure, charters, etc. by end of July 2018 to the Project Lead for approval.

The Governance Task Force begins work immediately. The Charter under which we will work is attached.

I will help to facilitate reporting back regularly as we progress. I look forward to 2018 showing progress on both of these initiatives.

I am, as always, very happy to chat through things - please say hello!

File attachments:  Governance Task Force Charter.pdf

Motorola Moto G6 im Test: Preis-Leistungs-Kracher

heise online Newsticker - 14. Mai 2018 - 16:30
Das Motorola Moto G 6 lockt mit guter Ausstattung, solider Verarbeitung und einem Preis von 249 Euro. Wie gut ist das Mittelklasse-Smartphone?

Windows 10: Das Cloud Clipboard kommt!

heise online Newsticker - 14. Mai 2018 - 16:30
Mit der neuesten Insider-Testversion von Windows 10 liefert Microsoft die angekündigte verbesserte Zwischenablage für das Betriebssystem aus. Die Daten landen jetzt in der Cloud.

Signal für Mac: Update soll Schwachstelle ausräumen

heise online Newsticker - 14. Mai 2018 - 15:30
Der neue Mac-Client des Krypto-Messengers stellt den Inhalt verschwindender Nachrichten nicht länger in der Mitteilungszentrale dar, um deren ungeschützte Protokollierung in einer Datenbank des Betriebssystems zu verhindern.

Nutanix .NEXT: Kostenkontrolle für die hybride Cloud

heise online Newsticker - 14. Mai 2018 - 15:00
Auf seiner vierten US-amerikanischen Hausmesse .NEXT in New Orleans konnte Nutanix mit 5000 Teilnehmern einen neuen Besucherrekord verzeichnen. Der Hersteller verlässt den reinen Infrastrukturmarkt und bietet ab sofort einen Plattformdienst.

OpenSense Labs: Drupal and GDPR: Everything You Need to Know

Planet Drupal - 14. Mai 2018 - 14:41
Drupal and GDPR: Everything You Need to Know Akshita Mon, 05/14/2018 - 18:11

A lot has been written in and around the EU’s new data privacy compliance - General Data Protection Regulation. As we near 25th May, the search around GDPR compliance is breaking the internet. 

Vor 20 Jahren: Apple stellt die Weichen auf X – für ein modernes Mac OS

heise online Newsticker - 14. Mai 2018 - 14:30
Unter großem Applaus kündigte Steve Jobs vor 20 Jahren an, das NextStep-basierte Rhapsody mit dem klassischen Mac OS zusammenzuführen – zu Mac OS X. Damit war die Grundlage für Apples moderne Betriebssysteme gelegt.

Analyse: eGK – Jens Spahn und das schwere Erbe des Hermann Gröhe

heise online Newsticker - 14. Mai 2018 - 13:30
Mitten im Online-Rollout hat der neue Gesundheitsminister die Zukunft der elektronischen Gesundheitskarte infrage gestellt. Von der Kanzlerin bekommt er Rückendeckung. Was Ärzte frustriert, könnte Jens Spahn den Weg ins Kanzleramt ebnen. Got a config schema error on saving a view?

Planet Drupal - 14. Mai 2018 - 13:15

We ran into an obscure error recently, when saving a view that used a custom views plugin. It was supposed to be a very simple extension to core's bundle (content type) filter:

InvalidArgumentException: The configuration property display.default.display_options.filters.bundle.value.article doesn't exist. in Drupal\Core\Config\Schema\ArrayElement->get() (line 76 of [...]/core/lib/Drupal/Core/Config/Schema/ArrayElement.php).

Several contrib projects ran into this issue too: Drupal Commerce, Search API and Webform Views integration. There's even a core issue that looked relevant... but it turned out to be a simple, if perhaps surprising fix. If you ever run into it, it will have a different property (i.e. due to whichever plugin or default value are used).

Our filter was little more than a simple subclass of \Drupal\views\Plugin\views\filter\Bundle, declared for a specific entity type in a very ordinary hook_views_data() (which had even been autogenerated by Drupal Console, so we were fairly confident the problem wasn't there). It just tailored the options form a little to work well for the entity type.

Views plugins all have their own configuration schema - for example, the bundle filter is declared in views.filter.schema.yml to use the 'in_operator', because multiple bundles can be selected for it. When we subclass such a plugin, we do not automatically get to inherit the configuration schema (as that is not part of the PHP class or even its annotation). (Perhaps core could be 'fixed' to recognise this situation ... but there are more important things to work on!)

The solution is to simply copy the schema from the plugin we've extended - in our case, that was 'views.filter.bundle', found in core's 'views.filter.schema.yml' file within views' config/schema sub-directory. Wherever it is, it's probably named 'views.PLUGIN.ID', where 'PLUGIN' is the type of your plugin (e.g. field, filter, area), and 'ID' is the ID in the class annotation of the class your plugin extends. We pasted the schema into our own schema file - which can be named something like /config/schema/mymodule.schema.yml, within our module's directory:

# Replace 'mymodule_special_type' with the ID in your plugin's annotation. views.filter.mymodule_special_type: type: views.filter.in_operator label: 'Customised type selector'

Once that file is in place correctly, I expect you just need to rebuild caches and/or the container for Drupal to happy again. Re-save the form, the error is gone :-)

Configuration schemas should normally help development by catching errors, but as I've written before, an incorrect schema can make things surprisingly difficult. I hope someone else finds this article solves their problem so it doesn't take them as long to figure out! I haven't used it, but it's possible that the Configuration inspector project could help you identify issues otherwise.

Intel investiert in RISC-V-Pionier

heise online Newsticker - 14. Mai 2018 - 13:00
Intels Investment-Sparte Intel Capital beteiligt sich an der jungen Firma SiFive, die die ersten RISC-V-Prozessoren auf den Markt gebracht hat.

Verlorene Schätze: Ist Facebook das neue Fundbüro?

heise online Newsticker - 14. Mai 2018 - 13:00
Gefundene Gegenstände müssen ins Fundbüro gebracht werden, doch zunehmend tauchen sie im Internet auf. Vielen Menschen ist nicht bewusst, welches Risiko sie dabei eingehen.

Amazee Labs: Progressive Decoupling 2: A How To Guide

Planet Drupal - 14. Mai 2018 - 12:52
Progressive Decoupling 2: A How To Guide

In this series we take a closer look at progressive decoupling in Drupal 8. We go through the project setup, check the tools and libraries and discuss potential applications. The first post of the series showed some new features that made it into JavaScript in the last few years. This time let’s see how to use it in a project.

Blazej Owczarczyk Mon, 05/14/2018 - 12:52

JavaScript transpilation has been added to Drupal core in 8.4.0. The Core JS contribution workflow has been described in the change record Drupal core now using ES6 for JavaScript development. Unfortunately, the scripts mentioned there cannot be used to transpile contrib code yet. There’s an ongoing discussion about that in Use ES6 for contrib and custom JavaScript development. So we need to wait for that to be solved, right?

Not really. It turns out that it is enough to place the package.json file from core/ two levels up in the directory tree (in case of a composer project) and adjust paths to scripts to enjoy modern JS in contrib and custom code. With this file in the repository root we can run

to install dependencies, and we’re good to go with ES6.

will start the watcher, which monitors all .es6.js files and transpiles them to their .js counterparts whenever a change is detected.

The scripts can be invoked in one of 4 ways

To commit or not to commit?

Is it fine to commit the output (.js) files? That depends on the nature of the code. If it’s a contrib module / theme it’s best to do so. Target users shouldn’t be forced to transpile themselves and the build process of Drupal modules is not adjustable at the time off writing this post.

Source maps

Contrib modules would most likely provide just the optimized code (without source maps). The committed source .es6.js files can be used to overwrite the output files with dev features enabled for individual environments if needed.

Custom code

The choice here depends on the hosting platform. If it supports adjusting the build process based on the environment, then the .js files don’t have to be committed at all. The source files are enough and the compilation can be done before each deployment. Source maps can be used for dev and prod should get the optimized build. This is how it looks like in an file for instance:

As with every artifact, ruling out the compiled versions of js files from the repository makes the development process smoother, mainly by reducing conflicts. On the other hand, it doesn’t have to be a big problem if the team is small enough.


Here’s a recipe for adding an example ES6 library to a theme.

  1. Add this package.json file the root of your project
  2. Install dependencies
  3. Start the file watcher
  4. Add a library definition to package_name.libraries.yml in your module or theme.
  5. Create the index file (js/mylib/index.es6.js)
  6. Save the file and check the terminal window with the file watcher, js/mylib/index.es6.js should be mentioned there and the compiled version - index.js - should be created next to the source file. The library is now ready to be used in a module or theme.

    That’s it for setting up ES6 in a project. In the next post we’ll take a look at polyfills, talk about the fetch API and a see how to use async functions - the undeniable game changer from ES8.

    If you want to learn more about Drupal libraries check these out

    Windows Remote Desktop: CredSSP-Update kann zu unerreichbaren Servern führen

    heise online Newsticker - 14. Mai 2018 - 12:30
    Ein Windows-Update aus dem März sollte auf allen Rechnern installiert werden, die über das Remote Desktop Protokoll angesprochen werden. Ansonsten kann es sein, dass sich RDP-Nutzer dort nicht mehr anmelden können.

    Differential-GPS und WLAN-RTT: Präzise Ortung mit Android P

    heise online Newsticker - 14. Mai 2018 - 12:30
    Google verbessert die Ortung mit Android. Im Freien geht das mit Dualband- und Differenzial-GPS. In Innenräumen müssen 3 WLAN-Hotspots mit 802.11mc bereitstehen.

    Drohnen sollen Apples Kartendienst verbessern

    heise online Newsticker - 14. Mai 2018 - 11:30
    Ein US-Pilotprojekt gibt Apple die Erlaubnis, Drohnen auch über Menschen und außer Sichtweite einzusetzen. Der Konzern will mit den Aufnahmen Apple Maps verbessern und verspricht, Gesichter unkenntlich zu machen.

    Googles ML Kit: Machine Learning für alle!

    heise online Newsticker - 14. Mai 2018 - 11:30
    Mit ML Kit, einem neuen Software Development Kit für Firebase, will Google Machine-Learning-Konzepte für mehr Nutzer zugänglich machen. Dazu bietet ML Kit Entwicklern fünf fertige APIs, die häufige Anwendungsfälle abdecken sollen.

    Lücke in Windows, Linux, macOS: Entwickler missverstehen Intel-Dokumentation

    heise online Newsticker - 14. Mai 2018 - 10:30
    Weil ihre Entwickler die Dokumentation einer CPU-Funktion missverstanden haben, sind nun fast alle Betriebssysteme anfällig für Manipulationen des Kernel-Speichers. Updates für die Lücke wurden bereits verteilt.

    Fünf Jahre Streiks bei Amazon – Gewerkschaft erneuert Kampfansage

    heise online Newsticker - 14. Mai 2018 - 10:30
    Fünf Jahre Arbeitskampf bei Amazon – die Bilanz ist so verschieden wie die Interessen: Verdi glaubt, viele Verbesserungen an deutschen Standorten befördert zu haben. Der Versandhandelsriese versichert, auch ohne Tarifvertrag ein guter Arbeitgeber zu sein.