5 Comments

  1. Mark Root-Wiley
    at

    Great post, Sami! I particularly like your first point about doing a “post-mortem” after every new default theme to trace issues back to _s.

    Regarding transparency if issue/ticket reviews, I completely agree and recently opened up a ticket asking for clarifications (which I know you know about!). If other people are interested in that issue, I’d encourage them to weigh in the issue 1069.

    1. Sami Keijonen
      at

      Thanks Mark for comment and contributions!

  2. Ulrich
    at

    The leads would be anyone working at Automattic with the exception of Philip who got to keep his commit access after he left Automattic.

    Personally I am also hesitant to contribute as I am not sure when the PR will be merged.

    I would like to see regular feedback instead of instead of PR’s being merged in a merging spree.

    There is also a clash between _s fulfilling Automattic needs and at the same time as the community needs.

    I would be potentially interested in creating a fork of it. If we did something like this then it we would need to define a few things:

    • Vision and goal of the project so that it does not get bloated
    • List of maintainers or people who are interested in maintaining it.
    • We would need to fork the generator too
    1. Sami Keijonen
      at

      I agree all of your points.

      With all those pain points many have their own fork of _s, I have also thought about it several times. If you decide to create your own fork I’m definitely interested contributing.

  3. Enes
    at

    Good point there, I think everyone should help contribute to improving underscores.

Comments are closed.