Our approach with WordPress has always been to make it run on common server configurations. We want users to have flexibility when choosing a host for their precious content. Because of this strategy, WordPress runs pretty much anywhere. Web hosting platforms, however, change over time, and we occasionally are able to reevaluate some of the requirements for running WordPress. Now is one of those times. You probably guessed it from the title — we’re finally ready to announce the end of support for PHP 4 and MySQL 4!

First up, the announcement that developers really care about. WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4.

For WordPress 3.2, due in the first half of 2011, we will be raising the minimum required PHP version to 5.2. Why 5.2? Because that’s what the vast majority of WordPress users are using, and it offers substantial improvements over earlier PHP 5 releases. It is also the minimum PHP version that the Drupal and Joomla projects will be supporting in their next versions, both due out this year.

The numbers are now, finally, strongly in favor of this move. Only around 11 percent of WordPress installs are running on a PHP version below 5.2. Many of them are on hosts who support PHP 5.2 — users merely need to change a setting in their hosting control panel to activate it. We believe that percentage will only go down over the rest of the year as hosting providers realize that to support the newest versions of WordPress (or Drupal, or Joomla), they’re going to have to pull the trigger.

In less exciting news, we are also going to be dropping support for MySQL 4 after WordPress 3.1. Fewer than 6 percent of WordPress users are running MySQL 4. The new required MySQL version for WordPress 3.2 will be 5.0.15.

WordPress users will not be able to upgrade to WordPress 3.2 if their hosting environment does not meet these requirements (the built-in updater will prevent it). In order to determine which versions your host provides, we’ve created the Health Check plugin. You can download it manually, or use this handy plugin installation tool I whipped up. Right now, Health Check will only tell you if you’re ready for WordPress 3.2. In a future release it will provide all sorts of useful information about your server and your WordPress install, so hang on to it!

In summary: WordPress 3.1, due in late 2010, will be the last version of WordPress to support PHP 4 and MySQL 4. WordPress 3.2, due in the first half of 2011, will require PHP 5.2 or higher, and MySQL 5.0.15 or higher. Install the Health Check plugin to see if you’re ready!

WordPress 3.0 Thelonious passed 3 million downloads yesterday, and today the plugin directory followed suit with a milestone of its own: 100 million downloads.

The WordPress community’s growth over the years has been tremendous, and we want to reinvest in it. So we’re taking the next two months to concentrate on improving WordPress.org. A major part of that will be improving the infrastructure of the plugins directory. More than 10,000 plugins are in the directory, every one of them GPL compatible and free as in both beer and speech. Here’s what we have in mind:

We want to provide developers the tools they need to build the best possible plugins. We’re going to provide better integration with the forums so you can support your users. We’ll make more statistics available to you so you can analyze your user base, and over time we hope to make it easier for you to manage, build, and release localized plugins.

We want to improve how the core software works with your plugin and the plugin directory. We’re going to focus on ensuring seamless upgrades by making the best possible determinations about compatibility, and offer continual improvements to the plugin installer. And we also want to give you a better developer tool set like SVN notifications and improvements to the bug tracker.

We’re also going to experiment with other great ideas to help the community help plugin authors. We want it to be easy for you to offer comments to plugin authors and the community, including user reviews and better feedback. We may experiment with an adoption process for abandoned plugins as a way to revitalize hidden gems in the directory. I’m not sure there is a better way to show how extendable WordPress is and how awesome this community is at the same time.

As Matt said in the 3.0 release announcement, our goal isn’t to make everything perfect all at once. But we think incremental improvements can provide us with a great base for 3.1 and beyond, and for the tens of millions of users, and hundreds of millions of plugin downloads to come.

It’s been summer for about a week now. Whether you’re on vacation or burning the midnight oil, attending a local/nearby WordCamp is a great way to spend a weekend. Meet other WordPress users, developers, designers & consultants, learn a little something, maybe share a little of your own experience and knowledge, and break bread (or raise a toast) with new friends and collaborators. Here are the WordCamps scheduled for this summer, along with what I know about them.

July 3: WordCamp Germany – Berlin, Germany. I love it that they’re using BuddyPress for their event site. They have multiple tracks, and what looks to be a nice variety of sessions. It’s only a few days away, so if you’re thinking of going, get your tickets now!

July 10: WordCamp Boulder – Boulder, Colorado, USA. This was WordCamp Denver last year, but the organizers have decided to mix it up and go back and forth between Denver and Boulder, which also has a thriving tech community. This year the venue is the Boulder Theater (so pretty!), and there will sessions for bloggers and devs alike, plus a Genius Bar to help people get their WordPress sites all fixed up. The speaker lineup looks good, and I hear they’re pumping up the wifi this year. I’ll be there, likely hunched over a notebook with Lisa Sabin-Wilson (author of WordPress for Dummies and BuddyPress for Dummies) to talk about the WordPress User Handbook project, and/or hunched over a sketchbook with Kevin Conboy (designed the new lighter “on” state for admin menus in WordPress 3.0) to work out a new default WordCamp.org theme (using BuddyPress). You can still get tickets!

July 17–18: WordCamp UK- Manchester, England, UK. The roving WordCamp UK will be in Manchester this year, and is probably the closest to BarCamp style of all the WordCamps, using a wiki to plan some speakers/sessions and organizing the rest ad-hoc on the first day of the event. I’ll be attending this one as well, and am looking forward to seeing WordPress lead developer Peter Westwood again. I’m also looking forward to meeting some core contributors for the first time in person, like Simon Wheatley and John O’Nolan. Mike Little, co-founder of WordPress, is on the organizing team of WordCamp UK. Tickets on sale now!

July 24: WordCamp Nigeria – Lagos, Nigeria. Their site seems to have a virus, so no link from here, but if you’re in Nigeria and interested in attending/getting involved, a quick Google search will get you to the organizers.

August 7: WordCamp Houston – Houston, TX, USA. Houston, Texas, birthplace of WordPress! Fittingly, Matt Mullenweg will be there to give the keynote. WordCamp Houston is running three tracks — Business, Blogger and Developer — in recognition of the fact that people who are interested in using WordPress for their business may not actually be bloggers or developers themselves. This used to get labeled as a “CMS” track at previous WordCamps (including NYC 2009), but with WordPress 3.0 supporting CMS functionality out of the box, “Business” is a much more appropriate label. Who wants to bet on if there will be BBQ for lunch?

August 7 : WordCamp Iowa – Des Moines, Iowa, USA. Another placeholder page. Happening, not happening? I’ve emailed the organizer and will update this post once I know more.

August 7–8: WordCamp New Zealand – Auckland, New Zealand. They haven’t announced this year’s speakers or topics, but they’ve been running polls to get community input into the program. Of note: in 2011 WordCamp New Zealand will be shifting seasons and will be in February instead, when the weather is nicer.

August 20–22: WordCamp Savannah – Savannah, Georgia, USA. Disclaimer: I am completely biased about Savannah, since I’m one of the organizers. This will be the first WordCamp in Savannah, and it’s being held at the Savannah College of Art and Design River Club, an awesome venue that used to be a cotton warehouse or something like that. Since Savannah doesn’t really have a cohesive WordPress community yet (though a fair number of people from Savannah attended WordCamp Atlanta earlier this year), this WordCamp is aimed squarely at building a local community. We’ll have a local meet-and-greet, regular sessions with visiting speakers (lots of core contributors coming to this one, plus Matt), and on Sunday it will be combination unconference/genius bar/collaborative workspace. Oh, and a potluck! We’ll also be running a pre-WordCamp workshop for people who have never used WordPress but want to get started, so that they’ll be able to follow the presentations and conversations littered with WordPress-specific vocabulary over the weekend. Ticket sales just opened, so get your tickets now.

For a schedule of all upcoming WordCamps, visit wordcamp.org. The autumn schedule is already packed! If you don’t see WordCamp in your area and are interested in organizing one, get more information and let us know.

Arm your vuvuzelas: WordPress 3.0, the thirteenth major release of WordPress and the culmination of half a year of work by 218 contributors, is now available for download (or upgrade within your dashboard). Major new features in this release include a sexy new default theme called Twenty Ten. Theme developers have new APIs that allow them to easily implement custom backgrounds, headers, shortlinks, menus (no more file editing), post types, and taxonomies. (Twenty Ten theme shows all of that off.) Developers and network admins will appreciate the long-awaited merge of MU and WordPress, creating the new multi-site functionality which makes it possible to run one blog or ten million from the same installation. As a user, you will love the new lighter interface, the contextual help on every screen, the 1,217 bug fixes and feature enhancements, bulk updates so you can upgrade 15 plugins at once with a single click, and blah blah blah just watch the video. (In HD, if you can, so you can catch the Easter eggs.)

