WordPress Blog

BuddyPress for One (and All!)

Posted February 26, 2010 by Jane Wells. Filed under Cousins.

Back in April of last year, Matt posted here on the dev blog about the release of BuddyPress 1.0, a plugin that adds a social networking layer to an installation of WordPress MU. Many people were excited about the idea, but were unable to experiment with BuddyPress because they ran single installations of WordPress rather than the multi-site WordPress MU. To those people, good news! A little over a week ago Andy Peatling, founder and lead developer of BuddyPress, announced the release of BuddyPress 1.2, which can be used on single installations of WordPress. Congratulations, BuddyPress! And congratulations to all the people who’ve been waiting with bated breath for this to happen.

The first thing I thought when I heard the news was, “Awesome! Now everyone can put BuddyPress on their site if they want it.” The second thought I had was, “Shoot! Average WordPress users won’t want to try BuddyPress if they have to switch their site themes over to the BuddyPress default theme just to try it out.” The third thought I had was, “That can’t be right. I’ll ask Andy.”

As it turned out, you could keep your current theme with BuddyPress if you added a couple of files and made a few file edits. There was even a link on the BuddyPress site to download the necessary files. That still seemed a little clunky, though, so Andy, super awesome guy that he is, went ahead and made a plugin to get you started. The BuddyPress Template Pack can be installed directly from your WordPress admin (Plugins > Add New), and will walk you through the theme additions step by step.*

Now you can use BuddyPress with your single site installation of WordPress, and you can keep your existing theme. Seriously, could BuddyPress have made it any easier for you to add social networking to your site? I know I can’t wait to try it out this weekend, how about you?

* Don’t forget to install BuddyPress itself, or the template pack plugin won’t do anything!

Menus, the Merge, and a Patch Sprint!

Posted February 23, 2010 by Jane Wells. Filed under Development.

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.

WordPress On The Go

Posted February 17, 2010 by Jane Wells. Filed under Development.

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:

Screenshot of WordPress mobile apps

“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 emailing the translation team. They’ll send you instructions on how to translate.

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.

WordPress 2.9.2

Posted February 15, 2010 by Ryan Boren. Filed under Releases.

Thomas Mackenzie alerted us to a problem where logged in users can peek at trashed posts belonging to other authors. If you have untrusted users signed up on your blog and sensitive posts in the trash, you should upgrade to 2.9.2.  As always, you can visit the Tools->Upgrade menu to upgrade.

WordPress Foundation

Posted January 22, 2010 by Jane Wells. Filed under Meta.

It is with extremely great pleasure that I point you to the first post at the new WordPress Foundation site. Not only am I excited about the things that will happen under the auspices of the Foundation, I’m excited to see a site running the 3.0 development version and the nascent theme called 2010. Go check it out for yourself.

2010 Open Source Design Plans

Posted January 13, 2010 by Jane Wells. Filed under Community, User Interface.

2010 is the year we dive into open source design. We’ve dipped our toes in this pool before (icon contest, graphic design component for Trac tickets, header refresh contest, etc.), but this year we’re going to cannonball and make a big splash. Here’s what you need to know if you want to get involved.

A list for all seasons. Developers have the wp-hackers mailing list to discuss core and plugin code. Sometimes UI/UX stuff comes up and gets discussed there, but there is a whole universe of discussion around navigation labels, gradients, button styling, layouts, alignment, etc. that would be clutter on wp-hackers. Designers need a list to call their own, and now we have one. You can sign up for the wp-ui list to discuss ways to improve the interface or user experience of WordPress, and to discuss progress on design-related projects for the open source project, like the design challenges we’re going to have.

Design Challenges. We learned a lot from the icon design and header refresh contests, and we want to do these kind of open design challenges on a regular basis to give UI/UX designers who want to contribute to the WordPress open source project more opportunities to do so. If we could do one per month, that would be ideal, keeping the challenges relatively bite-sized to allow potential contributors an easy way to get involved at first. As each challenge is posted, people can use the list to bounce ideas off each other and work toward optimal solutions. I’m hoping the design challenges will evolve to be less contest and more collaboration. We’ll announce the first one before the end of January, so if you’re interested, please sign up for the list! (Hint: one will likely be a touch up to the Right Now dashboard module, to improve the information design, and there will be a couple of screen layout challenges coming up as well.)

Distributed Usability Testing. We started to try this out last year, and several dozen usability professionals volunteered to help get the program going, but a combination of scheduling and infrastructure issues combined to stall the progress. Having the “UI/UX contributor team” infrastructure in place, starting with the mailing list, will make it much easier to get this project going again.

Chit-chat. The weekly developer chats in IRC at #wordpress-dev have been very productive. We’ve created an IRC room at #wordpress-ui on irc.freenode.net so that we can have the same kind of “water cooler” for UI/UX contributors as for core code contributors. In addition to being a place where you can drop in and discuss core UI/UX (note: this room will not be a place to discuss the design of blog themes, it’s to discuss the design of the Wordpress application itself), we’ll set up a weekly chat. Choosing a day and time for the chats will probably be the first discussion on the mailing list.

