I was going to submit a new Petition on here called “Support installing plugins (or themes) via GitHub” but I think this one is nearly the same.
Ultimately, I think one of the fastest ways that ClassicPress could attract serious attention among developers is not just by being “lighter” (and I think the ‘Business-focused CMS’ slogan should be dropped), but by making the entire ClassicPress “world” lighter and more dev-friendly as well.
Instead of trying to “aggregate” and control third party extensions, CP could act more like a platform that empowers agencies and beyond. A ClassicPress.net directory could act more like a meta-engine to index various extensions and perhaps power user reviews of plugins (etc), track active install counts, etc without actually requiring any of their code to be stored on its servers…
Recent Hacker News story:
Example of a meta-engine directory:
Our plugin boilerplate for LittleBizzy has experimented with automated updates via GitHub and its not very difficult. Literally, it could be applied to any repo if they simply add a
releases.json file to the repo root. In just a few minutes, volunteers could submit Pull requests to various plugins (etc) to add such a file, and automatic updates would be immediately supported. Of course, this would depend on ClassicPress Core already supporting this approach…
The meta-engine could also warn users when they’re installing plugins that are known to have security exploits, etc by recognizing the vendor/product namespace or even the PHP class names in the plugin.
But again, trying to over-moderate anything is a bad idea. Criticizing Automattic for allowing pretty much any plugins fails to recognize the business genius of how they’ve empowered an entire ecosystem of security plugins, web hosts, and free market (esque) competition. I’m not saying all their decisions are good, but not recognizing their genius hurts CP’s chances of success… I also strongly oppose cutting off WordPress.org plugin installations, at least for a very long time, because that would shoot ClassicPress in the foot.
If there is truly going to be decentralization of WordPress, its not going to happen just by slapping up some Democracy values or disabling some of the spam and tracking forced into WordPress by Automattic – it’s going to happen by actually turning over all plugin and theme development AND micro-community management over to the agencies and developers behind them, via GitHub.
In essence, the primary role of the so-called ClassicPress founders and Committee would be to guide Core development, while fielding suggestions and making decisions based on feedback. As a small team, this would be less demanding in financial terms or otherwise, and would also avoid turning CP into yet another dramatic and corrupt OSS fiefdom by emphasizing decentralization. Choosing the right battles, knowing when to honor “upstream”, and knowing how to differentiate ClassicPress in simple yet powerful ways is key to any success…
Edit: See also https://petitions.classicpress.net/posts/129/have-a-page-on-the-website-where-plugins-that-support-classicpress-can-be-added-and-rated
~ posted by Jesse