Hi Andrew.
I have been a user of siteorigin products for several years. I realize y’all aren’t a big team. And I realize having to make hard choices is most likely common for you when it comes to things like forks of WordPress.
I read your reply on one of the posts regarding compatibility with ClassicPress.
Given your response, would you be happy to see someone fork your projects if the time comes that compatibility updates might be needed for the ClassicPress project?
Thanks for all the work and the dedication you have shown to the WordPress community for so long.
Hi :)
Thanks for your understanding and support, it’s most appreciated.
Hopefully, there won’t be any big changes for a long time that would disrupt Page Builder running in ClassicPress.
Page Builder and our other plugins are licensed under GPL, if you’d like to fork any of them in the future, you can do so. My recommendation is to put that off for as long as possible. Due to the complexity of Page Builder, we’ve seen a notable number of issues with forked versions in the past. If it’s possible to resolve future challenges via an addon plugin, I’d also recommend doing that instead of forking. Whether that would be possible would depend on the type of challenge that arises.
Thanks again for your support.
A quick follow-up after chatting with the team. In the future, it might also be possible for you to maintain ClassicPress support by submitting the changes you need as PR’s to the main SiteOrigin Page Builder repo: https://github.com/siteorigin/siteorigin-panels
Thank you for that. I was wondering if y’all would come to that kind of decision. Makes more for a community minded project. Or that is the way I would see it.
Indeed. Sounds good :) Chat in the future if any challenges arise. Cheers for now.