Meeting notes We had a meeting today and…

Meeting notes

We had a meeting today and the archive is here: https://wordpress.slack.com/archives/themereview/p1433872742007643

Here are the summary points:

We are changing to have twice weekly meetings until we work through the backlog of issues and changes. This drops the tracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. meeting and sidebarSidebar A sidebar in WordPress is referred to a widget-ready area used by WordPress themes to display information that is not a part of the main content. It is not always a vertical column on the side. It can be a horizontal rectangle below or above the content area, footer, header, or any where in the theme. widgets have been updated to reflect this.
We talked about what would be the baseline for tests to allow themes to just go live.
Any themes auto made live would not include those with the 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) tag. These have to be checked by a human currently.
Surveys are up and happening. Will do a small update insight next week and in few weeks have a fuller summary report.
@grapplerulrich is going to start a post about the theme check and what we need to add to be the baseline. Keeping in mind the baseline not all or most requirements. Security we all agreed is a key there.
I am going to do two posts to outline a suggested flow for automatic upload and also GLP agreement ideas and discussion.
Next queue push day is 27th June. Some of us may be doing this on the 28th as at WCEU. To that point, I will be there with others and happy to meet up and chat outside of contribution day. Just let me know if anyone wants to chat and we can even grab coffee.

Next meeting is Thursday 18:00 UTC in 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/. #themereview

ShinichiN 2:37 am on June 10, 2015

Hi, thank you for the meeting notes.

I thought some flags for the Theme authors might work.

1) “Authorized” flag
Authors get marked as “authorized” if they have passed human review in the past and they go live directly after automatic machine review.

2) “Reported” flag
Authors get marked as “reported” if they get the “report” clicked and cleared away from the repository by reviewers or admins. Their theme goes to the queue and won’t go to live unless all their reported themes get approved.

3) “New” flag
This is for authors who have not marked “authorized” or “reported”. It’s neutral. If a new theme author uploads a theme, it goes live without human review. If they want to get rid of the new badge, they need to ask for human review.

The point is that the system doesn’t flag the themes but the authors.

This is like how people build their reputation on airbnb website, for example, where people try to be polite, quick and welcoming as much as possible. The aim of these flags is to encourage theme authors to build their reputation. We can highlight the authorized theme, list them higher in the search result and show explicitly on detail pages like “passing” badges in GithubGitHub GitHub is a website that offers online implementation of git repositories that can easily be shared, copied and modified by other developers. Public repositories are free to host, private repositories require a paid subscription. GitHub introduced the concept of the ‘pull request’ where code changes done in branches by contributors can be reviewed and discussed before being merged be the repository owner. https://github.com/.

What do you think?
- Tammie 2:42 pm on June 10, 2015
  
  I think the flags will happen by the queues. I’m sort of keen we don’t complicate this at this stage. I think having flags and associations can do this. I also am not sure new means they have any less good standing. I think if we do this we do it for all no matter what status. Actually it’s been proven even longer themers make mistakes and sometimes the newer are more up on the requirements.
  
  I think reputation will have a part but without flags and penalties that are so public. We have thought about how this could work in the theme directory. But, we are holding off on a lot of that until we get user research – which is happening.
  
  I am not keen we have tiered systems in the example I’m talking, we are thinking of just trying something globally as a starting point.
progmastery 9:18 am on June 10, 2015

Yes, definitely, people downloading themes should be able to see how many times the theme has been reported and for what reason. The reputation of an author is also a single parameter that can greatly help when deciding whether to download their theme or not. This changes will make authors pay more attention to the theme review guidelines, even if not all of them are checked manually by TRT.

I would also suggest to add Authors list to https://wordpress.org/themes/, sorted by weighted rating.
The rating can include ratings of themes by the author, penalty because of been reported, the popularity of themes (e.g. downloads per month per theme ).

TRT can effectively moderate the reports and serious issues, while spending less time to theme review itself.
WP.org theme repository can be mainly community regulated.
- Tammie 2:42 pm on June 10, 2015
  
  This is skipping a bit into the theme directory, the goal here is to focus on the review process not that yet. We will be looking at that based on survey and user research.

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

Meeting notes We had a meeting today and…

Meeting notes

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication

Meeting notes

Share this: