These Things Matter to Me
Tuesday, September 09, 2008
These Drupal links matter to you 20080909
- Drupal consultancy Lullabot has a new podcast out. It mostly recaps last week's Drupalcon Szeged, and is good as always.
- Oh yeah, Lullabot is the primary organizer behind a big Drupal conference, Do it with Drupal. 3 days in New Orleans in December. No BarCamp or Drupalcon, it looks to be a highly curated event, with major speakers from within and outside the Drupal community, 1000-2000 attendees (?). I'm super excited that Drupal is getting a major event like this. The Drupalcons and Drupalcamps are great, but I think this kind of context for Drupal can legitmize in some corporate environments.
- I swear I don't work for Lullabot, but another announcement related to them: There are some Lullabot Drupal workshops next week in Portland.
- BTW, Drupalcon Szeged was very well documented, often with full videos and slides from the talks. Check out the full session page with links to files and descriptions for the Drupalcon Szeged talks. Bravo to the group who ran it. I've heard only good things from those who attended, that it was a great atmosphere. Also, as somebody viewing from afar, the speed with which they've uploaded videos after the event is quite fast!
- This is interesting. Web-learning mainstay Lynda.com has Drupal training videos. As with most Lynda.com content, there are some free samples on the course page. It's great that they have some Drupal training, but it's confusing that they cover MAMP and WAMP installation, but neglect what is by far the most prominent Drupal hosting environment (or any web hosting environment): LAMP (Linux). Maybe the context is proof of concept?
Also, Lynda.com has WordPress coursework up, so Drupal is not the first open source tool to make the cut, but it's still significant that a site mostly known for teaching HTML and Final Cut Pro has Drupal videos. - LA People, DrupalCamp LA is next week, September 13th, 14th
(Very cool Drupal knitting chart by ejhogbin)
Labels: Do it with Drupal, drupal, Drupalcon, Lullabot, Lynda.com, pdx, portland, training
Monday, September 08, 2008
How to install the Python prerequisites for the Memetracker Drupal module
1. Make sure you have all "normal" LAMP and Linux utilities installed for your typical Drupal install.
How to install the Python prerequisites for the Memetracker Drupal module.
Usually the installation of Drupal modules is pretty straightforward:
- Download module to modules/
- Uncompress
- Enable
- Configure
- Profit
But the Memetracker module is a bit different, requiring a bunch of Python stuff, and ideally, "root" on your server. It's not that hard to set up, but if you're not used to installing stuff outside of the Druapl-verse, these notes might help you.
(These instructions are for Ubuntu Hardy Heron. The steps are likely very similar on other Debian-based distributions, including earlier versions of Ubuntu.
I've also successfully installed Memetracker on Centos 5.x/Redhat Enterprise Linux 5.x. I have a document for that coming soon, though the packages and steps are very similar, and you could extrapolate these notes and apply to other Linux versions.)
Most of you should skip to step 2, as you probably already have Drupal running..
1a. Install the LAMP stuff, mail server stuff that Drupal requires.
# apt-get install apache2 php5 libapache2-mod-php5 php5-mysql mysql-server php5-gd postfix
(Note: Though Drupal core can run on PHP4, the Memetracker module *requires* PHP5, so that's what we're using here. You don't have to go out of your way to get this on Hardy Heron, but there is a small possibility some of you went out of your way to get PHP4, so I'm steering you towards PHP5 here.)
1b. Though not required to run Drupal, these additional packages make life much easier, and it's just a matter of time before you miss them:
# apt-get install openssh-server wget build-essential groff-base man-db unzip
2. Unlike most Drupal setups, you also need to have some Python resources handy to run Memetracker.
2a. The first bunch of Python tools already have nice Ubuntu packages already made up for you.
# apt-get install python-numpy python-numeric python-dev python
2b. Pyclust doesn't have an Ubuntu package made for it. We need to compile it from source (There will be a python-cluster package in the next Ubuntu version, Intrepid Ibex.)
Get the source:
# wget http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/cluster/cluster-1.41.tar.gz
(Note, this is the newest version as of 20080908. Please check http://bonsai.ims.u-tokyo.ac.jp/~mdehoon/software/cluster/software.htm for newest version.)
Uncompress the source:
# tar -xvzf cluster-1.41.tar.gz
Now install it:
# cd cluster-1.41
# python setup.py install
You now have all your Python stuff installed.
Let's verify it works:
# python
>> from Pycluster import *
(You will get your Python prompt back if you have your Python stuff installed correctly.)
That's it. You now have your environment ready for Memetracker. There's lots of other stuff you can do to optimize your system for Memetracker, and I have some additional Memetracker documentation coming up. However I noticed an immediate need for this Python stuff to be written down in a step-by-step manner, as many Drupal folks don't usually have to do so much Python/Linux stuff.
Labels: drupal, linux, memetracker, python, sysadmin, ubuntu
Tuesday, April 15, 2008
Video: Drupal vs. WordPress. Presentation given at LUGRadio Live USA, 2008. San Francisco, CA
This weekend Selena and I spoke at the charming and hospitable LUG Radio Live USA, in San Francisco, CA. The topic was Choosing between Drupal and WordPress. It was very civil. A few people have asked for the video of our presentation, so I've uploaded it above with a Flash embed. More ambitious full-on video file to come later.
This weekend Selena and I spoke at the charming and hospitable LUG Radio Live USA, in San Francisco, CA. The topic was Choosing between Drupal and WordPress. It was very civil. A few people have asked for the video of our presentation, so I've uploaded it above with a Flash embed. More ambitious full-on video file to come later.
Labels: cms, drupal, lug radio live, lugradio, lugradiolive, lugradiolive2008, open source, usability, wordpress
Wednesday, April 09, 2008
So much dramz. Choosing between WordPress and Drupal.
Selz and I are giving a presentation on choosing between WordPress and Drupal at LUG Radio Live in San Francisco this weekend. She and I agree to disagree.
Selz and I are giving a presentation on choosing between WordPress and Drupal at LUG Radio Live in San Francisco this weekend. She and I agree to disagree.
Labels: choice, dilemma, drupal, lug radio live, lugradio, wordpress
Wednesday, March 19, 2008
Help artists be artists. A defense of drupalmodules.com
The myth of centralization, the reality of distributed information.
If the Internet has taught us anything, it's that that:
This applies to all sorts of activities and information, but today I'm talking about software reference material, in specific, Drupal reference material.
Drupal is an incredibly popular content management system framework. You can call it other things. Drupal helps you make websites.
Drupal's fight to centralize
I'm relatively new to Drupal, quite like it, and recommend it frequently. That said, I have some issues with it, and among them what seems like peer pressure in the Drupal community to not create, or feel self-conscious about creating, Drupal resources outside of Drupal.org. There is a surprising lack of websites about Drupal given how popular it is. This is thoroughly confusing as everybody knows that with both proprietary and open source software, bands, artists, etc... having a breadth of resources/fan sites/ forums is a sign of a healthy, thriving community/market/mindshare. There's a time and a place for "many eyes" and joining large group efforts (like Drupal.org) and there's a time and a place for shirking mass-meetings, votes, digging in by yourself or a few collaborators, and making something totally fresh, especially for "proof of concept." Neither approach is better or worse, but they each have their time and place, and nobody should feel guilty or self-conscious for working hard on their own and making something.
Recently a non-Drupal.org resource was created, drupalmodules.com. This has been mildly controversial within the Drupal community. Drupalmodules.com is too new for me to honestly judge on utility alone, but without a doubt, it's purpose is undeniable: navigating the world of Drupal modules is very challenging, for many different reasons. While many within the Drupal community agree there needs to be a way to sift through modules by "quality" (there are wildly varying degrees of quality), the problem is bigger than just that. Quality aside, it's challenging just to know if you're picking the module that mostly closely scratches your itch... Anyway, Drupal modules: tough to navigate, agreed! Not agreed? That making drupalmodules.com was the right thing to do. Crazy, right?
Apparently there have been discussions for ages on a rating system for modules on Drupal.org, let alone a general redesign of the site, and its sub-sites. Maybe people think drupalmodules.com undermines those efforts?
Really people, there's no downside to having another Drupal resource. In bizarro-land, the downside is that people who believe in centralizing everything, think the cost of keeping track of things and managing quality is not worth the benefit of having constantly-created resources, failing-fast, iterating often, and innovating often. In that reality, people should stop creating things, unless it's a thing inside the heavily formalized, but tracked, "system."
But on my planet, planet Internet, we're enjoying the abundance! (and we have RSS readers) John, thanks so much for working on drupalmodules.com! I hope it doesn't cause you too much grief. I hope you get lots of donations, and don't feel self-conscious about putting ads up on your site (unless you don't like them :D ). Do not feel self-conscious about the success or failure of your site! I hope more Drupal websites get born. I highly dig Drupal, and think it will get better faster not just with an ever-growing gigantic body of Drupal.org community members, but with highly-motivated independent visionaries who use Drupal as a canvas to express their vision.
Don't control artists.
We all know the expression "design by committee," and how it's a derisive term used to describe the dynamic of when the lack of a cohesive vision dilutes quality. And it's no secret that user experience and design is one of the most common criticisms of Drupal. So it's extra discouraging when the very thing that will lead to improved experience and design in Drupal, escape from design by committee, is frowned upon. Big groups are great for fixing bugs, raising money, and lot of other stuff. I don't want the awesome Drupal.org community to go anywhere. I just want it to recognize and appreciate that lots of cool Drupal stuff might not come from Drupal.org, but can still help Drupal.org.
The myth of centralization, the reality of distributed information.
If the Internet has taught us anything, it's that that:
- authoritativeness is subjective
- information is distributed
- if anything ever seems centralized, it's only because giant pockets of activity are hidden, and once surfaced, we can see, "oh yeah, information is distributed!, better to have it available, than invisible!"
This applies to all sorts of activities and information, but today I'm talking about software reference material, in specific, Drupal reference material.
Drupal is an incredibly popular content management system framework. You can call it other things. Drupal helps you make websites.
Drupal's fight to centralize
I'm relatively new to Drupal, quite like it, and recommend it frequently. That said, I have some issues with it, and among them what seems like peer pressure in the Drupal community to not create, or feel self-conscious about creating, Drupal resources outside of Drupal.org. There is a surprising lack of websites about Drupal given how popular it is. This is thoroughly confusing as everybody knows that with both proprietary and open source software, bands, artists, etc... having a breadth of resources/fan sites/ forums is a sign of a healthy, thriving community/market/mindshare. There's a time and a place for "many eyes" and joining large group efforts (like Drupal.org) and there's a time and a place for shirking mass-meetings, votes, digging in by yourself or a few collaborators, and making something totally fresh, especially for "proof of concept." Neither approach is better or worse, but they each have their time and place, and nobody should feel guilty or self-conscious for working hard on their own and making something.
Recently a non-Drupal.org resource was created, drupalmodules.com. This has been mildly controversial within the Drupal community. Drupalmodules.com is too new for me to honestly judge on utility alone, but without a doubt, it's purpose is undeniable: navigating the world of Drupal modules is very challenging, for many different reasons. While many within the Drupal community agree there needs to be a way to sift through modules by "quality" (there are wildly varying degrees of quality), the problem is bigger than just that. Quality aside, it's challenging just to know if you're picking the module that mostly closely scratches your itch... Anyway, Drupal modules: tough to navigate, agreed! Not agreed? That making drupalmodules.com was the right thing to do. Crazy, right?
Apparently there have been discussions for ages on a rating system for modules on Drupal.org, let alone a general redesign of the site, and its sub-sites. Maybe people think drupalmodules.com undermines those efforts?
Really people, there's no downside to having another Drupal resource. In bizarro-land, the downside is that people who believe in centralizing everything, think the cost of keeping track of things and managing quality is not worth the benefit of having constantly-created resources, failing-fast, iterating often, and innovating often. In that reality, people should stop creating things, unless it's a thing inside the heavily formalized, but tracked, "system."
But on my planet, planet Internet, we're enjoying the abundance! (and we have RSS readers) John, thanks so much for working on drupalmodules.com! I hope it doesn't cause you too much grief. I hope you get lots of donations, and don't feel self-conscious about putting ads up on your site (unless you don't like them :D ). Do not feel self-conscious about the success or failure of your site! I hope more Drupal websites get born. I highly dig Drupal, and think it will get better faster not just with an ever-growing gigantic body of Drupal.org community members, but with highly-motivated independent visionaries who use Drupal as a canvas to express their vision.
Don't control artists.
We all know the expression "design by committee," and how it's a derisive term used to describe the dynamic of when the lack of a cohesive vision dilutes quality. And it's no secret that user experience and design is one of the most common criticisms of Drupal. So it's extra discouraging when the very thing that will lead to improved experience and design in Drupal, escape from design by committee, is frowned upon. Big groups are great for fixing bugs, raising money, and lot of other stuff. I don't want the awesome Drupal.org community to go anywhere. I just want it to recognize and appreciate that lots of cool Drupal stuff might not come from Drupal.org, but can still help Drupal.org.
Labels: artists, design by committee, drupal, drupalmodules.com, quality
Sunday, March 02, 2008
Drupal "on rails." One of the ways Acquia's commercial Drupal will work
One of the challenges of Drupal is there is always more than module to scratch any itch, including some included modules (especially easy to reach for). And more than once I've chosen a module or approach to solve a problem, only to find out later about a superior solution I wish I would have known about earlier.
So it's a great relief to hear that Acquia will help guide us down the road of module selection by including a bunch on their to-be-released Drupal distro, code-named Carbon.
Modules currently under consideration:
(via a friend, this could be changed later, go here for freshest info (login required))
So it's a great relief to hear that Acquia will help guide us down the road of module selection by including a bunch on their to-be-released Drupal distro, code-named Carbon.
Modules currently under consideration:
(via a friend, this could be changed later, go here for freshest info (login required))
What’s Included
Carbon will include the latest release of Drupal 6 core along with a carefully selected set of modules. We are selecting modules based on their relevance to common social publishing use cases for both public-facing web sites and intranet team collaboration sites. The module set is still under review. Currently, it includes:
Page layout: Panels 2
Custom content: CCK, Date, Imagefield, File
Views: Views 2
Lightweight markup: Marksmarty
WYSIWYG: Kupu
Scheduled publishing: Workflow, Actions
Image management: As fields - Imagefield, Imagecache; As nodes - Image, Image assist
Events: Calendar
Forums: Forum
Comment spam filter: Mollom
Social bookmarks: TBD
Content rating: Voting API, Fivestar
Search: in core, Solr
Categorization: in core
RSS: in core
Content aggregation: tbd
Workflow: Workflow
Content versioning: Core, Diff
Tag clouds: Tagadelic
SEO URLs: Path Auto
Utilities: Primary Tag, Custom pager, JS Tools, Google Maps, Google Analytics, Wiki freelinks
Import / migration: tbd
Authentication: Persistent login, Securesite, LDAP, OpenID
User Groups: Organic groups
Email gateway: tbd
Email notification: Subscriptions
Wednesday, February 20, 2008
Two Dudes, One Drupe: Drupalmao, new Drupal videocast
New Drupal show alert! Drupal enthusiasts probably already know about Lullabot's excellent podcast/videocast. And now they have some company. Drupalmao has just launched, which is a casual, DIY show, not unlike Diggnation, where two friends in NYC/NJ just talk about stuff they'd probably talk about even without the camera there, and it's fun and super informative.
One of the critical skills for any Drupal developer/ administrator is constantly adjusting and tweaking your approach to your site(s) with an awareness of fading/emerging modules and how they're best used. In my first night with Drupalmao, I already learned about one module I hadn't heard of at all, and another one whose name I recognized, but whose purpose I was unclear on.
Keep up the good work guys!
New Drupal show alert! Drupal enthusiasts probably already know about Lullabot's excellent podcast/videocast. And now they have some company. Drupalmao has just launched, which is a casual, DIY show, not unlike Diggnation, where two friends in NYC/NJ just talk about stuff they'd probably talk about even without the camera there, and it's fun and super informative.
One of the critical skills for any Drupal developer/ administrator is constantly adjusting and tweaking your approach to your site(s) with an awareness of fading/emerging modules and how they're best used. In my first night with Drupalmao, I already learned about one module I hadn't heard of at all, and another one whose name I recognized, but whose purpose I was unclear on.
Keep up the good work guys!
Labels: drupal, drupalmao, podcast, video show, videocast
Tuesday, December 11, 2007
Drupal Therapy. Introduction: Drupal is like the Holodeck
(So, BTW, Amnesty.org just relaunched, using Drupal. via Dries.)
Last year I started using Drupal. I made it into a blog server. It is a fine blog server. For hosting multiple blogs by multiple authors, it might even be my favorite. But because I had previous exposure to Wordpress and its elegant admin panel, I couldn't help but be majorly disappointed by the administrative interface of Drupal. What made it worse was how little anybody talked about its horrible interface. The only people who seemed willing to talk about it were the people who tried Drupal and left.
I stuck with Drupal. I love Drupal. I think it's the best tool for building many types of web applications, but many parts of the administrative experience are ridiculous. I think many people in the Drupal community know this, and are working to change this, but we are likely a few versions away from any of the major turn-offs being healed.
In the meantime, I'm going to give back to Drupal. Not by beating it up about its shortcomings, but by acknowledging them, and working around them. By guiding people through them. People who have poked around Drupal and wrinkled your nose: You are not crazy. You are not stupid. Drupal doesn't make sense at first. But if you walk away, you are turning away from an amazing, amazing tool that likely does anything you were thinking of doing, but more!
Drupal is like a beautiful mansion. No. It's like a the holodeck. No. Drupal is like a holodeck mansion. If you want a loft, it can be an urban loft for you. If you want a beachfront property, bam! It's beachfront property. Drupal can adapt to your desires. But there's one problem. Drupal is a holodeck mansion without a door. There's a little doggy door. You have to get on your hands and knees and crawl. You're going to get very dirty. You might even scrape yourself. But once you've made it inside, there's nothing like it.
Stay tuned for Lesson One in Drupal Therapy: The beginning's not a good place to start.
It will help if you have the ability to use a virtual machine.
(So, BTW, Amnesty.org just relaunched, using Drupal. via Dries.)
Last year I started using Drupal. I made it into a blog server. It is a fine blog server. For hosting multiple blogs by multiple authors, it might even be my favorite. But because I had previous exposure to Wordpress and its elegant admin panel, I couldn't help but be majorly disappointed by the administrative interface of Drupal. What made it worse was how little anybody talked about its horrible interface. The only people who seemed willing to talk about it were the people who tried Drupal and left.
I stuck with Drupal. I love Drupal. I think it's the best tool for building many types of web applications, but many parts of the administrative experience are ridiculous. I think many people in the Drupal community know this, and are working to change this, but we are likely a few versions away from any of the major turn-offs being healed.
In the meantime, I'm going to give back to Drupal. Not by beating it up about its shortcomings, but by acknowledging them, and working around them. By guiding people through them. People who have poked around Drupal and wrinkled your nose: You are not crazy. You are not stupid. Drupal doesn't make sense at first. But if you walk away, you are turning away from an amazing, amazing tool that likely does anything you were thinking of doing, but more!
Drupal is like a beautiful mansion. No. It's like a the holodeck. No. Drupal is like a holodeck mansion. If you want a loft, it can be an urban loft for you. If you want a beachfront property, bam! It's beachfront property. Drupal can adapt to your desires. But there's one problem. Drupal is a holodeck mansion without a door. There's a little doggy door. You have to get on your hands and knees and crawl. You're going to get very dirty. You might even scrape yourself. But once you've made it inside, there's nothing like it.
Stay tuned for Lesson One in Drupal Therapy: The beginning's not a good place to start.
It will help if you have the ability to use a virtual machine.
Labels: amnesty, apologetics, cms, drupal, drupal therapy
Wednesday, October 03, 2007
These links matter to you. Thursday October 4th, 2007
- UC Berkeley posts entire course lectures on YouTube. Your move, MIT OpenCourseWare
- If your Drupal site is on the Internet, you can publish from Google Docs
- Notes from a DrupalCon Barcelona attendee
- Ubuntero.org is a social network for Ubunteros and their admirers
Tuesday, October 02, 2007
These Links Matter to You. Tuesday October 2, 2007
- 43 Folders switched over to Drupal
- New DrupalCamp alert: BADCamp '07, taking place in the Bay Area (northern California) early November 2007
- new episodes of LUG radio are noteworthy enough on their own, but this one has an interview with Miguel de Icaza
- most of this summer 2007's WordCamp (WordPress un-conference) talks have videos up
- (video) If Morgan Stanley can get social networking inside their business and present on Enterprise 2.0, there's hope for you. "Who knows who, and who knows what."
Labels: drupal, enterprise, event, miguel de icaza, wordpress
Thursday, September 06, 2007
These Links Matter to You. Thurday September 6, 2007
(GNOME Specimen Screenshot )
- GNOME Specimen, a great way to preview fonts, has been updated.
- You already know about the Fake Steve Jobs. But do you know about Fake Jonathan Schwartz?
- Miguel de Icaza nicely summarizes, and highlights an interesting question regarding the Network Appliance/ Sun lawsuit.
- The anatomy of a Drupal Installation Profile
- Delicious: Extreme. Makeover. Preview.
Labels: drupal, gnome specimen, jonathan schwartz
Wednesday, September 05, 2007
These Links Matter to You. Wednesday September 5, 2007
- I didn't intend on being the 5,000,000th person to talk about the iphone/ipod updates today, but I ran across this in a delicious feed:
Schadenfreude: iPhone Price Chopped Already, 8GB $200 Cheaper - Consumerist
Whatever. I was an iPhone-carrying rock star all summer and you know it
by werty to gadgets iphone ... saved by 1 other person ... 1 hour ago - An extremely interesting talk by Sun CEO Jonathan Schwartz about emerging markets (video)
- Leetspeak: as legit as Kitty Pidgin
- Another big media company is using Drupal. This time LifetimeTV. (They join mtv, WarnerMusic, among others)
- You didn't hear it from me, but Google may announce a presentation program (PowerPoint-ish) and wiki to go along with GoogleDocs and Google Spreadsheet at the Office 2.0 conference this week
Labels: drupal, iphone, jonathan schwartz, leetspeak, sun
Monday, May 07, 2007
These Links Matter to You. Monday May 7, 2007
(ideally this cat pidgin will be charming, hilarious, and familiar to readers of i can has cheezburger and Anil Dash)
(ideally this cat pidgin will be charming, hilarious, and familiar to readers of i can has cheezburger and Anil Dash)- This commenter on Matt Asay's InfoWorld blog has a theory that IBM will buy Novell (to get SUSE), that IBM helped Novell buy SUSE, and that ex-IBM execs are already slowly filling Novell VP spots
- Comcast is going to use open source + commercial application Zimbra to manage 12 million + mail accounts
- Ubuntu working with Intel on a mobile/ embedded edition of Ubuntu.
- Sun is helping port OpenOffice on the Mac with two dedicated engineers.
- New York Observer magazine recently relaunched their website using Drupal. With notes on the how. And why yes I will continue to document major commercial implementations of open source software like Drupal until y'all bow down and concede that open source is just fine for "mission critical" applications. Sheesh.
Labels: comcast, drupal, embedded, intel, mac, mobile, open source, openoffice, oss, social software, sysadmin, ubuntu, zimbra
Tuesday, January 23, 2007
These Links Matter to You. Tuesday, January 23, 2007
- wowza. Five kinda serious usability issues with Microsoft Vista. ( really well written)
- very funny podcast with mostly-Mac blog Daring Fireball's John Gruber, and Panic's Cabel Sasser (this was done at Macworld, soon after The Keynote. Lotsa Steve Jobs mocking that comes from a place of love.)
- For real. IBM announced gigantor social software suite, Lotus Connections. This kinda competes with Microsoft's gigantor Sharepoint. Many companies will pay for the privilege of buying these packages, and then learn how to use them and in some cases, if to use them. (see also, Enterprisey) Drupal's Dries Buytaert suggests an IBM/ Drupal collaboration.
- wait. that deserves its own bullet-point. Enterprisey. ("...a derogatory term describing sophisticated software architecture which is claimed to be good enough (robust, flexible, etc.) for use in enterprise applications, but in fact is merely excessively complex...")
Labels: drupal, enterprisey, interface, microsoft, usability, user experience, vista
Monday, January 22, 2007
And which do you choose, a hard or soft option? Drupal 5.0 is out, does Internet, Intranet, content, collaboration!
(original screenshot snagged from Drupal.org's 5.0 screenshot page)
What's Drupal? Drupal is open source software. Drupal can be used to manage blogs, communities, newspapers, magazines, forums, wikis, on-line video channels, and other kinds of content. You've probably visited a site powered by Drupal, and not even realized it! ('Da Drupes is humble like that.)
A new version of Drupal, Drupal 5.0 was released last week. What's new since Drupal 4.7, its last major revision?
(This is a compressed Flash movie of the "What's new in Drupal 5.0" video. Consider downloading the larger, but much higher quality mp4 here.)
While it's easy to find out that software like Drupal is being used when it's running a famous public website, it's a little harder to know when it's being used internally, in corporate, community, and organizational intranets. As it turns out, Yahoo! uses Drupal internally, and outlined the process. Based on this awesome Drupal case study from IBM, one can only assume they use it for collaboration stuff as well.
Related links:
(original screenshot snagged from Drupal.org's 5.0 screenshot page)A new version of Drupal, Drupal 5.0 was released last week. What's new since Drupal 4.7, its last major revision?
- There's a web-based installer! (It's not as nice as the Wordpress installer, but it's easier than Drupal 4.7's.)
- The administration panel/ tools is totally reworked since Drupal 4.7. In a good way.
- The new core theme lets you change color stuff dynamically with CSS
- more!
(This is a compressed Flash movie of the "What's new in Drupal 5.0" video. Consider downloading the larger, but much higher quality mp4 here.)
While it's easy to find out that software like Drupal is being used when it's running a famous public website, it's a little harder to know when it's being used internally, in corporate, community, and organizational intranets. As it turns out, Yahoo! uses Drupal internally, and outlined the process. Based on this awesome Drupal case study from IBM, one can only assume they use it for collaboration stuff as well.
Related links:
- Drupal project lead Dries Buytaert's personal blog (powered by Drupal, duh)
- Drupal superstars Lullabot
- The Digg.com Drupal 5.0 announcement thread. (for the patient and thick-skinned)
Labels: cms, collaboration, collaborative, content management system, drupal, enterprise, enterprisey, internet, intranet, open source, oss, software, sysadmin, video
