LG: Limitiertes Edel-V30 kostet über 1500 Euro

heise online Newsticker - 9. Dezember 2017 - 16:30
Da ist noch Luft nach oben: LG toppt den hohen Preis für das iPhone X mit einem limitierten Smartphone namens Signature Edition. Die aufgepumpte Variante des V30 kommt allerdings nur in Südkorea und in limitierter Stückzahl in den Handel.

Künstliche Intelligenz: AlphaZero meistert Schach, Shogi und Go

heise online Newsticker - 9. Dezember 2017 - 16:00
Googles KI-Firma DeepMind hat einen selbstlernenden Algorithmus entwickelt, der Schach und Shogi nur anhand der Regeln gelernt hat und nach nur wenigen Stunden die stärksten Programme schlagen konnte.

Qualcomm Snapdragon 845 mit 30 Prozent Plus und Secure Processing Unit

heise online Newsticker - 9. Dezember 2017 - 16:00
Rund 30 Prozent mehr Grafik- und Prozessorleistung sowie neue Funktionen wie eine Secure Processing Unit bringt der kommende Smartphone- und Mobilprozessor.

Videospiele: "Empire: Four Kingdoms"-Studio Goodgame für 270 Millionen verkauft

heise online Newsticker - 9. Dezember 2017 - 15:30
Das Hamburger Spielestudio Goodgame gehört jetzt der schwedischen Firma Stillfront Group. Die Entwicklerschmiede hinter "Empire: Four Kingdoms" wechselte für einen Kaufpreis von 270 Millionen Euro den Besitzer.

Tool erlaubt Einlesen von APFS-Volumes unter Windows und älteren Macs

heise online Newsticker - 9. Dezember 2017 - 15:30
Biskus APFS Capture kann Apples neues Dateiformat für Analysen und zum Kopieren von Dateien erfassen – auch auf Rechnern, die es nicht unterstützen. Billig ist das nicht.

Bislang fernstes und ältestes Schwarzes Loch überrascht Astronomen

heise online Newsticker - 9. Dezember 2017 - 14:00
Ein mehr als 13 Milliarden Lichtjahre entferntes Schwarzes Loch in einem Galaxienkern strahle schon weniger als 700 Millionen Jahre nach dem Urknall enorm hell. Forscher müssen nun ihre Modelle zur Frühzeit des Universums anpassen.

iTunes 12.7.2: Fehlerbehebungen, "mehr Leistung", aber kein iOS App Store

heise online Newsticker - 9. Dezember 2017 - 13:00
Apple hat seine Medienverwaltung aktualisiert. Der iOS App Store ist noch immer nicht zurückgekehrt – wer ihn braucht, muss weiterhin eine Sonderversion verwenden.

Steam nimmt keine Bitcoins mehr an – Kryptogeld trotzdem auf neuem Allzeithoch

heise online Newsticker - 9. Dezember 2017 - 12:30
Zu hohe Transaktionsgebühren und ständige Wertschwankungen – die Spieleplattform Steam schafft Bitcoins als Zahlungsmittel wieder ab. Der Kurs des Kryptogelds steigt trotzdem über 15.000 US-Dollar.

Kein Nutzerinteresse: Google beerdigt Chrome-Apps

heise online Newsticker - 9. Dezember 2017 - 11:45
Nach einer Ankündigung im Sommer 2016 hat Google nun die Chrome-Apps aus dem Sortiment seines Chrome-Web-Stores geschmissen. Die Apps bleiben bis Anfang nächsten Jahres funktionsfähig – die Nachfolge sollen PWAs antreten.

37 Sicherheitslücken in Chrome geschlossen

heise online Newsticker - 9. Dezember 2017 - 9:30
In Chrome klafft unter anderem eine kritische Schwachstelle. Darüber könnten Angreifer Computer übernehmen.

Wim Leers: API-First Drupal — really!

Planet Drupal - 8. Dezember 2017 - 23:54

This blog has been quiet for the last year and a half, because I don’t like to announce things until I feel comfortable recommending them. Until today!

Since July 2016, API-First Drupal became my primary focus, because Dries felt this was one of the most important areas for Drupal’s future. Together with the community, I triaged the issue queue, and helped determine the most important bugs to fix and improvements to add. That’s how we ended up with REST: top priorities for Drupal … plan issues for each Drupal 8 minor:

If you want to see what’s going on, start following that last issue. Whenever there’s news, I post a new comment there.

But enough background. This blog post is not an update on the entire API-First Initiative, it’s about a particular milestone.

100% integration test coverage!

The biggest problem we encountered while working on rest.module, serialization.module and hal.module was unknown BC breaks 1. Because in case of a REST API, the HTTP response is the API. What is a bug fix for person X is a BC break for person Y. The existing test coverage was rather thin, and was often only testing “the happy path”: the simplest possible case. That’s why we would often accidentally introduce BC breaks.

