Open Sourcing Meta Plugins

TL;DR: I’m proposing that some of the new plugins we write for The community site where WordPress code is created and shared by the users. This is where you can download the source code for WordPress core, plugins and themes as well as the central location for community conversations and organization. live in the official pluginPlugin A plugin is a piece of software containing a group of functions that can be added to a WordPress website. They can extend functionality or add new features to your WordPress websites. WordPress plugins are written in the PHP programming language and integrate seamlessly with WordPress. These can be free in the Plugin Directory or can be cost-based plugin from a third-party repo, rather than the MetaMeta Meta is a term that refers to the inside workings of a group. For us, this is the team that works on internal WordPress sites like WordCamp Central and Make WordPress. repo.

I’m working on #meta187 and part of it is a modification to P2P2 P2 or O2 is the term people use to refer to the Make WordPress blog. It can be found at to allow assigning a categoryCategory The 'category' taxonomy lets you group posts / content together that share a common bond. Categories are pre-defined and broad ranging. to a new post. I created a plugin for it, and initially I was just planning on putting it in the Meta SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the released code are all centrally managed through SVN. repo, but since this is generic functionality — rather than something specific to — I started thinking about where the best place for it to live would be.

One of our goals it to open-source as much of as possible, and putting the plugin in the Meta repo would achieve that, but probably not in the most effective way. 99% of WP users and plugin developers aren’t aware that the Meta repo exists, so the code isn’t very visible. And if they wanted to get updates, they’d have to set it up as an svn:external, rather than just using the regular plugin update system.

So for the most part, the only people who would benefit from using it outside, or contribute back to it, would be other developers on the Meta team.

So instead, I’m thinking we should put it — and other plugins like it, in the future — into the regular plugin repository. That would give it much more exposure and would make it easy for others to use the plugin. The extra exposure would lead to more feedback from users and more contributions from developers.

We could add the wordpressdotorg user as a contributor to the plugin, to ensure the Meta team still has commit access to it if the original developer isn’t available.

What does everyone think about that?

#meta, #open-source, #plugin-directory