Re: Idea for Stimulating Plugin Development
I’d hate to become dependent on someone’s plugin if it’s just going to be abandoned 6 months down the road
This is one of the drawbacks of the extendable model though isn’t it? money or no money we will all be reliant at some point on a plugin for vital (as we see it ) site functionality with no guarantee it will continue to function after core site file upgrades, if an author chooses to abandon something there’s not a lot you can do about it short of pick up the continued development of it.
The only real way of avoiding this is to be able to maintain plugins and files ones self and/or to place a onerous burden on core project developers to do their best to ensure things like plugins will always work, that core upgrades have some means of addressing backwards compatibility but it’s a lot to expect if possible at all.
