Seagate: HAMR-Festplatten mit 20 TByte und Multi-Aktuator mit 480 MByte/s kommen 2020

heise online Newsticker - 24. März 2018 - 11:30
Seagate stellt auf dem Open Computer Project Summit erneut zwei Techniken zur Steigerung von Festplattenkapazität und -leistung vor. 2020 sollen HAMR und Multi-Aktuator-Technik serienreif sein.

Nvidias 3100-Euro-Grafikkarte Titan V verrechnet sich angeblich

heise online Newsticker - 24. März 2018 - 10:30
Nvidias teure Volta-Grafikkarte kann offenbar bei komplexen, wissenschaftlichen Berechnungen falsche Ergebnisse ausspucken.

IETF 101: Entwickler fordert Diät für DNS-Protokollerweiterungen

heise online Newsticker - 24. März 2018 - 10:00
DNSSEC, ANAME, DNAME, QMinimization, EDNS – verstehen Sie alles nicht? Denen, die diese Erweiterungen des Domain Name System implementieren sollen, geht auch langsam die Luft aus. Ein Praktiker appelliert jetzt, kürzer zu treten.

Forscher entwickeln neuartiges elektronisches Gehirn

heise online Newsticker - 24. März 2018 - 10:00
Deep Learning und auf KI spezialisierte Beschleunigerchips sind erst der Anfang. Die nächste Generation neuromorpher Hardware soll dem Gehirn ein gutes Stück näher kommen.

Kommentar: #deletefacebook ist auch nicht die Lösung

heise online Newsticker - 24. März 2018 - 9:00
Nach dem Datenskandal hat Facebook das Vertrauen vieler Nutzer verloren. Auf Twitter macht der Hashtag #deletefacebook die Runde – doch müssen wir jetzt wirklich ohne Facebook auskommen?

KnackForge: How to update Drupal 8 core?

Planet Drupal - 24. März 2018 - 7:01
How to update Drupal 8 core?

Let's see how to update your Drupal site between 8.x.x minor and patch versions. For example, from 8.1.2 to 8.1.3, or from 8.3.5 to 8.4.0. I hope this will help you.

  • If you are upgrading to Drupal version x.y.z

           x -> is known as the major version number

           y -> is known as the minor version number

           z -> is known as the patch version number.

Sat, 03/24/2018 - 10:31

Ashday's Digital Ecosystem and Development Tips: The Future of Websites: CMS or Website Builder Tools?

Planet Drupal - 23. März 2018 - 22:00
Why Squarespace Will Replace Wordpress, Wordpress Will Replace Drupal, and Drupal Will Replace Drupal

When the open source WordPress blogging platform first came out, it opened up the world of internet publishing to the masses. Sure, there were website builders out there like GeoCities and Angelfire, but they lacked much and were very ugly. When WordPress came along it gave voice to those willing to overcome the barriers of setting up web hosting and installing the software. These days there are much better website builders for the common person. Squarespace being a standout of the group even has an easy to use e-commerce option. Because of this, the roles of many popular Content Management Systems (CMS)s are shifting.

DrupalCon News: Join the Developer Contest in Nashville

Planet Drupal - 23. März 2018 - 20:51

We're excited to welcome back the DrupalCon Developer Contest - our first since Los Angeles.

Acro Media: A Reaction to "A New Documentation Initiative"

Planet Drupal - 23. März 2018 - 20:06

Matthew Grasmick, grasmash on and, has written another inspiring post on documentation. As our CTO, Shawn McCabe has often said before, give Acro an easy button, and we’re 100% behind better documentation.

You can read Matthew’s original blog post for a more thorough and somewhat more roundabout explanation of his proposal. Below I’ve edited the heart of his post into 6 distinct proposals and responded to each one.

In general, I think we can all agree the documentation for Drupal has needed a breath of fresh air and is constant source of frustration for new and experienced users alike.

Proposal #1A:  Elevate some docs to "official"

Elevate the Drupal 8 User Guide to the status of "Official Documentation"