Hence the clear need for really thorough functional (integration) test coverage2, which was completed almost exactly a year ago. We added EntityResourceTestBase, which tests dozens of scenarios3 in a generic way4, and used that to test the 9 entity types, that already had some REST test coverage, more thoroughly than before.

But we had to bring this to all entity types in Drupal core … and covering all 41 entity types in Drupal core was completed exactly a week ago!

The test coverage revealed bugs for almost every entity type. (Most of them are fixed by now.)

Tip: Subclass that base test class for your custom entity types, and easily get full REST test coverage — 41 examples available!

Guaranteed to remain at 100%

We added EntityResourceRestTestCoverageTest, which verifies that we have test coverage for all permutations of:

  • entity type
  • format: json + xml + hal_json
  • authentication: cookie + basic_auth + anon

It is now impossible to add new entity types without also adding solid REST test coverage!

If you forget that test coverage, you’ll find an ASCII-art llama talking to you:

Good people of #Drupal, I present unto you the greatest method of all time. https://github.com/drupal/drupal/blob/8.5.x/core/modules/rest/tests/src/Functional/EntityResource/EntityResourceRestTestCoverageTest.php#L141 pic.twitter.com/TiWLPt7duH

— webcsillag (@webchick) December 8, 2017

That is why we can finally say that Drupal is really API-First!

This of course doesn’t help only core’s REST module, it also helps the contributed JSON API and GraphQL modules: they’ll encounter far fewer bugs!


So many people have helped! In random order: rogierbom, alexpott, harings_rob, himanshu-dixit, webflo, tedbow, xjm, yoroy, timmillwood, gaurav.kapoor, Gábor Hojtsy, brentschuddinck, Sam152, seanB, Berdir, larowlan, Yogesh Pawar, jibran, catch, sumanthkumarc, amateescu, andypost, dawehner, naveenvalecha, tstoeckler — thank you all!5

Special thanks to three people I omitted above, because they’re not well known in the Drupal community, and totally deserve the spotlight here, for their impressive contribution to making this happen:

That’s thirty contributors without whom this would not have happened!

And of course thanks to my employer, Acquia, for allowing me to work on this full-time!


What is going to be the next big milestone we hit? That’s impossible to say, because it depends on the chains of blocking issues that we encounter. It could be support for modifying and creating config entities, it could be support for translations, it could be that all major serialization gaps are fixed, it could be file uploads, or it could be ensuring all normalizers work in both rest.module & jsonapi.module

The future will tell, follow along!

  1. Backwards Compatibility. ↩︎

  2. Nowhere near 100% test coverage, definitely not every possible edge case is tested, and that is fine↩︎

  3. Including helpful error responses when unauthenticated, unauthorized or just a bad request. This vastly improves DX: no need to be a Drupal expert to talk to a REST API powered by Drupal! ↩︎

  4. It is designed to be subclassed for an entity type, and then there are subclasses of that for every format + authentication combination. ↩︎

  5. And this is just from all the per-entity type test issues, I didn’t look at the blockers and blockers of blockers. ↩︎

  • Acquia
  • Drupal

Playerunknown's Battlegrounds: Infos und Bilder zur Wüstenkarte Miramar

heise online Newsticker - 8. Dezember 2017 - 20:00
Bald erscheint die Wüstenkarte Miramar für das Multiplayer-Spiel Playerunknown's Battlegrounds. Die Entwickler haben die Karte nun offiziell enthüllt.

Aegir Dispatch: Re-positioning Ægir

Planet Drupal - 8. Dezember 2017 - 18:39
Last week, Colan and I attended SaasNorth, a conference for Software-as-a-Service founders and investors, with a strong focus on marketing, finance and growth. To be honest, we were a little skeptical at the near total absence of technical content. However, we were pleasantly surprised by some of the truly excellent speakers we heard. The one that had the most impact on us was April Dunford’s OBVIOUSLY AWESOME – Using context to move your customers from “What?

LakeDrops Drupal Consulting, Development and Hosting: 3 minutes: Starting Drupal 8 project with a composer template

Planet Drupal - 8. Dezember 2017 - 18:11
3 minutes: Starting Drupal 8 project with a composer template Jürgen Haas Fri, 12/08/2017 - 17:11

Starting a new Drupal 8 project with the LakeDrops composer template only takes less than 3 minutes. And in that short period of time you're note only getting the code base but also a number of extra benefits:

Der Kultfilm Wargames wird zur interaktiven Serie

heise online Newsticker - 8. Dezember 2017 - 18:00
Der Film aus den 80er Jahren, der sich um die Geschichte eines Hackers während der Zeit des Kalten Krieges dreht, soll als interaktive Serie 2018 erscheinen. Maßgeblich beteiligt ist Sam Barlow, bekannt als kreativer Kopf hinter dem Spiel "Her Story".

