Plugin Contributor
rajuru
(@rajuru)
Hello @fssbob
I’m one of the developers of the plugin.
SparkPost’s plugin is a community project and greatly contributed by its users along with the internal developers. The project is open source, released under GPL2 and also hosted on github.com/SparkPost/wordpress-sparkpost.
Historically, we have been addressing critical problems pretty quickly. Though we are here to deliver awesome customer experience, it’s difficult to give a commitment around time.
Again, as a community project, we’re looking for help from our users and developers like you. So if there is an issue or scope of improvements, feel free to submit a Pull Request.
-
This reply was modified 9 years, 3 months ago by
rajuru.
-
This reply was modified 9 years, 3 months ago by
rajuru.
Thread Starter
fssbob
(@fssbob)
It’s not really a commitment re time I care about. I’m just looking for reassurance that the plugin isn’t likely to be abandoned. In the case of the other plugin, I think the developer just moved on to other things. My hope is that in the case of the SparkPost plugin, if you and the other active SparkPost plugin developers were to “move on to other things”, the SparkPost organization would be motivated to encourage somebody to take your place. Does that seem like a reasonable assumption?
Thanks.
Plugin Contributor
rajuru
(@rajuru)
@fssbob
Thanks for your reply. TBH, I’m not sure how to address your concern. If I speak as a regular user of this plugin, even if the SparkPost doesn’t actively maintains it, it can’t be abandoned. The plugin is open source, out there for everyone’s use & contribution. If I use some piece of software which is no longer maintained by original maintainers and open source; I have nothing to worry as I’ll fork it and make necessary adjustments if I can’t find effective alternatives; isn’t it one of the advantages of being open source & flexible licensing?
Now as SparkPost, we are surely hoping maintain it for a foreseeable future and as long as it is valuable to user users.
Thanks