This week, the first version of privacy tools was committed to trunk. It is planned to get them into WordPress 4.9.6.
- »Dev Chat Summary: April 4th«. The initial plans for 4.9.6 contain the »Try Gutenberg« prompt and GDPR related things.
- »Dev Chat Summary: April 11th (4.9.6 week 2)«.
- »Media Meeting Recap – April 5«.
- »PHP Meeting Recap – April 9th«.
- »GDPR Compliance Chat Recap – April 11«. The first version of privacy tools was committed into trunk.
- »Polyglots weekly summary / chat notes April 11, 2018«.
- »Invitation to translate the WordPress 15th Anniversary website«.
Theme review team
Changes in the theme review process
The theme review team decided to make big changes to the review process, that takes a few months for a theme currently, because of the small number of active reviewers and the large number of requirements to check for. »The change is based on moving burden from reviewer’s shoulder to theme author’s and making theme authors more responsible«, like Nilambar Sharma writes in his post »Changes in Theme Review Process«.
With that change, reviewers just need to check for the following issues (quoted from Nilambar’s post):
- Malicious or egregious stuff
- Content Creation
After the themes are live, they will be spot checked by moderators.
Legal Compliance Added to Guidelines
There is a new item »implying that a plugin can create, provide, automate, or guarantee legal compliance« at Guideline 9 of the plugin guidelines.
That means that plugins are not allowed to present itself as a solution for legal compliance, because »no plugin in and of itself can provide legal compliance«, like Mika Epstein writes in her article »Legal Compliance Added to Guidelines«. That should prevent plugins from giving users a false sense of security.
- »Automated Greeting in the #training Slack Channel«.
- »Slack Integration with the Team GitHub Account«.
- »Why Should Developers Choose WordPress?«.
- »24 HR – React and REST API Case Study for Expohouse«.
- »Marketing Team Meeting Notes – April 11, 2018«.