Smart guys, great life, cool technology.

Last week, I had the pleasure of attending a development meeting in Stuttgart, Germany organized by the folks I work for. It really had the atmosphere of a small DrupalCon or similar FOSS conference -- a lot of intense thinking and discussion, but a lot of fun and really cool stuff at the same time.

Since some of the stuff we worked on is not ready for public consumption (though most will actually be contributed to the open source community eventually), I'll not write about it now.

Module plug-ins

I implemented a custom module for my employer to do real-time search transactions against a remote web service. Then I started to think about creating another one for a similar transaction against a different remote service. And I knew there would be more to come.

The module is pretty basic on the Drupal side. Present a form, do the lookup on submit, output the results if any followed by another form. All of that boilerplate would be the same between such modules above. Only the form and the output might vary a bit, and the ultimate backend data source would be different.

Split framework and core modules into new repositories

Based on a suggestion by Robert Douglass that the poll module be removed from core, and the follow up by Gerhad Killesreiter that perhaps the archive and blog modules should likewise be removed, I posted an old idea I had about how to provide better support for important modules and more diverse use of Drupal:

Moving modules out of core often means they fall of the face of the earth and no longer get support and updates. That's not good.

May Day at Drupal

Happy May Day with 2 big announcements from the Drupal community. First, the long-awaited release of Drupal 4.7.0 will make many a web site developer happy. Growth in usage and development has increased exponentially in the past 18 months, and now is the time to join the growing ranks of those who use, implement, customize and develop Drupal. Second, the official kick-off of the Drupal Google Summer of Code program applications.

Drupal in the corporate environment

I'm using Drupal as my framework to develop a whole bunch of web applications for my employer. For the most part, it has been really nice. There is a tremendous amount of leverage available by having so many parts of a web application already built for you.

Syndicate content