Performancing Metrics

Could Benefit From A GitHub Similar Platform?

githubWhen ‘canonical plugins’ for WordPress were announced the post also mentioned that these plugins might have to move to a new structure, setup:

In order to have a system like this, each canonical plugin’s development community would probably need similar infrastructure to WordPress itself, including things like Trac, mailing lists, support forums, etc. These things will be worked out within the development community over the coming months…

If the community decides to open up the platform more this could have great advantages for these plugins but it would only restrict the damage done daily elsewhere. The inconvenience of being a popular open source platform with extensions and themes directory: popular plugins become orphans, themes aren’t updated with the newest features and could break a standard WordPress setup with new releases.

All themes and plugins hosted on are required to be GPL licensed so it would be simple for developers, designers to re-release ‘updated abandoned’ plugins and themes but users would not receive updates in the plugin and themes installer.

Enter GitHub. GitHub is a popular distributed platform used for many opensource software projects. Rails uses it, scriptaculous and Lussumo garden are other popular projects using GitHub. The SourceForge of the modern internet.

Git is a fast, efficient, distributed version control system ideal for the collaborative development of software.

GitHub is the easiest (and prettiest) way to participate in that collaboration: fork projects, send pull requests, monitor development, all with ease.

Where GitHub excels is the possibility to follow projects and also to fork a project, all while keeping the project leader informed of contributions.


I am not saying that GitHub the future of the themes and plugin directory is, but GitHub does offer an easy platform to overview many different projects. If a plugin or theme becomes orphaned, chances that someone else has created a fork are big and ‘repository moderators’ could opt to replace the main, original plugin with an updated commit.
A GitHub similar platform would also offer an easy platform for theme designers and child-theme designers to keep ‘connected’. It literally becomes easy to follow a plugin’s or theme’s history (themeline?) and to download new commits.

Could benefit from a similar setup?

Categories: General, WordPress News
Tags: , , ,

This post was written by . You can visit the for a short bio, more posts, and other information about the author.

Comment with Your Facebook Account


  1. Remkus de Vries ) says: 5/10/2010

    I think it could. Not sure if it has to be GitHub necessarally, but this functionality is much needed in my opinion. There are way too many orphaned solutions out there…


  2. Mark Kubacki ) says: 5/25/2011

    You have already mentioned the GPL issue. Because of it I for one have moved my plugin(s) to Github. But y that the auto-update is no longer available, as that is only supported for plugins hosted at plugin site lacks one thing badly: A proper issue tracker. For example, users experiencing problems with my plugin have published their issues at forums. As the author, I don’t get automatically notified about that. Therefore that support requests don’t get resolved in a timely manner.

    Plus, is slow when accessed from Germany. Setting a stable version’s number in “readme.txt” and copying “trunk” right after that is – counter-intuitive at least. You cannot publish sites with more documentation at – which is possible with Github.

    Finally, if someone unknown wants to contribute to your works you get a patch either per email or have to dig it up from’s forums. Nope, that is definitely better implemented somewhere else. And GIT (or Mercurial, I am pragmatic here) the better tool for that kind of development than SVN.


  3. Adriana says: 2/25/2012

    thanks for share!