Requirements project March 23

Our next project meeting will be on Thursday at 19:00

Channel: #themereview

We have a few more short term fixes to discuss:

  • Child theme names
  • Theme URI and  footer credit links
  • Admin bar menu items
  • Screenshot

There is also one recommendation that perhaps should be removed:
Themes may optionally unregister core Widgets. This is allowed, but is it recommended?

As a reminder, we also have the Trello board.

 

Those who have time after the meeting are welcome to continue,  with the purpose of defining what a “Letting users decide” approach would be for the team. We need to define it before we can continue any productive discussion on the topic.

 

Child themes should not include the name of the parent theme.

Suggestion: Child themes may only use the parent theme name if both themes are made by the same author.

Suggestion 2: Remove it (again).

If the theme adds a footer credit link, there should only be one (link to WordPress.org does not count).

Suggestion: There can only be a single footer credit link, which is either the the Theme URI or Author URI (link to WordPress.org does not count).

Theme URI:

Using WordPress.org as theme URI is reserved for official themes.

This was brought up on slack this weekend:
“The purpose of the Theme URI is to point the user to a page specifically about the theme that we are hosting here on WordPress.org. That means that the majority of the info on that page should about the theme that we’re hosting.”
“Theme URI needs to be a) under a domain you control, not “wordpress.org”, and b) unique to the theme. Not unique to the theme and version number or anything else, just unique to the theme. ”

Themes are not allowed to add a menu item to the WordPress admin bar.

I believe this is used in practice but it is not currently listed on the requirement page. Is this something that we want to add or is it something that we would consider allowing?

The screenshot should be of the actual theme as it appears with default options, not a logo or mockup.

Suggestion: The screenshot should be of the theme, not a logo or mockup. The screenshot may optionally show plugins, settings and templates. The user should be able to make the theme look like the screenshot.

Agenda for 2017 March 7

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:

This week we do not have any topics so it will be more of an informal meeting this week.

Community Summit 2017

I have posted a comment the Community Summit post with the list of topics and list of people who could attend. If there is someone who thinks they could attend let me know and I will have a look to see if we can them too.

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.

Agenda for 2017 February 28

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:

Team Representatives

Matt has asked us to choose three representatives from the Theme Review Team to meet with him to discuss the future of the theme directory. He wants to make sure the tech changes for the plugin / theme directories are in line with what the moderation plans are.

We would like to suggest that @greenshady, @poena and @grapplerulrich would be the three representatives.

Let us know if there are any objections.

Community Summit 2017

In the last meeting we started to discuss topics for the community summit. A list of topics can be found below. The list of topics may change as we get nearer to the event.

  • How we improve the leadership of the TRT team? For example the forums team has one or two team reps and then moderators who have access to further moderations tools.
  • How can we encourage and enable more people to lead new projects?
  • What is the vision and goals of the team?
  • What is the future of the theme review team, can we change it to become the Theme Team and be more involved in theme related activities like improving the theme directory or the theme developers handbook?
  • A set of good slides on the introduction to theme reviewing that can be used for contributor days
  • Improving the documentation so that it is clearer and easier to understand
  • Work on improving the theme author and reviewer experience by analysing the whole theme review process.
  • Improving the review process and focus on quality and good codes
  • How we can encourage creative designs and how to stop more of copy themes which can just be child theme.
  • Future of the theme review theme and making it smoother and faster

Now the question is who should/can attend the community summit. Please post in the comments below if you can and would like to attend to the community summit. Not everyone can attend because of the size limit of the venue.

Current 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.

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.