A blog of our own. Once again, taking a page from the code contributor infrastructure, we’ll set up a blog for UI/UX updates, announcements, progress reports, etc. This will be on WordPress.org in the nearish future, and will be announced to the mailing list when it is live.

So, if you want to become a contributor to core WordPress by using your design skills, join the wp-ui mailing list and get ready for a fun year!

WordPress 2.9.1

Posted January 4, 2010 by Ryan Boren. Filed under Releases.

After over a million downloads of WordPress 2.9 and lots of feedback from all of you, we’re releasing WordPress  2.9.1.  This release addresses a handful of minor issues as well as a rather annoying problem where scheduled posts and pingbacks are not processed correctly due to incompatibilities with some hosts.  If any of these issues affect you, give 2.9.1 a try.  Download 2.9.1 or upgrade automatically from the Tools->Upgrade menu in your blog’s admin area.

Early 2010 WordCamps

Posted by Jane Wells. Filed under WordCamp.

Rested up from the holidays? I hope so, because the new year has begun and a lot is going to be happening with WordPress in 2010, and you definitely want to be a part of it. Later this week the scope for version 3.0 (featuring the addition of MU functionality to the WordPress codebase) will be decided in the IRC developer chat*, based on feedback provided by users like you. But it’s no fun to live by IRC alone, which is why we love WordCamps. Attending a WordCamp gives you a chance to meet people in your local community who are working with WordPress, as well as core contributors, theme designers, plugin developers, Codex writers, support forum moderators and other WordPress volunteers who’ve made WordPress what it is today. Add this New Year’s Resolution to your 2010 list if it’s not on there already: Attend a WordCamp, meet at least 5 new local people, learn something new, and if you have the chance, buy a drink for someone who’s volunteered their time and expertise to the WordPress open source project. To help you keep your resolution, here is a list of the upcoming WordCamps for the next three months, followed by what I know so far about each one.

January 8–9: WordCamp Atlanta
January 23: WordCamp Boston
January 30: WordCamp Greece in Thessaloniki
January 30: WordCamp Indonesia in Jakarta
February 27: WordCamp Fukuoka
March 6–7: WordCamp Ireland in Kilkenny
March 27–28: WordCamp Toronto

NORTH AMERICA

January 8–9: WordCamp Atlanta. First WordCamp of the year, and it’s already sold out — twice! They changed to a bigger venue based on demand, from Georgia Tech to the Atlanta campus of Savannah College of Art and Design (SCAD). They’re still letting people onto the waitlist, if you’re interested. A guaranteed way to get in would be to sponsor the event, and they’re taking last-minute sponsors right now. Atlanta will have sessions on Friday evening and all day Saturday. I’ll be opening the Saturday program with WordPress Resolutions: What to Expect in 2010. After a day of design, development and content track sessions, Lead Developer Mark Jaquith will take the closing slot for a Town Hall-style Q&A. The attendee list (follow link, scroll down) includes a number of WordPress core contributors, theme/plugin developers, and support providers as well as proof that Atlanta has a strong WordPress user base.

January 23: WordCamp Boston. I think WordCamp Boston is trying to one-up every WordCamp the organizers have been to, including the awesome NYC from November, and it looks like they might succeed. From Doc Searls and David Weinberger as keynote speakers to the multiple-track, unconference and Ignite sessions to the sweet-looking venue and the party plans, this one has got it going on. I credit it in part to the fact that they are one of the few WordCamps to follow the advice of having an organizing team of more than just 2 or 3 people, so the work is better distributed. I see a number of familiar names on the attendee list, but even more that I don’t know, so I’m looking forward to meeting the Boston WordPress community. They’re still selling tickets, so if you’re in the northeast, you should try to make it. I’ll be at this one also, talking about how the merge with MU will affect the WordPress admin (by then we should have started figuring it out!).

March 27–28: WordCamp Toronto. The last two Toronto WordCamps have been really good. I heard there would be one in March, but their site right now is just taking emails for notification. I’ve contacted the organizer to see what’s up, and he says the site will likely go live this week. They’re looking for volunteers to help organize this year’s event, so if you’re interested, it would be a great opportunity to get involved. Believe me, volunteering at a WordCamp is one of the best ways to make sure you meet a lot of other attendees.

ASIA

January 30: WordCamp Indonesia. WordCamp Indonesia will be in Jakarta again this year. I love how they worded the beginning of their sessions page. “Come in, we’ll get you breakfast and coffee, you’ll register, there’ll be networking. It’ll be great.” There will be a single track of sessions, but there are several time slots set aside for ad-hoc discussion and breakout sessions.

February 27: WordCamp Fukuoka. WordCamp Fukuoka is just getting its site up, too, so check back periodically a little later for more information. One of their visiting speakers will be Noel Jackson, developer of the Press This bookmarklet as well as themes like P2 and Monotone/Duotone.

EUROPE

January 30: WordCamp Greece. WordCamp Greece will be held in Thessaloniki, and they expect about 100-150 people to attend.The program includes regular sessions on the usual topics (how-to, programming, SEO, multi-language sites, etc) as well as “QuickRounds,” which will showcase Greek projects based on WordPress. I’m especially intrigued by the “WordPress vs. Expression Engine” session. Whenever people compare different publishing platforms, it’s interesting to see which features they highlight. I hope someone gets video from this one and posts it to the WordCamp section of WordPress.tv.