iOS 11.2: Apple schließt KRACK-WLAN-Lücke für ältere Geräte erst jetzt

heise online Newsticker - 8. Dezember 2017 - 18:00
Während iPhone 7 sowie iPad Pro 9.7 und neuere Geräte bereits im November mit einem Patch gegen den Angriff auf das vielverwendete WPA2-Protokoll versehen wurden, werden ältere Geräte erst mit iOS 11.2 abgesichert.

Deutscher Entwicklerpreis 2017: "The Surge" als bestes deutsches Computerspiel ausgezeichnet

heise online Newsticker - 8. Dezember 2017 - 17:30
Das Spiel "The Surge" wurde mit dem Deutschen Entwicklerpreis als bestes deutsches Spiel ausgezeichnet.

Mac & i Heft 6/2017 jetzt im Handel

heise online Newsticker - 8. Dezember 2017 - 17:30
Themen: WLAN tunen – so geht's • iPhone und iPad gebraucht • Intelligentes Spielzeug • SSDs auch für neuere MacBooks • Lieder selbst remixen • High-Sierra-Probleme lösen • Videoschnitt • Qi-Ladegeräte • Augmented Reality • Apples Steuertricks

Colan Schwartz: Ægir Turns 10!

Planet Drupal - 8. Dezember 2017 - 17:09
Topics:  This blog post has been re-published from Aegir's blog and edited with permission from its author, Christopher Gervais.

My tenure with the Ægir Project only dates back about 7 or 8 years. I can’t speak first-hand about its inception and those early days. So, I’ll leave that to some of the previous core team members, many of whom are publishing blog posts of their own.

New look for www.aegirproject.org

As part of the run-up to Ægir’s 10-year anniversary, we built a new site for the project, which we released today. It will hopefully do more justice to Ægir’s capabilities. In addition to the re-vamped design, we added a blog section, to make it easier for the core team to communicate with the community. So keep an eye on this space for more news in the coming weeks.

Ægir has come a long way in 10 years

When I first tried to use Ægir (way back at version 0.3), I couldn’t even get all the way through the installation. Luckily, I happened to live in Montréal, not too far from Koumbit, which, at the time, was a hub of Ægir development. I dropped in and introduced myself to Antoine Beaupré; then one of Ægir’s lead developers.

One of his first questions was how far into the installation process I’d reached. As it turns out, he frequently asked this question when approached about Ægir. It helped him gauge how serious poeple were about running it. Back then, you pretty much needed to be a sysadmin to effectively operate it.

A few months, Antoine had wrapped the installation scripts in Debian packaging, making installation a breeze. By that point I was hooked.

Free Software is a core value

Fast forward a couple years to DrupalCon Chicago. This was a time of upheaval in the Drupal community, as Drupal 7.0 was on the cusp of release, and Development Seed had announced their intention to leave the Drupal community altogether. This had far-reaching consequences for Ægir, since Development Seed had been the primary company sponsoring development, and employing project founder and lead developer Adrian Rossouw.

While in Chicago I met with Eric Gundersen, CEO of DevSeed, to talk about the future of Ægir. Whereas DevSeed had sold their flagship Drupal product, OpenAtrium, to another company, Eric was very clear that they wanted to pass on stewardship of Ægir to Koumbit, due in large part to our dedication to Free Software, and deep systems-level knowledge.

Community contributions are key

Since then Ægir has grown a lot. Here is one of the more interesting insights from OpenHub’s Ægir page:

Very large, active development team Over the past twelve months, 35 developers contributed new code to Aegir Hosting System. This is one of the largest open-source teams in the world, and is in the top 2% of all project teams on Open Hub.

To help visualize all these contributions, we produced a video using Gource. It represents the efforts of no less than 136 developers over the past 10 years. It spans the various components of Aegir Core, along with “Golden” contrib and other major sub-systems.

Of course, many other community members have contributed in other ways over the year. These include (but aren’t limited to) filing bug reports and testing patches, improving our documentation, answering other users’ questions on IRC, and giving presentations at local meetups.

The Future

The core team has been discussing options for re-architecting Ægir to modernize the codebase and address some structural issues. In the past few months, this activity has heated up. In order to simultaneously ensure ongoing maintenance of our stable product, and to simplify innovation of future ones, the core team decided to divide responsibilities across 3 branch maintainers.

Herman van Rink (helmo) has taken up maintenance of our stable 3.x branch. He’s handled the majority of release engineering for the project for the past couple years, so we can be very confident in the ongoing stability and quality of Ægir 3.

Jon Pugh, on the other hand, has adopted the 4.x branch, with the primary goal of de-coupling Ægir from Drush. This is driven largely by upstream decisions (in both Drupal and Drush) that would make continuing with our current approach increasingly difficult. He has made significant progress on porting Provision (Ægir’s back-end) to Symfony. Keep an eye out for further news on that front.

