Meeting notes from August 13th, 2019

A meeting was held with the proposed agenda.

The following is the recap of the meeting, you can read the meeting transcript in the slack archives (a Slack account is required).

Weekly Updates

Some authors asked their themes to be closed, which was done. If you need your existing tickets closed you can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” the leads.

In the past seven days:

  • 246 tickets were opened
  • 233 tickets were closed
  • 103 new tickets are waiting for review
  • 4 tickets are older than 4 weeks
  • 53 tickets are older than 2 weeks
  • 76 tickets are older than 1 week
  • 97 tickets are older than 3 days

Trusted Authors (TA) announcement

From today, the TA program is closed.

The program did not fulfil the intended plan and has ultimately caused more problems than solving.

Some reasons for removal of the program include:

  • Entry criteria was difficult to set, it was hard to maintain consistency.
  • Management of the queue required separate reports in tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. to be modified via SQL – that was unsustainable.
  • Being TA has benefits unavailable for other authors – how fair this is for everyone has been commented on a loads of times. 

The leads will make a blog post describing the reasoning behind removal of the TA program.

Open floor

A discussion was held about the removal of the TA. One issue that came up during the discussion, was the fairness of the admin queue. And of the review process in general, since some authors may get an experienced reviewer, and others may get a novice reviewer, which will require another inspection to see if they did a good job.

There were proposals to fix these issues, such as pairing new with experienced reviewers.

#meeting, #meeting-notes, #trt

Theme Review Team Meeting Agenda for August 13, 2019

Theme review team conducts a meeting on the second and fourth Tuesday of the month. We usually have fixed agendas for the fourth Tuesday meeting. But we have some agenda to discuss on this second Tuesday as well.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, 13th August 2019, 17:00 UTC

Agenda for Discussion

  1. Weekly Updates
  2. Announcement from team leads about the trusted authors (TA) status
  3. Open floor.

Meetings usually last around 60 minutes. If anyone wants anything else to add on the existing agenda comment below and we will try to fit it in.

Discussion can be held in the comments below.

#agenda

#agenda

Trusted Authors Program

We have an exciting announcement to make, we’ve decided to make things easier for you, the authors, by putting together a Trusted Authors Program. Eventually, it will lower the burden on reviewers/leads and we will have more time for other interesting programs. After a few days of brainstorming, here is what we have.

The Trusted Authors Program is an attempt to streamline the review process for authors who are consistently able to show they can to produce high quality code and themes that are in line with the current guidelines.

You should know from the start that applications for the Trusted Authors program and its queue will be handled only by team leads.

To apply to this program, you will need to select the ticket you want us to take into consideration:

  • It can be your latest approved (live) theme (not an update ticket)
  • Ticket in the New or Final Queue.

After that you can post your application in the comments, using this format (make sure you read the entire article carefully before you apply):

User: greenshady Ticket: https://themes.trac.wordpress.org/ticket/35636

The leads will make sure to take a note and contact you if your application is accepted or not.

The ticket you’re applying with must have the following characteristics:  

  1. Escaping/Sanitization – maximum of 3 issues.
  2. Licensing – maximum of 3 issues and you need to be 100% GPLGPL GPL is an acronym for GNU Public License. It is the standard license WordPress uses for Open Source licensing https://wordpress.org/about/license/. The GPL is a ‘copyleft’ license https://www.gnu.org/licenses/copyleft.en.html. This means that derivative work can only be distributed under the same license terms. This is in distinction to permissive free software licenses, of which the BSD license and the MIT License are widely used examples., all your products, either on your website or 3rd party sites.
  3. Content creation – none spotted, this also includes correct use of demo content.
  4. Malicious or egregious stuff – no PHPPHP PHP (recursive acronym for PHP: Hypertext Preprocessor) is a widely-used open source general-purpose scripting language that is especially suited for web development and can be embedded into HTML. http://php.net/manual/en/intro-whatis.php./JS or any types of errors, no pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the WordPress.org Plugin Directory https://wordpress.org/plugins/ or can be cost-based plugin from a third-party territory functionality. Correct use of prefixing, enqueue, translations, advertising.

As an author, you also need to know that:

  • You can submit a theme once a week (1 week). Please consider that authors in the New queue have to wait for a review and they are also limited to 1 theme/30 days.
  • You must have at least 2 live themes in the directory to be considered.
  • You can’t apply with a child themeChild theme A Child Theme is a customized theme based upon a Parent Theme. It’s considered best practice to create a child theme if you want to modify the CSS of your theme. https://developer.wordpress.org/themes/advanced-topics/child-themes/., just parent themes.
  • This privilege is not transferable,
  • Themes approved through this program cannot be transferred to other accounts for a minimum of 6 months.
  • AccessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) ready themes are filtered out of the TA queue. They’ll need a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) reviews.
  • You can only upload one theme per week if you are a trusted author, no matter how many theme author accounts you are affiliated with. Doing otherwise or getting caught will result in a permanent ban from TA and all themes removed for all users involved.

