<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="">Thank you for your detailed reply Robert.<br class=""><div><br class=""><blockquote type="cite" class=""><div class="">On 11.04.2021, at 19:55, Robert Kern <<a href="mailto:robert.kern@gmail.com" class="">robert.kern@gmail.com</a>> wrote:</div><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div class=""><br class=""></div><div class="">"It exists elsewhere" isn't my argument. While this is obviously a judgement call, and my opinion isn't necessarily that of anyone else's, I do have a rough rubric in mind when I consider things for inclusion in scipy. The main guiding principle is to make important functionality available to the scientific Python community. If including that functionality in scipy advances that, great, that's an argument for inclusion. But sometimes, inclusion inside scipy is just a neutral move, and I think that's the case here. That's not dispositive, but then we have to go to more specific reasons, like wanting to use the functionality inside other parts of scipy (like QMC in SHGO).</div></div></div></div></blockquote><div><br class=""></div><div>I guess this will be very subjective. As for the scientific impact, I will just point out that the known textbooks about SA have thousands of citations and are involved with policy-makers through things like JRC, EU.</div><div>Cf. people like Andrea Saltelli, Stefano Tarantola, IM Sobol’.</div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" style="caret-color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration: none;" class=""><div class="gmail_quote"><div class="">If the SALib developers expressed interest in merging SALib into scipy, that'd be one thing. But if they are interested in maintaining it as an independent project, I would recommend contributing to it to build on their success instead of starting from scratch. As a tentpole project of the scientific Python community, we want to support the efforts of the whole community, not replace them or absorb them.</div></div></div></div></blockquote><br class=""></div><div>Just to clarify that my proposal does not seek to eat other libraries, more to provide the basic tools for them.</div><div><br class=""></div><div>Let see what others think then :)</div><div><br class=""></div><div>Cheers,</div><div>Pamphile </div><br class=""></body></html>