Slashdot Mirror

• 3 years: Nobody thought to just "revert" the introduction of a feature and maintain the release schedule? Isn't this what project managers are around for?
• Bloat, bloat, and more bloat: Rather than elaborate on this, I'll just list the compressed size of the last three major releases: Drupal 5 (750KB), Drupal 6 (1.06MB), Drupal 7 (2.6MB).
• Most of the contributed modules still haven't seen a Drupal 7 release. Many of them seem to have been party to a "pledge" to time their release along with the Drupal 7 release and have reneged on it.
• The most important module outside Drupal's core release is Views which is supposedly used by at least 300000 sites. The vast majority of sites - beyond simple brochure sites - rely on Views and it has still not seen a Drupal 7 release. In other words, even with Drupal 7 being released, nobody is really using it as most developers are waiting for Views to see the light of day. Furthermore, this module, I'm told, was deemed important enough slated to be included in the core Drupal release ...
• A few years ago, when Drupal was small and flexible and touting slogans similar to we eat our own dogfood, the primary Drupal site would always run "the latest and greatest". Now, however, it's been 2 months since the release and drupal.org is still running Drupal 6 (and an outdated version at that). An integral community site, groups.drupal.org is still running Drupal 6.16 and has been pending a security update for months.

I think that I'll stop there :/ But I believe that all these issues are symptomatic of an inefficiency and backslap-happy community complacency that has crept into Drupal thanks to its recent success. The people behind Drupal seem to be busy chasing the almighty dollar and losing sight of what made the project interesting in the first place.

• 3 years: Nobody thought to just "revert" the introduction of a feature and maintain the release schedule? Isn't this what project managers are around for?
• Bloat, bloat, and more bloat: Rather than elaborate on this, I'll just list the compressed size of the last three major releases: Drupal 5 (750KB), Drupal 6 (1.06MB), Drupal 7 (2.6MB).
• Most of the contributed modules still haven't seen a Drupal 7 release. Many of them seem to have been party to a "pledge" to time their release along with the Drupal 7 release and have reneged on it.
• The most important module outside Drupal's core release is Views which is supposedly used by at least 300000 sites. The vast majority of sites - beyond simple brochure sites - rely on Views and it has still not seen a Drupal 7 release. In other words, even with Drupal 7 being released, nobody is really using it as most developers are waiting for Views to see the light of day. Furthermore, this module, I'm told, was deemed important enough slated to be included in the core Drupal release ...
• A few years ago, when Drupal was small and flexible and touting slogans similar to we eat our own dogfood, the primary Drupal site would always run "the latest and greatest". Now, however, it's been 2 months since the release and drupal.org is still running Drupal 6 (and an outdated version at that). An integral community site, groups.drupal.org is still running Drupal 6.16 and has been pending a security update for months.

I think that I'll stop there :/ But I believe that all these issues are symptomatic of an inefficiency and backslap-happy community complacency that has crept into Drupal thanks to its recent success. The people behind Drupal seem to be busy chasing the almighty dollar and losing sight of what made the project interesting in the first place.

• 3 years: Nobody thought to just "revert" the introduction of a feature and maintain the release schedule? Isn't this what project managers are around for?
• Bloat, bloat, and more bloat: Rather than elaborate on this, I'll just list the compressed size of the last three major releases: Drupal 5 (750KB), Drupal 6 (1.06MB), Drupal 7 (2.6MB).
• Most of the contributed modules still haven't seen a Drupal 7 release. Many of them seem to have been party to a "pledge" to time their release along with the Drupal 7 release and have reneged on it.
• The most important module outside Drupal's core release is Views which is supposedly used by at least 300000 sites. The vast majority of sites - beyond simple brochure sites - rely on Views and it has still not seen a Drupal 7 release. In other words, even with Drupal 7 being released, nobody is really using it as most developers are waiting for Views to see the light of day. Furthermore, this module, I'm told, was deemed important enough slated to be included in the core Drupal release ...
• A few years ago, when Drupal was small and flexible and touting slogans similar to we eat our own dogfood, the primary Drupal site would always run "the latest and greatest". Now, however, it's been 2 months since the release and drupal.org is still running Drupal 6 (and an outdated version at that). An integral community site, groups.drupal.org is still running Drupal 6.16 and has been pending a security update for months.

