3

A client asked me to write a WP plugin that is just for their website - it won't be on the repository. Basically it contains a form, place-able with a shortcode, and then sends the collected entry data to a third party private API - essentially nobody except my client has any use for the plugin. Is it mandatory to use the GPL, just because it is a plugin for one specific Wordpress-installation? Is it allowed to use a different license? My problem is, that the client pays for the development and has their customized set-up and doesn't want it to be open source. So is there a different license I could use? If yes which one? Thanks in advance

4
  • 1
    The client will run this plugin on their installed version of Wordpress only, and doesn't want to give copies of the plugin to anyone outside their organisation?
    – MadHatter
    Apr 21 at 8:34
  • Basically yes, it will run on their current website only but there is an external web admin company involved who takes care of the website. Possibly they might change that web admin company or other employees get access to the site.
    – gladys
    Apr 21 at 9:53
  • Will they want the ability to share the code of the plugin with the support company?
    – MadHatter
    Apr 21 at 10:08
  • Hopefully not, but since they have access to the entire site and server they can certainly access it and possibly modify/ reuse it if one assumes the worst
    – gladys
    Apr 21 at 17:29

2 Answers 2

2

Wordpress is distributed under GPLv2+, and I'm working on the assumption that Wordpress plugins are sufficiently tightly-integrated with the main program to constitute derivative works (more can be read about the FSF's position on this here).

My recommendation is to go with GPLv3 for your plugin. We discuss elsewhere on this site the much-clearer provision that GPLv3 makes for sharing covered code for the purposes of hosting and ongoing maintenance without having to do so under normal GPLv3 requirements. So the client will be able to share it with both their web admin company, and any future maintainer, without having to "open source" it.

1
  • Thank you! That seems to be the best solution
    – gladys
    Apr 25 at 10:34
0

For this kind of code it may be useful to just license the code as GPL, pack it as a zip file and wait for the unlikely event of someone explicitly requesting the code. Most licenses (like GPL) don't require you to make access easy. If it is as customer specific as you say, there's nothing to hide.

BUT (!) Although it might be a fair solution for you, this method is much too often used by companies that just want to use free stuff and never contributing to the community. Open sourcing on paper but then complicating the access as much as possible is just really bad. Don't ever do this if your code contains anything meaningful that might be reused.

ALSO (!) Releasing your code in an readily accessible repo comes with benefits. People will see your code and report potential flaws in it.

Think about publishing it. Source code takes just a few bytes of storage in the cloud and even if just a single person finds something interesting, you may have saved them A LOT of effort. Remember the times when YOU found something obscure that you would never have thought to find on the internet ;)

1
  • Thank you so much - clearly I am totally onboard with sharing the code, but the client and the third party API want to keep it closed for security reasons.
    – gladys
    Apr 25 at 10:35

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.