<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Dec 21, 2016 at 11:46 AM, Bruce Momjian <span dir="ltr"><<a href="mailto:bruce@momjian.us" target="_blank">bruce@momjian.us</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Dec 21, 2016 at 11:31:56AM -0800, Paul Ramsey wrote:<br>
> Imagine PgSQL was GPL. Would most users of PgSQL have any concerns about that?<br>
<br>
</span>Yes, they would it would affect closed-source versions of the Postgres<br>
backend, as well as perhaps closed source/binary functions and<br>
extensions.<br></blockquote><div><br></div><div>"Most users" would have concerns w/ closed source PgSQL and proprietary forks? I'm guessing that 99.9% of our user community is using the community open source version w/o alteration. Or in the case of AWS Aurora, using a forked version of PgSQL that is not being "distributed".</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Probably not, right, because they are just using the unmodified database, all<br>
> their proprietary IP would be on the other side of the client/server boundary.<br>
<br>
</span>Right, but that is not what the FAQ addresses, I thought.<br></blockquote><div><br></div><div>Then we should clarify it a bit, because it's mostly about those Frequent questions on "I'm building a SaaS thing using PgSQL/PostGIS, so I have to share all my code?". Basically questions about stuff that's on the far side of the client/server dividing line. Almost nobody asking the licensing question has actually modified either PgSQL or PostGIS.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> That leaves folks who are shipping proprietary PgSQL with PostGIS added in. Are<br>
> you wondering about them?<br>
<br>
</span>Yes, plus things like server-side functions and triggers.<br></blockquote><div><br></div><div>For the "proprietary fork of PgSQL folks", which are a very small subset of the user community, things are greyer and we leave it to their own lawyers to determine how comfortable they are w/ it. Our internal "we care about it" policy has been more LGPL'ish, in that we're concerned w/ people shipping closed, modified versions of PostGIS (apologies to strk if I'm granting more leniency than he might like). However, that doesn't stop lawyers and folks from applying a stronger interpretation around shipping proprietary PgSQL w/ un-modified community PostGIS. Does PgSQL depend on PostGIS? No. You can run it w/o. You can even have your users download a plug-in separate from the shipping PgSQL, so that you aren't "distributing" both parts together (I believe that's the line that historically EDB has taken w/ PostgresPlus?). There's all kinds of tap-dancing, depending on what companies have decided feels right. We aren't a $1B company, we aren't suing anybody, do your due diligence and abide by the spirit of the license as best you can.</div><div><br></div><div>P.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5"><br>
--<br>
Bruce Momjian <<a href="mailto:bruce@momjian.us">bruce@momjian.us</a>> <a href="http://momjian.us" rel="noreferrer" target="_blank">http://momjian.us</a><br>
EnterpriseDB <a href="http://enterprisedb.com" rel="noreferrer" target="_blank">http://enterprisedb.com</a><br>
<br>
+ As you are, so once was I. As I am, so you will be. +<br>
+ Ancient Roman grave inscription +<br>
______________________________<wbr>_________________<br>
postgis-users mailing list<br>
<a href="mailto:postgis-users@lists.osgeo.org">postgis-users@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/postgis-users" rel="noreferrer" target="_blank">http://lists.osgeo.org/<wbr>mailman/listinfo/postgis-users</a></div></div></blockquote></div><br></div></div>