I obviously won’t be able to go into detail about their pay but the basics aren’t really a secret. The majority of our Review team is remote and located all over the world, a large percentage having come from being authors, and work as independent contractors on an hourly rate.
I just wanted to quickly pop in and say thanks for your feedback and questions for additional clarification in so many places. We’re capturing this feedback and will be discussing it with the team and clarifying further as soon as we can.
A big thanks to Japh, our WordPress Evangelist, for doing a smashing job answering questions here until late into the night and providing really fantastic assistance in getting this update out as soon as we could. Now that it’s late for Japh and I, we’ll be getting some sleep and will catch up with this thread first thing in the morning.
In the mean time, Sid, our Review Projects Lead and CodeCanyon Senior Reviewer, will be available for awhile longer to answer questions.
We’ve just posted the updated submission requirements and made the announcement here: http://notes.envato.com/news/update-wordpress-theme-submission-requirements/
We’ve opened a new forum thread for further feedback and discussion here: http://themeforest.net/forums/thread/update-wordpress-theme-submission-requirements/103347
Thanks so much, everyone!
Last week we announced our newly published and recently updated WordPress theme submission requirements, which raised lots of valuable discussion over in the forum post. The insight everyone provided was valuable and greatly appreciated. It also reminded us that we need to be including more community input, from a wider group, from much earlier stages! Where you provided feedback and it was not taken on board, we also really apologise and hope the clarifications below address your concerns better this time.
The process also made it obvious that we hadn’t been communicating clearly enough at the launch of these submission requirements, which we’ll provide further clarification on here. We will continue working harder at improving our communications, especially from within the Review team and covering all other aspects of review.
[... Continue reading on Envato Notes ...]
I’m kinda wondering how the review process will go for all existing themes, if they don’t pass one of the req’s is that theme then soft-disabled until its fixed or are we notified with a grace period of lets say 5 days to remedy the problem and re-upload so we’re not losing out on sales. Especially for those of us like my self that have a massive portfolio of items and rely on TF as my sole full time income. Wouldn’t want to wake up one day and find 75% of my portfolio soft-disable over a column shortcode being included directly into the theme.
We definitely want to work with authors in advance to minimize any potential portfolio downtime (to none if at all possible). The specifics of how this particular project will need to run have yet to be determined but we’ll give everyone advanced notice before anything happens.
So existing themes will have a 6 months grace period. Wouldn’t that be an advantage?
So themes already released with tons of shortcodes and other features will clearly have a longer period to gain sales, over the new ones who will just have to see the impact of the new standard.
Why not use a 6 month grace period for all themes( released or future releases). Details:
Let’s say you get a start date like 1st of August 2013 and until 1st of February 2014 you will approve and also send notices to users to update to the future standard. So if an author releases a theme and it is approved but doesn’t meets the future standard you will send them notices to do that until 1st of February 2014.Therefore you are creating equal chances for everyone.
We’ll be posting more details for the revised timelines / plan (and are open to feedback) today via the Notes blog, so stay tuned for that.
Basically, we’ll be aiming for roughly November to start requiring some of the bigger changes to the submission requirements for new items submitted. This should allow everyone enough time to make adjustments to their theme development workflow without significantly disrupting anything.
Applying these requirements to existing themes is a big project by itself, so we won’t be able to do both of these at the same time (which would also be higher risk and impact to authors with large existing portfolios). We want to make sure we approach library re-reviews carefully and work closely with authors to ensure its a smooth transition.
designedbydash saidThanks for your patience, sorry it’s taking longer than expected. As Jarel, our review manager, posted a couple of days ago, we’re still pulling everything together for the update, but it really won’t be long now. I would imagine early this week.
I know Japh said it would be a few days, but just wondering if we have a more concrete date/time for the final confirmed requirements? It’s now starting to hold back the development of a new theme we’re working on as I don’t particularly want to do it one way, and then have to change it all to adhere to the new requirements.
Thanks for being patient while we work to clarify the requirements. We’re aiming for an update post by later today, but I’m also working to clarify a few other things with the review team which might delay the post until tomorrow. We’ll have more information soon!