For my part, I’m pursuing a more radical departure from our current architecture, re-writing Ægir from scratch atop Drupal 8 and Ansible with a full-featured (Celery/RabbitMQ) task queue in between. This promises to make Ægir significantly more flexible, which is being borne out in recent progress on the new system. While Ægir 5 will be a completely new code-base, the most of the workflows, security model and default interface will be familiar. Once it has proven itself, we can start pursuing other exciting options, like Kubernetes and OpenStack support.

So, with 10 years behind us, the future certainly looks Bryght*.

* Bryght was the company where Adrian Rossouw began work on “hostmaster” that would eventually become the Ægir Hosting System.

Amazee Labs: Amazee Agile Agency Survey Results - Part 5

Planet Drupal - 8. Dezember 2017 - 16:51
Amazee Agile Agency Survey Results - Part 5

Welcome to part five of our series, processing the results of the Amazee Agile Agency Survey. Previously I wrote about forming discovery and planning. This time let’s focus on team communication and process.

Josef Dabernig Fri, 12/08/2017 - 15:51 Team Communication

When it comes to ways how to communicate, the ones that got selected with the highest rating of “mostly practised” where “Written communication in tickets”, “Written communication via (i.e. Slack)” as well as “Group meetings for the entire team”. The options that most often got selected as “Not practised” where “Written communication in blog or wiki” and “Written communication in pull requests”.

For us at Amazee Labs Zurich, a variety of communication channels is essential. Regular 1-on-1 meetings between managers and their employees allow us to continuously talk about what’s important to either side and work on improvements. We communicate a lot via Slack where we have various team channels, channels together with clients related to projects, channels for work-related topics or just channels to talk about fun stuff. Each morning, we start with a short team stand-up for the entire company where we check in with each other, and that’s followed by a more in-depth standup for the Scrum teams where we talk about “What has been done, What will be done and What’s blocking us”. Written communication happens between the team and customers in Jira tickets. As part of our 4-eyes-principle peer review process, we also give feedback on code within pull requests that are used to ensure the quality of the code and train each other.


We talked about iteration length in part 1 of this series. Now let’s look into how much time we spend on which things.

According to the survey, the majority of standups take 15 minutes, followed by 5 minutes and 10 minutes with a few ones taking up to 30 minutes.

This also reflects ours: we take 10 minutes for the company-wide stand up amongst 24 team members and another 15 minutes for the Scrum Team specific stand-ups.

For the review-phase, teams equally often selected 2 hours and 1 hour as the top-rated option followed closely by 30 minutes. 4 hours has been chosen by a few other teams, and the last one would be one day. For the retrospectives, the top-rated option was 30 minutes, followed by 1 hour. Much fewer teams take 2 hours or even up to 4 hours for the retrospective. For planning, we saw the most significant gap regarding top rated options: 30 minutes is followed by 4 hours and then 2 hours and 1 hours were selected.

In the teams I work with, we usually spend half a day doing sprint review, retrospective and planning altogether. Our reviews typically take 45 minutes, the retrospective about 1.5 hours and the planning another 30 minutes. We currently don’t do these meetings together with customers because the Scrum teams are stable teams that usually work for multiple customers. Instead, we do demos along with the clients individually outside of these meetings. Also, our plannings are quite fast because the team split up stories already in part of grooming sessions beforehand and we only estimate smaller tasks that don’t get split up later on as usually done in sprint planning 2.

When looking at how much time is being spent on Client work (billable, unbillable) and Internal work we got a good variety of results. The top-rated option for “Client work (billable)” was 50-75%, “Client work (unbillable)” was usually rated below 10% and “Internal work” defaulted to 10-25%. Our internal statistics match these options that have been voted by the industry most often.

I also asked about what is most important to you and your team when it comes to scheduling time? Providing value while keeping our tech debt in a reasonable place has been mentioned which is also true for us. Over the last year, we started introducing our global maintenance team which puts a dedicated focus on maintaining existing sites and keeping customer satisfaction high. By using a Kanban-approach there, we can prioritise timely critical bugs fixes when they are needed and work on maintenance-related tasks such as module updates in a coordinated way. We found it particularly helpful that the Scrum-teams are well connected with the maintenance-team to provide know-how transfer and domain-knowledge where needed.

Another one mentioned, “We still need a good time tracker.” At Amazee we bill by the hour that we work so accurate time tracking is a must. We do so by using Tempo Timesheets for Jira combined with the Toggl app.

How do you communicate and what processes do you follow? Please leave us a comment below. If you are interested in Agile Scrum training, don’t hesitate to contact us.

Stay tuned for the next post where we’ll look at defining work.