Meeting Notes for Tuesday 15th October 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

In the past seven days:

  • 238 tickets were opened
  • 233 tickets were closed:
    • 208 tickets were made live
      • 3 new Themes were made live
      • 205 Theme updates were made live
      • 0 more were approved but are waiting to be made live
    • 15 tickets were not-approved
    • 0 tickets were closed-newer-version-uploaded

Handbook update regarding child themes

The current handbook is not presenting the recommended practices of how 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/. should handle loading the styles and overwriting the parent theme styles.

The argument is that child themes shouldn’t have to load the parent stylesheet using enqueue.
The handbook should explain the loading order and the non.overriding the stylesheet handle.

The proposal is to open up a google doc and make a draft of what would go to the handbook, this could then be discussed and added to the handbook.

Next review shindig planning

The last shindig had a low turnout, and there is a problem of having only one person doing it in one time zone. There was not much involvement from the community.

For now, we won’t continue with the monthly shindigs, unless people show more interest in it.

Featured page issue – proposals for solving it

During the last triage, there was a discussion regarding this ticket.
One proposal was to have a curated list of the themes featured for a certain amount of time.

A number of issues were discussed:

  • What are the criteria based on which the themes will be chosen?
  • How often will the themes be on the popular page?
  • Who will choose the themes?

We’ll need to come up with the rules regarding the featured themes (minimal upsell, unique design, good coding practices).

The TRT representatives will try to see if they can get an initial proposal regarding the featured page, the post will be made on the make page and we can continue discussing the details there, and finalize the discussion on the next meeting.

Other news

Next triage will be held on Wednesday October 23rd, 17:00 UTC

#meeting, #meeting-notes, #trt

Theme Review Team Meeting Agenda for October 15, 2019

Theme review team (TRT) conducts a meeting on the second and fourth Tuesday of the month. Along with the fixed agendas, we have open floor meeting at the end where you can ask or share anything related to themes.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, 15th October 2019, 17:00 UTC

Meeting Agenda

  1. Weekly Updates
  2. Handbook update regarding child themes (link to issue)
  3. Next review shindig planning
  4. Featured page issue – proposals for solving it
  5. Open floor

Meetings usually last around 60 minutes.

The discussion about the meeting agenda can be held in the comments below. You are encouraged to propose the topic for the agenda.

#meeting, #trt

Meeting Notes for Tuesday 24th September 2019

Theme review team holds twice-monthly meetings. All members are encouraged to attend and new faces are welcomed.

This meeting we had an announcement about a new team structure as well as discussions about the future and the team’s purpose, according to 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).

New Team Structure:

Team no longer has leads – the team now has respresentatives and it is a flat team structure with loosely defined roles and responsibilities where individuals can contribute in ways that they feel strongly about.

More about that in this post: New Theme Review Team Structure

Ticket Graph:

You can see the latest stats and the graph on the themes trac system.

In the past 7 days

  • 304 tickets were opened
  • 301 tickets were closed:
    • 291 tickets were made live
      • 12 new Themes were made live
      • 279 Theme updates were made live
      • 4 more were approved but are waiting to be made live
      • 10 tickets were not-approved
  • 0 tickets were closed-newer-version-uploaded

Update on Twenty Twenty

the single post mockup of the twenty twenty theme

The latest default theme Twenty Twenty Theme was ready to roll into the betaBeta A pre-release of software that is given out to a large group of users to trial under real conditions. Beta versions have gone through alpha testing in-house and are generally fairly close in look, feel and function to the final product; however, design changes often occur as part of the process. package and is now confirmed as on track for releaseRelease A release is the distribution of the final version of an application. A software release may be either public or private and generally constitutes the initial or new generation of a new or upgraded application. A release is preceded by the distribution of alpha and then beta versions of the software. in 5.3.

Lots of contributors as you can see on this trac ticket. Big thank you to everyone mentioned in the props.

Uncommon Theme Queue Issues:

@acosmin mentioned there has been an issue with mistaken theme uploads lately. We need to investigate this further, but a trac ticket was opened that seeks to solve this issue.

Review Shindig:

There was a discussion on when the shindig would happen. A weekend event with a focus on Saturday was proposed. Potentially 1st Saturday of the month. No fixed date was decided on.

The point of the shindig is to share review tips and review themes together. It can take place in the #theme-review 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/. channel with optionally a voice/video call if people are interested in that.

You are encouraged to leave comments below if you missed the meeting.

#meeting, #meeting-notes, #trt

Theme Review Team Meeting Agenda for September 24, 2019

