Agenda for 2017 February 21

The Theme Review Team holds a meeting weekly and we encourage all members to attend.

Channel: #themereview | Time: Tuesday at 18:00 UTC 18:00 UTC

Topics:

Community Summit 2017

@grapplerulrich wrote a post about it. We need to decide on topics that we want to discuss and who is able to attend.

It would be also good to discuss how we can keep people who are unable to attend informed and allow them voice their ideas and opinions but at the same time allowing the people attending the community summit to make decisions so to that changes can happen quickly.

Mentoring program

@thinkupthemes is leading the new mentoring program. Checkout the blog post https://make.wordpress.org/themes/2017/02/11/mentor-program-2017/

We are also collecting questions for a frequently asked questions page. https://make.wordpress.org/themes/2017/02/08/starting-a-frequently-asked-questions-page/

Projects page

As not everyone knows this we have a projects page with projects that we are working on and projects that we want to work on but need people to help out with them. https://make.wordpress.org/themes/handbook/get-involved/projects/

If you have any topics, then please reply to this post and include the topic, along with a brief description of what you would like to discuss.

Automation Meeting February 16

The last meeting was on December 22, where we discussed

  • @miyauchi was working on BDD (behavior-driven development) based review system.
    https://github.com/miya0001/wp-themeception
  • @rabmalin developed a plugin to run the PHPCS checks in WordPress https://github.com/ernilambar/ns-theme-check
  • @jrf was nearly ready to start pulling the utility functions to WPCS.
  • @jrf proposed that we start add PHP Compatibility testing and define which PHP version themes should support. In a previous TRT meeting we decided that all themes should support PHP7.
  • @grapplerulrich asked for feedback on which JavaScript functions to restricted and which parameters in PHP functions to not allow.

Channel: #themereview | Time: Thursday at 14:00 UTC 14:00 UTC

The agenda for the 16th February will be

  • Short update from the contributors what they have worked on.
  • Define goals for the next meeting.
  • Discuss any open issues and/or pull requests that need attention.

We need help with the following items.

If you are interested in writing sniffs, please DM me on Slack with an issue that you would like to work on and I can help you get started and answer any questions.

Pinging @frankklein, @jrf, @shinichin, @miyauchi, @iamdmitrymayorov, @jmichaelward, @marius2012, @djrmom, @rabmalin

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

Automation Meeting December 22

The last meeting was on November 10, which was a short meeting and there was a bit of confusion about the time change.

As I was unwell one time and recovering from travel we have not had any meetings.

The next one will be December 22. We will be keeping the time at 14:00 UTC as not every country changes their clocks and this UTC time works for everyone.

Channel: #themereview | Time: Thursday at 14:00 UTC 14:00 UTC

The agenda for the 22th December will be

  • Short update from the contributors what they have worked on.
  • Define goals for the next meeting.
  • Discuss any open issues and/or pull requests that need attention.

We need help with the following items.

If you want to to test out the current WordPress-Theme sniff you need to download it from our fork. https://github.com/WPTRT/WordPress-Coding-Standards

There is documentation how you can integrate it with your favourite IDE.

If you are interested in writing sniffs, please DM me on Slack with an issue that you would like to work on and I can help you get started and answer any questions.

Pinging @poena, @frankklein, @jrf, @shinichin, @miyauchi, @iamdmitrymayorov, @jmichaelward, @marius2012, @djrmom

If I have missed any usernames, it’s not on purpose and do consider yourself invited to the meeting.

December 6 meeting notes

Topics discussed

  • Finalize upsell
    • clarify that authors need to use the customizer api to add the upsell
    • Themes should not display obtrusive up-selling
  • demo and starter content requirements.
    • define what placeholder content is
      • Anything that is shown that you cannot pull from the user’s install ( 10 thumbsup )
    • Capability check
    • starter content
      • must use core
      • exception is: images ( 9 thumbsup )
  • Review Shindig
    • January 7-8
    • Livestream focus: tools

A Slack account is needed to view the archives.

December shindig recap

Stats

  • Tickets modified: 108
  • Themes made live: 10
  • Tickets closed: 21

Livestream

Link to video: https://youtu.be/HW4dP0ikNmQ

Thanks

The following is a list of people who modified a ticket over the weekend

@Alessandro-Vecchiato, @Bdur604, @DannyCooper, @Diwashc, @Fortisthemes, @Kuuak, @ShinichiN, @Thomas-Vitale, @Vala-bhavesh, @WPDevHQ, @acalfieri, @acosmin, @bplv, @catchthemes, @codexdemon, @cristian-ungureanu, @cristiano.zanca, @djrmom, @eazyee, @einsteinsboi, @emilysparkle, @emy1982, @f46vib, @firdaus666, @gmosso, @greenshady, @hardeepasrani, @ionutn, @jbobich, @juhise, @kafleg, @katmoody, @kharisblank, @lanche86, @lyrathemes, @megane9988, @meissudeep, @melsorrells, @miiitaka, @no1theme, @pallavihb, @parselearn, @poena, @ponvendhan, @pratikshrestha, @pressionate, @pypwalters, @rabmalin, @rinkuyadav999, @rodicaelena, @rohitink, @ryancanhelpyou, @sakinshrestha, @seufelipe, @strangerstudios, @svinqvmraka, @swetashrestha, @thinkupthemes, @wenthemes

WCUS Contributor Day

Contributor day also took place on Sunday during WCUS. @grapplerulrich started the day off with an excellent presentation on the theme review process and the guidelines. About 20 reviewers worked on reviews in person together while another group worked on our automation project.