The idea of creating a tiered documentation has been implemented partially already with the new documentation migration initiative. I think Matthew’s proposal goes one step further by wanting to introduce a new taxonomy term called “Official” for the “documentation page” and “documentation guide” that carries more weight. This idea is very drupally, as we currently do this exact same thing with marking modules as covered by the security policies. Providing a level of assurance that a certain module is produced by people who know what they’re doing and backed up by a team of specialists who voluntarily deal with logistics and other high-level situations.

In general, I think Matthew’s first proposal is a good one. We should implement it by “blessing” certain documentation pages and guides with a stamp of approval / official.

Proposal #1B:  Prominently Feature "Official Docs"

Update the UX on to prominently feature the Official Documentation on major site entry points.

Along with the “stamp of approval” we would “red light / green light” these pages. Essentially flagging pages as “red light, unofficial” and “green light, official” would go a long way to signalling to the community at large that we take documentation seriously and only greenlight the best of the documentation.

To take Matthew’s proposal seriously, though, we would also need to implement new call-to-actions on non-documentation pages that point to the “official” pages. Maybe revamp the navigation of header and footer on to clarify the difference between “official” documentation and “unofficial.”

Proposal #2:  Adopt Best Practices

We should adopt the following as best practices for all Official Documentation:

This is the heart of the proposals. Matthew wants to constrain the carrot, that “official” stamp of approval, through a high-level checklist of best practices. Agreed. Below is a quick run down of the best practices Matthew is proposing.

  1. A governance process
  2. Use version control
  3. Use and follow documentation standards
  4. Write documentation in markdown format
  5. Use continuous integration process to generate and update screen shots of Drupal interfaces. (<a href="">Additional Info</a>).
Proposal #3:  Integrate Semantic Versions

Let's integrate the semantic versions (8.5.x, 8.6.x, 9.0.x, etc.) into the Official Documentation UX, much in the way that Symfony and Laravel do.

This is absolutely critical but also a huge technical task (high risk). It means that official documentation would need to have it’s status coupled with minor releases of Drupal. The bigger our official documentation grows, the larger the task will be to maintain it adequately between minor versions. I think the manpower needed to make this idea happen might just burn out the individuals interested in stepping up to make it happen. If we, the Drupal community, can stomach the high risk nature of such a claim, then by all means, we need this.

Perhaps a way to reduce risk is to “evergreen” stamp certain pages, clarifying the fact that certain pages would not likely need updated between minor releases. We could also reach out to Symfony to ask how they manage minor releases and documentation.

Proposal #4:  Lower Contribution Barrier

Lower the contribution barrier.

Decoupling the documentation contributors could impact the early adopters positively and long term users negatively. I think think the primary way to achieve the goal set out in this proposal is tightly coupled with the next proposal, by letting users of an open source git-powered platform make the edits, we essentially open source our documentation and our processes at the same time.

I helped spearhead the move of Drupal Commerce’s documentation to the subdomain “docs” for the same reason. We have much better documentation because of this move. Anecdotally, for Drupal Commerce 1, we had maybe a handful of contributors to Drupal’s documentation. Now, for version 2, we have a myriad of contributors (51!!). Scaling documentation is hard, and this is one way to increase involvement.

Personally, I absolutely love this part of Matthew’s proposal. Professionally, I think the community is divided and people are picking sides. They are rightly asking: Why can't Drupal do this very content heavy thing better? Perhaps the answer is: Drupal can do this! We just have to accept this content lives in a version-controlled repo and not in the database.

Proposal #5:  Host Docs on Repo

Use a repository that is hosted on GitHub (or GitLab) to manage the official Drupal documentation.

Agreed. I’m looking forward to learning how will move to one of the git-based hosting services. I’d throw my hat into the github arena, but the initiative for has already chosen bitbucket. So let’s use bitbucket.

Proposal #6:  One Pager

Create a new class of documentation that we're lacking: "The Official One Pager."

Cool, love the idea. I think we could take or leave this. If I were proposing these changes to a client, I would mark this proposal as optional. This helps communicate that this proposal is a lower priority (unless the decision makers want to make it a higher priority) and helping the decision makers understand that this scope increase, while very beneficial, would impact the delivery and bottom line and could easily be moved on to a different delivery schedule.

