Drupal Planet

I am a Follower & Thinker

Lets start with a question - How often do you ask yourself:

  • How on earth did they think there/then?


...then set off spending quite a bit of time trying to reverse engineer it somehow!

I still do it all the time, more than once a day usually. Particularly when stumbling on new things, such as when hearing news about how bad state our world is in, or when watching a lecture or talk about an interesting topic.

To simplify, the big question for me ended something like this:

DrupalMill.com, .org and more, Up For Grabs

A couple of day ago I got a renewal notice from my domain registrar about drupalmill.com. It's a domain I have owned since a few years, a domain I had great plans and ambitions for when I got it. As time went bye, I never really got around to make those plans happened.

Adding to that, things have recently dramatically changed in my life. Changes that takes my personal goals and ambition in completely new directions. While Drupal still will play a central role, Drupal Mill wont.

Have We Allowed drupal.org to Become a Burden?

The community is currently having serious discussions exploring the possibility of moving important features and central tools from drupal.org to third party sites. This is important discussions and many good arguments for and against this is being presented. It also gives us much valuable knowledge about how other open source projects are organized and managed.

There is, however, cause for a lot of concern as a move would introduce fragmentation to the community. It will also force a large part of our user base to not only create accounts, but also to learn to use these tools. In many cases tools that they see little use for in their own roles.

In this post I am taking a look at our past and the current situation. I am also presenting thoughts and ideas about how we instead can turn what some see as a burden into a fantastic resource driving Drupal development and innovation forward.

Dogfooding our drupal.org Infrastructure

Most of the drupal.org infrastructure is currently running on Drupal 6. Drupal 7 has been out for soon three years and the work on upgrading our community home to it has gone on for almost a year now. At the same time we are busy getting Drupal 8 ready to be released.

The community is buzzing about Drupal 8 and motivated about getting it ready. But are we equally motivated about the needed work and maintenance of our infrastructure? Is there things we can do different? What would happen if we simply decided that we wont release a new major version of Drupal Core until after drupal.org runs on it?

In this post I am briefly outlining my ideas around how dogfooding drupal.org could lead to using our limited resources more efficient and in a way that the whole of the community would greatly benefit from.

Much to Learn From the drupal.org Password Reset

The Drupal Association staff and Drupal community did an amazing and transparent job in handling the recent security breach where user account and personal data got into the wrong hands. However, what haven't been addressed yet is the resulting sitewide password reset. What can we learn from that? How did drupal.org users experience it? What will happen if it would have been another site?

Do we need a sitewide password reset feature in Drupal Core?

That and other things is being discussed in this post, including how the Drupal community can take advantage of this unique opportunity to prepare for the next time it happens.

Drupal 8 WYSIWYG and File Cleanup

WYSIWYG in Drupal 8 is going to rock, simple as that. Practically all annoyances, complications and other stuff we have had to endure In Drupal 7 and earlier has been fixed. Read all about it and also watch Nate Haug's DrupalCon Portland 2013 session about the improvements here.

Unfortunately Nate also revealed that Drupal 8 will still automatically delete files when their usage gets zero. That is a bad thing and I'll explain why I strongly believe that.

Our Drupal Workplace: The Issue Queue

Sooner, not later, you will end up in the Issue Queue on d.o. Its practically unavoidable if you want to get the most out of your relation with Drupal.

The more involved you get, particularly as a code developer or themer, you will find that you spend more and more of your time working on and jumping around between issues. The list of issues you are active in and/or monitoring is constantly growing.

At this point you have turned the issues queue into: Your Workplace!

We are the Drupaleros

I saw this tweet flashing by in my stream today:


What immediately caught my eye was Drupaleros, the Spanish word for Drupal User. Its such a great word and just sounds great.

Or what do you say about:

We are the Drupaleros!

Awesome isn't it?

Don’t Make Drupal the New ‘Microsoft Office’!

If you’ve been around the IT business a couple of decades, I’m sure you also remember what happened whenever Microsoft released a new Office version. They received a storm of user complaints! It was about the same thing every time: Microsoft had focused on adding shiny new features while neglecting to fix the existing ones. For every version office simply became more and more bloated.

Drupal SBUI Update and Progress Report

Its two and a half month since my community initiative Drupal SBUI made its announcement and a lot has happened since. I would like to take this opportunity to give you an update and overview of things. Personally I am very excited about the progress we already have made.

This post is also great timing due to that yesterday we got our first community collaboration project when the maintainer of the Fill PDF module asked if we can help out with improving its UX. Its something we really look forward to working on.

What is Drupal SBUI?

The Content Editors Are Your Most Important Users

I have, shamelessly, stolen the headline from the second slide of Jeff Eaton’s keynote (see embedded video at the end) at DrupalCamp Toronto November 17th. For me, this quote encapsulates one of the biggest challenges sitebuilders have, namely being able to construct amazing UX and usability for users, and particularly for those users that work with the content. The whole keynote is about that, the UX and usability for users and Jeff is, as usual, spot on about everything.

Time Talks Against IE8 Support for Drupal 8

Yesterday I published the Why not Drop IE8 support for Drupal 8? post and it got some really great feedback in the comments. Thanks for that, its always nice to hear good arguments as well as tips of where to find more information about something.

In this post I would like to follow up on those comments. First though lets start with a look at the market share Internet Explorer 8 (IE8) has and how it has developed from its height in April last year.