Remember when I posted earlier about the Twitter account, and I said that hopefully you’d find out later today what has been keeping us all so busy? Beta testers, this is your moment: the WordPress 3.0 Beta 1 has arrived!

This is an early beta. This means there are a few things we’re still finishing. We wanted to get people testing it this weekend, so we’re releasing it now rather than waiting another week until everything is finalized and polished. There’s a ton of stuff going on in 3.0, so this time we’re giving you a list of things to check out, so that we can make sure people are testing all the things that need it.

You Should Know:

• The custom menus system (Appearance > Menus) is not quite finished. In Beta 2, the layout will be different and a bunch of the functionality will be improved, but we didn’t want to hold things up for this one screen. You can play with making custom menus, and report bugs if you find them, but this is not how the final screen will look/work, so don’t get attached to it.
• The merge! Yes, WordPress and WordPress MU have merged. This does not mean that you can suddenly start adding a bunch of new blogs from within your regular WordPress Dashboard. If you’re interested in testing the Super Admin stuff associated with multiple sites, you’ll need some simple directions to get started.
• We’re still fiddling with a few small things in the UI, as we were focused on getting the more function-oriented code finished first. For example, we’re getting a new icon for the Super Admin section.

Things to test:

• Play with the new default theme, Twenty Ten, including the custom background and header options.
• Custom Post Type functionality has been beefed up. It’s really easy to add new types, so do that and see how it looks!
• WordPress MU users should test the multiple sites functionality to make sure nothing broke during the merge.

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 beta 2 is ready.

Download the WordPress 3.0 Beta 1 now!

Scene: A college classroom

Professor: So. Out of the 20 students in the class, half wrote WordPress Summer of Code proposals good enough to receive an A. How many of you are planning to apply for the program?

Jack, a student: I am. They opened applications today.

Sophie, a student: I am. And that sentence was grammatically terrible.

Jack: Shut up.

Chris, a student: I’m not applying.

Jack (to Chris): Chicken?

Sophie: You’re such a jerk! Maybe he has a job lined up or something, did you ever think of that?

Professor: Whoa -

Chris: Actually, I’m going backpacking in Australia with my Dad. No internet for about half the time, and when I emailed the people at WordPress they said I should probably wait until next year to apply and make sure I’d be able to be online through the whole summer.

Professor: Fair enough. The application period opens today at 19:00 UTC and goes through April 9th, so let’s hear from the people who are applying.

Jack: I’m submitting mine today.

Sophie: That’s just stupid.

Andrea, a teacher’s assistant: Hey, that’s not necessary.

Jack: Yeah! The early bird gets the worm, or hadn’t you heard?

Sophie: What I heard was that the WordPress mentors are holding open IRC chats this week to talk to prospective students and give them feedback on proposals and ideas, and that talking directly to the mentors ups your chances of being selected. But I guess you don’t think you need the people who are actually choosing the students to know your name because your proposal is so brilliant?

Jack’s jaw drops.

Jack: Where did you hear that? It wasn’t on the GSoC mailing list.

Sophie: I joined the wp-hackers list and asked all the core contributors for feedback on my idea, and then I emailed 3 potential mentors to see what they thought of it personally. By the time applications are due, I’ll have revised it based on community and mentor feedback, and enough people will know who I am — and that I’m full of initiative — that my chances of being accepted will be much better.

Jack: You think you’re all Felicia Day with your MW2 level 70, but you’re just a computer nerd.

Sophie: Um, duh. We’re in an advanced computer programming class. We’re all computer nerds.

Professor: Now, now. Sophie’s correct; talking to community members and mentors will improve her chances. But, Jack, there’s no reason you can’t join the IRC chats and the mailing list to get your name out there, too, even if you submit your application today. Most proposals get tweaked a bit after the students are chosen anyway.

Sophie: Plus, Felicia Day is awesome! And she uses WordPress, so ha!

End Act II.

Here’s the deal. The application period opens today. Early applications will likely get a bit more attention up front, but it’s also important that your ideas and approach are vetted by the community and the mentors. If you haven’t already, you should join the wp-hackers mailing list and send your proposal to the list for feedback. We’ll also be doing a few IRC chats during the application period to give students a chance to talk directly with the mentors. Note that not every mentor will attend all three chats, so if you want to talk to a specific person, you might want to email them. Please arrive on time to the chats, as they will be scheduled for an hour, and will have to accommodate multiple students. IRC chats will be held at irc.freenode.net in room #wordpress-gsoc.

