We have nothing new to add to the known issues for 4.7 this week.
Supporting Themes from Jetpack
There was some confusion around how to support the themes installed by Jetpack. Quoting Support Team member and Automattic Theme Whisperer @zoonini:
1. vast majority of those themes already in the .org repo
2. small number of themes either waiting in the review queue or not yet submitted (due to one theme in queue rule)
3. small number of themes forked but not different enough to submit back to .org
if you see any in categories #2 or #3, please just add “wpcom-theme” tag and I or one of my colleagues will be happy to reply if it’s not something you’d like to handle
And, of course, if it’s a theme covered by category The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. #1, just direct them to the specific theme’s support forum WordPress Support Forums is a place to go for help and conversations around using WordPress. Also the place to go to report issues that are caused by errors with the WordPress code and implementations. on WordPress.org The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. https://wordpress.org/, just like any other theme in the official directory.
Theme Installation Confusion
Speaking of themes, we’re noticing an increase in folks mistaking the theme directory’s Upload Your Theme section for a way to install themes on their own site. For now, here’s a predef you can try:
https://wordpress.org/themes/getting-started/ is for developers to share the themes they make with the entire WordPress community.
To install themes on your site, follow this guide: https://codex.wordpress.org/Using_Themes#Adding_New_Themes
Additionally, please DM @jcastaneda in Slack with links to any reports of the confusion so the Theme Review Team can find the best way to improve the situation.
We held the final courtesy “Is this still what we want?” vote regarding the decision to change the meeting time from the March 9 meeting. Holding the meeting at 16:00 UTC continued to receive majority support, so the meeting time will continue as-is, meaning that the next meeting will be Thursday, April 6, 2017, 16:00 UTC.
This was the final vote, so the meeting time will not be changed again until most of us switch back to Standard Time, or some other situation arises that would necessitate changing the meeting’s time.
Checkin with International Support Liaisons
@macmanx @bcworkz @clorith @geost @jdembowski @t-p @bdbrown @kmessinger @zoonini @alchymyth @sterndata @contentiskey @sergeybiryukov @sage-chara @jcastaneda @lukecavanagh @bethannon1 @georgestephanis @kenshino @stephencottontail @abletec @fierevere @imazed @hardeepasrani @otto42 attended
Read the meeting transcript in the Slack archives. (A Slack account is required)