Agenda for June 27

This weeks meeting is estimated to take longer than our usual 30 minutes since we have several topics.

Meeting times and agendas

Since we don’t have agendas each week and because people are not able to participate every week, the suggestion is to have two meetings a month: one with a set agenda, and one with an open floor.
The meetings are estimated to be one hour long, compared to the 30 minutes we have now.
We will try to document topics that come up often, maybe on the FAQ page or a dedicated meeting topics page.
If you want to lead a meeting please DM one of the Team Leads which dates you are available.
The two weeks per month when we don’t have meetings should be dedicated to working on our ongoing projects.
We would like to remind everyone to please stick to the topics so that we can have productive meetings.

Shindigs

Our next review shindig is on saturday july 8.

Two themes rule

We suggest allowing authors to have two themes in the queue, up from one. This should then be evaluated after one month.

WordCampWordCamp WordCamps are casual, locally-organized conferences covering everything related to WordPress. They're one of the places where the WordPress community comes together to teach one another what they’ve learned throughout the year and share the joy. Learn more. Europe, community summit and contributor dayContributor Day Contributor Days are standalone days, frequently held before or after WordCamps but they can also happen at any time. They are events where people get together to work on various areas of https://make.wordpress.org/ There are many teams that people can participate in, each with a different focus. https://2017.us.wordcamp.org/contributor-day/ https://make.wordpress.org/support/handbook/getting-started/getting-started-at-a-contributor-day/. recap

New reviewer tool -TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. will be replaced
- Description of the current tool
Readme file will be parsed
No more queue
Reviewers will not be assigned to tickets
Tickets will not be closed just because there is no reply within 7 days
Tickets will not be closed because of code errors
Updates via SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/.

Discussion: What can we do now/short term?

Readme file and format will be required
- https://github.com/WPTRT/sample-theme-readme
Moderators can pick any open ticket ( responsibly )
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. disclaimer on the upload page
- Related ticket: https://meta.trac.wordpress.org/ticket/1513
- Related files: page-upload.php , page-getting-started.php, upload.php

Emil Uzelac 6:06 am on June 25, 2017

Great stuff!
Rinku Y 6:22 am on June 25, 2017

Let keep ‘one theme rule’, it allows theme author to submit new theme within 2-3 months otherwise authors will wait for 6-7 months (Past Problem). Anyway it helped and i think no need to modify.
- Carolina Nymark 11:45 am on June 25, 2017
  
  Yeah I sort of feel it is up to the authors. People have expressed that they want the rule gone, so it is up to them if they want a shorter queue or if they want to be able to submit more than one theme.
  There are authors who has several themes ready to be released, that are just sitting there waiting.
  
  Unfortunately, having a one theme per author rule opens up to abuse and trading of queue positions, that is what I personally want to avoid. It also means more administration.
  - kevinhaig 3:27 pm on June 25, 2017
    
    There are multiple themes submitted now by the same author. And I have pointed out other cases in the past. Nothing has been done.
    
    So really is a rule needed here? Just get rid of it 🙂
    - Carolina Nymark 8:24 am on June 26, 2017
      
      compromises 😉
    - Carolina Nymark 8:35 am on June 26, 2017
      
      And unless authors are trying to hide behind multiple usernames (which we can’t prove with certainty) , I can’t find any multiple theme submissions right now? ( I sorted the lists by reporter)
- Nilambar Sharma 9:53 am on June 26, 2017
  
  I am also big +1 on keeping the 1 theme limit, at least until our new system is live.
  - acosmin 10:31 am on June 26, 2017
    
    +1
Nilambar Sharma 7:58 am on June 25, 2017
- Since we are making theme’s system similar to 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, I strongly believe that, readme format would also have to same for both. Having different format will just create complexity.
- I like about 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. disclaimer in upload page. It is more like trusting author.
- Moderators can pick any open ticket ( responsibly ) – Even if we are trusting already “trusted reviewer”, there should be some restriction in this. Otherwise what may happen is that some author’s theme goes live frequently and other will be waiting for months.
- kevinhaig 3:30 pm on June 25, 2017
  
  I’m a little concerned about “moderators can pick any open ticket. There will without question be a number of “friendly you pat my back I’ll pat yours” reviews. Authors will be preferenced and others will be left without a review.
  - Nilambar Sharma 6:34 am on June 26, 2017
    
    This concerns me also. So, I believe we should add some restriction on that. Like, ticket could be allowed to take from only first page of queue. or whatever feasible
    - Carolina Nymark 6:47 am on June 26, 2017
      
      I like the suggestion about the first page.
      - acosmin 7:10 am on June 26, 2017
        
        that could work, so you would wait ~2-3 weeks. But please don’t take out the 1 theme rule
  - Ionut Neagu 11:31 am on June 26, 2017
    
    Hey,
    
    Moderators are humans and it will probably be some kind of “friendly you pat my back I’ll pat yours” in different formats, however if those themes worth making them live, I don’t mind much, if we know that all Automattic themes are good, they can be made live immediately.
    
    At the end this should make the queue and review time shorter for all of us 🙂
Joy 6:54 pm on June 25, 2017
- Is there any sort of timeline for implementing these ideas?
- What are the pieces that need to be in place before it can happen?
- Can we establish a method for getting something onto the agenda?
- The design team starting a new way to keep their team organized, and it looks like it will work very well. (See Make post) Maybe this would work for TRT?
- Carolina Nymark 8:22 am on June 26, 2017
  
  That is what the meeting is for 🙂
  
  -I looked briefly at the design teams setup, but knowing how difficult it has been for us just to post a weekly agenda, I don’t think it would work.
  - Nilambar Sharma 10:57 am on June 26, 2017
    
    What if we discuss in these threads and in the meeting we take vote for yay/nay? Most of the time in our meeting goes on discussion in a single or couple of topics and time flies without conclusion 🙂
    - Ionut Neagu 11:33 am on June 26, 2017
      
      I think voting yay/nay and listening to authors is important, however due to the fact that 10 authors cannot really represent 20% of the web ( or people using their admin to search for themes), the final decision should be up to the leadership of TRT which will also assume responsability .
      - Nilambar Sharma 11:47 am on June 26, 2017
        
        Agree. And that power has been already given to Team Leads from the restructuring of Theme Review Team. Listening to the team opinions and making a decision. 🙂

Welcome to the Themes team!

Handbooks and review requirements

Coding standards and plugins

Code Packages

Communication