4 Comments

  1. Daniel Llewellyn

    Well blow me down with a pocket fan.. I’ve made it onto the Tavern. There’s nothing I can’t do now!

    Seriously, though, thanks for the support – this is a topic I passionately believe in and want the world to understand. Well done for finding Ben Winding’s analysis that supports my stance, that helps to convey the problems that a stale bot introduces with little if any benefit.

    Report

  2. Nane

    The open tickets on WordPress is a much bigger problem. There are some ancient ones about functions that are not even used anymore. It’s an on growing challenge and I think we’ll need soon a very sophisticated AI to start cleaning it up. Seriously, it’s super unfriendly.

    Report

    • Marcus Kazmierczak

      We definitely need more powerful tools for issue management. I would love a way to focus efforts, for example if a release has a large set of changes around a specific feature, then be able to kick off a bot that looks at old issues around that feature and asks for confirmation. This would help reengage people on the issue, highlight changes in the product, and hopefully create a healthier repository.

      Thanks WP Tavern for highlighting the issue and discussion, it obviously is a tricky implementation to get right, which was the whole point of raising it as a post on Make.

      Report

  3. My 50 Cents Advice

    There is just too much stuff all over the place. Sometimes I do think that it’s a conspiracy of the open source. Yes, I know, it can’t be all lean, clean and streamlined like Apple. One of the downsides of democracy and open source in that matter as you end up having all this structural mess and management issues. It all starts to look messy. If it was a private company of which I was in charge I would:

    Redesign WP.org to match Gutenberg’s design.
    Streamline the navigation and thus – the functionality of it.
    Put emphasis on installing and CTA to get WP, but major focus on Blocks, Themes, Plugins.
    Dedicate a community forum which tolerates criticism.
    Streamline the blogs under one umberalla.
    Transfer dev of everything to GitHub.
    Ditch all third party offers, including the hostings – SiteGround does have vulnerability issues and is recommended.
    Hire a one-goal purpose to close tickets in order to highlight the important. When you do a spring cleanup you do it because you want to ditch the necessary and highlight the things that you have. When you have 6000+ issues and you have almost half or even more of them being already outdated, it’s hard to find the really important stuff.
    Find a more clean, minimal and streamlined way to advocate people to join in effort.

    Why do we mostly use Macs for dev work? Because it’s clean, minimal and simple. We need that hassle-free environment, the power of the identity throw branding. Clean structural changes for cognitive focus. We need that Googly type of environment where things are simple, yet deep.

    I can’t imagine how much better it would be to simplify things and close the doors of what didn’t matter and focus on what matters.

    Democracy is good, but it’s hard at fighting bureaucracy. The private sector is not democratic for a reason – in order to have efficiency and increase productivity – you have to ditch what doesn’t work, you have to willingly pull the plug on some stuff in order to focus on the other.

    Open source software development has a really hard time on streamlining stuff and cleaning things out of the way. I am not saying it’s bad and we should become Apple, but at least there should be a special position of someone who imposes his will in order to simplify stuff.

    One of the reasons why open source fails at the consumer level in many cases is exactly because of this – lack of efficiency.

    We need minimal, simplified and clean approach, clean structure which can handle the future.

    Report

Comments are closed.

%d bloggers like this: