<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On Jan 13, 2021, at 4:28 PM, Nyall Dawson <<a href="mailto:nyall.dawson@gmail.com" class="">nyall.dawson@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">On Thu, 14 Jan 2021 at 06:24, David Strip <<a href="mailto:gdal@stripfamily.net" class="">gdal@stripfamily.net</a>> wrote:<br class=""><blockquote type="cite" class="">What is the path forward? One path Howard suggests is establishing a foundation similar to that behind Qgis. Another alternative, probably far more controversial, is a license change.<br class=""></blockquote><br class="">I'm pretty clueless regarding licenses -- but this is an interesting<br class="">thought. I wonder if any new drivers added to GDAL could be done with<br class="">a dual-licensing under both GPL + some other license which requires<br class="">ongoing sponsorship of the GDAL project?<br class=""></div></div></blockquote></div><br class=""><div class="">License monkey business isn't viable in any way with GDAL. It would just create confusion and erode trust, which we can't get back if broken. </div><div class=""><br class=""></div><div class="">The big organizations running 100,000,000s of CPU hours extracting information from imagery they're reading in COGs with GDAL need to be donating substantial resources into an organization that provides coordination. The last time I did a fund raise with <a href="http://gdalbarn.com" class="">gdalbarn.com</a> I was called out for naming some of these organizations and expressing my disappointment they couldn't find a way to participate or simply ignored the request. Maybe they will step forward this time around.</div><div class=""><br class=""></div><div class="">Whether it is in a new foundation or an existing one like NumFocus, substantial resources need to be dumped in a pot that are earmarked for supporting <span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class="">work that generates value for the project. Chasing new feature work to subsidize project maintenance activities is not sustainable in two directions – burn out for the maintainer and creeping feature-itis for the project. </span></div><div class=""><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0, 0);" class=""><br class=""></span></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">It's clear what's happened in the past is a combination of luck and graciousness by both Frank and Even. </span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class=""><br class=""></span></font></div><div class=""><font color="#000000" class=""><span style="caret-color: rgb(0, 0, 0);" class="">Howard</span></font></div></body></html>