Good news! During the week of December 15, we're organizing a 5-day Fields in Drupal core code sprint at Acquia! The goal is to get CCK functionality into Drupal 7.

So far, Karen, Yves and Barry have signed up -- Karen and Yves are the main CCK maintainers, and Barry has done a lot of work on CCK as well.

To help us fund the sprint, please consider making a donation using the ChipIn widget on this page. We need money for airline tickets, hotel rooms, food and transportation. It would also be great to fly in a few additional people with extensive core and CCK experience.

I've tentatively worked out a budget of $7,000 USD, which covers flight, food and hotel costs for at least four people (Karen, Yves, and two additional people). Since Acquia is covering my travel expenses and allowing Barry to participate all week long, that gives us six people working on CCK-fields-in-core for an entire week. Any excess money will be used to add more people, or donated to the Drupal Association.

read more

The Asterisk.org development team has released Asterisk versions 1.2.30.3, 1.4.23-rc2, 1.6.0.2, 1.6.1-beta3, as well as Asterisk-Addons versions 1.6.0.1 and 1.6.1-rc2. These releases are available for immediate download from http://downloads.digium.com/.

read more

With the release of RC1, we’re in the final leg of development before the release of 2.7.  280 commits since beta 3 have polished the new admin UI (including new menu icons created by the winners of our icon design contest) and fixed all known blocker bugs.

We think RC1 is ready for everyone to try out.  Please download RC1 and help us make the final release the best it can be.  As always, back up your blog before upgrading.

Get RC1.

Drupal for Education and E-Learning is now available from Packt Publishing. This book covers Drupal 6, and describes how to build a community site to support teaching and learning. This book is designed for people new to Drupal, with no prior development experience. The hands-on, step-by-step instructions guide you through installing Drupal, configuring contributed modules and themes, and working with some of Drupal’s most useful and powerful modules, including CCK, Views, and Organic Groups. The book also covers site maintenance, upgrades, and backups – these essential steps, while not as fun as site building, are essential for keeping your site and data secure.

This book is written with the needs of educational users in mind, but the information in this book can be useful for site administrators, or for people looking to build a community/social networking site in Drupal outside of education as well.

read more

One mom's mission to create a safe online space for teens

Yoursphere.com is a safe kids-only social network (built with Drupal 5), which is complemented by an online safety blog and discussion site, internet-safety.yoursphere.com (built with Acquia Drupal).

Founder Mary Kay Hoal is a savvy mother of five. When her children started spending time on social network sites such as MySpace she did a little research and was shocked to find that social networks were magnets for sexual predators and rampant with inappropriate content targeting youth. "We wouldn't open our front door and invite 29,000 registered sex offenders into the house," Mary Kay told her kids, "so why should we accept that online?"

So she banned social networking from her home and saw her approval rating dip below that of steamed broccoli. Besides being unpopular at home, Mary Kay also knew that trying to banish MySpace would be a hopeless game of whack-a-mole. She really had no choice -- it was her duty as a mom to create a safe alternative.

read more

WordPress 2.6.5 is immediately available and fixes one security problem and three bugs. We recommend everyone upgrade to this release.

The security issue is an XSS exploit discovered by Jeremias Reith that fortunately only affects IP-based virtual servers running on Apache 2.x. If you are interested only in the security fix, copy wp-includes/feed.php and wp-includes/version.php from the 2.6.5 release package.

2.6.5 contains three other small fixes in addition to the XSS fix. The first prevents accidentally saving post meta information to a revision. The second prevents XML-RPC from fetching incorrect post types. The third adds some user ID sanitization during bulk delete requests. For a list of changed files, consult the full changeset between 2.6.3 and 2.6.5.

Note that we are skipping version 2.6.4 and jumping from 2.6.3 to 2.6.5 to avoid confusion with a fake 2.6.4 release that made the rounds. There is not and never will be a version 2.6.4.

Get WordPress 2.6.5.

While many people say that theming is one of the better organized topics in Drupal's documentation, many have expressed frustration that relevant pages are located in a variety of different branches, and even separate handbooks. The documentation team has also decided that this has created an unsustainable path for forward maintenance. Therefore, as a first step, we are going to merge nearly all theming-related information into a single Consolidated Theming Guide on Sunday, 23 November, to be located at http://drupal.org/theme-guide (currently pointing to the Drupal 6 Theme Guide). Existing links, both to individual nodes numbers and path aliases, will be preserved as much as possible.