• Wednesday, March March 31 at 20:30 UTC (4:30pm eastern)
• Saturday, April 3 at 21:30 UTC (5:30pm eastern)
• Wednesday, April 7 at 20:30 UTC (4:30pm eastern)

This chat room will remain open during the application period, and various mentors and community members may be there and able to answer questions, but the scheduled chats are the only official times at which they are scheduled to do so.

Oh, and if you want to help publicize the WordPress summer of code, grab a flyer and post it somewhere on a bulletin board at your local college campus. Professors, don’t forget to encourage your brightest students to apply!

Scene: A college classroom

Professor: Is anyone here applying for Google Summer of Code this year? If so, see me after class to discuss getting independent study credit toward your degree.

Jack, a student: Isn’t that a really hard program to get into? Like, hard like getting to level 70 in Modern Warfare 2?

Sophie, a student: I went past 70, I prestiged.

Jack (turning to Sophie): Shut up, you did not!

Sophie: I did, too!

Professor: Not the point, kids. So who’s going to try for a GSoC spot?

Andrea, a teacher’s assistant: There are some great open source projects participating this year. I’d love to see someone from this class get in on the WordPress project.

Jack: WordPress is awesome, but my friend Billy didn’t get chosen by them last year.

Sophie: Billy’s not as smart as he thinks he is.

Jack: You think you could do better?!

Sophie: Of course I do! Any primate could do better than Billy! Or you, for that matter!

Jack: What? I would so beat you out in a coding competition!

Andrea: Sounds like we have the makings of a friendly classroom competition, Prof.

Professor: I think you’re right, Andrea. Tell you kids what. They announce the students who’ve been accepted on April 26th, which is before the semester ends. Let’s turn this into a class project.

Jack (raising a suspicious eyebrow): How do you mean?

Professor: As a class assignment, everyone has one week to write a project proposal for the Google Summer of Code, specific to the WordPress project. The proposals will be graded like a regular assignment. Anyone who gets an A on the proposal can use me as a reference if they apply with the proposal to WordPress and Google for the program. The application deadline is April 9, so you’ll have time to revise your application after it’s been graded.

Sophie: What’s in it for us?

Andrea: If you’re successful in GSoC you earn $5000 for the summer.

Sophie (smirking, to Jack): That’s more than you’ll make working the hot dog cart by City Hall.

Jack: You wish. I’m totally getting in, and you’ll be on the hot dog cart this year.

Professor: And as I was starting to say in the first place, a GSoC project would qualify for independent study credit. Tell you what, as an added bonus, anyone who actually gets accepted into the WordPress GSoC program will get extra credit points on their year end average.

Sophie (perking up): Really? I’m in!

Jack: No way, they’ll choose me first!

Stay tuned for the continuing adventures of Jack and Sophie as they navigate the course of applying to Google Summer of Code to work with WordPress.

That’s right, WordPress is honored to be among the 150 open source organizations chosen to participate in Google Summer of Code this year. Students work on WordPress projects over the summer under the guidance of mentors from among the WordPress core developers, and if they complete their projects successfully Google pays them $5000! Talk about a win-win. Last year’s projects led to some very cool code being created, like the new search API targeted for version 3.0 and the Elastic theme generator.

Professors: Help us and your students by telling them about GSoC and encouraging them to apply. Consider having them write a WordPress plugin or core patch as a class assignment so they can get to know the codebase. Offer to sign on as an adviser for a summer independent study so they can get credit for their work with GSoC.

Students: Check out our Ideas page, and start thinking about projects you’d like to propose. Watch this space for an announcement of some live chat information sessions where you can ask potential mentors questions and get feedback on your pre-proposal ideas. This program is competitive, but is one of the best opportunities out there when it comes to programming. You get real-world experience as a member of an open source community, you make decent money, you make connections with industry leaders, and you get the attention of Google. Not to mention some serious bragging rights. What are you waiting for? Applications will be accepted from March 29-April 9, so start thinking about a project now!

A Report from the 3.0 Development Cycle

Menus

There’s been a flurry of blog posts about the integration of the WooThemes Custom Navigation into WordPress core, so I thought it was time we posted the official word. For 3.0, the main user-facing feature we wanted to include was a better site menu management system. Currently, dealing with menus is clunky, using Page IDs or in some cases categories, if a theme uses categories instead of pages for the menu. We wanted a menu system that had the drag and drop ease of the widget management screen, could combine Pages, Categories, and Links, was able to be re-ordered, allowed submenus, and enabled hiding specific Pages or Categories from the menu altogether. We were in the process of building this when WooThemes introduced their Custom Navigation system. Watching their introductory video, it seemed that their system did pretty much everything we wanted to do for core, so we reached out to them about contributing to core.

