[theme-reviewers] Core and a few other things

Jose Castaneda jomcastaneda at gmail.com
Tue May 13 21:36:32 UTC 2014


First of all to those reviewing themes: awesome, keep it up and huge thanks!

One thing I, personally, have noticed is that a few tickets haven't been
shown much love ( going on three weeks! )
#17850 <http:////themes.trac.wordpress.org/ticket/17850>
#18083 <http:////themes.trac.wordpress.org/ticket/18083>
#18143 <http:////themes.trac.wordpress.org/ticket/18143>
#18198 <http:////themes.trac.wordpress.org/ticket/18198>
#18212 <http:////themes.trac.wordpress.org/ticket/18212>
#18197 <http:////themes.trac.wordpress.org/ticket/18197>

I totally understand we can either get sidetracked, busy or sometimes
forget. If that happens don't hesitate to ask for help. We are all in this
together. Not going to lie I've been guilty of it myself at one point or
another.

I can't, and don't, speak for the admins but we can make things easier for
theme. As Chip posted on the blog: Making sure theme
passes<http://make.wordpress.org/themes/2014/04/07/how-to-ensure-your-ticket-passes-final-approval-audit/>
is
a great way to make sure that your review isn't reopened. If it happens,
learn from it. I know I have.

Now, for some things I find neat and feel we could be looking into:
1. WP-core
  a) metadata/api:
http://make.wordpress.org/core/2014/05/13/metadata-ui-api-status-update/
2. WP-UI
  a) front-end-editor:
http://make.wordpress.org/ui/2014/04/23/font-end-editor-meeting-22-april/
  b) media-grid: http://make.wordpress.org/ui/2014/05/09/media-grid-update/
3. 4.0 cycle underway
  If you aren't using version control: where have you been?? or, I guess,
you could use the beta-tester plugin. :) but yes, make sure you are testing
at least on release candidates.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.wordpress.org/pipermail/theme-reviewers/attachments/20140513/91328e2e/attachment.html>


More information about the theme-reviewers mailing list