A theming documentation workgroup is now forming to focus on reorganizing the new book's navigation hierarchy. For further information on the project and how to join in, please visit the group's project page.

read more

Andrew J. Turner (http://www.highearthorbit.com) suggested to me that we need a term for user-created, user-entered, user-discovered, and user-curated data. Of course, if you change "data" to "code" you have exactly what the Open Source Initiative is already doing for software. We could do the same thing for data. Write an Open Source Data Definition, which puts strictures on the attributes of data that claims to be Open Source Data.

read more

Just over a month ago, we announced that we opened up editing rights to much of the handbooks for all users on Drupal.org. Our one month trial period is over and the Documentation team has decided that overall it has been a success. We have seen many more edits and fixes in the handbook and, while we did see some limited mess to clean up, occurrences of vandalism (or playing around) were relatively uncommon. We feel, at this time, that open editing is a significant benefit to our handbooks. We have decided to leave open editing in place, with no further defined trial periods. Keep editing away!

In addition to helping out with fixing pages, we also need many eyes on the edits themselves. Anyone can review recent edits and check out the diffs. If you notice something awry about an edit, you can simply fix it by editing or, if you are a member of the documentation team, you can select the "revert" operation from the Revisions tab to undo the change.

This process did raise other discussions related to various improvements we could make to help track edits and thoughts about how the new page creation management, versus editing, could be improved. Feel free to join in those ongoing tasks and discussions. The next IRC meeting will be tomorrow, November 20 at 18:00 GMT (1 p.m. EST, 10 a.m. PST) and all are welcome. For more info on documentation activites and projects, check out our group.

read more

Shortly after last week's Django 1.0.1 release, several people noted that the packaging script used to produce the release omitted several directories from the Django source tree; mostly this affected some unit tests, but at least one of the omitted directories affected the use of Django itself (specifically, of django.contrib.gis). So tonight we're issuing Django 1.0.2, which is built around an updated packaging script and should resolve these problems.

This is a recommended upgrade for anyone using or targeting Django 1.0 or Django 1.0.1; to obtain a copy, swing by the downloads page, and don't forget to read the release notes. For the security conscious, a signed file containing the package's checksums is, as always, available.

The community has voted, and the votes have been tallied. The winner of Project Icon, with 35% of the votes, is Entry ID “BD,” otherwise known as Ben Dunkle. Congratulations, Ben! The runner-up was VS, otherwise known as Verena Segert, so we’ll be attaching that set to the alternate color palette that is selectable from the profile screen. As we prepare for RC1, Ben and Verena will be revising a couple of their icons so that both sets will use the same metaphors, creating the colored “on” states, and creating the larger size of each icon for use in the h2 screen headers. We are very grateful to have had the opportunity to select from so many great options, and would like to express again our appreciation for all the designers who participated in the contest. Thanks also to the more than 3700 people who completed the voting survey and took the time to weigh on on the individual icon sets.

Q.18 Which one of the sets do you think we should use as a basis for the 2.7 icons? Icon Set # of votes % of votes BD 1285 35% VS 1080 29% GB2 424 11% OSD 376 10% LS 300 8% GB1 235 6%

The wide lead of BD and VS made it clear that voters had a clear preference for these sets.

Q.20 If you could choose a runner-up, which would you choose? Icon Set # of votes % of votes VS 916 27% BD 647 19% LS 522 16% OSD 488 14% GB2 462 14% GB1 331 10%

Question 20 was not mandatory, so a few hundred people skipped it, but the responses we did get (3366 of them) reinforced the fact that the two most popular sets were also the most popular 2nd choices, which made the decision of the judges to go with the popular vote an easy one (take that, electoral college!).

A few of the individual icon metaphors also had a significant lead over the other choices.
Dashboard: 1333 voters (40%) chose a house as the best metaphor. We agree, so both Ben and Verena will be replacing their Dashboard icons.

Media: 2097 voters (65%) chose the combination camera + musical note icon, which was part of Ben’s set. We also really loved it, and Verena will amend her media icon to incorporate this idea.

Plugins: 1682 voters (53%) selected the outlet plug metaphor, which both Ben and Verena used in their sets.

Tools: 1581 voters (49%) liked the combination of two tools better than anything else, so Ben and Verena will try this approach.

So those are the results, and soon you’ll see the new icons coming to a 2.7 installation near you.

Need another look at the entries to remember which one you liked best? Here are some reminder images, as well as the identity of each set’s creator.

BD was Ben Dunkle, a designer, professor and artist from upstate/western New York State. In case you’ve already forgotten, Ben’s icon set is the winner of Project Icon and will become the default icon set after a few minor changes. VS was Verena Segert, our runner-up, a designer from Germany who presented sets in both grayscale and blue. Her blue icons received more specific voter comments than the gray ones, so we’re planning the second color palette to be in shades of blue so that we can use the blue icon set. GB was Guillaume Berry, a designer from France who submitted two sets in the same style in order to propose a couple of different metaphors. One of his sets came in third while the other came in last, but whether you only look at the higher scoring set or you combine their votes, Guillaume had the next highest percentage of votes, and many people liked the metaphors he used for various icons. In fact, given the enthusiasm of the community for Guillaume’s icons, we think a great plugin would be one that would allow the user to upload the icon set of their choice. Any volunteers? OSD was the Open Source Design class at Parson’s in New york City, taught by Mushon Zer-Aviv and consisting of students Alexandra Zsigmond, Ed Nacional, Karen Messing, Khurram Bajwa, Leonie Leibenfrost. Teacher and students worked together to determine their metaphors and visual style. LS was Luke Smith, a designer from Iowa who specializes in icons among his other design pursuits.

If you need to hire an icon designer any time soon, we highly recommend our Project Icon contestants, who all delivered great work in a very short timeframe. It was great to work with all of them, even for such a short assignment.

So, to sum up:

1. The winning icon sets by Ben Dunkle and Verena Segert will be incorporated into WordPress 2.7 RC1.
2. Someone should write a plugin that would allow anyone to upload a custom icon set (I bet the other contestants could be convinced to release their icon sets for such a purpose).
3. 2.7 is still trucking away, but we can always use help with patches, especially for IE6! (I know, that wasn’t in the main post, but it’s true, so hmph)

Thanks again to everyone who participated in this experiment, and we hope you enjoyed it as much as we did. And congratulations again to Ben and Verena!

Sam Folk-Williams recently blogged a response to an earlier blog posting I had written about Open Source and Sustainability. Over the past few months I've been having more and more discussions about this topic with IT executives, and I have been meaning to write and update on the latest. Sam's posting provides the perfect prompt and background.

read more

WordPress 2.7 Beta 3 has been released for your testing pleasure. Here are some of the changes since Beta 2 (over 160 changes in total):

• Numerous style improvements and refinements.
• All admin notices now go under the page title.
• PHP Notice fixes.
• Dashboard widget options now properly save.
• Menu fixes.
• New design for Quick Edit.
• Canonical feed URL fixes.
• Walker fixes.
• An update for Hello Dolly.
• Plugin installer updates.
• Numerous font updates.
• Updated login logo.
• Switch position of “Save Draft” and “Preview” buttons in publish module.
• File upload support for MS Office 2007+ file formats.
• Media upload buttons won’t show if the user doesn’t have the upload capability.
• Canonical redirects only do yes-www or no-www redirection for domains.
• Shift-click checkbox range selection improvement.
• Add New User page now separate.
• Tag suggest only suggests tags (not other taxonomy terms).
• QuickPress shows “Submit for Review” if user cannot publish.
• Private posts/pages, and password-protected posts/pages are rolled into new “Visibility” section of publish module.

If you have already installed Beta 1 or Beta 2, you can update to Beta 3 via the Tools -> Update menu. If you have problems, or if this is your first time in the 2.7 beta ring, you can download and upgrade the old fashioned way.

Get 2.7 Beta 3.

Following the previously-announced schedule, today the Django team has released Django 1.0.1. This is a bugfix-only release containing fixes and improvements to the Django 1.0 codebase, and is a recommended upgrade for anyone using or targeting Django 1.0.

For full details, check out the 1.0.1 release notes, and to grab a copy of Django 1.0.1, visit the downloads page. For the security-conscious, a file containing checksums of the 1.0.1 package, signed with the release manager's key, is available.

And with Thanksgiving coming up in the US, your friendly local release manager would like to pause for a moment and express thanks, on behalf of myself and the Django development team, for all the work put in by all the members of our community to help keep the releases coming, the tickets triaged and the bugs fixed. We wouldn't be able to do it without all of you, so give yourselves a big pat on the back and see if you can't sneak an extra slice of pie come Thanksgiving dinner.

We'll see you again in a few months, for either Django 1.0.2 or Django 1.1. Happy holidays!

Team Lullabot is really excited to unveil O'Reilly Media's first Drupal book, Using Drupal, due out next month. (BTW, that's a dormouse on the cover. :)) The book is written against Drupal 6.

Our motivation for writing this book was that most peoples' first experience with Drupal involves getting it installed successfully, but then being left with the question, "What next?" Using Drupal is all about answering this question. It shows in a practical, hands-on way how to combine over thirty of Drupal's contributed modules to build Drupal websites that can do things ranging from product reviews to event management to e-commerce, all through configuration with as little coding as possible. You can also think of it as a field guide to CCK and Views, since almost all chapters build on those base modules.

read more

Earlier in the beta period, we put out a call here on the development blog for designers in the WordPress community who might be interested in designing custom icons for the 2.7 admin interface. Over a dozen icon designers from around the world responded, so rather than choose just one, we decided to turn the icon design assignment into a contest so that more people could participate and the community could have a vote in what the new icons should look like.

Once we decided to go with a contest format instead of a single-designer gig, about half the original volunteers changed their minds. The remaining designers each submitted two icons (Posts, Links) in their proposed style. At this stage a couple of designers were thanked for their submissions but eliminated from the competition because their icons were considered too far afield from the WordPress visual style. The remaining designers were given feedback on the icons they had submitted and given about a week to complete the icon set for the menu as well as the list/excerpt icons that are shown on the Edit Posts screen. All but one of these designers finished a complete set, giving us five sets in total.

So now we need to choose a direction. For each of the icon sets, we’ll show you the set itself, the designer’s introduction, and some feedback from the lead developers. After you’ve reviewed all five, place your vote for the set you think has the visual style that is the most suitable for WordPress 2.7. This will be followed by additional votes on specific icons, so if you like the specific image used in one set but like the style of another, you can vote to change the metaphor for a given icon. You’ll also be able to leave general feedback throughout the voting process. When voting has concluded, we’ll review the comments and the votes, and will declare a winner.

Things to bear in mind when making your selections:
A week is not a long time to create 13 icons. The winning set will undergo a revision to be refined, and some icons may be substituted. We asked for all icons in grayscale for the contest. An “on” state and a larger size for screen headers will be designed by the winner. It seemed like too much work to have everyone do multiple states for so many icons.

Ready? Go and take the icon survey. (The survey has now been closed.) Voting will remain open for 48 hours from the time of this post to allow people from all time zones a chance to participate before we close the survey and make a decision (since we’d like to include the new icons in Beta 3).

A Note Regarding the 2.7 Release Date:
As we approach Beta 3, bug tickets continue to be added to Trac, the pain of making things look good in IE6 continues to be felt, and the need to improve accessibility looms. If you love WordPress, are a decent coder, and want to contribute like these icon designers contributed, please consider contributing a patch to help with one of these efforts. Jump right in on current Trac tickets, or pop into the #wordpress-dev IRC channel to ask what to do.

There's an argument commonly heard these days that open-source software is all very well for infrastructure or commodity software where the requirements are well-established, but that it can't really innovate. I laugh when I hear this, because I remember when the common wisdom was exactly the opposite -- that we hackers were great for exploratory, cutting-edge stuff but couldn't deliver reliable product.

How quickly people forget. We built the World Wide Web, fer cripessakes! The original browser and the original webservers were built by a hacker at CERN, not in some closed-door corporate shop. Before that, years before we got Linux and our own T-shirts, people who would later identify their own behavior correctly as open-source hacking built the Internet.

read more

Venkatesh Hariharan recently wrote an article titled The practical problem with software patents, a subject near and dear to my heart. He draws on the same research that I have cited in the past, the book "Patent Failure: How Judges, Bureaucrats, and Lawyers Put Innovators at Risk," by Boston University professors, James Bessen & Michael J. Meurer, but I confess that he shows both greater insights and certainly a better sense of humor than I do when I write abou the subject.

read more

Nearly 2,000 applications were filed for the Knight Foundation 2009 News Challenge. As you may recall, the Knight Foundation has committed to fund $25M over five years to projects that:

1. Use or create digital, open-source technology as the code base
2. Serve the public interest
3. Benefit one or more specific geographic communities

That is a lot of money supporting the development of open source software and citizen activism!

In the course of this process I have decided to sign on as an advisor to one such project, should it's $500,000 funding request and $500,000 matching grant be approved.

read more

It would be a bit of a stretch to claim that Barack Obama won the 2008 election because his website ran open source software while John McCain's ran on proprietary software. But what is not a stretch at all is that Barack Obama's campaign built a powerful synergy between grass-roots politics and grass-roots technology, while presenting what many consider to be the most disciplined campaign of any candidate in modern history.

read more