Like the previous meetings, we have some fixed agenda on this meeting as well. Theme review team (TRT) conducts a meeting on the second and fourth Tuesday of the month. Along with the fixed agendas, we have open floor meeting at the end where you can ask or share anything related to themes.

We encourage all members and anyone interested to attend.

Channel: #themereview | Time: Tuesday, 24th September 2019, 17:00 UTC

Agenda for the Meeting

  1. Weekly Updates
  2. Team Representatives – announcement of the new Team Representatives
  3. Review shindig date
  4. Open floor

In the previous meeting, we asked the attendees to nominate or show their interest in being a representative. We have gotten a few names for the nominees.
Below are the names of the positions that the new representatives would have.
Please comment below and show your interest in the role. We want to announce the final names at this meeting.

Representative role names

Theme packages representative
Automation representative
Theme review representative
Theme handbook representative
Communications representative

Each of the representatives has a certain skill set and experience that fits their roles, but they will work as a team on reaching the decisions that are agreed on the meetings with the entire team.
Representatives are the final deciding body – this is needed so that the progress can be made in the TRT.


We want more TRT members to join us and show their interest.

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 #meeting#trt

#meeting, #trt

Meeting notes from September 10th, 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

In the past seven days:

  • 399 tickets were opened
  • 374 tickets were closed:
    • 357 tickets were made live
      • 7 new Themes were made live
      • 350 Theme updates were made live
      • 5 more were approved but are waiting to be made live
    • 17 tickets were not-approved
    • 0 tickets were closed-newer-version-uploaded

Proposal: Revive monthly review shindigs

@djrmom Suggested that we revive the monthly review shindigs (https://make.wordpress.org/themes/2016/12/05/december-shindig-recap/)

For those who don’t know:

Every first weekend of the month we do a queue push where we try to review as many themes as we can. Please keep in mind that it is not just about numbers but we want to focus on quality reviews as well so don’t feel like you have to do 10 themes over the weekend.

Jose Castaneda (https://make.wordpress.org/themes/2016/11/04/november-review-shindig/)

It was agreed that we should schedule it, and see how it works.

Plan for the next team leads

@joyously wanted to know when was the last time since new leads were elected. Current team lead @williampatton had an announcement that we’ll share here

I have been acting as lead and dealing with various duties for a long time. An awful lot longer than I ever expected.

This month marks the 18 month point. Originally the intention was that a term should last 6 months only.

With uncertainty about what GutenbergGutenberg The Gutenberg project is the new Editor Interface for WordPress. The editor improves the process and experience of creating new content, making writing rich content much simpler. It uses ‘blocks’ to add richness rather than shortcodes, custom HTML etc. https://wordpress.org/gutenberg/ would hold and the future for themes I felt lead transitions would be highly disruptive and I wanted to avoid that. Perhaps it was not my place to make such a decision however I have done what I thought best at all times.

There will never be a perfect time to do lead transitions and with that being said: now is as good a time as any.

Please think about who you want to be leading TRT going forward and decide how best to guide them the direction the Team wants to go in. As is always the case I am available through transition to assist where that may be needed or useful. I’m not going anywhere, just stepping aside to let someone else have their turn.

Let’s try to have the transition process underway by the end of this month at the latest.

For me now is the right time for 2 reasons.

1. First and foremost it is time for someone else to have a turn at this. Being a team lead has been an incredibly rewarding experience which has allowed me to grow as a developer and feel like a very welcome part of our amazing WordPress community. Someone else deserves to be able to have that experience as well.
2. Secondly, I cannot guarantee availability as-and-when needed in the same way that I used to be able to. The more limited time I have here I want to be able to spend on things other than admin or management tasks. I have projects in mind I want to pursue but have not had the time to do it.

William Patton

It was proposed that an election for the new position is held. Anybody that is interested should directly message @kafleg, he will consult with the senior and key reviewers and will try to sort out the list of names for the election.

William mentioned that he would like to have a Theme Review Team reps instead of leads.
There are many people here with lots of various skills but have issues with the time commitment. Nobody really has a guarantee on how much time they can manage.

@poena mentioned that reps should be people who know what they do best and do that.

In the end, it was decided that a list of possible rep roles will be made and proposed rep leads in those areas.

Some questions remained unanswered and will be covered in the next meeting, such as a decision about ‘starter themes’ in the repo, impact of skip links and keyboard navigation requirements and the existing themes in the repo.

Triage meeting reminder

And in the end a small reminder about the Theme Review Triage meeting that will be held tomorrow.

#meeting, #meeting-notes, #trt