I think that I'll stop there :/ But I believe that all these issues are symptomatic of an inefficiency and backslap-happy community complacency that has crept into Drupal thanks to its recent success. The people behind Drupal seem to be busy chasing the almighty dollar and losing sight of what made the project interesting in the first place.

• 3 years: Nobody thought to just "revert" the introduction of a feature and maintain the release schedule? Isn't this what project managers are around for?
• Bloat, bloat, and more bloat: Rather than elaborate on this, I'll just list the compressed size of the last three major releases: Drupal 5 (750KB), Drupal 6 (1.06MB), Drupal 7 (2.6MB).
• Most of the contributed modules still haven't seen a Drupal 7 release. Many of them seem to have been party to a "pledge" to time their release along with the Drupal 7 release and have reneged on it.
• The most important module outside Drupal's core release is Views which is supposedly used by at least 300000 sites. The vast majority of sites - beyond simple brochure sites - rely on Views and it has still not seen a Drupal 7 release. In other words, even with Drupal 7 being released, nobody is really using it as most developers are waiting for Views to see the light of day. Furthermore, this module, I'm told, was deemed important enough slated to be included in the core Drupal release ...
• A few years ago, when Drupal was small and flexible and touting slogans similar to we eat our own dogfood, the primary Drupal site would always run "the latest and greatest". Now, however, it's been 2 months since the release and drupal.org is still running Drupal 6 (and an outdated version at that). An integral community site, groups.drupal.org is still running Drupal 6.16 and has been pending a security update for months.

I think that I'll stop there :/ But I believe that all these issues are symptomatic of an inefficiency and backslap-happy community complacency that has crept into Drupal thanks to its recent success. The people behind Drupal seem to be busy chasing the almighty dollar and losing sight of what made the project interesting in the first place.

Look at who started using Drupal in the last year or two: The Economist, The Grammys, Fast Company, The Examiner, House.gov (and all ~535 house websites) recently moved to Drupal, Energy.gov, WhiteHouse.gov, and here's a list of some 120 national governments using Drupal.

But hey, Drupal only has 2% market share of all sites on the web, is being adopted by government and corporate organizations at a maddening pace, and just had their first major release in 3 years. There's no reason why this Drupal shit should be discussed on Slashdot.

Careful what you wish for, you just might get it.

There are some movements in Drupal to become more of a framework, such as entities and features, and of course there's always drush. This article discusses the parallels between Drupal programming and OOP, interesting read for programmers new to Drupal.

There are some movements in Drupal to become more of a framework, such as entities and features, and of course there's always drush. This article discusses the parallels between Drupal programming and OOP, interesting read for programmers new to Drupal.

There are some movements in Drupal to become more of a framework, such as entities and features, and of course there's always drush. This article discusses the parallels between Drupal programming and OOP, interesting read for programmers new to Drupal.

There are some movements in Drupal to become more of a framework, such as entities and features, and of course there's always drush. This article discusses the parallels between Drupal programming and OOP, interesting read for programmers new to Drupal.

If you're just going to throw up some content with ads for a few $$, you'd be better advised to go with WordPress.

WordPress out of the box is far more featureful than Drupal out-of-box.

Granted, you can add (then configure) a huge bunch of Drupal modules to get the same functionality, but your goal is just adding content, right?

Oh, and WordPress handles both blog entries (chronological content), and pages at a specified URL (like /about, /contact, etc.)

And WP has far more (and nicer) themes (free and paid) than Drupal.

WordPress is better, easier, lighter than Drupal:
Why Drupal Devs Should Fear WordPress

WordPress is Better, Drupal Devs Take Note

It has no user permissions system, whereas Drupal follows the *nix perms model

Uh what? Drupal permissions are more like capabilities. Modules publish them under hook_perm and then test for them later. Users have roles but they're not quite the same thing as groups. If you want role-based access control you have to add a module. Which is not to say that Drupal is not light-years ahead of Wordpress, but it has more complicated access control than Unix (for good and ill.)

This book was clearly rushed to market for two reasons:

1. The Drupal coding standards are not adhered to when every single line should have been poured over for 100% accuracy, given it is such an important part of "the Drupal way" and how this will be many developer's first book.
2. One of the most important new concepts of Drupal 7, Entities, is not really given any coverage.

Shouldn't Wikimedia accept WebM as well then?

According to the Commons:Video page, "WebM support will likely be added in the future. See this bug report for its current status."

The bug report described is #23888, and was last updated on 2010-08-24 -- over 5 months ago. It appears that there needs to just be some hacking done on MediaWiki to support it.

