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:18:"Upcoming WordCamps";s:4:"link";s:62:"http://wordpress.org/development/2009/08/upcoming-wordcamps-2/";s:8:"comments";s:71:"http://wordpress.org/development/2009/08/upcoming-wordcamps-2/#comments";s:7:"pubdate";s:31:"Fri, 07 Aug 2009 01:07:03 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:11:"Development";s:4:"guid";s:39:"http://wordpress.org/development/?p=899";s:11:"description";s:322:"Every now and then I see someone ask in the dev channel how they can meet up with other local WordPress developers. We&#8217;re thinking about ways to make WordPress.org more of a resource to facilitate local connections, but in the meantime, I thought it might be helpful to publicize some  upcoming  WordCamps, the [...]";s:7:"content";a:1:{s:7:"encoded";s:2708:"<p>Every now and then I see someone ask in the dev channel how they can meet up with other local WordPress developers. We&#8217;re thinking about ways to make WordPress.org more of a resource to facilitate local connections, but in the meantime, I thought it might be helpful to publicize some <a href="http://central.wordcamp.org/schedule/"> upcoming  WordCamps</a>, the weekend conferences organized by local communities to talk about all things WordPress. </p>
<p><strong><a href="http://wordcamp.org.nz">WordCamp New Zealand</a>:</strong> Wellington, New Zealand, August 8-9, 2009</p>
<p><strong><a href="http://wordcamphsv.org/">WordCamp Huntsville</a>:</strong> Huntsville, Alabama, USA, August 15–16, 2009</p>
<p><strong><a href="http://la.wordcamp.org/">WordCamp Los Angeles</a>:</strong> Los Angeles, California, USA, September 12, 2009</p>
<p><strong><a href="http://wordcamp.ph">WordCamp Philippines</a>: </strong>Makati City, Philippines, September 19, 2009</p>
<p><strong><a href="http://www.wordcampportland.org/">WordCamp Portland</a>: </strong>Portland, Oregon, USA, September 19-20, 2009 <em>(Last year&#8217;s PDX WordCamp was awesome, IMO.)</em></p>
<p><strong><a href="http://www.wordcampseattle.com/">WordCamp Seattle</a>: </strong>Seattle, Washington, USA, September 26, 2009</p>
<p><strong><a href="http://wordcampbirmingham.org/">WordCamp Birmingham</a>:</strong> Birmingham, Alabama, USA, September 26-27, 2009</p>
<p><strong><a href="http://wordcampnl.org/">WordCamp Netherlands</a>:</strong> Utrecht, Netherlands, October 31, 2009</p>
<p><strong><a href="http://2009.newyork.wordcamp.org/">WordCamp NYC</a>:</strong> New York, New York, USA, November 14-15, 2009 <em>(<a href="http://2009.newyork.wordcamp.org/2009/07/24/logo-contest-again/">Logo contest in progress</a>!)</em></p>
<p><strong><a href="http://wordcampmexico.wordpress.com">WordCamp Mexico</a>:</strong> Mexico City, Mexico, November 20, 2009</p>
<p>If any of these are within a reasonable distance to you, consider attending. WordCamps are a great way to meet other WordPress users, find collaborators, and expand your t-shirt collection*. I know I&#8217;ll be hitting at least a few of these; WordCamps are also a great way to get user feedback to take into consideration while we&#8217;re making decisions about what to include in core. </p>
<p>You can always find an up-to-date list of upcoming WordCamps at <a href="http://central.wordcamp.org/">WordCamp Central</a>. You can also try searching for WordPress groups at <a href="http://www.meetup.com/">Meetup.com</a> to find more regular monthly gatherings in your area. </p>
<p>*<em>Most WordCamps include an event t-shirt in the registration fee. </em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:67:"http://wordpress.org/development/2009/08/upcoming-wordcamps-2/feed/";}s:5:"slash";a:1:{s:8:"comments";s:1:"5";}s:7:"summary";s:322:"Every now and then I see someone ask in the dev channel how they can meet up with other local WordPress developers. We&#8217;re thinking about ways to make WordPress.org more of a resource to facilitate local connections, but in the meantime, I thought it might be helpful to publicize some  upcoming  WordCamps, the [...]";s:12:"atom_content";s:2708:"<p>Every now and then I see someone ask in the dev channel how they can meet up with other local WordPress developers. We&#8217;re thinking about ways to make WordPress.org more of a resource to facilitate local connections, but in the meantime, I thought it might be helpful to publicize some <a href="http://central.wordcamp.org/schedule/"> upcoming  WordCamps</a>, the weekend conferences organized by local communities to talk about all things WordPress. </p>
<p><strong><a href="http://wordcamp.org.nz">WordCamp New Zealand</a>:</strong> Wellington, New Zealand, August 8-9, 2009</p>
<p><strong><a href="http://wordcamphsv.org/">WordCamp Huntsville</a>:</strong> Huntsville, Alabama, USA, August 15–16, 2009</p>
<p><strong><a href="http://la.wordcamp.org/">WordCamp Los Angeles</a>:</strong> Los Angeles, California, USA, September 12, 2009</p>
<p><strong><a href="http://wordcamp.ph">WordCamp Philippines</a>: </strong>Makati City, Philippines, September 19, 2009</p>
<p><strong><a href="http://www.wordcampportland.org/">WordCamp Portland</a>: </strong>Portland, Oregon, USA, September 19-20, 2009 <em>(Last year&#8217;s PDX WordCamp was awesome, IMO.)</em></p>
<p><strong><a href="http://www.wordcampseattle.com/">WordCamp Seattle</a>: </strong>Seattle, Washington, USA, September 26, 2009</p>
<p><strong><a href="http://wordcampbirmingham.org/">WordCamp Birmingham</a>:</strong> Birmingham, Alabama, USA, September 26-27, 2009</p>
<p><strong><a href="http://wordcampnl.org/">WordCamp Netherlands</a>:</strong> Utrecht, Netherlands, October 31, 2009</p>
<p><strong><a href="http://2009.newyork.wordcamp.org/">WordCamp NYC</a>:</strong> New York, New York, USA, November 14-15, 2009 <em>(<a href="http://2009.newyork.wordcamp.org/2009/07/24/logo-contest-again/">Logo contest in progress</a>!)</em></p>
<p><strong><a href="http://wordcampmexico.wordpress.com">WordCamp Mexico</a>:</strong> Mexico City, Mexico, November 20, 2009</p>
<p>If any of these are within a reasonable distance to you, consider attending. WordCamps are a great way to meet other WordPress users, find collaborators, and expand your t-shirt collection*. I know I&#8217;ll be hitting at least a few of these; WordCamps are also a great way to get user feedback to take into consideration while we&#8217;re making decisions about what to include in core. </p>
<p>You can always find an up-to-date list of upcoming WordCamps at <a href="http://central.wordcamp.org/">WordCamp Central</a>. You can also try searching for WordPress groups at <a href="http://www.meetup.com/">Meetup.com</a> to find more regular monthly gatherings in your area. </p>
<p>*<em>Most WordCamps include an event t-shirt in the registration fee. </em></p>
";}i:1;a:13:{s:5:"title";s:32:"WordPress 2.8.3 Security Release";s:4:"link";s:74:"http://wordpress.org/development/2009/08/wordpress-2-8-3-security-release/";s:8:"comments";s:83:"http://wordpress.org/development/2009/08/wordpress-2-8-3-security-release/#comments";s:7:"pubdate";s:31:"Mon, 03 Aug 2009 15:30:54 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=891";s:11:"description";s:380:"Unfortunately, I missed some places when fixing the privilege escalation issues for 2.8.1.  Luckily, the entire WordPress community has our backs.  Several folks in the community dug deeper and discovered areas that were overlooked.  With their help, the remaining issues are fixed in 2.8.3.  Since this is a security release, upgrading is highly recommended.  Download [...]";s:7:"content";a:1:{s:7:"encoded";s:476:"<p>Unfortunately, I missed some places when fixing the privilege escalation issues for 2.8.1.  Luckily, the entire WordPress community has our backs.  Several folks in the community dug deeper and discovered areas that were overlooked.  With their help, the remaining issues are fixed in 2.8.3.  Since this is a security release, upgrading is highly recommended.  <a href="http://wordpress.org/download/">Download</a> 2.8.3, or upgrade automatically from your admin.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:79:"http://wordpress.org/development/2009/08/wordpress-2-8-3-security-release/feed/";}s:5:"slash";a:1:{s:8:"comments";s:3:"234";}s:7:"summary";s:380:"Unfortunately, I missed some places when fixing the privilege escalation issues for 2.8.1.  Luckily, the entire WordPress community has our backs.  Several folks in the community dug deeper and discovered areas that were overlooked.  With their help, the remaining issues are fixed in 2.8.3.  Since this is a security release, upgrading is highly recommended.  Download [...]";s:12:"atom_content";s:476:"<p>Unfortunately, I missed some places when fixing the privilege escalation issues for 2.8.1.  Luckily, the entire WordPress community has our backs.  Several folks in the community dug deeper and discovered areas that were overlooked.  With their help, the remaining issues are fixed in 2.8.3.  Since this is a security release, upgrading is highly recommended.  <a href="http://wordpress.org/download/">Download</a> 2.8.3, or upgrade automatically from your admin.</p>
";}i:2;a:13:{s:5:"title";s:25:"2.9 Features Vote Results";s:4:"link";s:58:"http://wordpress.org/development/2009/07/2-9-vote-results/";s:8:"comments";s:67:"http://wordpress.org/development/2009/07/2-9-vote-results/#comments";s:7:"pubdate";s:31:"Fri, 31 Jul 2009 18:26:29 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:24:"Features2.9resultssurvey";s:4:"guid";s:39:"http://wordpress.org/development/?p=877";s:11:"description";s:308:"Earlier this month, over 3500 of you responded to our survey asking you to help us prioritize some of the media features that had been suggested for the 2.9 release. While the exact features for 2.9 have not been hammered out yet, as we continue to match up developers with features, we wanted to share [...]";s:7:"content";a:1:{s:7:"encoded";s:8608:"<p>Earlier this month, over 3500 of you responded to our survey asking you to help us prioritize some of the media features that had been suggested for the 2.9 release. While the exact features for 2.9 have not been hammered out yet, as we continue to match up developers with features, we wanted to share the survey results and let you know what we&#8217;re thinking in terms of approach.</p>
<p>First, the results. The first question, and the only one that was mandatory, asked what single media feature you would choose to include in version 2.9. The top vote-getter was standalone editable photo albums (as opposed to the current per-post gallery) at 17.5%, followed closely by easier embeds for videos and other third-party content at 16.5%. Next came basic image editing (such as rotating, cropping and resizing) at 13.7%, and post thumbnails (image teasers for posts featured on the home page) at 12.9%. The rest of the features each took less than ten percent of the vote. The full list came in like this:</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q1.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q1.png" alt="Results of question 1" width="620" /></a></p>
<p>The second question was optional (3406 people answered it), and asked you to rate each feature on a scale going from <em>top priority</em> down to <em>definitely not</em> for implementation priority. Results here were in line with the results from the first question, with most features rated as <em>nice to have</em> more often than anything else. The features that scored the highest in question 1 were more likely to have earned higher votes in the Top Priority column, but no feature was ranked as a Top Priority more often than it was ranked as a Nice to Have (though Media Albums, Easier Embeds and Post Thumbnails came close). The complete tabulations are shown in the chart below.</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q2.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q2.png" alt="Results for question 2" width="620" /></a></p>
<p>Question three was getting at the same thing, but in a more granular fashion, asking you to rank the eleven features in order of priority to you. As only one feature could be assigned to each position, this prevented people from assigning the same priority to multiple features, and we wondered if it would alter the results. Though some features got more recognition in this question, the overall rankings were still in line with the results from question 1. Here are the exact votes per feature/per position:</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q3.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q3.png" alt="Results for question 3" width="620" /></a></p>
<p>The fourth question asked for your preferences regarding including new media features in core, bundling them as plugins with the core download, or developing them as plugins but not bundling them with the core download. This vote was more interesting to watch. As the notice for the voting went first to the development community, then to the user community, it was possible to see a shift in the voting. Earlier in the voting cycle, there were more votes for bundling &#8216;core plugins&#8217; for the advanced media features, while later votes skewed heavily toward just putting the features in core. This vote shows, I think, one of the differences between developer and user perspectives. While developers are heavily interested in keeping the core code lean and relying on plugins for advanced functionality, many users would prefer features they want to be included in core rather than being a separate plugin. The final tally on this question was 56.2% for including features in core, 38.1% for bundled plugins, and 5.7% for non-bundled plugins. The actual numbers:</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q4.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q4.png" alt="Results for question 4" width="620" /></a></p>
<p>Clearly this issue deserves more discussion, and the concept of how we move toward a system of canonical plugins and/or core &#8220;packages&#8221; intended for different use cases (CMS, photoblog, portfolio, etc) will be a big topic in the months ahead.</p>
<p>So where does that leave us regarding features coming down the road? When the vote closed, the results were discussed in the #wordpress-dev IRC chat to divvy up feature development.</p>
<p>The top-voted feature, standalone photo albums, is being worked on as a <a href="http://gsoc2009wp.wordpress.com/rudolf-photo-albums/">Google Summer of Code project by Rudolf Lai</a>, under the mentorship of WordPress Lead Developer <a href="http://markjaquith.com/">Mark Jaquith</a>. The &#8220;pencils down&#8221; date for GSOC is in less than two weeks, at which point we&#8217;ll be assessing the state of Rudolf&#8217;s project. Hopefully, we&#8217;ll be able to incorporate it with 2.9 development, do some testing,  amend the code and/or UI as needed, and have this launch with the 2.9 release (in core or as plugin TBD). Undoubtedly, additional functionality will be contributed by core contributors who have also been working on media plugins.</p>
<p>Easier embeds, the second most popular feature, is being looked at in a couple of ways. One, more shortcodes for third-party services. Work on this has already begun. In addition, <a href="http://viper007bond.com">Viper007Bond</a>, of <a href="http://wordpress.org/extend/plugins/vipers-video-quicktags/">Viper&#8217;s Video Quicktags plugin</a> fame, has taken on the task of working on a way to improve the embed experience in core. We&#8217;re not sure quite how this will work yet, but stay tuned.</p>
<p>Adding some basic editing functions like 90-degree rotation, cropping and resizing was considered an obvious winner in the dev chat, and as several plugins handle this functionality, we&#8217;re hopeful it will be included soon.</p>
<p>Post thumbnails are being handled by Mark Jaquith, who has created this functionality before, with an assist from <a href="http://scribu.net/">Scribu</a>, who has a <a href="http://wordpress.org/extend/plugins/custom-field-images/">similar plugin</a> in the repository.</p>
<p>Lower ranked features aren&#8217;t off the radar, but may take lower priority than some other (non-media) features we have in the works. One of my favorite 2.9 features is in trunk now, and changes the way we delete content. Goodbye, annoying popup asking me if I&#8217;m sure I want to delete a comment/post/etc. Hello, fast and quiet removal into a trash can, from which the content can be retrieved if it was deleted by accident. Think Gmail style. We&#8217;re also hoping to work on improving page management, though that has a number of technical issues that may cause it to be a 3.0 feature instead.</p>
<p>As always, you can keep track of development progress in a number of ways:<br />
1. Keep track of Trac. Contribute a patch, test a patch, just read through tickets if you have some time to kill, whatever. There are <a href="https://core.trac.wordpress.org/query?status=reopened&amp;status=assigned&amp;status=reviewing&amp;status=new&amp;status=accepted&amp;group=status&amp;milestone=2.9">over 500 tickets against the 2.9 milestone</a> currently. Patches and testing can help us get that number down.</p>
<p>2. Follow Trac commits on Twitter. Don&#8217;t want to get involved in the nitty gritty, just want to see what&#8217;s getting committed? Follow <a href="http://twitter.com/wpdevel">wpdevel on Twitter</a> and you&#8217;ll get core commit updates in your stream.</p>
<p>3. See what&#8217;s on the dev agenda. Each week for the IRC dev chat, there&#8217;s an agenda, created based on developer suggestions posted at <a href="http://wpdevel.wordpress.com">wpdevel.wordpress.com</a>. This blog also contains discussions about specific development issues.</p>
<p>4. Join the dev chat. The day changed this week, to accommodate European schedules. Chats are now held for one hour each week on Thursday at 21:00 UTC. That&#8217;s 5pm NYC, 2pm in California, etc. Chats are in the #wordpress-dev room at irc.freenode.com.</p>
<p>5. Watch this blog. If you&#8217;re not a developer and prefer to stick to major announcements, the occasional survey to help decide a feature, and security notices, just keep doing what you&#8217;re doing. Reading this blog will get you all of these things.</p>
<p>Thanks again for your help in prioritizing features for version 2.9, hopefully coming toward the end of the year to a server near you!</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:63:"http://wordpress.org/development/2009/07/2-9-vote-results/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"19";}s:7:"summary";s:308:"Earlier this month, over 3500 of you responded to our survey asking you to help us prioritize some of the media features that had been suggested for the 2.9 release. While the exact features for 2.9 have not been hammered out yet, as we continue to match up developers with features, we wanted to share [...]";s:12:"atom_content";s:8608:"<p>Earlier this month, over 3500 of you responded to our survey asking you to help us prioritize some of the media features that had been suggested for the 2.9 release. While the exact features for 2.9 have not been hammered out yet, as we continue to match up developers with features, we wanted to share the survey results and let you know what we&#8217;re thinking in terms of approach.</p>
<p>First, the results. The first question, and the only one that was mandatory, asked what single media feature you would choose to include in version 2.9. The top vote-getter was standalone editable photo albums (as opposed to the current per-post gallery) at 17.5%, followed closely by easier embeds for videos and other third-party content at 16.5%. Next came basic image editing (such as rotating, cropping and resizing) at 13.7%, and post thumbnails (image teasers for posts featured on the home page) at 12.9%. The rest of the features each took less than ten percent of the vote. The full list came in like this:</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q1.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q1.png" alt="Results of question 1" width="620" /></a></p>
<p>The second question was optional (3406 people answered it), and asked you to rate each feature on a scale going from <em>top priority</em> down to <em>definitely not</em> for implementation priority. Results here were in line with the results from the first question, with most features rated as <em>nice to have</em> more often than anything else. The features that scored the highest in question 1 were more likely to have earned higher votes in the Top Priority column, but no feature was ranked as a Top Priority more often than it was ranked as a Nice to Have (though Media Albums, Easier Embeds and Post Thumbnails came close). The complete tabulations are shown in the chart below.</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q2.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q2.png" alt="Results for question 2" width="620" /></a></p>
<p>Question three was getting at the same thing, but in a more granular fashion, asking you to rank the eleven features in order of priority to you. As only one feature could be assigned to each position, this prevented people from assigning the same priority to multiple features, and we wondered if it would alter the results. Though some features got more recognition in this question, the overall rankings were still in line with the results from question 1. Here are the exact votes per feature/per position:</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q3.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q3.png" alt="Results for question 3" width="620" /></a></p>
<p>The fourth question asked for your preferences regarding including new media features in core, bundling them as plugins with the core download, or developing them as plugins but not bundling them with the core download. This vote was more interesting to watch. As the notice for the voting went first to the development community, then to the user community, it was possible to see a shift in the voting. Earlier in the voting cycle, there were more votes for bundling &#8216;core plugins&#8217; for the advanced media features, while later votes skewed heavily toward just putting the features in core. This vote shows, I think, one of the differences between developer and user perspectives. While developers are heavily interested in keeping the core code lean and relying on plugins for advanced functionality, many users would prefer features they want to be included in core rather than being a separate plugin. The final tally on this question was 56.2% for including features in core, 38.1% for bundled plugins, and 5.7% for non-bundled plugins. The actual numbers:</p>
<p><a href="http://wpdotorg.wordpress.com/files/2009/07/q4.png"><img src="http://wpdotorg.wordpress.com/files/2009/07/q4.png" alt="Results for question 4" width="620" /></a></p>
<p>Clearly this issue deserves more discussion, and the concept of how we move toward a system of canonical plugins and/or core &#8220;packages&#8221; intended for different use cases (CMS, photoblog, portfolio, etc) will be a big topic in the months ahead.</p>
<p>So where does that leave us regarding features coming down the road? When the vote closed, the results were discussed in the #wordpress-dev IRC chat to divvy up feature development.</p>
<p>The top-voted feature, standalone photo albums, is being worked on as a <a href="http://gsoc2009wp.wordpress.com/rudolf-photo-albums/">Google Summer of Code project by Rudolf Lai</a>, under the mentorship of WordPress Lead Developer <a href="http://markjaquith.com/">Mark Jaquith</a>. The &#8220;pencils down&#8221; date for GSOC is in less than two weeks, at which point we&#8217;ll be assessing the state of Rudolf&#8217;s project. Hopefully, we&#8217;ll be able to incorporate it with 2.9 development, do some testing,  amend the code and/or UI as needed, and have this launch with the 2.9 release (in core or as plugin TBD). Undoubtedly, additional functionality will be contributed by core contributors who have also been working on media plugins.</p>
<p>Easier embeds, the second most popular feature, is being looked at in a couple of ways. One, more shortcodes for third-party services. Work on this has already begun. In addition, <a href="http://viper007bond.com">Viper007Bond</a>, of <a href="http://wordpress.org/extend/plugins/vipers-video-quicktags/">Viper&#8217;s Video Quicktags plugin</a> fame, has taken on the task of working on a way to improve the embed experience in core. We&#8217;re not sure quite how this will work yet, but stay tuned.</p>
<p>Adding some basic editing functions like 90-degree rotation, cropping and resizing was considered an obvious winner in the dev chat, and as several plugins handle this functionality, we&#8217;re hopeful it will be included soon.</p>
<p>Post thumbnails are being handled by Mark Jaquith, who has created this functionality before, with an assist from <a href="http://scribu.net/">Scribu</a>, who has a <a href="http://wordpress.org/extend/plugins/custom-field-images/">similar plugin</a> in the repository.</p>
<p>Lower ranked features aren&#8217;t off the radar, but may take lower priority than some other (non-media) features we have in the works. One of my favorite 2.9 features is in trunk now, and changes the way we delete content. Goodbye, annoying popup asking me if I&#8217;m sure I want to delete a comment/post/etc. Hello, fast and quiet removal into a trash can, from which the content can be retrieved if it was deleted by accident. Think Gmail style. We&#8217;re also hoping to work on improving page management, though that has a number of technical issues that may cause it to be a 3.0 feature instead.</p>
<p>As always, you can keep track of development progress in a number of ways:<br />
1. Keep track of Trac. Contribute a patch, test a patch, just read through tickets if you have some time to kill, whatever. There are <a href="https://core.trac.wordpress.org/query?status=reopened&amp;status=assigned&amp;status=reviewing&amp;status=new&amp;status=accepted&amp;group=status&amp;milestone=2.9">over 500 tickets against the 2.9 milestone</a> currently. Patches and testing can help us get that number down.</p>
<p>2. Follow Trac commits on Twitter. Don&#8217;t want to get involved in the nitty gritty, just want to see what&#8217;s getting committed? Follow <a href="http://twitter.com/wpdevel">wpdevel on Twitter</a> and you&#8217;ll get core commit updates in your stream.</p>
<p>3. See what&#8217;s on the dev agenda. Each week for the IRC dev chat, there&#8217;s an agenda, created based on developer suggestions posted at <a href="http://wpdevel.wordpress.com">wpdevel.wordpress.com</a>. This blog also contains discussions about specific development issues.</p>
<p>4. Join the dev chat. The day changed this week, to accommodate European schedules. Chats are now held for one hour each week on Thursday at 21:00 UTC. That&#8217;s 5pm NYC, 2pm in California, etc. Chats are in the #wordpress-dev room at irc.freenode.com.</p>
<p>5. Watch this blog. If you&#8217;re not a developer and prefer to stick to major announcements, the occasional survey to help decide a feature, and security notices, just keep doing what you&#8217;re doing. Reading this blog will get you all of these things.</p>
<p>Thanks again for your help in prioritizing features for version 2.9, hopefully coming toward the end of the year to a server near you!</p>
";}i:3;a:13:{s:5:"title";s:47:"The WordPress 2.0.x Legacy Branch is Deprecated";s:4:"link";s:89:"http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/";s:8:"comments";s:98:"http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/#comments";s:7:"pubdate";s:31:"Thu, 30 Jul 2009 01:07:23 +0000";s:2:"dc";a:1:{s:7:"creator";s:12:"Mark Jaquith";}s:8:"category";s:45:"DevelopmentSecurity2.0branchdeprecationlegacy";s:4:"guid";s:39:"http://wordpress.org/development/?p=866";s:11:"description";s:344:"The WordPress team had initially committed to maintaining the WordPress 2.0.x legacy branch until 2010. Unfortunately, we bit off more than we could chew—the 2.0.x branch is now retired and deprecated, a few months shy of 2010.
Many of the security improvements to the new versions of WordPress in the last couple of years were complete [...]";s:7:"content";a:1:{s:7:"encoded";s:1149:"<p>The WordPress team had initially committed to maintaining the WordPress 2.0.x legacy branch until 2010. Unfortunately, we bit off more than we could chew—the 2.0.x branch is now retired and deprecated, a few months shy of 2010.</p>
<p>Many of the security improvements to the new versions of WordPress in the last couple of years were complete reworks of how various systems were handled. Porting those changes to the 2.0.x branch would have been a monumental task and could have introduced instability or new bugs. We had to make hard decisions between stability and merging in the latest security enhancements. Additionally, far fewer people stayed on the 2.0.x branch than we anticipated. I take that as a testament to the new features in WordPress and perhaps even more the features offered by plugins, many of which don&#8217;t support older versions of WordPress!</p>
<p>I&#8217;m disappointed that we weren&#8217;t able to keep the branch maintained until 2010, but since one of the big reasons for that failure was the massive scope of our security improvements for the newer versions of WordPress, 2.0.x doesn&#8217;t die in vain!</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:94:"http://wordpress.org/development/2009/07/the-wordpress-2-0-x-legacy-branch-is-deprecated/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"18";}s:7:"summary";s:344:"The WordPress team had initially committed to maintaining the WordPress 2.0.x legacy branch until 2010. Unfortunately, we bit off more than we could chew—the 2.0.x branch is now retired and deprecated, a few months shy of 2010.
Many of the security improvements to the new versions of WordPress in the last couple of years were complete [...]";s:12:"atom_content";s:1149:"<p>The WordPress team had initially committed to maintaining the WordPress 2.0.x legacy branch until 2010. Unfortunately, we bit off more than we could chew—the 2.0.x branch is now retired and deprecated, a few months shy of 2010.</p>
<p>Many of the security improvements to the new versions of WordPress in the last couple of years were complete reworks of how various systems were handled. Porting those changes to the 2.0.x branch would have been a monumental task and could have introduced instability or new bugs. We had to make hard decisions between stability and merging in the latest security enhancements. Additionally, far fewer people stayed on the 2.0.x branch than we anticipated. I take that as a testament to the new features in WordPress and perhaps even more the features offered by plugins, many of which don&#8217;t support older versions of WordPress!</p>
<p>I&#8217;m disappointed that we weren&#8217;t able to keep the branch maintained until 2010, but since one of the big reasons for that failure was the massive scope of our security improvements for the newer versions of WordPress, 2.0.x doesn&#8217;t die in vain!</p>
";}i:4;a:13:{s:5:"title";s:36:"Improving your plugin – Changelogs";s:4:"link";s:74:"http://wordpress.org/development/2009/07/improving-your-plugin-changelogs/";s:8:"comments";s:83:"http://wordpress.org/development/2009/07/improving-your-plugin-changelogs/#comments";s:7:"pubdate";s:31:"Tue, 21 Jul 2009 20:28:34 +0000";s:2:"dc";a:1:{s:7:"creator";s:14:"Peter Westwood";}s:8:"category";s:29:"Documentationpluginstutorials";s:4:"guid";s:39:"http://wordpress.org/development/?p=848";s:11:"description";s:340:"We&#8217;ve recently made some changes to help improve the communication between plugin authors and plugin users about the changes that are made between versions.
We feel that all software should have a changelog that details, at a high level, what changes have been made in each version so that the user can make an informed decision [...]";s:7:"content";a:1:{s:7:"encoded";s:1507:"<p>We&#8217;ve <a href="http://westi.wordpress.com/2009/06/20/changelogs-changelogs-changelogs/">recently made some changes</a> to help improve the communication between plugin authors and plugin users about the changes that are made between versions.</p>
<p>We feel that all software should have a changelog that details, at a high level, what changes have been made in each version so that the user can make an informed decision about when to upgrade and how much testing they should do with their site.</p>
<p>In order to make this an easy and open communication channel we have added support for a Changelog section in the plugins <code>readme.txt</code> file.  This changelog information is then displayed as a separate tab in the <a href="http://wordpress.org/extend/plugins/">plugin directory</a> and also in the back end of your WordPress blog when you view the details on a new version of a plugin.</p>
<p>The new section is formatted as follows:</p>
<pre name="code" class="css">

== Changelog ==

= 1.0 =
* A change since the previous version.
* Another change.

= 0.5 =
* List versions from most recent at top to oldest at bottom.
</pre>
<p>We would also like to recommend that you also provide meaningful log messages when you commit changes to the subversion repository for your plugin so that people who want to dig further into your changes can see why things are changing (At the moment is seems a large number of plugin authors leave this field blank which isn&#8217;t very helpful).</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:79:"http://wordpress.org/development/2009/07/improving-your-plugin-changelogs/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"16";}s:7:"summary";s:340:"We&#8217;ve recently made some changes to help improve the communication between plugin authors and plugin users about the changes that are made between versions.
We feel that all software should have a changelog that details, at a high level, what changes have been made in each version so that the user can make an informed decision [...]";s:12:"atom_content";s:1507:"<p>We&#8217;ve <a href="http://westi.wordpress.com/2009/06/20/changelogs-changelogs-changelogs/">recently made some changes</a> to help improve the communication between plugin authors and plugin users about the changes that are made between versions.</p>
<p>We feel that all software should have a changelog that details, at a high level, what changes have been made in each version so that the user can make an informed decision about when to upgrade and how much testing they should do with their site.</p>
<p>In order to make this an easy and open communication channel we have added support for a Changelog section in the plugins <code>readme.txt</code> file.  This changelog information is then displayed as a separate tab in the <a href="http://wordpress.org/extend/plugins/">plugin directory</a> and also in the back end of your WordPress blog when you view the details on a new version of a plugin.</p>
<p>The new section is formatted as follows:</p>
<pre name="code" class="css">

== Changelog ==

= 1.0 =
* A change since the previous version.
* Another change.

= 0.5 =
* List versions from most recent at top to oldest at bottom.
</pre>
<p>We would also like to recommend that you also provide meaningful log messages when you commit changes to the subversion repository for your plugin so that people who want to dig further into your changes can see why things are changing (At the moment is seems a large number of plugin authors leave this field blank which isn&#8217;t very helpful).</p>
";}i:5;a:13:{s:5:"title";s:15:"WordPress 2.8.2";s:4:"link";s:57:"http://wordpress.org/development/2009/07/wordpress-2-8-2/";s:8:"comments";s:66:"http://wordpress.org/development/2009/07/wordpress-2-8-2/#comments";s:7:"pubdate";s:31:"Mon, 20 Jul 2009 05:35:45 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=856";s:11:"description";s:298:"WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.  Download 2.8.2 or automatically upgrade from the Tools-&#62;Upgrade page of your blog&#8217;s admin.
";s:7:"content";a:1:{s:7:"encoded";s:349:"<p>WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.  <a href="http://wordpress.org/download/">Download</a> 2.8.2 or automatically upgrade from the Tools-&gt;Upgrade page of your blog&#8217;s admin.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:62:"http://wordpress.org/development/2009/07/wordpress-2-8-2/feed/";}s:5:"slash";a:1:{s:8:"comments";s:3:"244";}s:7:"summary";s:298:"WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.  Download 2.8.2 or automatically upgrade from the Tools-&#62;Upgrade page of your blog&#8217;s admin.
";s:12:"atom_content";s:349:"<p>WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.  <a href="http://wordpress.org/download/">Download</a> 2.8.2 or automatically upgrade from the Tools-&gt;Upgrade page of your blog&#8217;s admin.</p>
";}i:6;a:13:{s:5:"title";s:15:"WordPress 2.8.1";s:4:"link";s:57:"http://wordpress.org/development/2009/07/wordpress-2-8-1/";s:8:"comments";s:66:"http://wordpress.org/development/2009/07/wordpress-2-8-1/#comments";s:7:"pubdate";s:31:"Thu, 09 Jul 2009 20:20:54 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=836";s:11:"description";s:352:"WordPress 2.8.1 fixes many bugs and tightens security for plugin administration pages.   Core Security Technologies notified us that admin pages added by certain plugins could be viewed by unprivileged users, resulting in information being leaked.  Not all plugins are vulnerable to this problem, but we advise upgrading to 2.8.1 to be safe.
What [...]";s:7:"content";a:1:{s:7:"encoded";s:2224:"<p>WordPress 2.8.1 fixes <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.8.1&amp;resolution=fixed">many bugs</a> and tightens security for plugin administration pages.   <a href="http://corelabs.coresecurity.com/index.php?module=FrontEndMod&amp;action=list&amp;type=advisory">Core Security Technologies</a> notified us that admin pages added by certain plugins could be viewed by unprivileged users, resulting in information being leaked.  Not all plugins are vulnerable to this problem, but we advise upgrading to 2.8.1 to be safe.</p>
<p>What else is new since 2.8?  Read through the highlights below, or  <a href="http://core.trac.wordpress.org/log/branches/2.8/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=11699&amp;stop_rev=11553&amp;limit=500">view all changes since 2.8</a></p>
<ul>
<li>Certain themes were calling get_categories() in such a way that it would fail in 2.8. 2.8.1 works around this so these themes won&#8217;t have to change.</li>
<li>Dashboard memory usage is reduced.  Some people were running out of memory when loading the dashboard, resulting in an incomplete page.</li>
<li>The automatic upgrade no longer accidentally deletes files when cleaning up from a failed upgrade.</li>
<li>A problem where the rich text editor wasn&#8217;t being loaded due to compression issues has been worked around.</li>
<li>Extra security has been put in place to better protect you from plugins that do not do explicit permission checks.</li>
<li>Translation of role names fixed.</li>
<li>wp_page_menu() defaults to sorting by the user specified menu order rather than the page title.</li>
<li>Upload error messages are now correctly reported.</li>
<li>Autosave error experienced by some IE users is fixed.</li>
<li>Styling glitch in the plugin editor fixed.</li>
<li>SSH2 filesystem requirements updated.</li>
<li>Switched back to curl as the default transport.</li>
<li>Updated the translation library to avoid a problem with mbstring.func_overload.</li>
<li>Stricter inline style sanitization.</li>
<li>Stricter menu security.</li>
<li>Disabled code highlighting due to browser incompatibilities.</li>
<li>RTL layout fixes.</li>
</ul>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:62:"http://wordpress.org/development/2009/07/wordpress-2-8-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:3:"283";}s:7:"summary";s:352:"WordPress 2.8.1 fixes many bugs and tightens security for plugin administration pages.   Core Security Technologies notified us that admin pages added by certain plugins could be viewed by unprivileged users, resulting in information being leaked.  Not all plugins are vulnerable to this problem, but we advise upgrading to 2.8.1 to be safe.
What [...]";s:12:"atom_content";s:2224:"<p>WordPress 2.8.1 fixes <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.8.1&amp;resolution=fixed">many bugs</a> and tightens security for plugin administration pages.   <a href="http://corelabs.coresecurity.com/index.php?module=FrontEndMod&amp;action=list&amp;type=advisory">Core Security Technologies</a> notified us that admin pages added by certain plugins could be viewed by unprivileged users, resulting in information being leaked.  Not all plugins are vulnerable to this problem, but we advise upgrading to 2.8.1 to be safe.</p>
<p>What else is new since 2.8?  Read through the highlights below, or  <a href="http://core.trac.wordpress.org/log/branches/2.8/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=11699&amp;stop_rev=11553&amp;limit=500">view all changes since 2.8</a></p>
<ul>
<li>Certain themes were calling get_categories() in such a way that it would fail in 2.8. 2.8.1 works around this so these themes won&#8217;t have to change.</li>
<li>Dashboard memory usage is reduced.  Some people were running out of memory when loading the dashboard, resulting in an incomplete page.</li>
<li>The automatic upgrade no longer accidentally deletes files when cleaning up from a failed upgrade.</li>
<li>A problem where the rich text editor wasn&#8217;t being loaded due to compression issues has been worked around.</li>
<li>Extra security has been put in place to better protect you from plugins that do not do explicit permission checks.</li>
<li>Translation of role names fixed.</li>
<li>wp_page_menu() defaults to sorting by the user specified menu order rather than the page title.</li>
<li>Upload error messages are now correctly reported.</li>
<li>Autosave error experienced by some IE users is fixed.</li>
<li>Styling glitch in the plugin editor fixed.</li>
<li>SSH2 filesystem requirements updated.</li>
<li>Switched back to curl as the default transport.</li>
<li>Updated the translation library to avoid a problem with mbstring.func_overload.</li>
<li>Stricter inline style sanitization.</li>
<li>Stricter menu security.</li>
<li>Disabled code highlighting due to browser incompatibilities.</li>
<li>RTL layout fixes.</li>
</ul>
";}i:7;a:13:{s:5:"title";s:35:"WordPress 2.8.1 Release Candidate 1";s:4:"link";s:77:"http://wordpress.org/development/2009/07/wordpress-2-8-1-release-candidate-1/";s:8:"comments";s:86:"http://wordpress.org/development/2009/07/wordpress-2-8-1-release-candidate-1/#comments";s:7:"pubdate";s:31:"Tue, 07 Jul 2009 17:04:45 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Ryan Boren";}s:8:"category";s:8:"Releases";s:4:"guid";s:39:"http://wordpress.org/development/?p=833";s:11:"description";s:227:"2.8.1 is nigh.  Release Candidate 1 is our last stop before the final release.  Please download RC1, review the changes made since beta 2, and have a look at all of the tickets fixed in 2.8.1.  Thanks for testing WordPress.
";s:7:"content";a:1:{s:7:"encoded";s:586:"<p>2.8.1 is nigh.  Release Candidate 1 is our last stop before the final release.  Please <a href="http://wordpress.org/wordpress-2.8.1-RC1.zip">download</a> RC1, review the <a href="http://core.trac.wordpress.org/log/branches/2.8/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=&amp;stop_rev=11654&amp;limit=100">changes made since beta 2</a>, and have a look at <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.8.1&amp;resolution=fixed">all of the tickets fixed in 2.8.1</a>.  Thanks for testing WordPress.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:82:"http://wordpress.org/development/2009/07/wordpress-2-8-1-release-candidate-1/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"37";}s:7:"summary";s:227:"2.8.1 is nigh.  Release Candidate 1 is our last stop before the final release.  Please download RC1, review the changes made since beta 2, and have a look at all of the tickets fixed in 2.8.1.  Thanks for testing WordPress.
";s:12:"atom_content";s:586:"<p>2.8.1 is nigh.  Release Candidate 1 is our last stop before the final release.  Please <a href="http://wordpress.org/wordpress-2.8.1-RC1.zip">download</a> RC1, review the <a href="http://core.trac.wordpress.org/log/branches/2.8/?action=stop_on_copy&amp;mode=stop_on_copy&amp;rev=&amp;stop_rev=11654&amp;limit=100">changes made since beta 2</a>, and have a look at <a href="http://core.trac.wordpress.org/query?status=closed&amp;group=resolution&amp;order=priority&amp;milestone=2.8.1&amp;resolution=fixed">all of the tickets fixed in 2.8.1</a>.  Thanks for testing WordPress.</p>
";}i:8;a:13:{s:5:"title";s:27:"Vote for 2.9 Media Features";s:4:"link";s:69:"http://wordpress.org/development/2009/07/vote-for-2-9-media-features/";s:8:"comments";s:78:"http://wordpress.org/development/2009/07/vote-for-2-9-media-features/#comments";s:7:"pubdate";s:31:"Tue, 07 Jul 2009 14:32:10 +0000";s:2:"dc";a:1:{s:7:"creator";s:10:"Jane Wells";}s:8:"category";s:19:"DevelopmentFeatures";s:4:"guid";s:39:"http://wordpress.org/development/?p=816";s:11:"description";s:351:"Last Wednesday, the core development team and a number of contributing developers met in the IRC #wordpress-dev channel to talk about which features should be included in version 2.9, which is now entering the development phase. We&#8217;ve been planning to focus on media features in 2.9 for some time, and unsurprisingly, it was media features [...]";s:7:"content";a:1:{s:7:"encoded";s:4793:"<p>Last Wednesday, the core development team and a number of contributing developers met in the IRC #wordpress-dev channel to talk about which features should be included in version 2.9, which is now entering the development phase. We&#8217;ve been planning to focus on media features in 2.9 for some time, and unsurprisingly, it was media features that dominated the discussion.* A large percentage of the requests we get from users are for more/better media features, so we&#8217;ve decided to focus 2.9 on building an infrastructure for improved media handling that we can continue to build on in versions to come. In that vein, we need your input to determine which features to prioritize and build sooner rather than later.</p>
<p>These are the features that we&#8217;re asking people to vote on (in alphabetical, not prioritized, order):</p>
<p><strong>Additional Media Filters:</strong> In the uploader, you can currently upload an image from your hard drive, link to an image from a URL, or select an image from the Media Library. This proposed feature would add links in the Media Library pane that would allow you to filter images to those that had been used most recently, used most often, and/or marked as a favorite. These filters would be available on the Media Library screen as well.<br />
<strong><br />
Basic Image Editing:</strong> Enable cropping, resizing and 90-degree rotation of uploaded images.<br />
<strong><br />
Better Media Settings: </strong>Enable the creation of more default media settings controlled in the Settings section, and allow settings to be overridden  during the individual media upload process as needed.</p>
<p><strong>Bulk Media Import API: </strong>Develop an API to allow for bulk media importing by plugins or importers.<br />
<strong><br />
Custom Image Sizes:</strong> Instead of hardcoded thumbnail, medium, large, etc. image sizes, custom image sizes would allow you to configure the maximum dimensions for each of the sizes.</p>
<p><strong>Easier Embeds:</strong> Make it easier to embed third-party content such as YouTube videos, etc. Similar to Viper&#8217;s Video Quicktags plugin.</p>
<p><strong>Media Albums: </strong>Ability to create and edit photo albums that can stand alone (as opposed to galleries being tied only to a post), including photostream functionality.<br />
<strong><br />
Media Metadata: </strong>Enable the use of categories and tags on media files.</p>
<p><strong>Photostream:</strong> Create a Flickr-style photostream that simply displays images in a chronological stream (as opposed to grouping in galleries).</p>
<p><strong>Post thumbnails:</strong> Choose an image to appear as a thumbnail with your post/article/excerpt.</p>
<p><strong>Revised Media UI: </strong>Redesign the uploader UI to make uploading and editing media files a simpler, more user-friendly process.</p>
<p>These descriptions are repeated in the beginning of the voting survey, so if you forget what something means you&#8217;ll be able to scroll up to remind yourself. Only the first question (pick your top choice) is mandatory. This survey isn&#8217;t very long. Question two lets you assign a general high/low priority to each of the 11 feature suggestions, while question 3 asks you to rank the 11 features in order of priority from 1-11. A text box or two allow you to make additional suggestions, and that&#8217;s it. The survey is anonymous, and will be open all week, until Friday, July 10, 2009 at 11:59 PM UTC.</p>
<p><script language="javascript" type="text/javascript">
var PDF_surveyID = '2F95783C8744F81A';
 var PDF_openText = 'Vote now!';
</script><br />
<script type="text/javascript" language="javascript" src="http://www.polldaddy.com/s.js"></script><br />
<noscript><a href="http://surveys.polldaddy.com/s/2F95783C8744F81A/">Vote now!</a></noscript></p>
<p><a href="http://surveys.polldaddy.com/s/2F95783C8744F81A/">No JavaScript? Take the survey here. </a></p>
<p>Results of the survey will be used to help developers decide which features to focus on for version 2.9. The 2.9 anticipated feature list will be posted here later in July, after the priority has been determined. How many contributing developers are available to code various features will play a large part in the decision-making process, so if you&#8217;ve ever thought of contributing code to WordPress development, now&#8217;s a great time to get involved. Developer chats are held each Wednesday in the IRC channel (irc.freenode.com #wordpress-dev) at 9 PM UTC (5pm Eastern, 2pm Pacific).</p>
<p><em>* &#8211; Other non-media features that were discussed either were determined to be better held for a future version for technical reasons, or were so widely desired that they were accepted for the 2.9 roadmap without requiring a vote.</em></p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:74:"http://wordpress.org/development/2009/07/vote-for-2-9-media-features/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"36";}s:7:"summary";s:351:"Last Wednesday, the core development team and a number of contributing developers met in the IRC #wordpress-dev channel to talk about which features should be included in version 2.9, which is now entering the development phase. We&#8217;ve been planning to focus on media features in 2.9 for some time, and unsurprisingly, it was media features [...]";s:12:"atom_content";s:4793:"<p>Last Wednesday, the core development team and a number of contributing developers met in the IRC #wordpress-dev channel to talk about which features should be included in version 2.9, which is now entering the development phase. We&#8217;ve been planning to focus on media features in 2.9 for some time, and unsurprisingly, it was media features that dominated the discussion.* A large percentage of the requests we get from users are for more/better media features, so we&#8217;ve decided to focus 2.9 on building an infrastructure for improved media handling that we can continue to build on in versions to come. In that vein, we need your input to determine which features to prioritize and build sooner rather than later.</p>
<p>These are the features that we&#8217;re asking people to vote on (in alphabetical, not prioritized, order):</p>
<p><strong>Additional Media Filters:</strong> In the uploader, you can currently upload an image from your hard drive, link to an image from a URL, or select an image from the Media Library. This proposed feature would add links in the Media Library pane that would allow you to filter images to those that had been used most recently, used most often, and/or marked as a favorite. These filters would be available on the Media Library screen as well.<br />
<strong><br />
Basic Image Editing:</strong> Enable cropping, resizing and 90-degree rotation of uploaded images.<br />
<strong><br />
Better Media Settings: </strong>Enable the creation of more default media settings controlled in the Settings section, and allow settings to be overridden  during the individual media upload process as needed.</p>
<p><strong>Bulk Media Import API: </strong>Develop an API to allow for bulk media importing by plugins or importers.<br />
<strong><br />
Custom Image Sizes:</strong> Instead of hardcoded thumbnail, medium, large, etc. image sizes, custom image sizes would allow you to configure the maximum dimensions for each of the sizes.</p>
<p><strong>Easier Embeds:</strong> Make it easier to embed third-party content such as YouTube videos, etc. Similar to Viper&#8217;s Video Quicktags plugin.</p>
<p><strong>Media Albums: </strong>Ability to create and edit photo albums that can stand alone (as opposed to galleries being tied only to a post), including photostream functionality.<br />
<strong><br />
Media Metadata: </strong>Enable the use of categories and tags on media files.</p>
<p><strong>Photostream:</strong> Create a Flickr-style photostream that simply displays images in a chronological stream (as opposed to grouping in galleries).</p>
<p><strong>Post thumbnails:</strong> Choose an image to appear as a thumbnail with your post/article/excerpt.</p>
<p><strong>Revised Media UI: </strong>Redesign the uploader UI to make uploading and editing media files a simpler, more user-friendly process.</p>
<p>These descriptions are repeated in the beginning of the voting survey, so if you forget what something means you&#8217;ll be able to scroll up to remind yourself. Only the first question (pick your top choice) is mandatory. This survey isn&#8217;t very long. Question two lets you assign a general high/low priority to each of the 11 feature suggestions, while question 3 asks you to rank the 11 features in order of priority from 1-11. A text box or two allow you to make additional suggestions, and that&#8217;s it. The survey is anonymous, and will be open all week, until Friday, July 10, 2009 at 11:59 PM UTC.</p>
<p><script language="javascript" type="text/javascript">
var PDF_surveyID = '2F95783C8744F81A';
 var PDF_openText = 'Vote now!';
</script><br />
<script type="text/javascript" language="javascript" src="http://www.polldaddy.com/s.js"></script><br />
<noscript><a href="http://surveys.polldaddy.com/s/2F95783C8744F81A/">Vote now!</a></noscript></p>
<p><a href="http://surveys.polldaddy.com/s/2F95783C8744F81A/">No JavaScript? Take the survey here. </a></p>
<p>Results of the survey will be used to help developers decide which features to focus on for version 2.9. The 2.9 anticipated feature list will be posted here later in July, after the priority has been determined. How many contributing developers are available to code various features will play a large part in the decision-making process, so if you&#8217;ve ever thought of contributing code to WordPress development, now&#8217;s a great time to get involved. Developer chats are held each Wednesday in the IRC channel (irc.freenode.com #wordpress-dev) at 9 PM UTC (5pm Eastern, 2pm Pacific).</p>
<p><em>* &#8211; Other non-media features that were discussed either were determined to be better held for a future version for technical reasons, or were so widely desired that they were accepted for the 2.9 roadmap without requiring a vote.</em></p>
";}i:9;a:13:{s:5:"title";s:19:"Themes are GPL, too";s:4:"link";s:60:"http://wordpress.org/development/2009/07/themes-are-gpl-too/";s:8:"comments";s:69:"http://wordpress.org/development/2009/07/themes-are-gpl-too/#comments";s:7:"pubdate";s:31:"Thu, 02 Jul 2009 05:50:35 +0000";s:2:"dc";a:1:{s:7:"creator";s:4:"Matt";}s:8:"category";s:4:"Meta";s:4:"guid";s:39:"http://wordpress.org/development/?p=810";s:11:"description";s:348:"If WordPress were a country, our Bill of Rights would be the GPL because it protects our core freedoms. We&#8217;ve always done our best to keep WordPress.org clean and only promote things that are completely compatible and legal with WordPress&#8217;s license. There have been some questions in the community about whether the GPL applies to [...]";s:7:"content";a:1:{s:7:"encoded";s:5925:"<p>If WordPress were a country, our Bill of Rights would be <a href="http://wordpress.org/about/gpl/">the GPL</a> because it <a href="http://www.gnu.org/philosophy/free-sw.html">protects our core freedoms</a>. We&#8217;ve always done our best to keep WordPress.org clean and only promote things that are completely compatible and legal with WordPress&#8217;s license. There have been some questions in the community about whether the GPL applies to themes like we&#8217;ve always assumed. To help clarify this point, I reached out to the <a href="http://en.wikipedia.org/wiki/Software_Freedom_Law_Center">Software Freedom Law Center</a>, the world&#8217;s preeminent experts on the GPL, which spent time with WordPress&#8217;s code, community, and provided us with an official legal opinion. One sentence summary: PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.</p>
<blockquote><p>Matt,</p>
<p>You asked the Software Freedom Law Center to clarify the status of themes as derivative works of WordPress, a content management software package written in PHP and licensed under version 2 of the GNU General Public License.</p>
<p>We examined release candidate 1 of WordPress 2.8, which you provided to us at http://wordpress.org/wordpress-2.8-RC1.tar.gz.  The &#8220;classic&#8221; and &#8220;default&#8221; themes included in that release candidate comprise various PHP and CSS files along with an optional directory of images.  The PHP files contain a mix of HTML markup and PHP calls to<br />
WordPress functions.  There is some programmatic logic in the PHP code, including loops and conditionals.</p>
<p>When WordPress is started, it executes various routines that prepare information for use by themes.  In normal use, control is then transferred via PHP&#8217;s include() function to HTML and PHP templates found in theme package files.  The PHP code in those template files relies on the earlier-prepared information to fill the templates for serving to the client.</p>
<p>On the basis of that version of WordPress, and considering those themes as if they had been added to WordPress by a third party, it is our opinion that the themes presented, and any that are substantially similar, contain elements that are derivative works of the WordPress software as well as elements that are potentially separate works. Specifically, the CSS files and material contained in the images directory of the &#8220;default&#8221; theme are works separate from the WordPress code.  On the other hand, the PHP and HTML code that is intermingled with and operated on by PHP the code derives from the WordPress code.</p>
<p>In the WordPress themes, CSS files and images exist purely as data to be served by a web server.  WordPress itself ignores these files[1]. The CSS and image files are simply read by the server as data and delivered verbatim to the user, avoiding the WordPress instance altogether.  The CSS and images could easily be used with a range of HTML documents and read and displayed by a variety of software having no relation to WordPress.  As such, these files are separate works from the WordPress code itself.</p>
<p>The PHP elements, taken together, are clearly derivative of WordPress code.  The template is loaded via the include() function.  Its contents are combined with the WordPress code in memory to be processed by PHP along with (and completely indistinguishable from) the rest of WordPress.  The PHP code consists largely of calls to WordPress functions and sparse, minimal logic to control which WordPress functions are accessed and how many times they will be called.  They are derivative of WordPress because every part of them is determined by the content of the WordPress functions they call.  As works of authorship, they are designed only to be combined with WordPress into a larger work.</p>
<p>HTML elements are intermingled with PHP in the two themes presented. These snippets of HTML interspersed with PHP throughout the theme PHP files together form a work whose form is highly dependent on the PHP and thus derivative of it.</p>
<p>In conclusion, the WordPress themes supplied contain elements that are derivative of WordPress&#8217;s copyrighted code.  These themes, being collections of distinct works (images, CSS files, PHP files), need not be GPL-licensed as a whole.  Rather, the PHP files are subject to the requirements of the GPL while the images and CSS are not.  Third-party developers of such themes may apply restrictive copyrights to these elements if they wish.</p>
<p>Finally, we note that it might be possible to design a valid WordPress theme that avoids the factors that subject it to WordPress&#8217;s copyright, but such a theme would have to forgo almost all the WordPress functionality that makes the software useful.</p>
<p>Sincerely,<br />
James Vasile<br />
Software Freedom Law Center</p>
<p>[1] There is one exception.  WordPress does reads CSS and image files to create previews of templates for the template selection portion of the administrative interface.  Even in that case, though, nothing in those files calls any WordPress functions, is treated as a command by PHP, or alters any other WordPress data structure.  These files are read as data and used to create an image and display a miniaturized version of a webpage to the user.</p></blockquote>
<p>Even though graphics and CSS aren&#8217;t <em>required</em> to be GPL legally, the lack thereof is pretty limiting. Can you imagine WordPress without any CSS or javascript? So as before, we will only promote and host things on WordPress.org that are 100% GPL <a href="http://en.wikipedia.org/wiki/License_compatibility">or compatible</a>. To celebrate a few folks creating 100% GPL themes and providing support and other services around them, <a href="http://wordpress.org/extend/themes/commercial/">we have a new page listing GPL commercially supported themes</a>.</p>
";}s:3:"wfw";a:1:{s:10:"commentrss";s:65:"http://wordpress.org/development/2009/07/themes-are-gpl-too/feed/";}s:5:"slash";a:1:{s:8:"comments";s:2:"77";}s:7:"summary";s:348:"If WordPress were a country, our Bill of Rights would be the GPL because it protects our core freedoms. We&#8217;ve always done our best to keep WordPress.org clean and only promote things that are completely compatible and legal with WordPress&#8217;s license. There have been some questions in the community about whether the GPL applies to [...]";s:12:"atom_content";s:5925:"<p>If WordPress were a country, our Bill of Rights would be <a href="http://wordpress.org/about/gpl/">the GPL</a> because it <a href="http://www.gnu.org/philosophy/free-sw.html">protects our core freedoms</a>. We&#8217;ve always done our best to keep WordPress.org clean and only promote things that are completely compatible and legal with WordPress&#8217;s license. There have been some questions in the community about whether the GPL applies to themes like we&#8217;ve always assumed. To help clarify this point, I reached out to the <a href="http://en.wikipedia.org/wiki/Software_Freedom_Law_Center">Software Freedom Law Center</a>, the world&#8217;s preeminent experts on the GPL, which spent time with WordPress&#8217;s code, community, and provided us with an official legal opinion. One sentence summary: PHP in WordPress themes must be GPL, artwork and CSS may be but are not required.</p>
<blockquote><p>Matt,</p>
<p>You asked the Software Freedom Law Center to clarify the status of themes as derivative works of WordPress, a content management software package written in PHP and licensed under version 2 of the GNU General Public License.</p>
<p>We examined release candidate 1 of WordPress 2.8, which you provided to us at http://wordpress.org/wordpress-2.8-RC1.tar.gz.  The &#8220;classic&#8221; and &#8220;default&#8221; themes included in that release candidate comprise various PHP and CSS files along with an optional directory of images.  The PHP files contain a mix of HTML markup and PHP calls to<br />
WordPress functions.  There is some programmatic logic in the PHP code, including loops and conditionals.</p>
<p>When WordPress is started, it executes various routines that prepare information for use by themes.  In normal use, control is then transferred via PHP&#8217;s include() function to HTML and PHP templates found in theme package files.  The PHP code in those template files relies on the earlier-prepared information to fill the templates for serving to the client.</p>
<p>On the basis of that version of WordPress, and considering those themes as if they had been added to WordPress by a third party, it is our opinion that the themes presented, and any that are substantially similar, contain elements that are derivative works of the WordPress software as well as elements that are potentially separate works. Specifically, the CSS files and material contained in the images directory of the &#8220;default&#8221; theme are works separate from the WordPress code.  On the other hand, the PHP and HTML code that is intermingled with and operated on by PHP the code derives from the WordPress code.</p>
<p>In the WordPress themes, CSS files and images exist purely as data to be served by a web server.  WordPress itself ignores these files[1]. The CSS and image files are simply read by the server as data and delivered verbatim to the user, avoiding the WordPress instance altogether.  The CSS and images could easily be used with a range of HTML documents and read and displayed by a variety of software having no relation to WordPress.  As such, these files are separate works from the WordPress code itself.</p>
<p>The PHP elements, taken together, are clearly derivative of WordPress code.  The template is loaded via the include() function.  Its contents are combined with the WordPress code in memory to be processed by PHP along with (and completely indistinguishable from) the rest of WordPress.  The PHP code consists largely of calls to WordPress functions and sparse, minimal logic to control which WordPress functions are accessed and how many times they will be called.  They are derivative of WordPress because every part of them is determined by the content of the WordPress functions they call.  As works of authorship, they are designed only to be combined with WordPress into a larger work.</p>
<p>HTML elements are intermingled with PHP in the two themes presented. These snippets of HTML interspersed with PHP throughout the theme PHP files together form a work whose form is highly dependent on the PHP and thus derivative of it.</p>
<p>In conclusion, the WordPress themes supplied contain elements that are derivative of WordPress&#8217;s copyrighted code.  These themes, being collections of distinct works (images, CSS files, PHP files), need not be GPL-licensed as a whole.  Rather, the PHP files are subject to the requirements of the GPL while the images and CSS are not.  Third-party developers of such themes may apply restrictive copyrights to these elements if they wish.</p>
<p>Finally, we note that it might be possible to design a valid WordPress theme that avoids the factors that subject it to WordPress&#8217;s copyright, but such a theme would have to forgo almost all the WordPress functionality that makes the software useful.</p>
<p>Sincerely,<br />
James Vasile<br />
Software Freedom Law Center</p>
<p>[1] There is one exception.  WordPress does reads CSS and image files to create previews of templates for the template selection portion of the administrative interface.  Even in that case, though, nothing in those files calls any WordPress functions, is treated as a command by PHP, or alters any other WordPress data structure.  These files are read as data and used to create an image and display a miniaturized version of a webpage to the user.</p></blockquote>
<p>Even though graphics and CSS aren&#8217;t <em>required</em> to be GPL legally, the lack thereof is pretty limiting. Can you imagine WordPress without any CSS or javascript? So as before, we will only promote and host things on WordPress.org that are 100% GPL <a href="http://en.wikipedia.org/wiki/License_compatibility">or compatible</a>. To celebrate a few folks creating 100% GPL themes and providing support and other services around them, <a href="http://wordpress.org/extend/themes/commercial/">we have a new page listing GPL commercially supported themes</a>.</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:"Fri, 07 Aug 2009 01:07:03 +0000";s:9:"generator";s:32:"http://wordpress.org/?v=2.9-rare";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";}}