If you’d like to embed the WordPress 3.0 video tour in your blog, copy and paste this code for the high quality version:

<embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.21" type="application/x-shockwave-flash" width="640" height="360" wmode="transparent" seamlesstabbing="true" allowfullscreen="true" allowscriptaccess="always" overstretch="true" flashvars="guid=BQtfIEY1&amp;width=640&amp;height=360&amp;locksize=no&amp;dynamicseek=false&amp;qc_publisherId=p-18-mFEk4J448M" title="Introducing WordPress 3.0 &quot;Thelonious&quot;"></embed>

For a more comprehensive look at everything that has improved in 3.0 check out 3.0′s Codex page or the long list of issues in Trac. (We’re trying to keep these announcement posts shorter.) Whew! That’s a lot packed into one release. I can’t think of a better way to kick off the 3.X cycle we’ll be in for the next two and a half years.

The Future

Normally this is where I’d say we’re about to start work on 3.1, but we’re actually not. We’re going to take a release cycle off to focus on all of the things around WordPress. The growth of the community has been breathtaking, including over 10.3 million downloads of version 2.9, but so much of our effort has been focused on the core software it hasn’t left much time for anything else. Over the next three months we’re going to split into ninja/pirate teams focused on different areas of the around-WordPress experience, including the showcase, Codex, forums, profiles, update and compatibility APIs, theme directory, plugin directory, mailing lists, core plugins, wordcamp.org… the possibilities are endless. The goal of the teams isn’t going to be to make things perfect all at once, just better than they are today. We think this investment of time will give us a much stronger infrastructure to grow WordPress.org for the many tens of millions of users that will join us during the 3.X release cycle.

It Takes a Village

I’m proud to acknowledge the contributions of the following 218 people to the 3.0 release cycle. These are the folks that make WordPress what it is, whose collaboration and hard work enable us to build something greater than the sum of our parts. In alphabetical order, of course.

