Can anyone give some really good reasons NOT to use Drupal as the sturcture for my school district's Intranet?

Also, does anyone know where else I can post this question to get good feedback?

Gallery 1.3.3 has now been ported to Drupal and released as a module. This integrates into the Drupal user permissions system, and offers simple user-management for creation/addition/admin of galleries and photos. You can bulk-upload photos using zip files, view slideshows (with nifty cross-fade transition effects in Internet Explorer) and take advantage of many of the other cool features of Gallery.

It's working with the current Drupal release (version 4.1.0), and you can grab it from the downloads page.

Nearly everything works, but there are certain minor limitations due to the way Drupal and Gallery are implemented. Please see the README for details and for more information.

I just wanted to begin with a short thank-you for the work that's already been done on this impressive CMS. I've been working with *phpNuke for a little more than a year, however even with the eventual release of 6.5, I find there's still a lot I wish Nuke could do that can't be done without substantial modification. I've been pouring over the package and it's add-ons the last couple of days and learning to use them and I'm impressed by the flexibility and overall organization, not to mention a level of minimalism that's quite refreshing after a year of playing with Nuke and it's descendants.

*Shrug* Even if I find some glaring issue that completely prevents me from putting the package into production on my site, it's worth saying that I still would have had a great time just tinkering with the software and learning to use it (and I don't really see any glaring issues lurking around the corner). This is the coolest re-thinking of the "dynamic content management system" I've come across since I first got Nuke to work, so many months ago.

And credit where it's due: I still like Nuke a great deal and wouldn't hesitate to use it again under different circumstances. It just seems to be headed in a direction that's leaving me behind these days. ;(

Drupal 4.1.0 is now available.

This release adds support for user profiles, comment moderation, improved forums, an auto-throttle congestion control mechanism, improved statistics tracking, paging, various performance improvements, and much more.

The source code is available at:

http://www.drupal.org/drupal/drupal-4.1.0.tgz

For bug reports or future features use the project page:

http://www.drupal.org/module.php?mod=project

For support try the forums or the mailing lists:

http://www.drupal.org/module.php?mod=forum&tid=1
http://www.drupal.org/node.php?id=322

Drupal documentation:

http://www.drupal.org/node.php?id=253

There's a new version of the import module available for testing. In this implementation both feeds and items are nodes. It is able to read RSS 0.9x, 1.0 and 2.0 and has support for some DC items, the SY module and the content:encoded stuff. In addition to that it also makes use of RSS 2.0's guid and comments elemens (and some more). Adding a feed is as simple as supplying the url and all the other options will be filled in automagically. There's also an option to promote news items automatically .

It needs (lots of) testing and bugs fixed, while some features still need to be implemented. I need some help of taxonomy specialists to find a way to set taxonomy terms on items automatically. When a feed is administered you should be able to specify a set of taxonomy terms for the items.

If you want to test it out on your own installation read the INSTALL file carefully, as there are some important changes when using the cron.php script. You can see it in action on my test site.

Hope you like it. Please send feature suggestions, bug fixes, comments, questions etc. to me.

Linking vocabularies to specific content types (page, story, project etc) is great, and what I think is one of the best features of drupal. However, there are definitely elements of this implementation that could be improved. Here are some of my initial usability impressions. Just some initial rapidfire thoughts, as there are some tricky issues which i am yet to fully get my head around. overall i think that drupal sets a very good standard, and i'd like to see it get better...

1) multiple selects are great, but i would find checkboxes far easier to use in forms. i think this interface for joining nodes to terms could be a little more advanced - maybe the admin could control the input type of a vocabularly- select box, radio, checkbox, etc...

2) rather than being static markers, multiple select terms could be able to be filtered - so you could combine two or three terms, and filter the content of the site from this combination, or cruise from page to page with the filter storing your settings, and loading all content based on those settings...

3) logically following on from this, there could be some capacity for assigning specific terms to certain users, this would be particularly useful for sites with magazine focused categories, where there might be individual sub-editors for different sections...

4) different vocabularies have variations in meaning and weight, it would be good to have more options for the way a specific vocabulary interacts with the content/navigation - there could be built in vocabulary types such as Subject , Section , Topic , etc... focusing on being more of a type language, rather than generic labels... just a possibility, and i really have to think it through a bit more coherently - but just thought i'd float a few things out...