@otto42: Was there ever any resolution to the issue of plugin search for exact name matches? Search for “contact form 7″ and it’s the 14th result. Is there any way we can improve that for exact text matches?

WordCamp Phoenix Developer Day

We’ll list some simple tickets here that you guys can work on right now. Please post a link to the ticket you are working on so we can help. You can help by writing a patch or testing the current patch to see if it applies cleanly and fixes the bug.

#14955, #14994, #15358, #16293, #16302, #16235, #16214

more to come

We spun WordPress 3.1 off into a branch. Several of us are at the WordCamp Phoenix core development workshop, and wanted to be able to tackle some minor enhancements or bugs so that we can get “buy in” by the participants and get them their first props.

Subversion switch your test installs to branches/3.1. Except for today at the workshop, we’re not going to be doing any 3.2 stuff. Don’t get distracted! We still need you to test the heck out of 3.1, and are hopeful that we can release soon.

Update: I created a “wcphx” milestone, against which we can close any tickets we do today. That will become the 3.2 milestone after 3.1 is released, so we have the historical record that the tickets were closed against 3.2. I just don’t want to call it 3.2 now or people will start putting tickets in that milestone.

Update 2: We sort of ran out of time before we got to committing stuff. Got a lot of people hooked up with local dev environments (or better local dev environments). and spent a lot of time getting them up to speed on Trac. And of course spreading the gospel of debug bar. Going to just leave the 3.1 branch. We’d have to create it in a few days anyway. So until 3.1 launches, trunk and branches/3.1 should remain identical.

Core contributors: who will be at SxSW this year? Looking at putting something together, want to get an idea of how many people might attend.

General Trac usage note:

Please don’t edit your own comments beyond fixing typos or improper formatting. Many of us consume Trac through the mailing list, and adding to a comment or changing its meaning makes this much more difficult.

I don’t think it’s necessary to need to go through the process of installing a Trac plugin to prevent comment editing. I’d just like to see edits be rare and trivial.

I added child theme support to the theme previewer for /extend/themes. The only child theme we have in there at present that I know of is this one: http://wordpress.org/extend/themes/mazeld , but now the preview works for it. Note that the parent theme of a child theme must also be in /extend/themes for this to work.

#wptybee update!

Thursday

• The core commit team (+me) talked with the people working on the WordPress mobile apps via audio skype chat after several attempts at video were an utter failure due to bandwidth issues. All agreed that we needed to build a stronger tie between the web app and the mobile apps. To that end, the mobile app devs will start attending our weekly dev chats to stay up to date with new developments (heh), and will occasionally post updates here on this blog to keep everyone aware of mobile app news. We’ll also get the UI group involved in mobile app UI/usability testing where appropriate. A link has been added to the Extend submenu on .org that goes to a page listing all the mobile apps and their sites, to raise visibility.
• Huge Tracfest. Sifted through awaiting review and future release tickets, talked about ways that we could improve the triage/bug gardening process. Trac-ity Trac-ity Trac-ity.
• BBQ dinner brought over by Gerald of Gerald’s Pig and Shrimp BBQ (though there was no shrimp). His business is closed for the season and he doesn’t usually cook for such small groups in the off-season, but he let himself be sweet-talked into it because he has a WordPress blog. Running Kubrick! He came over with a truck full of meat, black eyed peas, lima beans, rice, and fried okra. It fortified the guys for…
• All-night continuation of Tracfest.

Friday

• We started out the day by talking about ways to improve the plugin repo submission experience, possible ways to promote good/safe plugins and de-emphasize abandoned ones that no longer work with current version, and infrastructure that could help with these goals. We also had a knock-down, drag-out fight over the best way to deal with plugins whose authors have abandoned them if someone else wants to step up to take over. I say this not to imply there is dissension in the ranks of the core leadership, but to show that this is a group of passionate people with strong opinions about the best way to do things to further the WP project. If you’ve ever been bummed because half the core team didn’t agree with you and shot down your idea, at least take heart that we’re all in the same boat!
• Licensing. We committed to reviewed every licensing ticket opened by hakre or anyone else on Trac. We got through all of them, and wound up with a list of what to do about them/assigning people to make whatever patches were deemed necessary. Also see Mark’s post from last night, related to one of them.
• Improving updates. Talked about things like partial updates, language packs, compatibility checks, notifications, memory leaks, etc.
• Unit tests. We need more stuff. Also, Peter is going to write up Mac and Windows instructions for getting the test suite running.
• Tracfest.
• Lost time to tangents not directly related to either 3.1 release or the topics on the agenda for 2011 vision due to vocal minority/people who are convinced that their needs are more important than anyone else’s. I’m supposed to be savvy enough not to come right out and say things like that, but it’s been a long week, and lets face it: if half the core team didn’t lose so much time to the handful of people who loudly demand attention on wp-hackers, twitter, etc, we probably could have had 3.1 launched by now.
• Regained better humor (lowered due to said time suck of tangents) by invading ##wpchat and being silly. Sorry guys, for the interruption. At least our bandwidth was bad enough that we weren’t there for long!

Saturday

We have a long list of things to get through today. May try to enforce a period of social media silence and make everyone close twitter etc so we can’t be distracted as outlined above. If we don’t answer you about something today, please don’t be offended — we just really need to get a lot of work done, and we only have one day left to do it.

In the meantime, since the internet connection has made doing a live town hall impossible, we could at least try to record one and post it. Feel free to post questions you’d like us to answer on video in the comments. You can ask of the general team, or ask someone specifically (people here include Matt M, Ryan Boren, Mark Jaquith, Peter Westwood, Dion Hulse (dd32), Andrew Nacin, Daryl Koopersmith, Pete Mall, Austin Matzko (filosofo), Mike Adams (mdawaffe), John Ford (aldenta), John James Jacoby (jjj) and me).

Clarification in Licensing Language

WordPress has always stated that its license was the GNU GPL, and has bundled version 2 of the license, even though no GPL version was specified. The text of version 2 (as well as 1 and 3) says that if no version is specified, the software can be redistributed under the terms of any version of the GPL published by the FSF.

However, WordPress contains libraries which are licensed under the GPL “version 2 or any later version,” which obviously excludes version 1 of the GPL. Here is the reality: the GPL version 1 is effectively irrelevant. It hasn’t been a commonly used license since before Matt Mullenweg was in third grade! Clarifying WordPress as being licensed under the GPL “version 2 or later” resolves these niggling library licensing concerns or ambiguities, and clarifies where WordPress stands.

It was the intention of the WordPress founders and developers to be GPL version 2 or later from the beginning, and we have now made that license properly explicit.

FYI – Akismet WordPress plugin 2.5.2 was released today – announcement.

diff from 2.5.1 to 2.5.2

This release was mostly to refine a few issues that had been observed in 2.5.1.

Added a new page to WordPress.org: http://wordpress.org/extend/mobile/
Also added it to the dropdown menu under extend.