I think that this bug report is a perfect example of what needs to be done to give WebM the traction to take the upper hand in web video. Do you want support for WebM video in Gallery2 or Gallery3? Do you want support for WebM video in MediaWiki? How about Drupal, Plone, or Joomla? Or how about just plain-old mime-type support for WebM in Ubuntu?

Yes, there are projects underway to support WebM in these FOSS projects, but nearly all of them aren't ready for daily use yet. If we want to see WebM deployed as the video format of choice for the web, we really need to step up and make sure that WebM is as supported as a video format as PNG and JPEG are supported as image formats.

I guess things like hook_comment_update, hook_comment_insert are not good enough for you, you'd rather have a conspiracy theory that Drupal is somehow hiding its api ala Microsoft.

http://api.drupal.org/api/drupal/modules--comment--comment.api.php/function/hook_comment_insert/7
http://api.drupal.org/api/drupal/modules--comment--comment.api.php/function/hook_comment_update/7

I guess things like hook_comment_update, hook_comment_insert are not good enough for you, you'd rather have a conspiracy theory that Drupal is somehow hiding its api ala Microsoft.

http://api.drupal.org/api/drupal/modules--comment--comment.api.php/function/hook_comment_insert/7
http://api.drupal.org/api/drupal/modules--comment--comment.api.php/function/hook_comment_update/7

From the front page:

Sites Made With Drupal
http://drupal.org/cases

Have you looked at Drupal lately, or even understand how it works? I don't see any other cms that is more development friendly. Need to create a new page layout? Use panels and views. Need more help on modifying a theme template? Try contemplate. The webform module makes forms easy, but if you learn a little bit about the form API and use ctools, it's not bad. Oh and you need to push all your changes from one staging site to another? Try features.

Have you looked at Drupal lately, or even understand how it works? I don't see any other cms that is more development friendly. Need to create a new page layout? Use panels and views. Need more help on modifying a theme template? Try contemplate. The webform module makes forms easy, but if you learn a little bit about the form API and use ctools, it's not bad. Oh and you need to push all your changes from one staging site to another? Try features.

Have you looked at Drupal lately, or even understand how it works? I don't see any other cms that is more development friendly. Need to create a new page layout? Use panels and views. Need more help on modifying a theme template? Try contemplate. The webform module makes forms easy, but if you learn a little bit about the form API and use ctools, it's not bad. Oh and you need to push all your changes from one staging site to another? Try features.

Have you looked at Drupal lately, or even understand how it works? I don't see any other cms that is more development friendly. Need to create a new page layout? Use panels and views. Need more help on modifying a theme template? Try contemplate. The webform module makes forms easy, but if you learn a little bit about the form API and use ctools, it's not bad. Oh and you need to push all your changes from one staging site to another? Try features.

Have you looked at Drupal lately, or even understand how it works? I don't see any other cms that is more development friendly. Need to create a new page layout? Use panels and views. Need more help on modifying a theme template? Try contemplate. The webform module makes forms easy, but if you learn a little bit about the form API and use ctools, it's not bad. Oh and you need to push all your changes from one staging site to another? Try features.

Have you looked at Drupal lately, or even understand how it works? I don't see any other cms that is more development friendly. Need to create a new page layout? Use panels and views. Need more help on modifying a theme template? Try contemplate. The webform module makes forms easy, but if you learn a little bit about the form API and use ctools, it's not bad. Oh and you need to push all your changes from one staging site to another? Try features.

Very much so. Facebook could have been implemented out of ancient technologies years ago, but it wasn't and now we have Facebook. There's no use crying about it; instead, the whiners should work on the next big thing.

Ultimately I would like to see some sort of system for federation of miscellaneous content brokered peer-to-peer but protected by strong crypto handed out by authorities, yet where all of us are authorities, implementing a web of trust. Presumably you'd have some kind of scoring system to determine levels of trust and you could share (or restrict) content according to scoring and other criteria. New content would simply be hosted via HTTP, and syndicated via RSS. It seems like all of the tools to do this already exist and it is left only to assemble them all.

Diaspora seems like an attempt to do this by reusing some wheels and reinventing others. But since statistically nobody is using it, perhaps another approach is needed. Probably a good proof of concept could be created using one of the typical CMSes like Wordpress or Drupal, using password authentication and the existing syndication and access control facilities. I don't know Wordpress well but it seems like something you could do in Drupal by reusing existing modules and producing some new GUIs. For access control it seems like you would want to utilize either node relationships or something like community tags. Or even Node Relativity Access and just allow users to create group nodes only they can see, and then make content the child of the groups for access control? There's a bit of code to be written there.

Very much so. Facebook could have been implemented out of ancient technologies years ago, but it wasn't and now we have Facebook. There's no use crying about it; instead, the whiners should work on the next big thing.

Ultimately I would like to see some sort of system for federation of miscellaneous content brokered peer-to-peer but protected by strong crypto handed out by authorities, yet where all of us are authorities, implementing a web of trust. Presumably you'd have some kind of scoring system to determine levels of trust and you could share (or restrict) content according to scoring and other criteria. New content would simply be hosted via HTTP, and syndicated via RSS. It seems like all of the tools to do this already exist and it is left only to assemble them all.

Diaspora seems like an attempt to do this by reusing some wheels and reinventing others. But since statistically nobody is using it, perhaps another approach is needed. Probably a good proof of concept could be created using one of the typical CMSes like Wordpress or Drupal, using password authentication and the existing syndication and access control facilities. I don't know Wordpress well but it seems like something you could do in Drupal by reusing existing modules and producing some new GUIs. For access control it seems like you would want to utilize either node relationships or something like community tags. Or even Node Relativity Access and just allow users to create group nodes only they can see, and then make content the child of the groups for access control? There's a bit of code to be written there.

Very much so. Facebook could have been implemented out of ancient technologies years ago, but it wasn't and now we have Facebook. There's no use crying about it; instead, the whiners should work on the next big thing.

Ultimately I would like to see some sort of system for federation of miscellaneous content brokered peer-to-peer but protected by strong crypto handed out by authorities, yet where all of us are authorities, implementing a web of trust. Presumably you'd have some kind of scoring system to determine levels of trust and you could share (or restrict) content according to scoring and other criteria. New content would simply be hosted via HTTP, and syndicated via RSS. It seems like all of the tools to do this already exist and it is left only to assemble them all.

Diaspora seems like an attempt to do this by reusing some wheels and reinventing others. But since statistically nobody is using it, perhaps another approach is needed. Probably a good proof of concept could be created using one of the typical CMSes like Wordpress or Drupal, using password authentication and the existing syndication and access control facilities. I don't know Wordpress well but it seems like something you could do in Drupal by reusing existing modules and producing some new GUIs. For access control it seems like you would want to utilize either node relationships or something like community tags. Or even Node Relativity Access and just allow users to create group nodes only they can see, and then make content the child of the groups for access control? There's a bit of code to be written there.

I've been keeping up with the indispensible help of drupal.org and the coder module!

So are stream wrappers a pretty big topic in the book and if so is this a dealbreaker for buying the book?

Why not try reading the fine issue? They're just going to change them to default to remote type instead of local type. A tiny change really, which needs to be rested regressively hence becoming a big deal in the queue.

For managing lots of Drupal sites (even across multiple servers) try the Aegir project, its close to a 1.0 release but is stable enough for production use now.

http://groups.drupal.org/aegir-hosting-system

Kind of related, check out Drush, which lets you manage drupal sites from a linux command line & drush_make which lets you create make files for drupal sites.

Drupal is very powerful, but its not for the faint-hearted.

• "Do not enable the management menu by default". This is about removing some on-screen duplication that wastes pixels.
• "Cannot install on PHP 5.3.2". I have a working version on 5.3.2. This is a false positive - something to do with the reporters set up. D7 needs PHP PDO extension, which is part of the default PHP. Most likely not enabled for the person who reported the bug.
• "Links are needlessly unable to fully participate in D7 AJAX framework" Making sure that the Ajax framework is orthogonal with respect to content types, I think.
• "Security harden stream wrappers by defaulting them as remote" We worry about security. This would subject streams to the level of scrutiny that remote data is subject to. If allow_url_include in php.ini is false, then Drupal should not allow remote streams as content.
• "Skip to main content" link doesn't work correctly in the overlay" We are screen-reader friendly by default. We also have a new mode of operation - overlaying a screen with things that need to be done before you can continue with your original task. This should work for screen readers too, so the link needs to point to the 'topmost' content.
• "All fields are hidden after the administrator newly configures a view mode to not use 'default' display" Oops! It shouldn't be possible to get into a state where critical stuff seemingly disappears. A feature that's central to D7 is fields - that is, all content is extensible with new fields. It should always be possible to set fields to display correctly.
• "Some schema code incorrectly rely on the generic type instead of the engine-specific type" D7 supports storing data in different storage formats, including several database engines. There's some small inconsistency; the schema (and things that manipulate it) should use the column types specific to a particular engine - for instance it's AUTO_INCREMENT in MySQL, but Serial in PostgreSQL, and different rules apply to how each is used.
• "Clean-up the upgrade path: UPGRADE.txt" If you are upgrading from Drupal 6, we'd like it to be a smooth ride.
• "Screen reader users need a clear, quick way to disable the overlay". Not all the screen readers will like the overlay system, so there should be a ridiculously easy way to stop using overlays, which is immediately accessible from a screen reader. "Allow dashboard to limit available blocks" Users can configure their own dashboard, but not everything that is displayable makes sense on the dashboard page, so it would be sensible to limit what can be displayed. The User Interface for this is being tested.

