Canonical plugins would be plugins that are community developed (multiple developers, not just one person) and address the most popular functionality requests with superlative execution. These plugins would be GPL and live in the WordPress.org repo, and would be developed in close connection with WordPress core. There would be a very strong relationship between core and these plugins that ensured that a) the plugin code would be secure and the best possible example of coding standards, and b) that new versions of WordPress would be tested against these plugins prior to release to ensure compatibility. There would be a screen within the Plugins section of the WordPress admin to feature these canonical plugins as a kind of Editor’s Choice or Verified guarantee. These plugins would be a true extension of core WordPress in terms of compatibility, security and support.
In order to have a system like this, each canonical plugin’s development community would probably need similar infrastructure to WordPress itself, including things like Trac, mailing lists, support forums, etc. These things will be worked out within the development community over the coming months, but in the meantime, we really need a better name for this. Many people have no idea what canon/canonical means (clearly, they are not Dr. Who fans!), and having to define the word distracts from discussing the core ideas behind the concept. So, we thought we’d do a community poll to see what people think we should call canonical plugins. We brainstormed a few dozen ideas yesterday and whittled it down to our top handful. Based on the definition of canonical plugins given above, which of these terms do you think best describes them? I’m including a short description of our thoughts on each.
Standard - Implies that these are the standard by which all other plugins should be judged, as well as the idea of them being the default plugins.
Core - Makes the close relationship to core WordPress development very clear, and has the implication of bundled plugins (even though we don’t need to actually bundle them now that the installer is right in the admin tool).
Premium – Identifies these officially-supported plugins as best-in-class and of the highest value, and could potentially disambiguate the word Premium as it is currently being used in the community (to refer to anything from commercial support to licensing terms to actual code quality).
Validated - Focuses on the fact that the code is reviewed for compatibility with core and for security.
Official – Makes it plain that these are the plugins officially endorsed by the core team as being the best at their functions.
Canonical – Maybe once people get used to it, canonical wouldn’t confuse so many people?
Cast your vote in the poll below to have your opinion considered during the decision-making process. And if you can think of a word that we haven’t listed here that you think is better, please submit it in the poll! The poll will remain open until 11:59pm UTC Thursday, December 10, 2009.
Just a heads up that Trac commits will be pretty low over the next couple of days, as all the core committers are in Orlando: Matt, Ryan, Andrew, Peter and Mark. We all came for WordCamp Orlando (fun!) and are staying a couple of extra days to discuss the vision for WordPress in the coming year, the merge, canonical plugins, the WordPress.org site, community stuff, and all the other things that are important but that we never seem to have time to address. Since when things like this come up in the IRC dev chat or in various forums there’s inevitably a point at which someone says, “We really need to have [insert a core committer name here] here to make a decision,” we thought it would make sense to get together and figure out where everyone stands on all these ideas so that we can move forward a little more efficiently. Also, not all the committers had met in person before (and I’d never met Andrew or Peter), so it’s also a chance for us to just get to know each other a little. Watch this space around Tuesday or Wednesday for a post summarizing the things we’ve discussed, and the beginning of planning for how members of community can get involved in (or spearhead) the things that interest them.
]]>Forum volunteers don’t get a lot of flashy attention. There aren’t flame wars about whether or not the support forums should be commercial instead of free and community-run. There generally aren’t big arguments and debates over whose point of view is the right one. What the forums do have is amazing volunteers who give their time to help other WordPress users and developers learn. People who only know a little answer easy questions that maybe they’ve only recently learned the answers to themselves. People with more expert skills help troubleshoot larger issues. If someone offers advice that could be better, others will add their solutions to the mix. Of all the WordPress users I’ve met in person, not one person got started without visiting the forums. In many cases, people turn to the forums even before the Codex. In the support forums, I see a lot of what is best about our community, and almost none of that which is not.*
Without further ado, here’s my thank you to the volunteers who make the support forums work. Without them, we would be less than what we are today. I’m listing people by their Wordpress.org usernames, since that’s how you see them in the forums.
Official WordPress.org Support Forum Moderators
These are the people who’ve officially got your back and have been active in the past few months. See them at a WordCamp? Buy them a beer! Otto42, jeremyclark13, MichaelH, samboll, Chris_K. MichaelH suggested we also recognize Moshu, Podz, Kafkaesqui for past meritorious service.
The Honor Roll
These people are not official moderators, but their knowledge and activity levels have caught the attention of those who are. A big round of thanks to these folks for selflessly sharing their knowledge with other WordPress users.
Most active volunteers, nominated by more than one official moderator for recognition (for the reasons given):
alchymyth – “Overall knowledge”
apljdi – “Overall knowledge and programming skills”
t31os_ – “Programming skills”
whooami – “For her security responses” “Knows her stuff”
Generally active volunteers, nominated by official moderators for recognition:
esmi, ClaytonJames, numeeja, stvwlf, buddhatrance, songdogtech, alism, alchymyth, Ipstenu, RVoodoo, jdingman, kmessinger, ArnoldGoodway, Shane G., figaro, jonimueller, blepoxp, cais, mfields, designdolphin, doc4, greenshady, mercime, mrmist, bh_WP_fan , henkholland, krembo99, jdembowski, pboosten, adiant, andrea_r, GDHosting, Gangleri.
Some newcomers who’ve been getting active:
a_johnson, equalmark, WebTechGlobal, kymac.
And an additional shoutout to plugin authors who take an active role in moderating threads regarding their plugins, again nominated by official moderators for recognition:
scribu, GDragoN, sivel, MikeChallis, GamerZ, alexrabe, arnee, sociable, takayukister, hallsofmontezuma, joostdevalk, filosofo, roytanck, donncha, Hiroaki Miyashita, manojtd, froman118, error, Viper007Bond, alexkingorg, cavemonkey50, azaozz, aaroncampbell, isa.goksu, flipper, joedolson, redwallhp, eight7teen, orenshmu, WebGeek, Otto42, toddiceton, the_dead_one, mywpplugin, MattyRob, markjaquith, TobiasBg, Txanny, elfin, jolley_small, stastoc, anmari, micropat, frekel.
One more time, a huge THANK YOU to everyone who contributes to the support forums at WordPress.org.
As we close out 2009 and get closer to 2010, it would be great for us to start thinking about some ways we could make it easier/more rewarding for people to be involved in the forums and other aspects of the open source project. I’ve started a forum thread to discuss some ideas with the thought that we can try a couple after the holidays and see what takes.
* I say almost because let’s face it, we all get caught in the traps of trolls sometimes, and patience can be hard to keep when someone is a jerk. So a reminder to all who use the forums: be nice to the people who are trying to help you! 
P.S. While I’m at it, here’s another tip/request. Search the forums for your problem before posting; if it’s already been answered before (often more than once), you’re kind of wasting people’s time by posting it again without trying the previous solutions first. Please respect the time of the volunteers by searching first (and mention in your post what you’ve already tried).
]]>As Hiro Nakamura said when he first bent time and space to land in Times Square: “Yatta!”
In addition to winning in the Overall Best Open Source CMS category, WordPress was named first runner-up in the Best Open Source PHP CMS category. This is significant because we weren’t even in the top 5 last year, and now we’re #2, ahead of Joomla! As is stated on the Award site, “WordPress made its way into the top five for the first time. The fact that it was outranked by Drupal by a very slight margin indicates how popular it has become with users as well as developers over the past year.”
Every day thousands of new people are embracing WordPress to power not just their blogs but entire sites and communities without compromising on usability or scalability (as would be the case with a legacy CMS). Every member of the WordPress community, from core developer to beginning user, should be proud to be part of this momentum: congratulations to us all!
]]>
From left: Matt Martz (sivel), Jeremy Clarke, Shane Froebel (^BuGs^), Jane Wells, Matt Mullenweg, Mark Jaquith, Beau Lebens, Andy Peatling, John James Jacoby (jjj).
Photo by Chris Cochran.
The first problem is an XSS vulnerability in Press This discovered by Benjamin Flesch. The second problem, discovered by Dawid Golunski, is an issue with sanitizing uploaded file names that can be exploited in certain Apache configurations. Thanks to Benjamin and Dawid for finding and reporting these.
]]>WordCamp Phoenix is first up, on November 13. I’d planned on attending this one myself before they changed the date (it was originally scheduled for the 7th), but will sadly have to miss it as it conflicts with WordCamp NYC. If you, like me, can’t make it to Phoenix, be sure to check their web site for information on the live stream they’re planning to provide. If it’s anywhere near the quality of the stream from Portland or Seattle earlier this fall, it’ll be just like being there, but without a t-shirt to show for it (and theirs has stripes, so if you’re local, you should go!). My only consolation in missing this WordCamp is that I’ve seen about half of the speakers before. If you’re going, don’t miss the session by John Hawkins on Building a WordPress Plugin; it got me to write my first plugin in Portland! Matt‘ll be there, will you?
WordCamp Victoria is next, on November 14. This is another one I’d love to go to, but can’t because it’s at the same time as New York’s. I would especially have liked to go because it looks like the speakers are all local, and I haven’t seen any of them speak before. Occasionally WordCamps lose a little of the local feeling by focusing on visiting speakers, so it’s nice to see so many Vancouverites on the list. They’ll have a Blogger track and a Technical track running concurrently, so there should a little something for everyone. No word on a live stream, but hopefully they’ll be able to catch some of the presentations on video and post them to WordPress.tv after the event.
WordCamp Bangkok is scheduled for November 15. I have to admit that the first thing that catches my eye on their agenda is “WordPress Band.” I’ve known WordCamps to have people performing songs before, but a whole band? Might be a first. I hope they’ll post the video to WordPress.tv, too.
WordCamp New York City is the same weekend as the previous three, on November 14-15. In the interest of full disclosure, I need to tell you that I’m one of the organizers of WordCamp NYC, so my informative comment about it here may be a little biased. That said, we have over 50 confirmed speakers (both local and visiting), and 2 full days of content in 8 — count ‘em, 8 — tracks. Newbies get a free year of hosting and walked through setting up a WordPress blog in workshop format, while the other tracks have specialized content for Bloggers, CMS Users, Beginning Developers, Advanced Developers, Academic Users, people interested in MU/BuddyPress, and the Open Source Community. Did I mention the theme and plugin contest? Or the awesome shirts? How about the Genius Bar, or the Hacker Room? The additional Unconference sessions? If you’re anywhere near NYC that weekend (and with the Acela, that’s anywhere from Boston to D.C.), you should definitely come. I’ll be there, Matt’ll be there, lead developer Mark Jaquith will be there, lead developer of BuddyPress Andy Peatling will be there, and too many other WordPress luminaries and locals to mention. If we hit 800 registrations by November 12, I’m baking cookies for everyone.
WordCamp Peru will be on November 28 in Lima. I was checking out their topics list, and it looks like they’re planning to cover all the usual topics around blog administration, security, increasing traffic, and integration with social media sites. No speaker list yet, but if you’re in Peru, it looks like this will be a nice gathering of WordPress users, and they’re hoping to have around 100 people attend.
WordCamp Orlando is the last of the year, on December 5. They haven’t published a speaker list or schedule yet, but I know Matt will be there, Mark Jaquith will be there, and I will be there. I know some other awesome core contributors are planning to come, but I don’t want to jinx anything, so if you’re curious, come see for yourself. Plus, Florida in December!
]]>
#1 – The first bug hunt of 2.9 will be Thursday through Saturday, November 5-7, 2009. This should give people a few days to plan for it, upgrade their dev environments if they haven’t been following trunk, and figure out how to allot their time. We’re stretching over both weekdays and weekend to try and accommodate everyone’s schedule.
#2 - The second bug hunt will be a week later, Saturday through Monday, November 14-16, 2009. This should make it possible for anyone who needs more than a week to set some time aside to participate. This bug hunt will coincide with WordCamp NYC, where a special Hacker Room will be set aside for people to go and work on 2.9 bug tickets alongside regular core contributors including Mark Jaquith and Matt Martz (sivel from IRC).
The Goals
Test, test, test existing patches! You can see all tickets with patches that need testing by checking this report. When you’ve tested a patch, report your results in the ticket comments, so core committers can see how the patch is faring.
Fix known bugs! You can see the bugs that need patches by checking this report. Look for the ones that seem that they’ll affect the most people or have the biggest impact by being fixed. Edge case bugs should be lower priority.
Report new bugs! As you’re testing out the development version, if you come across a bug, search trac to see if someone has reported it yet. If so, add a comment with your experience to the ticket so we’ll know it’s affecting more than one person. If no ticket exists yet, create one.
Core committers will be around (in the #wordpress-dev channel at irc.freenode.com) both weekends to review patches that have been thoroughly tested, answer questions as needed, and give feedback on patches that need more work before being commit-worthy.
If you’ve never participated in a WordPress bug hunt before, but you’d like to get involved, we’d love to have you join us! To prepare, you’ll want to set up a test environment, start using the current development version/maybe install the beta testing plugin, join us in the #wordpress-dev IRC channel, and read up on automated testing.
]]>