Committers: azaozz (Andrew Ozz) (prof), dd32 (Dion Hulse) (prof), donncha (Donncha O Caoimh) (prof), iammattthomas (Matt Thomas) (prof), josephscott (Joseph Scott) (prof), markjaquith (Mark Jaquith) (prof), matt (Matt Mullenweg) (prof), nacin (Andrew Nacin) (prof), nbachiyski (Николай Бачийски) (prof), ryan (Ryan Boren) (prof), westi (Peter Westwood) (prof), and wpmuguru (Ron Rennick) (prof). Contributors: aaroncampbell (Aaron Campbell) (prof), akerem (prof), alexkingorg (Alex King) (prof), amattie (prof), ampt (Luke Gallagher) (prof), andrea_r (prof), andreasnrb (Andreas Nurbo) (prof), anilo4ever (Angelo Verona) (prof), apeatling (Andy Peatling) (prof), apokalyptik (Demitrious Kelly) (prof), arena (André Renaut) (prof), barry (Barry Abrahamson) (prof), batmoo (Mohammad Jangda) (prof), beaulebens (Beau Lebens) (prof), belg4mit (prof), bigdawggi (Matthew G. Richmond) (prof), blepoxp (Glenn Ansley) (prof), brentes (Brent Shepherd) (prof), briancolinger (Brian Colinger) (prof), bumbu (prof), caesarsgrunt (Caesar Schinas) (prof), camiloclc (prof), CAMWebDesign (prof), carbolineum (prof), caspie (prof), catiakitahara (Cátia Kitahara) (prof), CharlesClarkson (Charles Clarkson) (prof), chdorner (Christof Dorner) (prof), chrisbliss18 (Chris Jean) (prof), chrisscott (Chris Scott) (prof), cnorris23 (Brandon Allen) (prof), coffee2code (Scott Reilly) (prof), computerwiz908 (prof), cyberhobo (Dylan Kuhn) (prof), dancole (Dan Cole) (prof), Daniel Koskinen , deepak.seth (Deepak Seth), demetris (Δημήτρης Κίκιζας) (prof), Denis-de-Bernardy (prof), dimadin (Milan Dinić) (prof), dndrnkrd (Dan Drinkard) (prof), docwhat (prof), dougwrites ( href="http://profiles.wordpress.org/dougwrites">prof), dphiffer (Dan Phiffer) (prof), dragoonis (prof), dremeda (Dre Armeda) (prof), dtoj , dougal (Dougal Campbell) (prof), duck_ (Jon Cave) (prof), dxjones (David Jones) (prof), eddieringle (Eddie Ringle) (prof), edward mindreantre (Edward Hevlund), eoinomurchu (prof), empireoflight/Ben Dunkle (prof), ericmann (Eric Mann) (prof), etiger13 (Eddie Monge Jr.) (prof), filosofo (Austin Matzko) (prof), firebird75 (prof), frankieroberto (Frankie Roberto) (prof), Frumph (Philip M. Hofer) (prof), garyc40 (Gary Cao) (prof), gautam2011 (prof), Gary Ross (Gazzer) , GDragoN (Milan Petrovic) (prof), greenshady (Justin Tadlock) (prof), GIGALinux (Dennis Morhardt) (prof), hakre (prof), husky (prof), iandstewart (Ian Stewart) (prof), ipstenu (Mika Epstein) (prof), jacobsantos (Jacob Santos) (prof), jamescollins (James Collins) (prof), jane (Jane Wells) (prof), jbsil (Jesse Silverstein) (prof), jdub (Jeff Waugh) (prof), jeffikus (Jeffrey Pearce) (prof), jeffstieler (Jeff Stieler) (prof), jeremyclarke (Jeremy Clarke) (prof), jfarthing84 (Jeff Farthing) (prof), Jick (James Dimick) (prof), jmstacey (Jon Stacey) (prof), jobjorn (Jobjörn Folkesson) (prof), johanee (Johan Eenfeldt) (prof), johnbillion (John Blackbourn) (prof), johnjamesjacoby/jjj (John James Jacoby) (prof), johnjosephbachir (John Joseph Bachir) (prof), johnl1479 (John Luetke) (prof), johnonolan (John O’Nolan) (prof), JohnPBloch/wmrom (John Bloch) (prof), joostdevalk/yoast (Joost de Valk) (prof), jorbin (Aaron Jorbin) (prof), joshtime (prof), jshreve (prof), junsuijin (prof), kallewangstedt (Karl Wångstedt) (prof), keighl (Kyle Truscott) (prof), kevinB (Kevin Behrens) (prof), koopersmith (Daryl Koopersmith) (prof), kpdesign (Kim Parsell)
(prof), ktdreyer (Ken Dreyer) (prof), kurtmckee (Kurt McKee) (prof), laceous (prof), lancewillett (Lance Willett) (prof), lloydbudd (Lloyd Budd) (prof), lriggle (prof), markauk (prof), markmcwilliams (Mark McWilliams) (prof), markoheijnen (Marko Heijnen) (prof), markup (Sasha Mukhin) (prof), mattsains (prof), matveb (Matias Ventura) (prof), mdawaffe (Michael Adams) (prof) , mentel_br (prof), messenlehner (Brian Messenlehner) (prof), miau_jp (prof), Michael (Michael Heilemann) (prof), MichaelH (prof), mikeschinkel (Mike Schinkel) (prof), Miloslav Beňo , minusfive (prof), miqrogroove (Robert Chapin) (prof), misterbisson (Casey Bisson) (prof), mitchoyoshitaka (mitcho (Michael 芳貴 Erlewine)) (prof), MMN-o (prof), momo360modena (Amaury Balmer) (prof), morganestes (Morgan Estes) (prof), mrmist (David McFarlane) (prof), mtdewvirus (Nick Momrik) (prof), nadavvin (prof), Nao (Naoko McCracken) (prof), nathanrice (Nathan Rice) (prof), neoxx (Bernhard Riedl) (prof), niallkennedy (Niall Kennedy) (prof), ninjaWR (Ryan Murphy) (prof), noel (Noël Jackson) (prof), nomulous (Fletcher Tomalty) (prof), ocean90 (Dominik Schilling) (prof), Otto42 (Samuel Wood) (prof), pedger (prof), PeteMall (prof), pampfelimetten (prof), pnettle (prof), PotterSys (Juan) (prof), prettyboymp (Michael Pretty) (prof), ptahdunbar (Ptah Dunbar) (prof), ramiy (prof), RanYanivHartstein (Ran Yaniv Hartstein) (prof), reaperhulk (Paul Kehrer) (prof), reko (prof), remi (Rémi Prévost) (prof), rlerdorf (Rasmus Lerdorf) (prof) , rmccue (Ryan McCue) (prof), rooodini (prof), rovo89 (prof), ruslany ( "http://profiles.wordpress.org/ruslany">prof), sc0ttkclark (Scott Kingsley Clark) (prof), scottbasgaard (Scott Basgaard) (prof), ScottMac (prof), scribu (prof), SergeyBiryukov (Сергей Бирюков) (prof), ShaneF (prof), sillybean (Stephanie Leary) (prof), Simek (Bartosz Kaszubowski) (prof), simonwheatley (Simon Wheatley) (prof), simosx (Σίμος Ξενιτέλλης) (prof), sirzooro (Daniel Frużyński) (prof), sivel (Matt Martz) (prof), skeltoac (Andy Skelton) (prof), snumb130 (Luke Howell) (prof), solarissmoke (Samir Shah) (prof), sorich87 (prof), ssandison (prof), stencil (prof), stephdau (Stephane Daury) (prof), tai (prof), TECannon (Tracy Cannon) (prof), technosailor (Aaron Brazell) (prof), tenpura (prof), thales.tede , TheDeadMedic (prof), thee17 (Charles E. Frees-Melvin) (prof), thetoine (Antoine Girard) (prof), tinkerpriest (c.bavota) (prof), TobiasBg (Tobias Bäthge) (prof), tomtomp (prof), tychay (Terry Chay) (prof), typeomedia (prof), uglyrobot (Aaron Edwards) (prof), UnderWordPressure (prof), usermrpapa (prof), Utkarsh (Utkarsh Kukreti) (prof), validben (Benoit Gilloz ) (prof), Viper007Bond (Alex Mills) (prof), vladimir_kolesnikov (Vladimir Kolesnikov) (prof), willmot (Tom Willmot) (prof), wahgnube (prof), waltervos (Walter Vos) (prof), wds-chris (Christopher Cochran) (prof), williamsba1 (Brad Williams) (prof), wnorris (Will Norris) (prof), xibe (Xavier Borderie) (prof), yoavf (Yoav Farhi) (prof), zeo (Safirul Alredha) (prof), znarfor (François Hodierne) (prof), and zoranzaric (Zoran Zaric) (prof).