March 6–7: WordCamp Ireland. WordCamp Ireland will be in Kilkenny, and for such a geographically small country, it’s got an impressive list of speakers, including Donncha O Caoimh, lead developer of WordPress MU. The program includes three tracks: Intro, Blogger, and Developer, and I think this will be the first WordCamp I’ve heard of that is deliberately family-friendly, with on-site child care. They’re also going to have a charging station for mobile devices, which is clever. It’s not confirmed yet, but I think I’ll be at this one, too.

If you want to attend a WordCamp but don’t know of one near you, check out WordCamp.org for the official list (updated frequently). That’s also where you would start if you wanted to organize a WordCamp in your area.

*Developer chats are held Thursdays at 21:00 UTC in the #wordpress-dev channel at irc.freenode.com.

WordPress 2.9.1 Release Candidate 1

Posted December 29, 2009 by Ryan Boren. Filed under Development, Releases.

Thanks to everyone who tested 2.9.1 Beta 1.  We’re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of fixed tickets up to 23.  If you are already running Beta 1, visit Tools->Upgrade in your blog’s admin to get RC1.  You can also  download the RC1 package and install manually.  If all goes well, 2.9.1 will be here soon.

Setting Scope

Posted December 25, 2009 by Jane Wells. Filed under Development.

Merry Christmas! One of the things that was discussed at the core commit team meetup was release scope (and scope creep). Now that 2.9 is out and it’s time to start thinking about 3.0, we think it would be appropriate to stop and take a breath before diving in, and make a plan in advance. What winds up happening is that during each release cycle a few new features are selected for inclusion, but then right up until feature freeze (and/or beta cycle), people keep adding feature requests, patches for enhancements, and ongoing bug reports. This means each release winds up getting pushed out later than planned, and with so many things going in per release, it becomes harder to catch new bugs.

The as-long-as-we’re-not-in-freeze-yet model isn’t working. People wind up waiting months longer for new features they want, like Trash and Image Editing, because we’re still adding other things and then we need to test them all. If we kept the releases smaller feature-wise, we could push out the new stuff sooner (3 releases per year is the goal) and have more focused beta testing, making the releases themselves better. It’s hard, because everyone has their pet features and fixes, and if there’s a patch, why not get it in this release rather than waiting? Sometimes people complain that a patch has been waiting to be committed for weeks or months, but what no one ever seems to bring up is that sometimes patches introduce new bugs, and the more we add at once, the harder it is to keep it all well-tested on various platforms, in different hosting environments, etc. So. What’s our proposal?

We take a page from the world of project management and we make a project plan before we jump into the dev cycle. We let everyone propose features and enhancements, and we choose a limited number to include in 3.0 (in this case we need to be especially stringent, because the merge of WordPress and WordPress MU will automatically mean a lot of work) and set a realistic release date that we stick to. We create a tentative set of features for the next two releases, to be re-evaluated at the beginning of the next cycle, so that people know the community is committed to certain features, as opposed to the vague “future release” label we now use for everything not included in the current version. We fix bugs that are reproducible and affect a large number of users before focusing on edge case bugs or bugs that haven’t been well-described or reproduced. We stop diverting our attention from agreed-upon goals when a “squeaky wheel” decides we should all be focused on something else. There are always things that pop up unexpectedly, but we need to do a better job of restraining ourselves when it comes to trying to sneak things into the current release (I include myself in this, of course…as a UX person I always wish we could do everything all at once!).

As an open source project, we accomplish more when we work together than we do following individual agendas, and we need to keep our project focused on commonly-agreed-upon goals instead of following tangents whenever a community member starts to take us on one, regardless of whether it’s to follow a cool idea that everyone loves or a suggestion based on a personal agenda, and regardless of whether it’s a newbie who doesn’t know any better or a frequent contributor or committer who has a strong opinion and a loud voice (so to speak). The issue here is that it’s easy to get distracted, so we need to create a structure that will help us keep moving forward instead of getting sidetracked. We need to keep Trac clean for the current dev cycle so that it includes confirmed features and bug reports, and all new feature suggestions go into a different milestone.

We think it’s at least worth a try. When we re-start the weekly IRC dev chats in 2010, the first meeting will be to talk about the scope of 3.0. When we’ve got a general agreement about what will be included, we’ll create the appropriate Trac tickets, and punt tickets for non-3.0 feature requests/enhancements to a future release so we can stay focused. New bug reports will still come in to the current milestone. It’s going to be hard. There are at least a dozen new features that I feel like we’ve pushed back multiple times that I’d like to see in core, but for this experiment, I’m just going to keep reminding myself, “You can do that with a plugin!”

Sound off on the features you would like to see in version 3.0.

Older Posts »

0.093

See Also:

For more WordPress news, check out the WordPress Planet.

There’s also a development P2 blog.

To see how active the project is check out our Trac timeline, it often has 20–30 updates per day.

Categories