O:9:"magpierss":17:{s:6:"parser";i:0;s:12:"current_item";a:0:{}s:5:"items";a:10:{i:0;a:13:{s:5:"title";s:35:"WordPress 2.9.1 Release Candidate 1";s:4:"link";s:77:"http://wordpress.org/development/2009/12/wordpress-2-9-1-release-candidate-1/";s:8:"comments";s:86:"http://wordpress.org/development/2009/12/wordpress-2-9-1-release-candidate-1/#comments";s:7:"pubdate";s:31:"Tue, 29 Dec 2009 23:27:23 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:19:"DevelopmentReleases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1119";s:11:"description";s:334:"Thanks to everyone who tested 2.9.1 Beta 1.  We&#8217;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-&#62;Upgrade in your blog&#8217;s admin to get RC1.  You can also  download the RC1 package and [...]";s:7:"content";a:1:{s:7:"encoded";s:682:"<p>Thanks to everyone who tested <a href="http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/">2.9.1 Beta 1</a>.  We&#8217;re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">fixed tickets</a> up to 23.  If you are already running Beta 1, visit Tools-&gt;Upgrade in your blog&#8217;s admin to get RC1.  You can also  <a href="http://wordpress.org/wordpress-2.9.1-RC1.zip">download the RC1 package</a> and install manually.  If all goes well, 2.9.1 will be here soon.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:82:"http://wordpress.org/development/2009/12/wordpress-2-9-1-release-candidate-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:334:"Thanks to everyone who tested 2.9.1 Beta 1.  We&#8217;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-&#62;Upgrade in your blog&#8217;s admin to get RC1.  You can also  download the RC1 package and [...]";s:12:"atom_content";s:682:"<p>Thanks to everyone who tested <a href="http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/">2.9.1 Beta 1</a>.  We&#8217;re following that up with Release Candidate 1.  RC1 contains a few more fixes, bringing the number of <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">fixed tickets</a> up to 23.  If you are already running Beta 1, visit Tools-&gt;Upgrade in your blog&#8217;s admin to get RC1.  You can also  <a href="http://wordpress.org/wordpress-2.9.1-RC1.zip">download the RC1 package</a> and install manually.  If all goes well, 2.9.1 will be here soon.</p>
";}i:1;a:13:{s:5:"title";s:13:"Setting Scope";s:4:"link";s:55:"http://wordpress.org/development/2009/12/setting-scope/";s:8:"comments";s:64:"http://wordpress.org/development/2009/12/setting-scope/#comments";s:7:"pubdate";s:31:"Fri, 25 Dec 2009 16:56:38 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:11:"Development";s:4:"guid";s:40:"http://wordpress.org/development/?p=1096";s:11:"description";s:301:"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&#8217;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. [...]";s:7:"content";a:1:{s:7:"encoded";s:4722:"<p>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&#8217;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.</p>
<p>The as-long-as-we&#8217;re-not-in-freeze-yet model isn&#8217;t working. People wind up waiting months longer for new features they want, like Trash and Image Editing, because we&#8217;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&#8217;s hard, because everyone has their pet features and fixes, and if there&#8217;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&#8217;s our proposal?</p>
<p>We take a page from the world of project management and we make a project plan <strong>before</strong> 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 &#8220;future release&#8221; 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&#8217;t been well-described or reproduced. We stop diverting our attention from agreed-upon goals when a &#8220;squeaky wheel&#8221; 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&#8230;as a UX person I always wish we could do everything all at once!).</p>
<p>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&#8217;s to follow a cool idea that everyone loves or a suggestion based on a personal agenda, and regardless of whether it&#8217;s a newbie who doesn&#8217;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&#8217;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.</p>
<p>We think it&#8217;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&#8217;ve got a general agreement about what will be included, we&#8217;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&#8217;s going to be hard. There are at least a dozen new features that I feel like we&#8217;ve pushed back multiple times that I&#8217;d like to see in core, but for this experiment, I&#8217;m just going to keep reminding myself, &#8220;You can do that with a plugin!&#8221;</p>
<p><a href="http://wordpress.org/support/topic/345127">Sound off on the features you would like to see in version 3.0</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2009/12/setting-scope/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:301:"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&#8217;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. [...]";s:12:"atom_content";s:4722:"<p>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&#8217;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.</p>
<p>The as-long-as-we&#8217;re-not-in-freeze-yet model isn&#8217;t working. People wind up waiting months longer for new features they want, like Trash and Image Editing, because we&#8217;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&#8217;s hard, because everyone has their pet features and fixes, and if there&#8217;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&#8217;s our proposal?</p>
<p>We take a page from the world of project management and we make a project plan <strong>before</strong> 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 &#8220;future release&#8221; 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&#8217;t been well-described or reproduced. We stop diverting our attention from agreed-upon goals when a &#8220;squeaky wheel&#8221; 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&#8230;as a UX person I always wish we could do everything all at once!).</p>
<p>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&#8217;s to follow a cool idea that everyone loves or a suggestion based on a personal agenda, and regardless of whether it&#8217;s a newbie who doesn&#8217;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&#8217;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.</p>
<p>We think it&#8217;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&#8217;ve got a general agreement about what will be included, we&#8217;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&#8217;s going to be hard. There are at least a dozen new features that I feel like we&#8217;ve pushed back multiple times that I&#8217;d like to see in core, but for this experiment, I&#8217;m just going to keep reminding myself, &#8220;You can do that with a plugin!&#8221;</p>
<p><a href="http://wordpress.org/support/topic/345127">Sound off on the features you would like to see in version 3.0</a>.</p>
";}i:2;a:13:{s:5:"title";s:22:"WordPress 2.9.1 Beta 1";s:4:"link";s:64:"http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/";s:8:"comments";s:73:"http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/#comments";s:7:"pubdate";s:31:"Wed, 23 Dec 2009 19:58:34 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1098";s:11:"description";s:354:"Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help [...]";s:7:"content";a:1:{s:7:"encoded";s:1162:"<p>Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help us get 2.9.1 ready to go by testing 2.9.1 Beta 1.  The easiest way to test Beta 1 is to install the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin, elect to get on the point release development track, and then perform an automatic upgrade via the Tools-&gt;Upgrade menu.  You can also <a href="http://wordpress.org/wordpress-2.9.1-beta1.zip">download the Beta 1 package</a> and install manually.  <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">Fourteen tickets</a> have been fixed in 2.9.1 Beta 1.  Since the curl problem and a couple of other problems are dependent on specific hosting configurations, any and all testing help is greatly appreciated.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:69:"http://wordpress.org/development/2009/12/wordpress-2-9-1-beta-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"1";}s:7:"summary";s:354:"Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help [...]";s:12:"atom_content";s:1162:"<p>Unfortunately, the recent 2.9 release triggered a bug in certain versions of PHP&#8217;s curl extension.  With these versions of curl, scheduled posts and pingbacks are not processed correctly.  To fix this problem as well as a handful of other, lesser issues, we are quickly releasing 2.9.1, the first maintenance release of the 2.9 line.  Help us get 2.9.1 ready to go by testing 2.9.1 Beta 1.  The easiest way to test Beta 1 is to install the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin, elect to get on the point release development track, and then perform an automatic upgrade via the Tools-&gt;Upgrade menu.  You can also <a href="http://wordpress.org/wordpress-2.9.1-beta1.zip">download the Beta 1 package</a> and install manually.  <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.9.1&amp;resolution=fixed">Fourteen tickets</a> have been fixed in 2.9.1 Beta 1.  Since the curl problem and a couple of other problems are dependent on specific hosting configurations, any and all testing help is greatly appreciated.</p>
";}i:3;a:13:{s:5:"title";s:25:"WordPress 2.9, oh so fine";s:4:"link";s:55:"http://wordpress.org/development/2009/12/wordpress-2-9/";s:8:"comments";s:64:"http://wordpress.org/development/2009/12/wordpress-2-9/#comments";s:7:"pubdate";s:31:"Sat, 19 Dec 2009 00:46:11 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:8:"Releases";s:4:"guid";s:40:"http://wordpress.org/development/?p=1075";s:11:"description";s:360:"I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of WordPress version 2.9 &#8220;Carmen&#8221; named in honor of magical jazz vocalist Carmen McRae (whom we&#8217;ve added to our Last.fm WP release station). You can upgrade [...]";s:7:"content";a:1:{s:7:"encoded";s:14105:"<p>I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of <a href="http://wordpress.org/download/">WordPress version 2.9 &#8220;Carmen&#8221;</a> named in honor of magical jazz vocalist <a href="http://www.carmenmcrae.com/">Carmen McRae</a> (whom we&#8217;ve <a href="http://www.last.fm/tag/wordpress-release-jazz">added to our Last.fm WP release station</a>). You can upgrade easily from your Dashboard by going to <strong>Tools</strong> &gt; <strong>Upgrade</strong>, or you can <a href="http://wordpress.org/download/">download from WordPress.org</a>. And of course, it wouldn&#8217;t be a major release without a short video summarizing some of the cool things about the new version:<br />
<embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.11" type="application/x-shockwave-flash" width="640" height="360" allowscriptaccess="always" allowfullscreen="true" flashvars="guid=NBZ853Xn&amp;width=640&amp;height=360" title="Introducing WordPress 2.9 Carmen"></embed></p>
<p>The coolest new stuff from a user point of view is:</p>
<ol>
<li><strong>Global undo/&#8221;trash&#8221; feature</strong>, which means that if you accidentally delete a post or comment you can bring it back from the grave (i.e., the Trash). This also eliminates those annoying &#8220;are you sure&#8221; messages we used to have on every delete.</li>
<li><strong>Built-in image editor</strong> allows you to crop, edit, rotate, flip, and scale your images to show them who&#8217;s boss. This is the first wave of our many planned media-handling improvements.</li>
<li><strong>Batch plugin update and compatibility checking,</strong> which means you can update 10 plugins at once, versus having to do multiple clicks for each one, and we&#8217;re using the new compatibility data from the plugins directory to give you a better idea of whether your plugins are compatible with new releases of WordPress. This should take the fear and hassle out of upgrading.</li>
<li><a href="http://codex.wordpress.org/Embeds"><strong>Easier video embeds</strong></a> that allow you to just paste a URL on its own line and have it magically turn it into the proper embed code, with Oembed support for YouTube, Daily Motion, Blip.tv, Flickr, Hulu, Viddler, Qik, Revision3, Scribd, Google Video, Photobucket, PollDaddy, and WordPress.tv (and more in the next release).</li>
</ol>
<p>2.9 provides the smoothest ride yet because of a number of improvements under the hood and more subtle improvements you&#8217;ll begin to appreciate once you&#8217;ve been around the block a few times. Here&#8217;s just a sampling:</p>
<ul>
<li>We now have <code>rel=canonical</code> support for better SEO.</li>
<li>There is automatic database optimization support, which you can enable in your <code>wp-config.php</code> file by adding <code>define('WP_ALLOW_REPAIR', true);</code>.</li>
<li>Themes can register &#8220;post thumbnails&#8221; which allow them to attach an image to the post, especially useful for magazine-style themes.</li>
<li>A new <code>commentmeta</code> table that allows arbitrary key/value pairs to be attached to comments, just like posts, so you can now expand greatly what you can do in the comment framework.</li>
<li>Custom post types have been upgraded with better API support so you can juggle more types than just post, page, and attachment. (More of this planned for 3.0.)</li>
<li>You can set custom theme directories, so a plugin can register a theme to be bundled with it or you can have multiple shared theme directories on your server.</li>
<li>We&#8217;ve upgraded TinyMCE WYSIWYG editing and Simplepie.</li>
<li>Sidebars can now have descriptions so it&#8217;s more obvious what and where they do what they do.</li>
<li>Specify category templates not just by ID, like before, but by slug, which will make it easier for theme developers to do custom things with categories &#8212; like post types!</li>
<li>Registration and profiles are now extensible to allow you to collect things more easily, like a user&#8217;s Twitter account or any other fields you can imagine.</li>
<li>The XML-RPC API has been extended to allow changing the user registration option. We fixed some Atom API attachment issues.</li>
<li>Create custom galleries with the new include and exclude attributes that allow you to pull attachments from any post, not just the current one.</li>
<li>When you&#8217;re editing files in the theme and plugin editors it remembers your location and takes you back to that line after you save. (Thank goodness!!!)</li>
<li>The Press This bookmarklet has been improved and is faster than ever; give it a try for on-the-fly blogging from wherever you are on the internet.</li>
<li>Custom taxonomies are now included in the WXR export file and imported correctly.</li>
<li>Better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query</li>
</ul>
<p>All of this and more is reflected in the <a href="http://core.trac.wordpress.org/query?status=closed&amp;milestone=2.9">over 500 tickets, bugs, and enhancements that WP developers in this release cycle</a>.</p>
<p>This release included code from over 140 contributors, here&#8217;s everyone we were able to identify: <a href="http://xavisys.com/">aaroncampbell (Aaron Campbell)</a>, <a href="http://sixohthree.com/">abackstrom (Adam Backstrom)</a>, <a href="http://www.aldenta.com/">aldenta (John Ford)</a>, <a href="http://alexking.org/">alexkingorg (Alex King)</a>, [amilanov], <a href="http://antony.lesuisse.org/">antonylesuisse (Antony Lesuisse)</a>, <a href="http://apeatling.wordpress.com/">apeatling (Andy Peatling)</a>, <a href="http://blog.apokalyptik.com/">apokalyptik (Demitrious Kelly)</a>, <a href="http://www.mailpress.org/">arena (André Renaut)</a>, <a href="http://digitalize.ca/">batmoo (Mohammad Jangda)</a>, <a href="http://bendunkle.com/">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/benbe1987">BenBE1987</a>, <!--PROFILES.wp.org--> <a href="http://blog.bf-itservice.de/">Benjamin Flesch</a>, <a href="http://www.happyhumans.com/">bookchiq (Sarah Lewis)</a>, <a href="http://profiles.wordpress.org/brianwhite">brianwhite</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/c0nstruct">c0nstruct</a>, <!--PROFILES.wp.org--> <a href="http://www.caesarsgrunt.com/">caesarsgrunt (Caesar Schinas)</a>, <a href="http://kniffenwebdesign.com/">CalebKniffen (Caleb Kniffen)</a>, <a href="http://profiles.wordpress.org/chrisbliss18">chrisbliss18</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/chrisscott">chrisscott (Chris Scott)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/christoph179">christoph179</a>, <!--PROFILES.wp.org--> <a href="http://coffee2code.com/">coffee2code (Scott Reilly)</a>, [cross country flight], <a href="http://www.curioso.org/">Curioso</a>, <a href="http://dave.pageportfolio.co.uk/">davecpage (Dave Page)</a>, <a href="http://dan-cole.com/">dcole07 (Dan Cole)</a>, <a href="http://dd32.id.au/">dd32 (Dion Hulse)</a>, <a href="http://op111.net/">demetris (ΔημήτÏης Κίκιζας)</a>, <a href="http://www.semiologic.com/">Denis-de-Bernardy</a>, <a href="http://profiles.wordpress.org/dj-wp">dj-wp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/dwright">dwright</a>, <!--PROFILES.wp.org--> <a href="http://eddieringle.com/">eddieringle (Eddie Ringle)</a>, <a href="http://www.homelandstupidity.us/">error (Michael Hampton)</a>, <a href="http://profiles.wordpress.org/ewestp">ewestp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/fabifott">fabifott</a>, <!--PROFILES.wp.org--> <a href="http://www.ilfilosofo.com/">filosofo (Austin Matzko)</a>, <a href="http://justintadlock.com/">greenshady (Justin Tadlock)</a>, <a href="http://gsnedders.com/">gsnedders/link92 (Geoffrey Sneddon)</a>, <a href="http://hailin.wordpress.com/">hailin (Hailin Wu)</a>, <a href="http://codex.wordpress.org/User:Hakre">hakre</a>, <!--CODEX.wp.org--> <a href="http://profiles.wordpress.org/hanilovesme">hanilovesme</a>, <!--PROFILES.wp.org--> <a href="http://ondskap.net/wp/">Harald Nesland</a>, <a href="http://profiles.wordpress.org/harrym">harrym</a>, <!--PROFILES.wp.org--> <a href="http://holizz.com/">holizz (Tom Adams)</a>, <a href="http://profiles.wordpress.org/ikonst">ikonst</a>, <!--PROFILES.wp.org--> <a href="http://jacobsantos.com/">jacobsantos (Jacob Santos)</a>, <a href="http://jane.wordpress.com/">janeforshort (Jane Wells)</a>, <a href="http://om4.com.au/">jamescollins (James Collins)</a>, <a href="http://bethesignal.org/">jdub (Jeff Waugh)</a>, <a href="http://www.modulaweb.fr/">jeff_ (Jean-François “Jeffâ€ VIAL)</a>, <a href="http://simianuprising.com/">jeremyclarke (Jeremy Clarke)</a>, <a href="http://jeremy.visser.name/">JeremyVisser (Jeremy Visser)</a>, <a href="http://profiles.wordpress.org/jikamens">jikamens</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jmulley">jmulley</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/joern_w">Joern_W</a>, <!--PROFILES.wp.org--> <a href="http://devel.kostdoktorn.se/">johanee (Johan Eenfeldt)</a>, <a href="http://lud.icro.us/">johnbillion (John Blackbourn)</a>, <a href="http://johnjamesjacoby.com/">johnjamesjacoby (John James Jacoby)</a>, <a href="http://profiles.wordpress.org/johnjosephbachir">johnjosephbachir (John Joseph Bachir)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jonathanrogers">JonathanRogers</a>, <!--PROFILES.wp.org--> <a href="http://yoast.com/">joostdevalk (Joost de Valk)</a>, <a href="http://rooibo.wordpress.com/">Jose Carlos Norte</a>, <a href="http://josephscott.org/">josephscott (Joseph Scott)</a>, <a href="http://tyco.ws/">junsuijin</a>, <a href="http://agapetry.net/">kevinB (Kevin Behrens)</a>, <a href="http://kometbomb.net/">kometbomb</a>, <a href="http://www.yuriko.net/">lilyfan (IKEDA Yuriko)</a>, [lostinlafayette], <a href="http://profiles.wordpress.org/madhyde">madhyde</a>, <!--PROFILES.wp.org--> <a href="http://subscribe2.wordpress.com/">MattyRob</a>, <a href="http://blogwaffe.com/">mdawaffe (Michael Adams)</a>, <a href="http://www.mittineague.com/">Mittineague</a>, <a href="http://blogyul.miqrogroove.com/">miqrogroove</a>, <a href="http://profiles.wordpress.org/morfiusx">morfiusx</a>, <!--PROFILES.wp.org--> <a href="http://www.misthaven.org.uk/blog/">mrmist (David McFarlane)</a>, <a href="http://nickmomrik.com/">mtdewvirus (Nick Momrik)</a>, <a href="http://urzenia.net/">mysz</a>, <a href="http://twitter.com/nacin">nacin (Andrew Nacin)</a>, <a href="http://thebookofjoe.com/">nanochrome</a>, <a href="http://blog.detlog.org/">nao (Naoko  McCracken)</a>, <a href="http://www.nathanrice.net/">nathanrice (Nathan Rice)</a>, <a href="http://nikolay.bg/">nbachiyski (Ðиколай БачийÑки)</a>, <a href="http://www.niallkennedy.com/">niallkennedy (Niall Kennedy)</a>, <a href="http://nickohrn.com/">nickohrn (Nick Ohrn)</a>, <a href="http://www.rpmurphy.com/">ninjaWR (Ryan Murphy)</a>, <a href="http://noel.io/">noel (Noël Jackson)</a>, <a href="http://ottodestruct.com/">Otto42 (Samuel Wood)</a>, <a href="https://redmine.kirdev.sch.bme.hu/">pairg</a>, <a href="https://peaceable-whale.pip.verisignlabs.com/">peaceablewhale (Franklin Tse)</a>, <a href="http://cnpstudio.com/">prettyboymp (Michael Pretty)</a>, <a href="http://www.prodevstudio.net">ProDevStudio</a>, <a href="http://www.bdihot.co.il/">ramiy</a>, <a href="http://www.red-sweater.com/blog/">redsweater (Daniel Jalkut)</a>, <a href="http://ruslany.net/">ruslany</a>, <a href="http://unlettered.org/">sambauers (Sam Bauers)</a>, <a href="http://scribu.net/">scribu</a>, <a href="http://profiles.wordpress.org/sewar">Sewar</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/simek">Simek</a>, <!--PROFILES.wp.org--> <a href="http://www.simonwheatley.co.uk/">simonwheatley (Simon Wheatley)</a>, <a href="http://www.poradnik-webmastera.com/">sirzooro (Daniel Frużyński)</a>, <a href="http://sivel.net/">sivel (Matt Martz)</a>, <a href="http://skeltoac.com/">skeltoac (Andy Skelton)</a>, <a href="http://smallvoid.com/about/">snakefoot</a>, <a href="http://stephanreiter.info/">stephanreiter (Stephan Reiter)</a>, <a href="http://striderweb.com/nerdaphernalia/">strider72 (Stephen Rider)</a>, <a href="http://profiles.wordpress.org/taco1991">taco1991</a>, <!--PROFILES.wp.org--> <a href="http://ideasilo.wordpress.com/">takayukister (Takayuki Miyoshi)</a>, <a href="http://tellyworth.wordpress.com/">tellyworth</a>, <a href="http://profiles.wordpress.org/tenpura">tenpura</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/usermrpapa">usermrpapa</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/utkarsh">utkarsh</a>, <!--PROFILES.wp.org--> <a href="http://www.viper007bond.com/">Viper007Bond</a>, <a href="http://blog.sjinks.org.ua/">vladimir_kolesnikov (Vladimir Kolesnikov)</a>, <a href="http://voxpelli.se/">VoxPelli (Pelle Wessman)</a>, [voyou1], <a href="http://emphaticallystatic.org/">wahgnube</a>, <a href="http://www.waltervos.com/">waltervos</a>, <a href="http://weston.ruter.net/">westonruter (Weston Ruter)</a>, <a href="http://willnorris.com/">wnorris (Will Norris)</a>, <a href="http://xentek.net/">xenlab (Eric Marden)</a>, <a href="http://blog.yoavfarhi.com/">yoavf (Yoav Farhi)</a>. Wowza!</p>
<p>2.9 has been an exciting development cycle, and I must say it has whetted our appetite for 3.0, which is coming next (probably this spring) and will include at the very least the merge of MU with the WordPress core, and a new default theme. We can&#8217;t wait to start working on it. But first, some Carmen McRae tunes and a beer. Join us! <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>(<em>After</em> you upgrade, of course!)</p>
<p>I hope everyone is having a wonderful holiday season.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:60:"http://wordpress.org/development/2009/12/wordpress-2-9/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"35";}s:7:"summary";s:360:"I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of WordPress version 2.9 &#8220;Carmen&#8221; named in honor of magical jazz vocalist Carmen McRae (whom we&#8217;ve added to our Last.fm WP release station). You can upgrade [...]";s:12:"atom_content";s:14105:"<p>I want to make you mine, all the time&#8230; oh wait. Hello. I&#8217;m here on behalf of the entire WordPress development team and community to announce the immediate availability of <a href="http://wordpress.org/download/">WordPress version 2.9 &#8220;Carmen&#8221;</a> named in honor of magical jazz vocalist <a href="http://www.carmenmcrae.com/">Carmen McRae</a> (whom we&#8217;ve <a href="http://www.last.fm/tag/wordpress-release-jazz">added to our Last.fm WP release station</a>). You can upgrade easily from your Dashboard by going to <strong>Tools</strong> &gt; <strong>Upgrade</strong>, or you can <a href="http://wordpress.org/download/">download from WordPress.org</a>. And of course, it wouldn&#8217;t be a major release without a short video summarizing some of the cool things about the new version:<br />
<embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.11" type="application/x-shockwave-flash" width="640" height="360" allowscriptaccess="always" allowfullscreen="true" flashvars="guid=NBZ853Xn&amp;width=640&amp;height=360" title="Introducing WordPress 2.9 Carmen"></embed></p>
<p>The coolest new stuff from a user point of view is:</p>
<ol>
<li><strong>Global undo/&#8221;trash&#8221; feature</strong>, which means that if you accidentally delete a post or comment you can bring it back from the grave (i.e., the Trash). This also eliminates those annoying &#8220;are you sure&#8221; messages we used to have on every delete.</li>
<li><strong>Built-in image editor</strong> allows you to crop, edit, rotate, flip, and scale your images to show them who&#8217;s boss. This is the first wave of our many planned media-handling improvements.</li>
<li><strong>Batch plugin update and compatibility checking,</strong> which means you can update 10 plugins at once, versus having to do multiple clicks for each one, and we&#8217;re using the new compatibility data from the plugins directory to give you a better idea of whether your plugins are compatible with new releases of WordPress. This should take the fear and hassle out of upgrading.</li>
<li><a href="http://codex.wordpress.org/Embeds"><strong>Easier video embeds</strong></a> that allow you to just paste a URL on its own line and have it magically turn it into the proper embed code, with Oembed support for YouTube, Daily Motion, Blip.tv, Flickr, Hulu, Viddler, Qik, Revision3, Scribd, Google Video, Photobucket, PollDaddy, and WordPress.tv (and more in the next release).</li>
</ol>
<p>2.9 provides the smoothest ride yet because of a number of improvements under the hood and more subtle improvements you&#8217;ll begin to appreciate once you&#8217;ve been around the block a few times. Here&#8217;s just a sampling:</p>
<ul>
<li>We now have <code>rel=canonical</code> support for better SEO.</li>
<li>There is automatic database optimization support, which you can enable in your <code>wp-config.php</code> file by adding <code>define('WP_ALLOW_REPAIR', true);</code>.</li>
<li>Themes can register &#8220;post thumbnails&#8221; which allow them to attach an image to the post, especially useful for magazine-style themes.</li>
<li>A new <code>commentmeta</code> table that allows arbitrary key/value pairs to be attached to comments, just like posts, so you can now expand greatly what you can do in the comment framework.</li>
<li>Custom post types have been upgraded with better API support so you can juggle more types than just post, page, and attachment. (More of this planned for 3.0.)</li>
<li>You can set custom theme directories, so a plugin can register a theme to be bundled with it or you can have multiple shared theme directories on your server.</li>
<li>We&#8217;ve upgraded TinyMCE WYSIWYG editing and Simplepie.</li>
<li>Sidebars can now have descriptions so it&#8217;s more obvious what and where they do what they do.</li>
<li>Specify category templates not just by ID, like before, but by slug, which will make it easier for theme developers to do custom things with categories &#8212; like post types!</li>
<li>Registration and profiles are now extensible to allow you to collect things more easily, like a user&#8217;s Twitter account or any other fields you can imagine.</li>
<li>The XML-RPC API has been extended to allow changing the user registration option. We fixed some Atom API attachment issues.</li>
<li>Create custom galleries with the new include and exclude attributes that allow you to pull attachments from any post, not just the current one.</li>
<li>When you&#8217;re editing files in the theme and plugin editors it remembers your location and takes you back to that line after you save. (Thank goodness!!!)</li>
<li>The Press This bookmarklet has been improved and is faster than ever; give it a try for on-the-fly blogging from wherever you are on the internet.</li>
<li>Custom taxonomies are now included in the WXR export file and imported correctly.</li>
<li>Better hooks and filters for excerpts, smilies, HTTP requests, user profiles, author links, taxonomies, SSL support, tag clouds, query_posts and WP_Query</li>
</ul>
<p>All of this and more is reflected in the <a href="http://core.trac.wordpress.org/query?status=closed&amp;milestone=2.9">over 500 tickets, bugs, and enhancements that WP developers in this release cycle</a>.</p>
<p>This release included code from over 140 contributors, here&#8217;s everyone we were able to identify: <a href="http://xavisys.com/">aaroncampbell (Aaron Campbell)</a>, <a href="http://sixohthree.com/">abackstrom (Adam Backstrom)</a>, <a href="http://www.aldenta.com/">aldenta (John Ford)</a>, <a href="http://alexking.org/">alexkingorg (Alex King)</a>, [amilanov], <a href="http://antony.lesuisse.org/">antonylesuisse (Antony Lesuisse)</a>, <a href="http://apeatling.wordpress.com/">apeatling (Andy Peatling)</a>, <a href="http://blog.apokalyptik.com/">apokalyptik (Demitrious Kelly)</a>, <a href="http://www.mailpress.org/">arena (André Renaut)</a>, <a href="http://digitalize.ca/">batmoo (Mohammad Jangda)</a>, <a href="http://bendunkle.com/">Ben Dunkle</a>, <a href="http://profiles.wordpress.org/benbe1987">BenBE1987</a>, <!--PROFILES.wp.org--> <a href="http://blog.bf-itservice.de/">Benjamin Flesch</a>, <a href="http://www.happyhumans.com/">bookchiq (Sarah Lewis)</a>, <a href="http://profiles.wordpress.org/brianwhite">brianwhite</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/c0nstruct">c0nstruct</a>, <!--PROFILES.wp.org--> <a href="http://www.caesarsgrunt.com/">caesarsgrunt (Caesar Schinas)</a>, <a href="http://kniffenwebdesign.com/">CalebKniffen (Caleb Kniffen)</a>, <a href="http://profiles.wordpress.org/chrisbliss18">chrisbliss18</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/chrisscott">chrisscott (Chris Scott)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/christoph179">christoph179</a>, <!--PROFILES.wp.org--> <a href="http://coffee2code.com/">coffee2code (Scott Reilly)</a>, [cross country flight], <a href="http://www.curioso.org/">Curioso</a>, <a href="http://dave.pageportfolio.co.uk/">davecpage (Dave Page)</a>, <a href="http://dan-cole.com/">dcole07 (Dan Cole)</a>, <a href="http://dd32.id.au/">dd32 (Dion Hulse)</a>, <a href="http://op111.net/">demetris (ΔημήτÏης Κίκιζας)</a>, <a href="http://www.semiologic.com/">Denis-de-Bernardy</a>, <a href="http://profiles.wordpress.org/dj-wp">dj-wp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/dwright">dwright</a>, <!--PROFILES.wp.org--> <a href="http://eddieringle.com/">eddieringle (Eddie Ringle)</a>, <a href="http://www.homelandstupidity.us/">error (Michael Hampton)</a>, <a href="http://profiles.wordpress.org/ewestp">ewestp</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/fabifott">fabifott</a>, <!--PROFILES.wp.org--> <a href="http://www.ilfilosofo.com/">filosofo (Austin Matzko)</a>, <a href="http://justintadlock.com/">greenshady (Justin Tadlock)</a>, <a href="http://gsnedders.com/">gsnedders/link92 (Geoffrey Sneddon)</a>, <a href="http://hailin.wordpress.com/">hailin (Hailin Wu)</a>, <a href="http://codex.wordpress.org/User:Hakre">hakre</a>, <!--CODEX.wp.org--> <a href="http://profiles.wordpress.org/hanilovesme">hanilovesme</a>, <!--PROFILES.wp.org--> <a href="http://ondskap.net/wp/">Harald Nesland</a>, <a href="http://profiles.wordpress.org/harrym">harrym</a>, <!--PROFILES.wp.org--> <a href="http://holizz.com/">holizz (Tom Adams)</a>, <a href="http://profiles.wordpress.org/ikonst">ikonst</a>, <!--PROFILES.wp.org--> <a href="http://jacobsantos.com/">jacobsantos (Jacob Santos)</a>, <a href="http://jane.wordpress.com/">janeforshort (Jane Wells)</a>, <a href="http://om4.com.au/">jamescollins (James Collins)</a>, <a href="http://bethesignal.org/">jdub (Jeff Waugh)</a>, <a href="http://www.modulaweb.fr/">jeff_ (Jean-François “Jeffâ€ VIAL)</a>, <a href="http://simianuprising.com/">jeremyclarke (Jeremy Clarke)</a>, <a href="http://jeremy.visser.name/">JeremyVisser (Jeremy Visser)</a>, <a href="http://profiles.wordpress.org/jikamens">jikamens</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jmulley">jmulley</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/joern_w">Joern_W</a>, <!--PROFILES.wp.org--> <a href="http://devel.kostdoktorn.se/">johanee (Johan Eenfeldt)</a>, <a href="http://lud.icro.us/">johnbillion (John Blackbourn)</a>, <a href="http://johnjamesjacoby.com/">johnjamesjacoby (John James Jacoby)</a>, <a href="http://profiles.wordpress.org/johnjosephbachir">johnjosephbachir (John Joseph Bachir)</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/jonathanrogers">JonathanRogers</a>, <!--PROFILES.wp.org--> <a href="http://yoast.com/">joostdevalk (Joost de Valk)</a>, <a href="http://rooibo.wordpress.com/">Jose Carlos Norte</a>, <a href="http://josephscott.org/">josephscott (Joseph Scott)</a>, <a href="http://tyco.ws/">junsuijin</a>, <a href="http://agapetry.net/">kevinB (Kevin Behrens)</a>, <a href="http://kometbomb.net/">kometbomb</a>, <a href="http://www.yuriko.net/">lilyfan (IKEDA Yuriko)</a>, [lostinlafayette], <a href="http://profiles.wordpress.org/madhyde">madhyde</a>, <!--PROFILES.wp.org--> <a href="http://subscribe2.wordpress.com/">MattyRob</a>, <a href="http://blogwaffe.com/">mdawaffe (Michael Adams)</a>, <a href="http://www.mittineague.com/">Mittineague</a>, <a href="http://blogyul.miqrogroove.com/">miqrogroove</a>, <a href="http://profiles.wordpress.org/morfiusx">morfiusx</a>, <!--PROFILES.wp.org--> <a href="http://www.misthaven.org.uk/blog/">mrmist (David McFarlane)</a>, <a href="http://nickmomrik.com/">mtdewvirus (Nick Momrik)</a>, <a href="http://urzenia.net/">mysz</a>, <a href="http://twitter.com/nacin">nacin (Andrew Nacin)</a>, <a href="http://thebookofjoe.com/">nanochrome</a>, <a href="http://blog.detlog.org/">nao (Naoko  McCracken)</a>, <a href="http://www.nathanrice.net/">nathanrice (Nathan Rice)</a>, <a href="http://nikolay.bg/">nbachiyski (Ðиколай БачийÑки)</a>, <a href="http://www.niallkennedy.com/">niallkennedy (Niall Kennedy)</a>, <a href="http://nickohrn.com/">nickohrn (Nick Ohrn)</a>, <a href="http://www.rpmurphy.com/">ninjaWR (Ryan Murphy)</a>, <a href="http://noel.io/">noel (Noël Jackson)</a>, <a href="http://ottodestruct.com/">Otto42 (Samuel Wood)</a>, <a href="https://redmine.kirdev.sch.bme.hu/">pairg</a>, <a href="https://peaceable-whale.pip.verisignlabs.com/">peaceablewhale (Franklin Tse)</a>, <a href="http://cnpstudio.com/">prettyboymp (Michael Pretty)</a>, <a href="http://www.prodevstudio.net">ProDevStudio</a>, <a href="http://www.bdihot.co.il/">ramiy</a>, <a href="http://www.red-sweater.com/blog/">redsweater (Daniel Jalkut)</a>, <a href="http://ruslany.net/">ruslany</a>, <a href="http://unlettered.org/">sambauers (Sam Bauers)</a>, <a href="http://scribu.net/">scribu</a>, <a href="http://profiles.wordpress.org/sewar">Sewar</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/simek">Simek</a>, <!--PROFILES.wp.org--> <a href="http://www.simonwheatley.co.uk/">simonwheatley (Simon Wheatley)</a>, <a href="http://www.poradnik-webmastera.com/">sirzooro (Daniel Frużyński)</a>, <a href="http://sivel.net/">sivel (Matt Martz)</a>, <a href="http://skeltoac.com/">skeltoac (Andy Skelton)</a>, <a href="http://smallvoid.com/about/">snakefoot</a>, <a href="http://stephanreiter.info/">stephanreiter (Stephan Reiter)</a>, <a href="http://striderweb.com/nerdaphernalia/">strider72 (Stephen Rider)</a>, <a href="http://profiles.wordpress.org/taco1991">taco1991</a>, <!--PROFILES.wp.org--> <a href="http://ideasilo.wordpress.com/">takayukister (Takayuki Miyoshi)</a>, <a href="http://tellyworth.wordpress.com/">tellyworth</a>, <a href="http://profiles.wordpress.org/tenpura">tenpura</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/usermrpapa">usermrpapa</a>, <!--PROFILES.wp.org--> <a href="http://profiles.wordpress.org/utkarsh">utkarsh</a>, <!--PROFILES.wp.org--> <a href="http://www.viper007bond.com/">Viper007Bond</a>, <a href="http://blog.sjinks.org.ua/">vladimir_kolesnikov (Vladimir Kolesnikov)</a>, <a href="http://voxpelli.se/">VoxPelli (Pelle Wessman)</a>, [voyou1], <a href="http://emphaticallystatic.org/">wahgnube</a>, <a href="http://www.waltervos.com/">waltervos</a>, <a href="http://weston.ruter.net/">westonruter (Weston Ruter)</a>, <a href="http://willnorris.com/">wnorris (Will Norris)</a>, <a href="http://xentek.net/">xenlab (Eric Marden)</a>, <a href="http://blog.yoavfarhi.com/">yoavf (Yoav Farhi)</a>. Wowza!</p>
<p>2.9 has been an exciting development cycle, and I must say it has whetted our appetite for 3.0, which is coming next (probably this spring) and will include at the very least the merge of MU with the WordPress core, and a new default theme. We can&#8217;t wait to start working on it. But first, some Carmen McRae tunes and a beer. Join us! <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>(<em>After</em> you upgrade, of course!)</p>
<p>I hope everyone is having a wonderful holiday season.</p>
";}i:4;a:13:{s:5:"title";s:21:"2010: A Theme Odyssey";s:4:"link";s:62:"http://wordpress.org/development/2009/12/2010-a-theme-odyssey/";s:8:"comments";s:71:"http://wordpress.org/development/2009/12/2010-a-theme-odyssey/#comments";s:7:"pubdate";s:31:"Fri, 18 Dec 2009 18:36:43 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:34:"Development2010defaultkubricktheme";s:4:"guid";s:40:"http://wordpress.org/development/?p=1065";s:11:"description";s:327:"After the video from the core team meetup was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.
When Kubrick was bundled [...]";s:7:"content";a:1:{s:7:"encoded";s:2819:"<p>After the <a href="http://wordpress.org/development/2009/12/core-team-meetup-results/">video from the core team meetup</a> was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.</p>
<p>When Kubrick was bundled with core back in 2005, it was a cutting edge theme. Custom header, rounded corners, clean design&#8230; if you were using WordPress back then, let&#8217;s face it, you were impressed. Time moves on, though, fashions change, new styles become old standards, and what was once cutting edge suddenly seems old-fashioned and out of date.</p>
<p>So, a new bundled theme in 2010? We think it&#8217;s a good idea. Something nice and light that can serve as a good example theme, include newer theme-based features, and look nice (and current) on a public site. We&#8217;d like to introduce a new default theme with version 3.0, which is anticipated to come out in mid-2010 (hence the name), and think it would be good for it to blend well aesthetically with WordPress itself.</p>
<p>I&#8217;d been advocating moving toward <a href="http://elastictheme.org/">Elastic</a>, the theme framework/WYSIWYG theme editor that was one of our Google Summer of Code student projects, but after some discussion I agreed with the guys that while Elastic is awesome and should be promoted as a community development project, it&#8217;s heavier than a default theme needs to be. The default theme doesn&#8217;t need to be a full-featured framework, it just needs to work well, look awesome, have good code and be a good starting point for beginning themers. We were thinking of a fairly minimalist design that would make it easy to customize.</p>
<p>As for the code, there&#8217;s a question of if it will really be a new theme, or if it will be a re-styled and updated version of Kubrick.  We don&#8217;t know the final answer to that yet, because the ultimate decision will be made with the community&#8217;s input, but we believe all new markup is the way to go. What do you think? Without venturing into theme framework territory, are there features you think a new default theme should have? Some people have been <a href="http://core.trac.wordpress.org/ticket/9015">talking about it on Trac</a> over the past year, if you wonder what&#8217;s been tossed around so far. I thought about posting a poll here (you know how I love posting polls to gauge opinion), but in this case I think a discussion thread might be better, so that each vote can explain the reason behind it. So, have an opinion on what a new default theme should include? <a href="http://wordpress.org/support/topic/342819">Weigh in at the forums</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2009/12/2010-a-theme-odyssey/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:327:"After the video from the core team meetup was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.
When Kubrick was bundled [...]";s:12:"atom_content";s:2819:"<p>After the <a href="http://wordpress.org/development/2009/12/core-team-meetup-results/">video from the core team meetup</a> was posted, the topic that seemed to get the most attention on Twitter and various community sites was Matt&#8217;s announcement that there would be a new default theme in 2010, so I thought I&#8217;d start with that as the first of the meetup summaries.</p>
<p>When Kubrick was bundled with core back in 2005, it was a cutting edge theme. Custom header, rounded corners, clean design&#8230; if you were using WordPress back then, let&#8217;s face it, you were impressed. Time moves on, though, fashions change, new styles become old standards, and what was once cutting edge suddenly seems old-fashioned and out of date.</p>
<p>So, a new bundled theme in 2010? We think it&#8217;s a good idea. Something nice and light that can serve as a good example theme, include newer theme-based features, and look nice (and current) on a public site. We&#8217;d like to introduce a new default theme with version 3.0, which is anticipated to come out in mid-2010 (hence the name), and think it would be good for it to blend well aesthetically with WordPress itself.</p>
<p>I&#8217;d been advocating moving toward <a href="http://elastictheme.org/">Elastic</a>, the theme framework/WYSIWYG theme editor that was one of our Google Summer of Code student projects, but after some discussion I agreed with the guys that while Elastic is awesome and should be promoted as a community development project, it&#8217;s heavier than a default theme needs to be. The default theme doesn&#8217;t need to be a full-featured framework, it just needs to work well, look awesome, have good code and be a good starting point for beginning themers. We were thinking of a fairly minimalist design that would make it easy to customize.</p>
<p>As for the code, there&#8217;s a question of if it will really be a new theme, or if it will be a re-styled and updated version of Kubrick.  We don&#8217;t know the final answer to that yet, because the ultimate decision will be made with the community&#8217;s input, but we believe all new markup is the way to go. What do you think? Without venturing into theme framework territory, are there features you think a new default theme should have? Some people have been <a href="http://core.trac.wordpress.org/ticket/9015">talking about it on Trac</a> over the past year, if you wonder what&#8217;s been tossed around so far. I thought about posting a poll here (you know how I love posting polls to gauge opinion), but in this case I think a discussion thread might be better, so that each vote can explain the reason behind it. So, have an opinion on what a new default theme should include? <a href="http://wordpress.org/support/topic/342819">Weigh in at the forums</a>.</p>
";}i:5;a:13:{s:5:"title";s:23:"2.9 Release Candidate 1";s:4:"link";s:49:"http://wordpress.org/development/2009/12/2-9-rc1/";s:8:"comments";s:58:"http://wordpress.org/development/2009/12/2-9-rc1/#comments";s:7:"pubdate";s:31:"Wed, 16 Dec 2009 18:33:39 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:11:"Development";s:4:"guid";s:40:"http://wordpress.org/development/?p=1057";s:11:"description";s:335:"We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.
If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you [...]";s:7:"content";a:1:{s:7:"encoded";s:1702:"<p>We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.</p>
<p>If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you expect it to. <a href="http://codex.wordpress.org/Version_2.9">Here&#8217;s a list of all the fun and geeky new stuff in 2.9 to try out</a>. Second, and more importantly, we need everyone to test out their plugin compatibility.</p>
<p>If you&#8217;re a user of plugins, there&#8217;s a groovy new compatibility feature on the plugin directory where you can vote on whether a plugin is compatible with a version or not and it&#8217;ll get registered in the new plugin compatibility checker. This is as a replacement to the old wiki-based lists we&#8217;d do before. To see it in action <a href="http://wordpress.org/extend/plugins/akismet/">check out this Akismet plugin page</a>, as you can see 14 people have already registered that it&#8217;s compatible with 2.9.</p>
<p>If you&#8217;re a plugin author, of course you should update your &#8220;Tested up to:&#8221; in the <code>readme.txt</code> for your plugin.</p>
<p>If all goes according to plan, WordPress 2.9 will be out before the end of the week. <a href="http://wordpress.org/wordpress-2.9-RC1.zip">You can download the release candidate here</a>.</p>
<p>For more details on the changes since Beta please review the <a href="https://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=12416&amp;stop_rev=12315&amp;limit=150">revision log on Trac</a>, and happy testing!</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:54:"http://wordpress.org/development/2009/12/2-9-rc1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:335:"We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.
If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you [...]";s:12:"atom_content";s:1702:"<p>We&#8217;re at that exciting point in WordPress development where the dev team feels like version 2.9 is complete and ready for the world.</p>
<p>If you&#8217;ve been waiting for your moment to pitch in, it&#8217;s now. First we need tech savvy testers to upgrade their blogs and kick the tires, make sure everything is rolling like you expect it to. <a href="http://codex.wordpress.org/Version_2.9">Here&#8217;s a list of all the fun and geeky new stuff in 2.9 to try out</a>. Second, and more importantly, we need everyone to test out their plugin compatibility.</p>
<p>If you&#8217;re a user of plugins, there&#8217;s a groovy new compatibility feature on the plugin directory where you can vote on whether a plugin is compatible with a version or not and it&#8217;ll get registered in the new plugin compatibility checker. This is as a replacement to the old wiki-based lists we&#8217;d do before. To see it in action <a href="http://wordpress.org/extend/plugins/akismet/">check out this Akismet plugin page</a>, as you can see 14 people have already registered that it&#8217;s compatible with 2.9.</p>
<p>If you&#8217;re a plugin author, of course you should update your &#8220;Tested up to:&#8221; in the <code>readme.txt</code> for your plugin.</p>
<p>If all goes according to plan, WordPress 2.9 will be out before the end of the week. <a href="http://wordpress.org/wordpress-2.9-RC1.zip">You can download the release candidate here</a>.</p>
<p>For more details on the changes since Beta please review the <a href="https://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=12416&amp;stop_rev=12315&amp;limit=150">revision log on Trac</a>, and happy testing!</p>
";}i:6;a:13:{s:5:"title";s:24:"Core Team Meetup Results";s:4:"link";s:66:"http://wordpress.org/development/2009/12/core-team-meetup-results/";s:8:"comments";s:75:"http://wordpress.org/development/2009/12/core-team-meetup-results/#comments";s:7:"pubdate";s:31:"Mon, 14 Dec 2009 19:16:36 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:11:"Development";s:4:"guid";s:40:"http://wordpress.org/development/?p=1023";s:11:"description";s:333:"To get started, here&#8217;s a short video from the meetup discussing some of the topics and 2.9. In the opening pan, you&#8217;ll see (L-R) Andrew Ozz, Mark Jaquith, Jane Wells, Peter Westwood, and Ryan Boren, followed by Matt Mullenweg as the first person talking. Tip: go full-screen in HD to feel like you were there.

Last [...]";s:7:"content";a:1:{s:7:"encoded";s:3519:"<p>To get started, here&#8217;s a short video from the meetup discussing some of the topics and 2.9. In the opening pan, you&#8217;ll see (L-R) Andrew Ozz, Mark Jaquith, Jane Wells, Peter Westwood, and Ryan Boren, followed by Matt Mullenweg as the first person talking. <em>Tip: go full-screen in HD to feel like you were there</em>.</p>
<p><embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.11" type="application/x-shockwave-flash" width="400" height="224" allowscriptaccess="always" allowfullscreen="true" flashvars="guid=OxzyETzZ&amp;width=400&amp;height=224" title="WordPress Core Commit Team Meetup"></embed></p>
<p>Last week, I posted about the fact that Trac would be quiet for a few days while the core commit team met in person for the first time to talk about some goals for WordPress in the coming year. That prediction wound up being a little inaccurate, as having everyone together inspired a Trac sprint to get us closer to shipping 2.9. As of this morning there are only <a href="https://core.trac.wordpress.org/query?status=reopened&#038;status=assigned&#038;status=reviewing&#038;status=new&#038;status=accepted&#038;group=status&#038;milestone=2.9">11 tickets</a> left against the 2.9 milestone. Yay! I&#8217;m sensing a Release Candidate in the near future.</p>
<p>I&#8217;d planned to write a summary post to encapsulate the discussions we had over our 3 day meetup, but to be honest, all-day (and night) every-day meetings creates a ton of things to summarize, and the post would be a novella. So instead of one long post, I&#8217;m going to split it up into a series and post a summary of the discussion on one or two topics per day until I&#8217;ve posted them all. Think of it like a WordPress advent calendar. For today&#8217;s post, enjoy the video above and I&#8217;ll list the topics we covered to give you an idea of what will be included in the upcoming summary posts.</p>
<p><strong>Topics: </strong>Direction for the coming year(s), canonical plugins, social i18n for plugins, plugin salvage (like UDRP for abandoned plugins), WordPress/MU merge, default themes, CMS functionality (custom taxonomies, types, statuses, queries), cross-content taxonomy, media functions and UI, community &#8220;levels&#8221; based on activity, defining scope of releases, site menu management, communications within the community, lessons learned from past releases, mentorship programs, Trac issues, wordpress.org redesign, documentation, community code of conduct.</p>
<p>You can see why I didn&#8217;t want to try to cram it all into one post, right? <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Just to make sure it&#8217;s clear in everyone&#8217;s minds, I want to reiterate that these discussions were just that: discussions. They were not secret meetings ending in hard and fast decisions. The idea was to 1) get the core commit team on the same page in order to improve workflow efficiency and communication, and 2) come out of the meetup with a long list of things we know we want to work on in the coming year, and from there to work with the broader community to determine priorities/strategies before starting the work of getting it all done. As I finish off 2009 by posting summaries of the meetup conversations, I hope you&#8217;ll all plan to start 2010 with enthusiastic participation in one or more of the projects that will take these conservations from concept to reality.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:71:"http://wordpress.org/development/2009/12/core-team-meetup-results/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"2";}s:7:"summary";s:333:"To get started, here&#8217;s a short video from the meetup discussing some of the topics and 2.9. In the opening pan, you&#8217;ll see (L-R) Andrew Ozz, Mark Jaquith, Jane Wells, Peter Westwood, and Ryan Boren, followed by Matt Mullenweg as the first person talking. Tip: go full-screen in HD to feel like you were there.

Last [...]";s:12:"atom_content";s:3519:"<p>To get started, here&#8217;s a short video from the meetup discussing some of the topics and 2.9. In the opening pan, you&#8217;ll see (L-R) Andrew Ozz, Mark Jaquith, Jane Wells, Peter Westwood, and Ryan Boren, followed by Matt Mullenweg as the first person talking. <em>Tip: go full-screen in HD to feel like you were there</em>.</p>
<p><embed src="http://v.wordpress.com/wp-content/plugins/video/flvplayer.swf?ver=1.11" type="application/x-shockwave-flash" width="400" height="224" allowscriptaccess="always" allowfullscreen="true" flashvars="guid=OxzyETzZ&amp;width=400&amp;height=224" title="WordPress Core Commit Team Meetup"></embed></p>
<p>Last week, I posted about the fact that Trac would be quiet for a few days while the core commit team met in person for the first time to talk about some goals for WordPress in the coming year. That prediction wound up being a little inaccurate, as having everyone together inspired a Trac sprint to get us closer to shipping 2.9. As of this morning there are only <a href="https://core.trac.wordpress.org/query?status=reopened&#038;status=assigned&#038;status=reviewing&#038;status=new&#038;status=accepted&#038;group=status&#038;milestone=2.9">11 tickets</a> left against the 2.9 milestone. Yay! I&#8217;m sensing a Release Candidate in the near future.</p>
<p>I&#8217;d planned to write a summary post to encapsulate the discussions we had over our 3 day meetup, but to be honest, all-day (and night) every-day meetings creates a ton of things to summarize, and the post would be a novella. So instead of one long post, I&#8217;m going to split it up into a series and post a summary of the discussion on one or two topics per day until I&#8217;ve posted them all. Think of it like a WordPress advent calendar. For today&#8217;s post, enjoy the video above and I&#8217;ll list the topics we covered to give you an idea of what will be included in the upcoming summary posts.</p>
<p><strong>Topics: </strong>Direction for the coming year(s), canonical plugins, social i18n for plugins, plugin salvage (like UDRP for abandoned plugins), WordPress/MU merge, default themes, CMS functionality (custom taxonomies, types, statuses, queries), cross-content taxonomy, media functions and UI, community &#8220;levels&#8221; based on activity, defining scope of releases, site menu management, communications within the community, lessons learned from past releases, mentorship programs, Trac issues, wordpress.org redesign, documentation, community code of conduct.</p>
<p>You can see why I didn&#8217;t want to try to cram it all into one post, right? <img src='http://wordpress.org/development/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
<p>Just to make sure it&#8217;s clear in everyone&#8217;s minds, I want to reiterate that these discussions were just that: discussions. They were not secret meetings ending in hard and fast decisions. The idea was to 1) get the core commit team on the same page in order to improve workflow efficiency and communication, and 2) come out of the meetup with a long list of things we know we want to work on in the coming year, and from there to work with the broader community to determine priorities/strategies before starting the work of getting it all done. As I finish off 2009 by posting summaries of the meetup conversations, I hope you&#8217;ll all plan to start 2010 with enthusiastic participation in one or more of the projects that will take these conservations from concept to reality.</p>
";}i:7;a:13:{s:5:"title";s:29:"Canonical Plugins (Say What?)";s:4:"link";s:59:"http://wordpress.org/development/2009/12/canonical-plugins/";s:8:"comments";s:68:"http://wordpress.org/development/2009/12/canonical-plugins/#comments";s:7:"pubdate";s:31:"Tue, 08 Dec 2009 00:44:03 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:27:"Developmentcanonicalplugins";s:4:"guid";s:40:"http://wordpress.org/development/?p=1005";s:11:"description";s:340:"There have been a lot of references to &#8220;canonical plugins&#8221; over the past year, especially at WordCamps by Matt, but we haven&#8217;t really posted anything official about the idea, nor have we really made much progress beyond discussions about how awesome it would be to have canonical plugins and how good it would be for [...]";s:7:"content";a:1:{s:7:"encoded";s:4461:"<p>There have been a lot of references to &#8220;canonical plugins&#8221; over the past year, especially at WordCamps by Matt, but we haven&#8217;t really posted anything official about the idea, nor have we really made much progress beyond discussions about how awesome it would be to have canonical plugins and how good it would be for the community. <em>But what are canonical plugins</em>, you ask? Well, that&#8217;s one of the many things the core commit team has been talking about over the past few days, and everyone agrees that we need to prioritize this aspect of the project sooner rather than later. So, here&#8217;s a super high-level description of how we&#8217;re currently thinking about canonical plugins, which we&#8217;d like to use to initiate some focused community discussion on the topic.</p>
<p>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&#8217;s Choice or Verified guarantee. These plugins would be a true extension of core WordPress in terms of compatibility, security and support.</p>
<p>In order to have a system like this, each canonical plugin&#8217;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&#8217;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&#8217;m including a short description of our thoughts on each.<br />
<blockquote><strong>Standard </strong>- 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.<br />
<strong>Core </strong>- Makes the close relationship to core WordPress development very clear, and has the implication of bundled plugins (even though we don&#8217;t need to actually bundle them now that the installer is right in the admin tool).<br />
<strong>Premium</strong> &#8211; 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).<br />
<strong>Validated </strong>- Focuses on the fact that the code is reviewed for compatibility with core and for security.<br />
<strong>Official</strong> &#8211; Makes it plain that these are the plugins officially endorsed by the core team as being the best at their functions.<br />
<strong>Canonical</strong> &#8211; Maybe once people get used to it, canonical wouldn&#8217;t confuse so many people?
</p></blockquote>
<p>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&#8217;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.<br />
<script src="http://static.polldaddy.com/p/2352794.js" type="text/javascript"></script><noscript><br />
<a href="http://answers.polldaddy.com/poll/2352794/">What should we call canonical plugins? &#8220;________________&#8221; Plugins</a><span style="font-size:9px;">(<a href="http://www.polldaddy.com">survey software</a>)</span><br />
</noscript></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:64:"http://wordpress.org/development/2009/12/canonical-plugins/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"9";}s:7:"summary";s:340:"There have been a lot of references to &#8220;canonical plugins&#8221; over the past year, especially at WordCamps by Matt, but we haven&#8217;t really posted anything official about the idea, nor have we really made much progress beyond discussions about how awesome it would be to have canonical plugins and how good it would be for [...]";s:12:"atom_content";s:4461:"<p>There have been a lot of references to &#8220;canonical plugins&#8221; over the past year, especially at WordCamps by Matt, but we haven&#8217;t really posted anything official about the idea, nor have we really made much progress beyond discussions about how awesome it would be to have canonical plugins and how good it would be for the community. <em>But what are canonical plugins</em>, you ask? Well, that&#8217;s one of the many things the core commit team has been talking about over the past few days, and everyone agrees that we need to prioritize this aspect of the project sooner rather than later. So, here&#8217;s a super high-level description of how we&#8217;re currently thinking about canonical plugins, which we&#8217;d like to use to initiate some focused community discussion on the topic.</p>
<p>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&#8217;s Choice or Verified guarantee. These plugins would be a true extension of core WordPress in terms of compatibility, security and support.</p>
<p>In order to have a system like this, each canonical plugin&#8217;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&#8217;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&#8217;m including a short description of our thoughts on each.<br />
<blockquote><strong>Standard </strong>- 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.<br />
<strong>Core </strong>- Makes the close relationship to core WordPress development very clear, and has the implication of bundled plugins (even though we don&#8217;t need to actually bundle them now that the installer is right in the admin tool).<br />
<strong>Premium</strong> &#8211; 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).<br />
<strong>Validated </strong>- Focuses on the fact that the code is reviewed for compatibility with core and for security.<br />
<strong>Official</strong> &#8211; Makes it plain that these are the plugins officially endorsed by the core team as being the best at their functions.<br />
<strong>Canonical</strong> &#8211; Maybe once people get used to it, canonical wouldn&#8217;t confuse so many people?
</p></blockquote>
<p>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&#8217;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.<br />
<script src="http://static.polldaddy.com/p/2352794.js" type="text/javascript"></script><noscript><br />
<a href="http://answers.polldaddy.com/poll/2352794/">What should we call canonical plugins? &#8220;________________&#8221; Plugins</a><span style="font-size:9px;">(<a href="http://www.polldaddy.com">survey software</a>)</span><br />
</noscript></p>
";}i:8;a:13:{s:5:"title";s:20:"A Brief Intermission";s:4:"link";s:54:"http://wordpress.org/development/2009/12/intermission/";s:8:"comments";s:63:"http://wordpress.org/development/2009/12/intermission/#comments";s:7:"pubdate";s:31:"Sun, 06 Dec 2009 14:45:21 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:25:"Generalcoremeetupplanning";s:4:"guid";s:39:"http://wordpress.org/development/?p=998";s:11:"description";s:296:"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 [...]";s:7:"content";a:1:{s:7:"encoded";s:1480:"<p><img style="margin-right: 10px;" title="Core Team in Orlando (minus Matt)" src="http://jane.wordpress.com/files/2009/12/core_wcorlando.jpg?w=250" alt="picture of core team minus Matt" width="250" align="left" height="187" />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&#8217;s inevitably a point at which someone says, &#8220;We really need to have [insert a core committer name here] here to make a decision,&#8221; 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&#8217;d never met Andrew or Peter), so it&#8217;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&#8217;ve discussed, and the beginning of planning for how members of community can get involved in (or spearhead) the things that interest them.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:59:"http://wordpress.org/development/2009/12/intermission/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:296:"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 [...]";s:12:"atom_content";s:1480:"<p><img style="margin-right: 10px;" title="Core Team in Orlando (minus Matt)" src="http://jane.wordpress.com/files/2009/12/core_wcorlando.jpg?w=250" alt="picture of core team minus Matt" width="250" align="left" height="187" />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&#8217;s inevitably a point at which someone says, &#8220;We really need to have [insert a core committer name here] here to make a decision,&#8221; 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&#8217;d never met Andrew or Peter), so it&#8217;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&#8217;ve discussed, and the beginning of planning for how members of community can get involved in (or spearhead) the things that interest them.</p>
";}i:9;a:13:{s:5:"title";s:20:"WordPress 2.9 Beta 2";s:4:"link";s:62:"http://wordpress.org/development/2009/12/wordpress-2-9-beta-2/";s:8:"comments";s:71:"http://wordpress.org/development/2009/12/wordpress-2-9-beta-2/#comments";s:7:"pubdate";s:31:"Wed, 02 Dec 2009 00:58:17 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Andrew Ozz";}s:8:"category";s:15:"Developmentbeta";s:4:"guid";s:39:"http://wordpress.org/development/?p=991";s:11:"description";s:196:"Version beta-2 of WordPress 2.9 is ready for your testing pleasure. You can download it or use the WordPress Beta Tester plugin and auto-upgrade a test installation. See all changes since beta 1.
";s:7:"content";a:1:{s:7:"encoded";s:475:"<p>Version beta-2 of WordPress 2.9 is ready for your testing pleasure. You can <a href="http://wordpress.org/wordpress-2.9-beta-2.zip">download it</a> or use the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin and auto-upgrade a test installation. See <a href="http://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=12314&amp;stop_rev=12191&amp;limit=200">all changes</a> since beta 1.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2009/12/wordpress-2-9-beta-2/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"0";}s:7:"summary";s:196:"Version beta-2 of WordPress 2.9 is ready for your testing pleasure. You can download it or use the WordPress Beta Tester plugin and auto-upgrade a test installation. See all changes since beta 1.
";s:12:"atom_content";s:475:"<p>Version beta-2 of WordPress 2.9 is ready for your testing pleasure. You can <a href="http://wordpress.org/wordpress-2.9-beta-2.zip">download it</a> or use the <a href="http://wordpress.org/extend/plugins/wordpress-beta-tester/">WordPress Beta Tester</a> plugin and auto-upgrade a test installation. See <a href="http://core.trac.wordpress.org/log/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=12314&amp;stop_rev=12191&amp;limit=200">all changes</a> since beta 1.</p>
";}}s:7:"channel";a:8:{s:5:"title";s:26:"WordPress Development Blog";s:4:"link";s:32:"http://wordpress.org/development";s:11:"description";s:33:"WordPress development and updates";s:13:"lastbuilddate";s:31:"Tue, 29 Dec 2009 23:27:23 +0000";s:9:"generator";s:33:"http://wordpress.org/?v=3.0-alpha";s:8:"language";s:2:"en";s:2:"sy";a:2:{s:12:"updateperiod";s:6:"hourly";s:15:"updatefrequency";s:1:"1";}s:7:"tagline";s:33:"WordPress development and updates";}s:9:"textinput";a:0:{}s:5:"image";a:0:{}s:9:"feed_type";s:3:"RSS";s:12:"feed_version";s:3:"2.0";s:5:"stack";a:0:{}s:9:"inchannel";b:0;s:6:"initem";b:0;s:9:"incontent";b:0;s:11:"intextinput";b:0;s:7:"inimage";b:0;s:13:"current_field";s:0:"";s:17:"current_namespace";b:0;s:19:"_CONTENT_CONSTRUCTS";a:6:{i:0;s:7:"content";i:1;s:7:"summary";i:2;s:4:"info";i:3;s:5:"title";i:4;s:7:"tagline";i:5;s:9:"copyright";}}