5 Comments

  1. Lenin Zapata
    · Reply

    All this sounds fabulous, even if you get to apply it, I don’t know to what extent I can review a theme less than 4 months for an approval, if this is not resolved it is not very useful to pass it to github if the slowness continues.

    Report

    • Denis
      · Reply

      One of the things we are trying to solve is cutting down the queue waiting time. The reasons the queue is long is: lack of senior reviewers and the fact that authors keep making the same mistakes over and over and over, despite the fact that there are tons of resources in two handbooks (theme developer and reviewer).
      The aim of moving to GH is improving review speed, both in having automated tools helping and in changes being more visible.

      It’s a proposal, and an experiment I’d like to see happen so that we can determine if it works for the benefit of all :)

      Report

  2. David McCan
    · Reply

    Or WordPress could adopt git to replace subversion for core, themes, and plugins. It seems past time to move to git.

    Report

    • Denis
      · Reply

      There are a lot of people wanting to do this. We just have to see if the systems team is up for it, and what it would mean for the way things are currently working (with deploying versions and all).

      Report

  3. Anh Tran
    · Reply

    This is a great idea. Github has more tools for collaboration than Trac. And their notification also works better. I think if the team can move to Github, the time for reviewing themes and educating theme authors will reduce a lot.

    Report

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: