SBarnes wrote:Whilst I agree with you that an embedded reference and just the plugin as shell would cover this, I know it's something Jiwa are not a fan of as it could create an issue that one of their customers could end up with the situation of the developer and the source code disappearing into the sunset
This was one of the core directives given for the the plugin system when developing it - to not leave customers vulnerable to authors unable or unwilling to maintain customisations.
Just a few months ago, I was tasked with upgrading a version 6 customer who had encrypted stored procedures, obfuscated VB Script and other nasties which validated our philosophy on keeping customisations maintainable in version 7. It wasn't a fun ride, and in this particular case what they were attempting to protect was pretty much just inflated ongoing maintenance costs - nothing was built to be reused or remotely looked useful outside the customers specific business scenario (which had changed a lot since the customisations were implemented). We certainly don't want situations like that, and will not encourage or empower developers to do this.
But, as you suggested, a compromise where the IP is protected AND the customer is protected in some way would be ideal.
The legalities are probably going to be the biggest hurdle here. If there was a system where customisations can be published to customers and protected from piracy - yet we (Jiwa) have the ability to maintain the customisation if need be - what would constitute the legal right for us (Jiwa) to step in and do so? Would the original author making demands of unreasonable compensation be considered grounds for us to step in and take over their IP? If it was deemed "abandoned" - then what is the measure of "abandoned"? - if they died does their next of kin inherit the rights to that IP and can we legally also take on the maintenance of that IP?