And I'd like to take this opportunity to advertise - Drupalcon Chicago will be in March 2011. And if you are in Europe, I have it on reasonably good authority that you can look forward to the announcement of the location of the Autumn conference either later this week or next week. And this week we moved the Drupal.org site redesign live.

• "Do not enable the management menu by default". This is about removing some on-screen duplication that wastes pixels.
• "Cannot install on PHP 5.3.2". I have a working version on 5.3.2. This is a false positive - something to do with the reporters set up. D7 needs PHP PDO extension, which is part of the default PHP. Most likely not enabled for the person who reported the bug.
• "Links are needlessly unable to fully participate in D7 AJAX framework" Making sure that the Ajax framework is orthogonal with respect to content types, I think.
• "Security harden stream wrappers by defaulting them as remote" We worry about security. This would subject streams to the level of scrutiny that remote data is subject to. If allow_url_include in php.ini is false, then Drupal should not allow remote streams as content.
• "Skip to main content" link doesn't work correctly in the overlay" We are screen-reader friendly by default. We also have a new mode of operation - overlaying a screen with things that need to be done before you can continue with your original task. This should work for screen readers too, so the link needs to point to the 'topmost' content.
• "All fields are hidden after the administrator newly configures a view mode to not use 'default' display" Oops! It shouldn't be possible to get into a state where critical stuff seemingly disappears. A feature that's central to D7 is fields - that is, all content is extensible with new fields. It should always be possible to set fields to display correctly.
• "Some schema code incorrectly rely on the generic type instead of the engine-specific type" D7 supports storing data in different storage formats, including several database engines. There's some small inconsistency; the schema (and things that manipulate it) should use the column types specific to a particular engine - for instance it's AUTO_INCREMENT in MySQL, but Serial in PostgreSQL, and different rules apply to how each is used.
• "Clean-up the upgrade path: UPGRADE.txt" If you are upgrading from Drupal 6, we'd like it to be a smooth ride.
• "Screen reader users need a clear, quick way to disable the overlay". Not all the screen readers will like the overlay system, so there should be a ridiculously easy way to stop using overlays, which is immediately accessible from a screen reader. "Allow dashboard to limit available blocks" Users can configure their own dashboard, but not everything that is displayable makes sense on the dashboard page, so it would be sensible to limit what can be displayed. The User Interface for this is being tested.

And I'd like to take this opportunity to advertise - Drupalcon Chicago will be in March 2011. And if you are in Europe, I have it on reasonably good authority that you can look forward to the announcement of the location of the Autumn conference either later this week or next week. And this week we moved the Drupal.org site redesign live.

The list of issues currently blocking a release candidate is publicly available.

Strangely, considering we're a Microsoft shop where MIS people choose Microsoft becuase it stops them having to make decisions or think (something they're not too good at anyway), we have a Drupal site for our user community.

http://drupal.org/

Its quite good, basically its another CMS, so pretty much everything sharepoint does, but less oriented on being a web-based network fileshare, without folders. Its used by a couple of high-profile websites, the Economist and the White House for example.

Apparently you can connect a Drupal site to Sharepoint "back end" using its CMIS module, and there are several file management modules in addition to the basic functionality. Collaboration doesn't even need to be discussed as its what the thing was designed to do :)

The site itself has fairly good documentation, and if you wantg really good example - check out Apache or Subversion, both very comprehensively documented.