As you’ve probably heard, it worked out, and the first patch has been submitted. It does require some code modification, which is happening now. The decision to incorporate the Woo menus happened right before our planned feature freeze for the 3.0 development cycle, so we pushed our freeze date back by two weeks to allow the addition. We’re now targeting the 3.0 release for early May, and we think it will be worth the extra two-week wait.

I’m personally really happy that it worked out this way, because I think it will show commercial theme and plugin authors that contributing to core is a win-win proposition. More people can contribute to and improve the basic functional code now, while WooThemes can continue to innovate on top of it for their customers. They get massive bragging rights (which I have no doubt will lead to even more customers), core gets a nice menu system without having to reinvent the wheel, and WordPress users all over the world will benefit. I’m hoping other plugin and theme developers will take a cue from Woo and look at core as a place for collaboration, rather than competition.

The Merge

It was announced at WordCamp San Francisco last year that WordPress and WordPress MU would be merging codebases. This has now happened in 3.0-alpha, and we’re working on smashing bugs and tidying up a few screens. If you’re currently using a single install of WordPress, when you upgrade to 3.0 you won’t see any of the extra screens associated with running a network of sites. If you’re currently running MU, when you upgrade you’ll notice a few labels changing, but upgrading should be as painless as usual. If you’re going to set up a new WordPress installation, you’ll be asked as part of the setup if you want one site or multiple sites, so that’s pretty simple. If you want to turn your single install into one that supports multiple sites, we’ll have a tool for you to use to do that, too. So if you’ve been worried about the merge, have a cup of chamomile tea and relax; it will all be fine.

Patch Sprint!

Okay, so where are we now? The new feature freeze date is on Monday, March 1, 2010. That means that after that date, no more enhancements or features will be added, and we’ll switch gears to focus solely on crushing bugs and fixing up the features that have already made it in. That means we only have a week to try and finish up the many Trac tickets on the 3.0 milestone that either need a patch or have a patch that needs testing. You can help! From now until noon eastern time on March 1 (that’s 17:00 UTC on March 1), head on over to Trac and pitch in. If you hit a wall, hop into the core development channel at #wordpress-dev on irc.freenode.net and hopefully one of the friendly core contributors can give you a push.

I like to moderate comments when I’m waiting for something: a checkout clerk to help me, the dentist to call me back to the office, a soy chai to be made. I don’t lug my laptop everywhere I go,* so I love it that we have mobile apps that make this possible. I don’t know of any other blogging platform that has mobile apps for iPhone, Android and Blackberry. Do you?

The iPhone app is up to version 2.2 (note that iPhone app version numbers do not correlate to WordPress core versions, due to separate dev cycles), while the Android and Blackberry apps are brand new. You can write posts (save drafts or publish right away), moderate comments, blog photos from your phone (and video on Blackberry!**), and more. Check out the glory that is mobile WordPress in the image below:

“But what about my Nokia,” you ask? Raanan Bar-Cohen, who oversees the mobile projects, recently announced:

“We are very excited to share with all of you that in the coming weeks we’ll be opening up a beta test for the official Open Source WordPress for Nokia app. For developers who are interested in getting involved, we just opened up a dev blog with details, links to the source code and trac tickets, and an early alpha build. We’ll be leveraging the Qt framework which means will be able to support both the S60 and Maemo platforms.”

W00t!

Getting Involved

All of these mobile WordPress apps are free and open source. They are developed in the same manner as WordPress core, which means anyone can contribute! If you’ve got some mad mobile development skills and want to get involved, a) you’re awesome, and b) here are a bunch of useful links.

Development Blogs: Android | BlackBerry | iPhone

Development Tracs: Android | Blackberry | iPhone

Feedback Forums: Android | BlackBerry | iPhone

Language Support: WordPress users come from all over the world. The mobile apps here are available in multiple languages but need volunteers to enable even more people to use them. If you’re interested in helping localize these mobile apps, you can get involved by visiting translate.wordpress.org.

Getting the Apps

So go for it — download the app for your platform of choice and soon you, too, can be live posting about how slow the cashier is while you wait for him to ring you up!

* Okay, yes, I do bring my laptop everywhere, but I leave it in the bag on these occasions.

** Video support should  be coming soon to the iPhone and Android apps.