Aktionäre stimmen Milliarden-Vergütungsplan für Tesla-Chef Musk zu

heise online Newsticker - 23. März 2018 - 19:30
50 Milliarden US-Dollar stellen die Aktionäre dem Tesla-Chef in Aussicht. Allerdings muss er dafür ehrgeizige Ziele erreichen.

Streit mit China: iPhone für 4,4 Prozent des US-Handelsbilanzdefizits verantwortlich

heise online Newsticker - 23. März 2018 - 19:00
Das Apple-Smartphone soll allein 15,7 Milliarden US-Dollar zum gesamten Handelsbilanzdefizit der USA gegenüber China beigetragen haben. Allerdings ist die Rechnung problematisch.

Standardisierungsorganisation fürs Internet kämpft weiter mit Geldproblemen und wird unabhängig

heise online Newsticker - 23. März 2018 - 19:00
Drei Jahrzehnte nach ihrem Start gibt sich die Standardisierungsorganisation fürs Internet, die IETF, eine Rechtsform und wird in finanziell schwieriger Zeit eine Limited Liability Company.

Tod mit autonomem Auto: Uber-Fahrerin schaute vor Unfall nach unten

heise online Newsticker - 23. März 2018 - 18:30
Die Polizei von Tempe, wo sich ein tödlicher Unfall mit einem autonomen Auto ereignete, hat ein Video veröffentlicht, das die Situation kurz vor dem Ereignis zeigt.

Übernahme von Drillisch beschert United Internet erfolgreiches Geschäftsjahr

heise online Newsticker - 23. März 2018 - 18:30
Ein gutes Geschäft hat der Internet-Provider United Internet im vergangenen Jahr gemacht. Umsatz und Gewinne stiegen deutlich – auch wegen der Übernahme des Mobilfunkanbieters Drillisch.

"Konsolenreife" mobile Spiele: Apple sieht sich ganz vorne

heise online Newsticker - 23. März 2018 - 18:00
90 Prozent der Geräte verwendeten die aktuelle iOS-Version, was die Entwicklung für die Hersteller viel einfacher macht als unter Android, sagt Produktmarketing-Chef Greg Joswiak.

Drupal stellt Sicherheitsupdate für extrem kritische Lücke in Aussicht

heise online Newsticker - 23. März 2018 - 17:30
Wer das CMS Drupal einsetzt, sollte sich den 28. März im Kalender markieren, um wichtige Sicherheitsupdates für verschiedene Versionen zu installieren.

SuedLink-Stromtrassenbau: Bürgerinitiativen formieren sich zum Widerstand

heise online Newsticker - 23. März 2018 - 17:30
Der geplante Bau der Nord-Süd-Stromtrasse SuedLink bekommt immer mehr Gegenwind. Die Gegner beklagen ein fehlendes Gesamtkonzept für die Energiewende und bezweifeln die Notwendigkeit des Baus. Jetzt wollen sie sich treffen, um ihn insgesamt zu verhindern.

Debatte um Waffengewalt: Youtube untersagt Waffenwerbung, Reddit Waffenhandel

heise online Newsticker - 23. März 2018 - 17:00
Auf Youtube dürfen Videos bald auch keine Werbung mehr für Seiten machen, die mit Schußwaffen handeln. Auch Reddit geht gegen derartige Transaktionen vor. Beide beziehen damit offenbar in der Debatte über die Ursachen der US-Waffengewalt Stellung.

KI-Einsatz bei Ubisoft: Vom Computer-Praktikanten zum Spieldesigner

heise online Newsticker - 23. März 2018 - 16:00
KI-Routinen greifen Ubisoft-Designern bei der Entwicklung unter die Arme, während in den fertigen Spielwelten Auto-KIs für den Ernstfall üben. Und am Horizont grüßen Spielfiguren, die komplett ohne menschliches Zutun entstehen.

Brian Osborne: Overriding module configuration in a Drupal 8 installation profile (with some "gotchas")

Planet Drupal - 23. März 2018 - 15:31

I'm working in creating a Drupal 8 installation profile and learning how they can override default configuration that its modules provide at install time.