The drop is always movingYou know that saying about standing on the shoulders of giants? Drupal is standing on a huge pile of midgetsAll content management systems suck, Drupal just happens to suck less.Popular open source software is more secure than unpopular open source software, because insecure software becomes unpopular fast. [That doesn't happen for proprietary software.]Drupal makes sandwiches happen.There is a module for that

Breakthrough in unit testing on the Paris Code Sprint day 1

Submitted by nk on Sun, 2008-04-20 07:47

As numerous others are blogging about all that's done, I can concentrate on one thing: unit testing. As the unit testing plan on Drupal.org says

To perform unit testing each function needs to be isolated from all other functions. To do this all "sub calls" to other drupal functions need be located and each drupal function needs to be overridden to return a static value. The current plan is to use runkit.

.

Drupal is not a simple system to theme (even for Monsters)

Submitted by nk on Mon, 2008-04-14 22:33

And because of that we need Drupal specific theme sites like http://www.topnotchthemes.com and not generic template sites like Template Monster selling you an oversimplified template that's so simplified it's unusable.

Edit: oScommerce users have already been burned. Beware!

We love contrib authors

Submitted by nk on Thu, 2008-04-10 15:17

We all make mistakes; that's how we learn. Sometimes, though, we need someone to point out our mistakes, to sift through the chaos that is Drupal's contributions repository. Inspired by jpoesen's comment on Morbus's code quality entry, Morbus and I have taken up the task of giving some tough love to Drupal's greatest strength: the army of developers using its APIs. Want your own code publicly reviewed?

To make Drupal 7 the best release ever

Submitted by nk on Tue, 2008-04-08 21:27

If you suppose that Drupal growth is linear (it was always faster than that) and then crunch the numbers in webchick's Drupal 6 announcement then you will quickly see that we will need to deal with about 1200 contributors and 20000 patches for Drupal 7. If we want to keep up Drupal quality this needs automated testing. We are past the point where a few fanatics (catch, webernet and webchick, mostly) can click around to find obvious glitches.

On volunteers

Submitted by nk on Sun, 2008-04-06 16:20

This is a repost of deborahSusan Clarkson's mail to the Summer of Code mentors list (reposted with permission, of course):

Having worked as a volunteer and with volunteers for the past 30 years, there is a myriad of reasons that motivate people to get involved. Most are motivated by a combination of factors.

Those motivated by passion, as Karoly mentioned, are willing to go above and beyond. Passion drives them to overcome their shortcomings, and they accomplish more than one might expect.

The single biggest problem with Drupal

Submitted by nk on Wed, 2008-04-02 08:20

Reviewers. More precisely, the lack of them. People come to me months after a release and complain that they do not like how feature X is implemented. Others complain that patches in core queue just languish and they move to contrib instead where they can achieve something. This in itself is responsible for the quality of contrib -- they can achieve something because there commits happen without peer reviews. Here is a simple rule of thumb: if you spend a day creating a Drupal site, spend one hour on reviewing patches related to the functionality you just touched be it contrib or core.

Testing status

Submitted by nk on Tue, 2008-04-01 15:39

We have a slimmed down version of SimpleTest 1.0.1beta2 in my repository ( https://4si.devguard.com/svn/public/simpletest readable by anonymous, get commit rights by contacting me ). The browser now supports uploads. Now every tests starts from a fresh default.profile Drupal install. There were serious cleanups. I expect simpletest to be submitted for core inclusion this weekend. Remaining tasks are more cleanup and more slimming down and updating the slimmed down code to RC1.

It's not just developers

Submitted by nk on Thu, 2008-03-27 14:15

Today I read a post on Drupal Planet urging you to "place a friendly popup request for IE6 users to upgrade their browsers". Consider that Microsoft already pushed this upgrade, hard, and if someone is on IE6 still it very well can be that it's not her own decision but her IT people. There are bank applications that are broken with IE7. So, while it is true that we have every reason to hate IE6 pushing your visitors around might not be the best idea.

print_r is your friend?

Submitted by nk on Wed, 2008-03-26 06:05

Someone said this in #drupal today. I long wanted to blog about this. I never use print_r. There is no need for it, var_export is far superior IMO -- if I need to write a quick script which actually does something on the data, I can copypaste the output into PHP code. Little but annoying things like escaping apostrophes are handled too, so it's even useful for dumping strings. Of course, var_dump is also useful as that dumps type info -- how cool it would be if it would do that in a PHP comment and then it would also render valid PHP code as debug output.

Testing status

Submitted by nk on Wed, 2008-03-19 08:55

I will report approx weekly here. I have written a cURL, DOM and SimpleXML based browser instead of the sockets-based, PHP4-compatible Simpletest browser. This lets us inherit from unit_tester.php instead of web_tester.php, removing lots of code. I strive to finish it within a few days. Things you can help include making Simpletest to always start with a clean state, a new set of prefixed tables, see the issue for more.

User login