Consequences of not following the rules:

  1. Content creation, licensing issues result in 1 week suspensions without warning and removal from the program. You’ll need to fix the theme, suspension won’t be lifted until you do so.  You’ll be able to re-apply for the program after 3 months from the date when the theme is reinstated.
  2. Any type of hacks, malware, attract a permanent ban and removal of all your themes. (unless you were hacked and can provide hard proof for that).
  3. The other rules result in a warning, a period of 7 days to fix those issues, otherwise point 1’s consequences apply.
  4. We’ll not take into consideration active installs counts, how old a theme is or your financial distress. Suspensions will be applied without hesitation.
  5. Two strikes will result in removal from the program. You will not be allowed to re-apply to the program for a minimum of 4 months. Timescales may be decided on a case by case basis deepening on severity.

We would like to keep things civilized. All complaints are addressed in ticket, don’t call out people on SlackSlack Slack is a Collaborative Group Chat Platform https://slack.com/. The WordPress community has its own Slack Channel at https://make.wordpress.org/chat/.. You can pingPing The act of sending a very small amount of data to an end point. Ping is used in computer science to illicit a response from a target server to test it’s connection. Ping is also a term used by Slack users to @ someone or send them a direct message (DM). Users might say something along the lines of “Ping me when the meeting starts.” any of the team leads if you have any concerns.

Please do not take advantage of being a trusted author. Post reviews will be done at random to ensure the program is not being abused. If we find the program is being abused, any abusive authors will be removed without notice.


✌

Meeting notes from July 23rd, 2019

A meeting was held with the proposed agenda.

The following is the recap of the meeting, you can read the meeting transcript in the slack archives (a Slack account is required).

Updates

We got positive and supportive feedback about the skip links (accessibilityAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility)). Even though it is simple to implement, the authors were confused. But we have a post explaining what they are and how to implement them.

Authors are starting to change the admin notices, according to the guidelines.

Promoting other themes from within popular themes isn’t allowed. Few authors were caught doing this and they changed it upon request. Ignoring the request to remove the promotions will result in theme suspension.

After meeting with the documentation team, @acalfieri was selected as a representative from the Theme review team to update the theme developer handbook.

A new version of Theme Sniffer and WPThemeReview coding standards was released.

In the past seven days:

  • 449 tickets were opened
  • 463 tickets were closed
  • 416 tickets were set live
  • 25 new Themes were set live
  • 391 Theme updates were set live
  • 10 more were approved but are waiting to be set live
  • 39 tickets were not-approved
  • 8 tickets were closed-newer-version-uploaded

An automatic way of notifying theme authors

It was proposed that all the theme authors get automatically subscribed to the TRT blog so that they can be made aware of the announcements when they are made.

Another proposal was to send mass emails to all theme authors to make sure their themes are compliant with the newest requirements. Those whose email bounced would get suspended or changed to reviewing status.

An agreement was not reached. It was agreed that the TRT will reach out to other teams so that we can see how they are dealing with this issue, and if this can be solved on a more global basis.

Looking for good examples of keyboard navigation

A team needs a good example for keyboard navigation, especially for menus, so that we can provide an example for theme authors, as this is going to be the next a11yAccessibility Accessibility (commonly shortened to a11y) refers to the design of products, devices, services, or environments for people with disabilities. The concept of accessible design ensures both “direct access” (i.e. unassisted) and “indirect access” meaning compatibility with a person’s assistive technology (for example, computer screen readers). (https://en.wikipedia.org/wiki/Accessibility) measure that will be implemented.

Currently, we don’t have an agreement to what is the best way to move forward with this so any contribution is welcomed.

Open floor discussion

The feature packages project needs active contributors, so if you are interested in contributing to the TRT open-source projects check out the official TRT Github repository.

#meeting, #meeting-notes, #trt

Theme Review Team Meeting Agenda for July 23, 2019

Theme review team conducts a meeting on the second and fourth Tuesday of the month. We usually have fixed agendas for the fourth Tuesday meeting.

We have several topics to discuss. Hence, we encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, 09th July 2019, 17:00 UTC

Agenda for Discussion

  1. Weekly Updates
  2. Creating a mailing list, so that we can send information about requirement changes to all theme authors not only those who have open tickets.
  3. Looking for good examples of keyboard navigation.
  4. Open Floor

Meetings usually last around 60 minutes. If anyone wants anything else to add on the existing agenda comment below and we will try to fit it in.

Discussion can be held in the comments below.

#agenda