<story><title>Grafana, Loki, and Tempo will be relicensed to AGPLv3</title><url>https://grafana.com/blog/2021/04/20/grafana-loki-tempo-relicensing-to-agplv3/</url></story><parent_chain><item><author>watermelon0</author><text>I have a question regarding AGPL, that I couldn&amp;#x27;t answer by Googling or reading the license.&lt;p&gt;Let&amp;#x27;s say that Postgres server is licensed under AGPL, and I modify it to my needs. I have a closed source web application, that is publicly accessible, and uses Postgres for storing data.&lt;p&gt;a) Do I need to publish source code of my version of Postgres?&lt;p&gt;b) Does my application (which relies on Postgres, and my patches) need to also be under AGPL, and be available in source code form to all my users&amp;#x2F;visitors?</text></item><item><author>blendergeek</author><text>I applaud this decision.&lt;p&gt;I would like to see &lt;i&gt;all&lt;/i&gt; major SaaSS projects be AGPLv3. End users still have freedom to user, modify, and distribute the software. Cloud providers must share contributions.&lt;p&gt;This is how I like it.</text></item></parent_chain><comment><author>zmmmmm</author><text>I&amp;#x27;m going to split hairs the other answers don&amp;#x27;t: you specify you have modified Postgres. My answer is, it entirely depends if your application is considered a &amp;quot;derivative work&amp;quot; of Postgres. This hinges on a couple of things:&lt;p&gt;- does your application directly include AGPL postgres code in any form (headers, binary, etc etc) to its own source or its own runtime process?&lt;p&gt;- keep in mind, in answering the above, that your application probably &lt;i&gt;does&lt;/i&gt; have to include a postgresql driver of some kind. Is the driver licensed AGPL too? If yes, your answer to the above is probably &lt;i&gt;yes&lt;/i&gt;. This was the problem for years with MySQL, because they licensed their driver code GPL along with the actual database code.&lt;p&gt;- a final consideration that only comes into play if there is genuine ambiguity on the other points: is your application able to perform its functions if Postgresql is missing or swapped out for another database? To the extent it depends on Postgresql functionality, this will sway a jury towards considering it is in fact a derivative work of Postresql. If you on the other hand support 6 different databases and Postgresql is just one of them - it will be much less likely your application is considered a derivative work of it. As I said, this only comes into play if the other factors can&amp;#x27;t be decided decisively.</text></comment>
<story><title>Grafana, Loki, and Tempo will be relicensed to AGPLv3</title><url>https://grafana.com/blog/2021/04/20/grafana-loki-tempo-relicensing-to-agplv3/</url></story><parent_chain><item><author>watermelon0</author><text>I have a question regarding AGPL, that I couldn&amp;#x27;t answer by Googling or reading the license.&lt;p&gt;Let&amp;#x27;s say that Postgres server is licensed under AGPL, and I modify it to my needs. I have a closed source web application, that is publicly accessible, and uses Postgres for storing data.&lt;p&gt;a) Do I need to publish source code of my version of Postgres?&lt;p&gt;b) Does my application (which relies on Postgres, and my patches) need to also be under AGPL, and be available in source code form to all my users&amp;#x2F;visitors?</text></item><item><author>blendergeek</author><text>I applaud this decision.&lt;p&gt;I would like to see &lt;i&gt;all&lt;/i&gt; major SaaSS projects be AGPLv3. End users still have freedom to user, modify, and distribute the software. Cloud providers must share contributions.&lt;p&gt;This is how I like it.</text></item></parent_chain><comment><author>eitland</author><text>I&amp;#x27;ve tried really hard to understand this a few times and yesterday or early today or something I found an interesting thread here: &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11354475&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;news.ycombinator.com&amp;#x2F;item?id=11354475&lt;/a&gt;&lt;p&gt;reitanqild seems to misunderstand and the other posters fill in with more information.&lt;p&gt;If the information in that thread is correct and I read it correctly it is totally fine to use an AGPL server that touches connects to a lot of stuff, it won&amp;#x27;t affect any of that.&lt;p&gt;Only if you somehow touches the codebase of the AGPL licensed code by modifying it or creating a combined work then the AGPL will take effect in the same way as today - except that allowing access to a running instance over a network will trigger it too, not only distribution of the binaries or the code.</text></comment>