Weekly meeting notes
Our meeting archive is here: https://wordpress.slack.com/archives/themereview/p1415120399001516
Housekeeping:
1. The Twenty Fifteen chat is still happening on 15:30 UTC on Tuesdays, it happened earlier. It is still not released so be great to get reviewers helping there. The chats are in #core-themes.
2. I am in the process of refactoring the guidelines and handbook based on what was posted on make.blog. The idea is we make this have a better UX UX is an acronym for User Experience - the way the user uses the UI. Think ‘what they are doing’ and less about how they do it. and structure for all. It’s got a bit ‘unweildy’. For now, I am working on the structure. Whilst I do this for the next week anyone that has permissions to edit please do not change things yet. I won’t be removing anything or adding anything new, new pages will be created none deleted so we can merge if needed. My goal is to simply refactor the structure as outlined add add the required and recommended. I expect this all to be done by a week tomorrow.
3. As many of you know there have been a flurry of posts from some our time at SF. We not only attended the WordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. and summit, but we also got to for 2 days sit around a table and discuss the world of theme reviews. I know for me and I think for others around the table this was a valuable experience. For those unable to attend, I have put up all the notes and will be double checking to ensure you have all of them. I’m excited what we can create now with this in place.
General topics:
1. From this next week the meetings all move and stay at 18:00 UTC.
2. Lets hold off on feature themes as this will be automated by end of next week – yay!
We went through each guideline in contest and revised the language and content:
- [ New guideline ] 1 Unique slug – as the themeslug appears in style.css. If it uses a framework then no more than 2 unique slugs.
- No hard coding of scripts, styles and favicons unless a browser workaround.
- No minification of scripts or files unless provide original files
- Themes can use any language for front facing text. However, they should only use the same one for all text.
- Themes should use either the Settings API An API or Application Programming Interface is a software intermediary that allows programs to interact with each other and share data in limited, clearly defined ways. or the Customizer Tool built into WordPress core that hooks into most modern themes. You can use it to preview and modify many of your site’s appearance settings. for implementing theme options.
Additional:
- 7 days is how long inactivity before we close or re-assign a ticket. This will be a rule all work to. You can at least comment to say will get to it, communication in tickets is important and we should do more.
Meetings:
- Monthly google hang out to see everyone – open topic
- Regular queue scrub together
Queues:
- We are removing queues to only 2 – updates and new. @emiluzelac is going to adjust the queues.
