<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8" /></head><body style='font-size: 10pt; font-family: Verdana,Geneva,sans-serif'>
<p>Looks good to me.</p>
<p>So the first version of QGIS that could potentially ship the HANA provider would be 3.12 - right?</p>
<p>How about backporting to 3.10 - would this be an option or not?</p>
<p>Greetings,</p>
<p>Andreas</p>
<p id="reply-intro">On 2019-09-12 10:54, Paolo Cavallini wrote:</p>
<blockquote type="cite" style="padding: 0 0.4em; border-left: #1010ff 2px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ignored -->
<div class="pre" style="margin: 0; padding: 0; font-family: monospace">Hi all,<br />I'd like to finalize the reply ASAP. Please send comments to the following.<br />Cheers.<br />---<br /><br />Dear xxxx<br /><br />We wanted to reach out to you regarding your proposed patch for QGIS to<br />add support for Hana. As you have probably realised, there have been<br />some concerns raised about the integration of this code. We don't<br />believe these are insurmountable but we would like to ask you if you<br />could respond on a few points as outlined below.<br /><br />* Testing platform: Currently it is difficult for us to test the work<br />you have done since we do not have a test / sandbox instance of the<br />provider that we can use to try it out. Could we ask you to provide us<br />with a perpetually available Hana database instance that we can use to<br />test your provider both now and in the future? It would be ideal if you<br />could set up and maintain this instance for us and simply supply the<br />connection details since we do not have the time or expertise to manage<br />this from within the community. We also ask that you waive any licensing<br />fees for this test platform so that it is freely available to the<br />project. The testing platform needs to be accessible via our CI<br />infrastructure, and you should include unit tests implementing the<br />provider conformance suite which run on our CI.<br />* Community participation: We would like to ask if you can send one or<br />more of your developer team members to attend our regular QGIS<br />Contributor Meetings (next one planned for spring 2020 in The<br />Netherlands) - details will be added to our wiki soon:<br /><a href="https://github.com/qgis/QGIS/wiki" target="_blank" rel="noopener noreferrer">https://github.com/qgis/QGIS/wiki</a>. We ask this because we would a) like<br />you to be familiar with the norms and expectations of the QGIS Community<br />and b) so that we can get to know your team members and gain a sense of<br />confidence that you are committed to the ongoing maintenance of the Hana<br />provider and related impacted code in QGIS.<br />* Packaging and Integration Effort: We would like to ask you if you can<br />give us some indication of the packaging overhead expected for shipping<br />your provider in our standard QGIS packages that we distribute for<br />macOS, Windows and Linux. Have you been able to test on all of these<br />platforms and is the provider fully self-contained? Or does it depend on<br />additional libraries that need to be installed on the host operating<br />system? If so are all of the aforementioned operating systems supported?<br />Also, note that providers are shipped on mobile implementations of QGIS<br />(QField and INPUT) and we would like to know that these platforms will<br />also support your Hana provider. Finally with regard to packaging, if<br />there is additional overhead for packaging we would like to ask you to<br />support the QGIS project, either financially or by providing developer<br />time, to ensure that everything is cleanly packaged for all supported<br />platforms.<br />* Point of contact: We would like to ask you to provide a single point<br />of contact who will be technically knowledgeable and responsive to<br />requests such as bug reports or questions from our community concerning<br />your provider implementation.<br />* Upcoming API changes: For QGIS 3.10 we are planning to integrate a new<br />abstraction layer for provider connection management. We would like to<br />ask you to work with Alessandro Pasotti to get the Hana provider in line<br />with the other providers. This may involve subcontracting him directly<br />if the process requires more time than he is willing to donate.<br /><br />Lastly, we would like to say big "thank you" for choosing QGIS as a<br />platform for your Hana provider implementation - we do appreciate that<br />having it in QGIS and the new opportunities that it will open for our<br />users in enterprise environments. We hope you enjoy working with the<br />QGIS Community and we look forward to having a long and fruitful<br />association together! We would also like to invite you to consider<br />financially supporting the QGIS project through our sustaining<br />membership programme<br />(<a href="https://www.qgis.org/en/site/getinvolved/governance/sustaining_members/sustaining_members.html#qgis-sustaining-memberships" target="_blank" rel="noopener noreferrer">https://www.qgis.org/en/site/getinvolved/governance/sustaining_members/sustaining_members.html#qgis-sustaining-memberships</a>)<br />- as you probably realised from this email and the discussions<br />surrounding your pull request, there is a lot of community / volunteer<br />effort that goes into maintaining and managing the QGIS project and<br />financial support allows us to offload the maintenance burden introduced<br />by adding new provider such as the Hana driver to ad hoc contractors or<br />paid community members.<br /><br />Best regards<br /><br />The QGIS Community</div>
</blockquote>
<p><br /></p>
</body></html>