We had been looking for a "Content Management System" for quite a while, and one of our employees discovered Drupal while researching CMS software on the web. Drupal appeared to be much more flexible than PHP Nuke, which we were using, and the more we looked at it the more impressed we became. At that time all of the features we thought we would need, except one, which we decided to write a module to provide, were on the table to be implemented in the next Drupal release.
We have successfully pulled together the logistics, funding, and developer support needed to hold our first worldwide Drupal conference this year. Please visit the event details page for more information, and feel free to discuss the event in this forum.
Last year around New Year we had an interesting thread where I asked people to look back at 2003 and to share some predictions for 2004. Let's take a moment to look at these predictions, to reflect on 2004 and to make some predictions for 2005. What are the Drupal highlights of 2004 and what lies ahead for Druplicon in 2005?
A second round of Drupal quickies for those who don't have the time to keep on top of all the recent happenings in Drupal land. Just don't get used to them.
Over the past few months, the spam module has evolved from a simple idea to a fully functional collection of tools that can automatically deal with spam comments and other spam content posted to a Drupal powered website. The module currently provides four methods for detecting spam: a trainable Bayesian filter, support for manually entered custom filters, the ability to count number of links in content, and detection of content posted from open email relays.
All Drupal handbook contributors have been generous with their time in developing documentation for others to use in the spirt of open source. Drupal needs your help for just a moment with another task: approving a formal, copyleft licensing agreement for the Drupal handbook. A copyleft license would
make clear that Drupal community members can use the documentation in the Drupal handbook in other contexts, such as revising and developing site specific help docs.
allow the integration of already existing Drupal documentation being developed outside of drupal.org by Bryght, CivicSpace, and others.
eliminate potential legal conflicts over rights of use.
Thus, the Drupal handbook is moving to a Creative Commons Attribution-ShareAlike 2.0 license. This will allow anyone to copy, modify, and distribute revised documentation from the Drupal handbook as long as any copy or new version is released under the same license and attributes drupal.org as the original source.
