By the way: <a href="http://wpdevel.wordpress.com/version-3-1-project-schedule/">WP 3.1 beta is scheduled for November 15th</a>, so we really need to hit version-specific changes hard in our next meeting.<div><br></div><div>
Chip<br><br><div class="gmail_quote">On Fri, Nov 5, 2010 at 1:39 PM, Chip Bennett <span dir="ltr"><<a href="mailto:chip@chipbennett.net">chip@chipbennett.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><br></div><div>By the way, here's the <a href="http://codex.wordpress.org/Version_3.1" target="_blank">master list of major 3.1 changes</a>. Anything else in there we should be considering?</div><div><br></div><div>
As for other Guidelines changes for 3.1, I would add the following proposals:</div>
<div><br></div><div>1) Everything currently marked as "draft" in the Guidelines</div><div>2) Use of "License"/"License URI" header tags increases in criticality from *recommended* to *required*</div>
<div>3) Use of TimThumb prohibited (*required* not to use, even for backward compatibility). If we go this route, I will volunteer to put together a tutorial for how to migrate TimThumb-generated images using custom fields over to the WordPress media manager. </div>
<div><br></div><div>Additional changes to the Theme Review Codex page: </div><div><br></div><div>1) Once we are up and running on our WPORG site, I propose that we move all non-Guideline information (e.g. Process, Scope, How to Become a Theme Reviewer) over to the WPORG site. (Perhaps leave the "Resources" section, as it has links to various Theme check/validation tools.)</div>
<div>2) Re-write the Guidelines so that we have a condensed list of the Guidelines in principle, with intra-page links to expanded/detailed information about each Guideline (as per the mail-list discussion from a couple weeks ago).</div>
<div><br></div><div>Anything else?</div><div><br></div><div>Just as an FYI: WP 3.1 is scheduled for a December release, so we need to get any version-specific Guidelines revisions up as soon as possible. I would want to shoot for having the version-specific changes published at or around the time of the first beta release of 3.1.</div>
<div><br></div><div><font color="#888888">Chip</font></div></blockquote></div></div>