<story><title>Re-Licensing Sentry</title><url>https://blog.sentry.io/2019/11/06/relicensing-sentry</url></story><parent_chain><item><author>JoshTriplett</author><text>So, Sentry is no longer Open Source at all, though people might potentially be able to collaborate on three-year-old versions (or, hopefully, use whatever unified fork pops up from the last Open Source release).&lt;p&gt;That&amp;#x27;s disappointing. Unfortunately, the more companies use such licenses, the more others see it as &amp;quot;safety in numbers&amp;quot; for them to do the same.</text></item></parent_chain><comment><author>the_mitsuhiko</author><text>&amp;gt; Sentry is no longer Open Source at all&lt;p&gt;I just want to clarify that in addition to BSL converting into an Open Source license after the conversion date, we also did not BSL license everything.  Client libraries are completely unaffected and so is a lot that is going on behind the scenes.  We&amp;#x27;re firmly committed to being good Open Source citizens.  For instance a lot of the work that is going on behind the scenes is separated into independent reusable libraries that retain their original licenses.</text></comment>
<story><title>Re-Licensing Sentry</title><url>https://blog.sentry.io/2019/11/06/relicensing-sentry</url></story><parent_chain><item><author>JoshTriplett</author><text>So, Sentry is no longer Open Source at all, though people might potentially be able to collaborate on three-year-old versions (or, hopefully, use whatever unified fork pops up from the last Open Source release).&lt;p&gt;That&amp;#x27;s disappointing. Unfortunately, the more companies use such licenses, the more others see it as &amp;quot;safety in numbers&amp;quot; for them to do the same.</text></item></parent_chain><comment><author>emidln</author><text>It seems the restriction is on offering a competing product with Sentry&amp;#x27;s codebase. This seems fine. I&amp;#x27;ll still submit bug reports or even contribute fixes here. My current employer isn&amp;#x27;t a cloud provider or an exception handling as a service company, but we still might want to run Sentry in-house. Previously, we might have contributed fixes&amp;#x2F;features in the interest of spreading our own maintenance burden. This still seems possible and I don&amp;#x27;t see a reason to not contribute back for my use case.</text></comment>