Happy

Drupal Marketshare

For some time, Drupal has a marketshare above 1% of all the sites onlne. Now there are numerous ways of counting and presenting data and if you know a bit about measuring and statistics, you know there are a zillion ways to lie.

The fact that Drupal has a big marketshare is something all can agree on. According to the way Dries has measured this is by visiting and fingerprinting the top 1 miljon websites (in hits) and see what percentage is being served with Drupal, as presented during DrupalCon SF.

According to builtwith.com Drupal now has 1.7% marketshare of all the sites entered at buildwith:

  1. Drupal 1.69%
  2. vBulletin 0.69%
  3. Joomla! 0.32%

And Drupal is growing fast, see this (flash) graph. Is it relevant how many sites are using Drupal? Well, in open source it is all about eyeballs. Many eyeballs make all bugs shallow. Yet, eyeballs without installs means nothing. So yes, marketshare is important. More installs means more eyeballs and better code. Or if you are not a developer, more installs means bigger market and more money :-)

Brecht, werelddominantie

Donderdag 22 juli 2011, Lymes Regis, United Kingdom

Aart (3) loopt uit het zomerhuisje naar de veranda waar Brecht (6) op het trappetje zit.


Aart: "Wat doe je Brecht?"
Brecht : "De wereld veroveren!"


Goed te weten dat ze later open source software developer wordt :-)

76/365 Are you pondering what I'm pondering?

Drupal Dev Days, a retrospective

Last week we held the “Drupal Dev Days" at the HQ of dop.nu. This post reflects some thoughts on why we organised this camp, what we did and what we learned.

We started the smaller unconference Dev camp because we want to facilitate smaller groups to come together and work on targeted items. In the Netherlands we also have the DrupalJam’s. The last Jam had nearly 300 attendees and with the growing demand of Drupal services, this conference will grow for some time, 400 attendees in half a year is realistic.


Robert Douglass’ keynote during last DrupalJam, (c) Wessel Zwiers

To put this in perspective, a DrupalJam now is as big as a European DrupalCon only 4 years ago. And while having a big local conference is a good thing for networking and promotion, there is a growing need to get smaller more focussed “unofficial" camps to get better communication and more interaction. So DOP decided to facilitate a smaller camp with only developers, laptops, wifi, a nice location, tents, a BBQ, some beer and water-pistols. All the ingredients for having a good Drupal camp!


360 panorama of the place where DDD was held

And we did have a good time, the weather was very nice, lots of people brought local beer and while there was no program, we actually did a lot. That is, some just wanted to site and discuss, other wanted to learn and share and some just wanted to code.

For an impression of the camp, see this collection.


So what did we do during these three days apart from throwing buckets of water?

  • Marc van Gend and Erik Stielstra started a module codenamed “turn me on" that enables the current site of a state to be saved. The idea is to have multiple states of a site for staging and production so one can easy turn on and off modules or settings that you want in a preproduction environment but not on a production site. This module will be released once completed.

  • 10 people discussed on how to get a better User Interface for Hansel “breadcrumbs done right!" by co-worker Maurits Lawende. Hansel is a very powerful way of providing very flexible breadcrumbs on all pages and views yet with this power is currently hidden in a sub optimal interface. Hansel will never be as popular as the direct “competitors" (such as custom breadcrumbs) since you need to understand arguments and rules, yet we cam up with an easier interface that will hit d.o in the next release.

  • Coworkers Maarten Verbaarschot and Sietse de ruiter did some work on the base theme Ink Ribbon

  • Karten Frohwein gave a good presentation on simpletest

  • The best part IMHO was kicked of by Clemens Tolboom, a session about helping develops -and users- to clean up their issue queue by using a system called Triage. Triage is a way to of prioritising patients based on the severity of their condition by relatively unskilled personal. This so professionals (doctors, maintainers) have a better queue where they can focus on musts and shoulds and users are forced to give better input to them. This system is in use at Gnome and seems to work fine there. For example, bigger modules like views have more then 1000 issues open, unworkable for those wanting to help out and the maintainer(s). If we would have a system where anyone could help by classifying bugs and by asking for more information or closing old bugs related to 4.x version, all benefit. If you want to help out in this prococes, please read 838682 and work from there.

  • Maurits also worked on the Rate module. A module build on voting API that has a broader range then for example 5star with more value types. See a screenshot below:


  • and

  • Morten -lead organiser of the upcoming DrupalCon in Copenhagen, skyped in to promote in his special way this event and was shown on the beamer. Nearly all of the attendees were already planning on visiting the DrupalCon Copenhagen, yet spreading the word always helps!



So what did we learn? The number of no shows is always high on these events. Sending out mails to the attendees on a regular basis is a good way to get feedback and ask if people are really coming. It is also a good thing to have some kind of program as a backup even if it is an unconference.


It was fun co-organising this with Rolf van de Krol and we will be doing this again next year!

Drupal data visualisation

Via PBS.org I found dataviz.org A website funded by Knight with a data visualization toolkit called VIDI.

I love good visualisations of data. And while most of the modules that are available are not that shocking, but the fact that one can use this as SAAS or download the modules and drop them on your own site, gives the power of data visualization to the masses.

Great work and I expect to see a lot more data and presentation of data on the web. Many small eyes for a better vision :-)

ooh, and please put these modules on d.o

How to mount an EXT2 or EXT3 (linux) disk under Mac OS-X


Mac OSX. A powerful open Unix with a cool interface and a very closed philosophy behind it. If Steve thought it was not needed, it is not in the system. So mounting an external harddisk formatted with EXT2 or EXT3 (journaling mostly Linux filesystem) on a Mac is not an option... By default. Because a couple of mouseclicks and a Unix command made it possible or me to mount my external EXT3 formatted harddisk on my iMac.

Start with MacFuse and download it. Macfuse is a very powerfull framework that makes it possible to mount all kind of drives; from amazon S3 to SSH (scp) mounted disk. And it is also plugable so once you have installed it, download fuse-ext2. Do not be fooled by the name, it can mount ext3 disk as well.

Mount an EXT3 disk on Mac OSX

Once you have both installed, open a terminal and type for example:

mkdir /Volumes/temp1TB
This is needed to make a volume that is mounted. In my case I wanted temporary to mount a 1 TByte external USB disk, hence the name.

I only needed to get data off the disk , so to be sure I mounted it Read Only. To find what device name your disk is using, best to power of the disk and press [tab] twices to see what devices are in /dev/. Now power the disk, wait and redo to see what drives have been added. IN my case it was disk2s1

fuse-ext2 /dev/disk2s1 /Volumes/temp1TB/ -o ro

And you now have mounted a EXT2 or EXT3 formatted disk under /Volumes/temp1TB

Note that Macfuse can do lots of other stuff as well, see the video! Happy hacking.

XML feed