Strangely, considering we're a Microsoft shop where MIS people choose Microsoft becuase it stops them having to make decisions or think (something they're not too good at anyway), we have a Drupal site for our user community.

http://drupal.org/

Its quite good, basically its another CMS, so pretty much everything sharepoint does, but less oriented on being a web-based network fileshare, without folders. Its used by a couple of high-profile websites, the Economist and the White House for example.

Apparently you can connect a Drupal site to Sharepoint "back end" using its CMIS module, and there are several file management modules in addition to the basic functionality. Collaboration doesn't even need to be discussed as its what the thing was designed to do :)

The site itself has fairly good documentation, and if you wantg really good example - check out Apache or Subversion, both very comprehensively documented.

How about a Drupal site that can do 2.8 million page views per day? And actually the figures have been higher since with a peak of 3.4 million per day, and 92 million per month. And all that is on a single medium box.

And for the rest of the drivel in that link, how about sites like The White House using it?

My 4.5 modules worked with 4.6 with no changes. My 4.6 modules worked with 4.7 with no changes. My 4.7 modules worked with 5 with very minor changes. My 5 modules worked with 6 with very small changes. I haven't tried porting any 6 modules to 7 yet, but looking at the list of modules that already support 7, I'm not quivering with fright at the prospect.

The API is not guaranteed not to change, but a lot of people work hard to make sure that the change is evolutionary and the thousands of automated tests help to make sure that

First of all, it isn't surprising that changes from 4.5->4.6->4.7 didn't require any rewriting of modules. Only major version number change break backward compatibility. I think the change to Drupal 7 will be bigger than the previous changes. The changes to the code I've written will be anything but minor. The entire database abstraction layer is changing. No more db_fetch_object for instance, and my code has about 50 calls to that function. Also, INSERT and UPDATE db_queries will need to change as they will be handled by special functions. And that's just the database stuff. There are a lot of other functions that are changing as well, see the documentation for just some of the changes.

Drupal coding standards

Your need seems to be similar (but on a smaller scale) to what a public library uses:
- index books and magazines by title, publication date, author, keywords
- query the index
Koha is the major open source software in this area but probably too big for you. However the Wikipedia page links to others software which may be of interest:
- PhpMyBibli
- Alexandria
- OpenBiblio
- GCstar

Also I suggest you to have a look into dedicated modules for CMS platforms such as Drupal. Drupal has the eXtensible Catalog Drupal Toolkit which probably has the features you need.

