WordPress as a CMS (Content Management System) commands a great deal of respect, as do its developers. And while the Open Source heritage of WordPress is laudable, is it time to consider offering tools to “incentivize” commercial development?
I ask because I’m currently in the process of performing a feasibility study into developing another WordPress Plugin that would work in conjunction with several other applications across a variety of web services.
My main concern is that the moment I launch my Plugin, anyone can read my code. And I have to wonder how many other businesses have looked into Plugin development only to discover there’s no formal WordPress-sanctioned method of safeguarding their code.
Quite recently, I released my Socialize Me! Plugin for free. But there are very definite business benefits in doing that — I managed to get some solid, global exposure, demonstrating my ability to write innovative software.
This “loss leader” exercise helps build up a sense of credibility and trust, both of which are essential ingredients for the success of any business.
Encrypted PHP — the obfuscation generation
There are methods to encode and encrypt PHP (a common programming language for web applications, which is also the language WordPress is written in) but I’ll admit I don’t know enough about that kind of thing.
And to the best of my knowledge, the encoding part is where the cost is, while the decoding aspect doesn’t appear to be supported across all LAMP (Linux, Apache, MySQL & PHP) web hosting providers.
The lack of built in mechanisms for encrypting PHP could be looked at in one of two ways: 1. the Open Source ancestry of PHP might have looked upon such proprietary-friendly methods of obfuscation with disdain, or 2. Zend are protecting their own business interests by charging for such things.
I’ve noticed more Linux people passing through my ‘blog recently, maybe you guys know more?
Adding value to WordPress Plugin development
I’m pretty new to writing Plugins for WordPress. But I’m not new to writing PHP web applications.
When I look at WordPress, I see a CMS that’s not perfect — the hideous template architecture being a prime example. But I also see room for additional features that could help win over the business crowd, such as:
- A certification procedure for Plugins, that considers stability, security and privacy, among other factors.
- Some portable method of “locking down” and protecting commercially sensitive code.
I fully appreciate that some of the Open Source advocates might not like the second idea, but from my point of view, I really do not want to be sharing all of my efforts with everyone else. But this is an old debate, so I’ll spare you the arguments.
And I must stress that in both cases, I’m proposing an elective and not mandatory process.
Knowing what I do about company IT departments, concerns about a software package need to addressed, policies must be remain tact and procedures followed through.
By having some formal, recognized method of certification, those same IT departments would have one less reason to deny WordPress server space, raising the already high level of credibility that WordPress enjoys and possibly beating off bespoke or paid-for “shrink wrapped” solutions in the process.
I’ll freely admit I’m by no means an authority on WordPress. But as a businessman, if I’m to write more Plugins for WordPress, being rewarded for my efforts comes first, with my love of programming coming a distant second…