Bonus

If you’ve made it this far, check out my 2010 State of the Word speech at WordCamp San Francisco, it’s jam-packed with information on the growth of WordPress, 3.0, what we’re planning for the future, and the philosophy of WordPress.

A weekend present, in haiku:

Last call; final bugs
Itch, scratch, contort; calmly wait
For now: RC3

That’s right. What will hopefully be the final release candidate, RC3, is now available for download and testing.

Plugin developers: test your plugins!

When I was a kid my dad used to practice his typing skills (on a real typewriter no less) with the phrase:

Now is the time for all good men to come to the aid of their country.

For some reason that has stuck with me all these years. Today I’m going to rephrase and re-purpose that line:

Now is the time for great theme developers to come to the aid of their community.

The theme directory has been chugging along for more than a year now. During that time we’ve tinkered with the review process and some of the management tools, but haven’t really opened it up as much as we’d like. It’s time to rip off the band-aid and take some action; to that end, we’re looking for community members to help with the process of reviewing themes for the directory.

Right now this is a bit like a New Year’s resolution to exercise every day: it’s what we need to do, but we’re still figuring out exactly how it will all work. That’s part of the community involvement as well — we expect that those who pitch in will also help shape the process.

What’s involved in reviewing themes for the directory? There are some obvious things, such as being familiar with PHP and WordPress theme code (and the theme development checklist), with an eye for security issues. You would also need to have the ability to set up a separate install of the latest version of WordPress for testing theme submissions.

Hopefully a few talented theme developers are reading this right now and saying to themselves, “I’d love to help! How do I get started?” Just join the new theme reviewers mailing list and we’ll get you up to speed on this new opportunity to come to the aid of your community.

As Matt teased earlier, the first release candidate (RC1) for WordPress 3.0 is now available. What’s an RC? An RC comes after beta and before the final launch. It means we think we’ve got everything done: all features finished, all bugs squashed, and all potential issues addressed. But, then, with over 20 million people using WordPress with a wide variety of configurations and hosting setups, it’s entirely possible that we’ve missed something. So! For the brave of heart, please download the RC and test it out (but not on your live site unless you’re extra adventurous). Some things to know:

• Custom menus are finished! Yay!
• Multi-site is all set.
• The look of the WordPress admin has been lightened up a little bit, so you can focus more on your content.
• There are a ton of changes, so plugin authors, please test your plugins now, so that if there is a compatibility issue, we can figure it out before the final release.
• Plugin and theme *users* are also encouraged to test things out. If you find problems, let your plugin/theme authors know so they can figure out the cause.
• There are a couple of known issues.

If you are testing the RC and come across a bug, you can:

• Report it on the wp-testers mailing list
• Join the dev chat and tell us live at irc.freenode.net #wordpress-dev
• File a bug ticket on the WordPress Trac

We hope you enjoy playing with the 3.0 RC as much as we’ve enjoyed making it for you. Enjoy!

Download WordPress 3.0 RC1

Has it really been seven years since the first release of WordPress? It seems like just yesterday we were fresh to the world, a new entrant to a market everyone said was already saturated. (As a side note, if the common perception is that a market is finished and that everything interesting has been done already, it’s probably a really good time to enter it.)

The growth over the past year has blown me away. Since our last birthday we’ve doubled theme downloads to over 10 million, and doubled plugin downloads to 60 million. Most importantly, we continued to grow the development community to 1,528 people active on Trac and 13 committers, both numbers the highest in the history of WordPress.

That’s 1,528 people pouring their hearts and souls into GPL software we all own, we all build on, we can use as we please, we can all make better. We’ve evolved from a simple script to a web platform.

We’re on the cusp of version 3.0, with a release candidate coming out any minute now.

If you’d like to celebrate WordPress’s birthday with us — tell a friend! Help them upgrade their blog or find the perfect theme. Talk about how WordPress is built by and for a community. Drop in to help test 3.0, including all the plugins you use. Write something to take advantage of the new 3.0 features, or teach your friends how to. If you buy any themes or plugins, make sure they’re GPL or compatible just like WordPress. We’ve got a long road ahead of us, it’s important that we not forget that Open Source got us this far, and is the only way we’re going to get to the next level. The whole of what we can build together is far greater than the sum of our parts. Spread the good word.

Following the successful post-WordCamp San Francisco code sprint, we are now ready to release the second beta of WordPress 3.0.
Things to test:

• Revised menu user interface
• Changes to the WordPress exporter and importer to make it more flexible

Already have a test install that you want to switch over to the beta? Try the beta tester plugin.

Testers, don’t forget to use the wp-testers mailing list to discuss bugs you encounter.

We hope you like it! And if you don’t, well, check back when the release candidate is ready.

Download the WordPress 3.0 Beta 2 now!

A week from today on May 1, hundreds of WordPress users, developers, designers and general enthusiasts will descend upon San Francisco for the 4th annual WordCamp SF. Since that first WordCamp in 2006, back when WordPress was on version 2.0 (Duke), the number of people using WordPress to power their web publishing — from personal blogs to large-scale commercial sites — has grown by millions. It’s no wonder this year’s event is going to be so great.

If you’re unfamiliar with WordCamps, here’s the skinny: the San Francisco event is the flagship, put together each year under the direction of WordPress co-founder and lead developer Matt Mullenweg, who traditionally reports on the “State of the Word” and assembles a lineup of speakers that have inspired him over the past year. This year’s lineup includes luminaries such as Richard Stallman, the father of Free Software, best-selling author Scott Berkun, and Salon.com co-founder Scott Rosenberg. As the final speaker list is finalized, the remaining speakers will be added to the WordCamp SF website, but a surprise or two is still possible.

Though the main event is on Saturday, May 1, there are additional days of WordPress goodness in store. Saturday, May 1 will be the main conference with scheduled speakers. There will be keynotes, session tracks for both bloggers/end-users and developers, and lightning talks to provide a broad mix of content, followed by a raging afterparty. Sunday, May 2 will shift location and tone, with a low-key developers’ unconference for the super-code-focused attendees. May 3 and 4 are conference-free, but a WordPress core contributor in-person code sprint will span those two days, bringing together core contributors old and new from around the globe for two days of intense hacking (and let’s face it, 3.0 bug fixes).

If you’re in the Bay Area, or can be, and want to attend WordCamp San Francisco, go get your ticket today!

*     *      *      *     *

Other Upcoming WordCamps

It’s definitely WordCamp season; just check out the growing list of upcoming WordCamps over the next couple of months! If you don’t see a WordCamp near you listed here, check the rest of the schedule at WordCamp.org. In the meantime, don’t forget that many WordCamps post video of their presentations on WordPress.tv.

April 24 (today!) – WordCamp Orange County
Irvine, CA USA

April 29 – WordCamp Nashville
Nashville, TN USA

May 1 – WordCamp San Francisco
San Francisco, CA USA

May 8 – WordCamp Paris
Paris, France

May 8 – WordCamp Argentina
Buenos Aires, Argentina

May 8 – WordCamp Chile
Santiago, Chile

May 15–16 – WordCamp Denmark
Copenhagen, Denmark

May 15 – WordCamp Victoria
Victoria, BC Canada

May 21–22 – WordCamp Italy
Milan, Italy

May 22 – WordCamp Malaysia
Kuala Lumpur, Malaysia

May 22–23 – WordCamp Raleigh
Raleigh, North Carolina USA

May 29–30 – WordCamp Fayetteville
Fayetteville, Arkansas USA

May 29 – WordCamp Yokohama
Yokohama, Japan

June 5–6 – WordCamp Chicago
Chicago, Illinois USA

June 12 – WordCamp Reno-Tahoe
Reno, Nevada USA

June 12 – WordCamp Vancouver
Vancouver, Canada

June 18 – WordCamp Catania
Catania, Italy

June 19 – WordCamp Columbus
Columbus, Ohio USA

Early next week, we’re hoping to release the 2nd beta release of WordPress 3.0 on our journey toward the final version. There are still over 200 bugs in the 3.0 milestone, and we can use all the help we can get on fixing these problems. If you’re a developer, take a look at the list of bugs that still need fixing in 3.0. Write a patch, or test and give feedback on someone else’s. The tickets around custom post types and taxonomies are especially in need of help. Every little bit helps, so if you’re a developer who’s never contributed to core before, maybe now is the right time! Check out our information on contributing to WordPress core, and head over to Trac to see if there’s a problem you might know how to fix. If you get stuck, need collaborators, or have a question about the best way to approach a fix, hop into the dev channel on IRC at irc.freenode.net, channel #wordpress-dev. Core developers will be around over the weekend working on bugs themselves, so if you’re trying to help, don’t be afraid to ask questions. With your help, maybe by Monday we can knock the bug count down to half of what it is right now. How great would that be? (Answer: pretty great)

The sprint will go full force until Monday afternoon, when the lead developers and core committers will all stop to take a breath and look at the remaining bug reports to see how we did over the weekend, so don’t wait! And thanks!

Summary: A web host had a crappy server configuration that allowed people on the same box to read each others’ configuration files, and some members of the “security” press have tried to turn this into a “WordPress vulnerability” story.

WordPress, like all other web applications, must store database connection info in clear text. Encrypting credentials doesn’t matter because the keys have to be stored where the web server can read them in order to decrypt the data. If a malicious user has access to the file system — like they appeared to have in this case — it is trivial to obtain the keys and decrypt the information. When you leave the keys to the door in the lock, does it help to lock the door?

A properly configured web server will not allow users to access the files of another user, regardless of file permissions. The web server is the responsibility of the hosting provider. The methods for doing this (suexec, et al) have been around for 5+ years.

I’m not even going to link any of the articles because they have so many inaccuracies you become stupider by reading them.

If you’re a web host and you turn a bad file permissions story into a WordPress story, you’re doing something wrong.

P.S. Network Solutions, it’s “WordPress” not “Word Press.”

The deadline for students applying for Google Summer of Code this year is today, at 19:00 UTC. That’s about 3 hours from now. Still working on your application? Double check your time zone here. No late applications will be accepted.

There are a lot of potential projects on our Ideas list, so if you’ve been hemming and hawing over whether or not to apply, this is your last chance for this year. We have great people lined up to mentor the students, including most of the WordPress lead developers, some dedicated core contributors, plugin developers, the BuddyPress lead developers, etc. Google is providing a great opportunity for both students and the open source projects that act as mentoring organizations (like WordPress), so don’t pass it up if you’re an eligible student.

You can’t win if you don’t play, right? Five thousand bucks for two months of coding over the summer with WordPress hotshots. I know a lot of people that would love that deal. Oh, and hey, student girl wonders of WordPress-land: why haven’t you applied yet?

Apply now! (Don’t forget to use our application template.)