Use Drupal (http://drupal.org), with Apache Solr (http://lucene.apache.org/solr/ and http://drupal.org/project/apachesolr) for indexing. At the last Drupalcon (SF 2010), there were even presentations by library staff related to article indexing, etc. Some handy resources, but there are far more, this was just a 1m search based on the conference alone... http://sf2010.drupal.org/conference/sessions/build-powerful-site-search-user-friendly-easy-install-search-lucene-api-module , http://sf2010.drupal.org/conference/sessions/how-build-jobs-aggregation-search-engine-nutch-apache-solr-and-views-3-about , http://sf2010.drupal.org/conference/sessions/case-studies-non-profits-jane-goodall-and-musescore , http://sf2010.drupal.org/conference/sessions/case-studies-academia-drupal-asu-john-hopkins-knowledge-health

Use Drupal (http://drupal.org), with Apache Solr (http://lucene.apache.org/solr/ and http://drupal.org/project/apachesolr) for indexing. At the last Drupalcon (SF 2010), there were even presentations by library staff related to article indexing, etc. Some handy resources, but there are far more, this was just a 1m search based on the conference alone... http://sf2010.drupal.org/conference/sessions/build-powerful-site-search-user-friendly-easy-install-search-lucene-api-module , http://sf2010.drupal.org/conference/sessions/how-build-jobs-aggregation-search-engine-nutch-apache-solr-and-views-3-about , http://sf2010.drupal.org/conference/sessions/case-studies-non-profits-jane-goodall-and-musescore , http://sf2010.drupal.org/conference/sessions/case-studies-academia-drupal-asu-john-hopkins-knowledge-health

Use Drupal (http://drupal.org), with Apache Solr (http://lucene.apache.org/solr/ and http://drupal.org/project/apachesolr) for indexing. At the last Drupalcon (SF 2010), there were even presentations by library staff related to article indexing, etc. Some handy resources, but there are far more, this was just a 1m search based on the conference alone... http://sf2010.drupal.org/conference/sessions/build-powerful-site-search-user-friendly-easy-install-search-lucene-api-module , http://sf2010.drupal.org/conference/sessions/how-build-jobs-aggregation-search-engine-nutch-apache-solr-and-views-3-about , http://sf2010.drupal.org/conference/sessions/case-studies-non-profits-jane-goodall-and-musescore , http://sf2010.drupal.org/conference/sessions/case-studies-academia-drupal-asu-john-hopkins-knowledge-health

Use Drupal (http://drupal.org), with Apache Solr (http://lucene.apache.org/solr/ and http://drupal.org/project/apachesolr) for indexing. At the last Drupalcon (SF 2010), there were even presentations by library staff related to article indexing, etc. Some handy resources, but there are far more, this was just a 1m search based on the conference alone... http://sf2010.drupal.org/conference/sessions/build-powerful-site-search-user-friendly-easy-install-search-lucene-api-module , http://sf2010.drupal.org/conference/sessions/how-build-jobs-aggregation-search-engine-nutch-apache-solr-and-views-3-about , http://sf2010.drupal.org/conference/sessions/case-studies-non-profits-jane-goodall-and-musescore , http://sf2010.drupal.org/conference/sessions/case-studies-academia-drupal-asu-john-hopkins-knowledge-health

Use Drupal (http://drupal.org), with Apache Solr (http://lucene.apache.org/solr/ and http://drupal.org/project/apachesolr) for indexing. At the last Drupalcon (SF 2010), there were even presentations by library staff related to article indexing, etc. Some handy resources, but there are far more, this was just a 1m search based on the conference alone... http://sf2010.drupal.org/conference/sessions/build-powerful-site-search-user-friendly-easy-install-search-lucene-api-module , http://sf2010.drupal.org/conference/sessions/how-build-jobs-aggregation-search-engine-nutch-apache-solr-and-views-3-about , http://sf2010.drupal.org/conference/sessions/case-studies-non-profits-jane-goodall-and-musescore , http://sf2010.drupal.org/conference/sessions/case-studies-academia-drupal-asu-john-hopkins-knowledge-health

Why aren't newspaper come together and build or enhance an open source software, just for the need of the newspaper industry?

For the Web: http://groups.drupal.org/newspapers-on-drupal would be one example; lots of contributions to the open-source Drupal project from newspapers and broadcasters. Django and Zope, both of which were created at newspaper companies, also are examples.

For print: JRC is pioneering. Printies are technologically conservative (otherwise they wouldn't be printies) and print IT departments tend to be defensive. I don't know how bad things were at Journal Register when John Paton took over, but it's not unusual to see daily newspapers dependent on an OS 9 Macintosh that's driving an imagesetter.

What Paton is trying to do is not really about open source or free software in the RMS definition, but more about shaking up all the assumptions in a company that needed a good shake.

This isn't a one-day thing.

I love how in Drupal everything is simply a node, so I can create products to sell, and using views make some decent categories, create a side-bar with top sellers, create an news feed of new products, etc.

Except that in basic drupal, not everything is a node. For example, taxonomy elements are not node objects unless you install the category module, which is beta code. Users are not node objects, and the user node module seems to be gone these days. Themes and modules are not node objects, though they richly deserve to be. If you want everything to be a node, you need to try The Everything Engine. And then you need to suffer with mod_perl.

When i used a store module, I am creating products, not content.

Is that why the default menu options created for adding content are in a menu called "Create Content"?

Drupal has been providing open-source community plumbing for years.

Dave Cole, Deputy Director for Technology at the White House Office of New Media, @ DrupalCon SF this month:
Open Source in Government Keynote

This is one of three possibilities. The other two being, they started using the code from open sourced modules and thus are still bound by that license or they contracted the work out and the copyright was reassigned to the whitehouse, in which case they can license it.

Drupal considers modules derivative works, so modules must be licensed under the GPL. Drupal Licensing FAQ. Not sure if it'd hold up in court, but thats what the Drupal community understands as their obligations.

There's a discussion here: http://drupal.org/node/30708

If being GPL is a problem for a piece of government code, there's still no problem with a module being of a different license. The modules are not part of the Drupal distribution.

Perhaps the Drupal XML Sitemap module would help? It's just a module to implement the sitemap.xml protocol mentioned above. It'd involve messing with your setup but has the potential to save you a lot of bandwidth.