<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Case Studies on remixware.com</title>
    <link>https://remixware.com/tags/case-studies/</link>
    <description>Recent content in Case Studies on remixware.com</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Mon, 26 Oct 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://remixware.com/tags/case-studies/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Case Study: CoyIM Took Code From Another XMPP Client and Kept Its Licence</title>
      <link>https://remixware.com/case-study-coyim-took-code-from-another-xmpp-client-and-kept-its-licence/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/case-study-coyim-took-code-from-another-xmpp-client-and-kept-its-licence/</guid>
      <description>&lt;p&gt;CoyIM is a chat client for the XMPP protocol, written in Go, that sets safe and secure options by default. Its README says it is built upon xmpp-client, an earlier XMPP client at &lt;a href=&#34;https://github.com/agl/xmpp-client&#34;&gt;github.com/agl/xmpp-client&lt;/a&gt;. CoyIM is under GPL-3.0. xmpp-client uses the three-clause BSD licence that Go itself uses, under the line &amp;ldquo;Copyright (c) 2012 The Go Authors. All rights reserved.&amp;rdquo; BSD code can go into a GPL-3.0 program, as long as the BSD notice goes with it.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Case Study: Pip Ships 18 Vendored Libraries With Their Licences, Except One NOTICE</title>
      <link>https://remixware.com/case-study-pip-ships-18-vendored-libraries-with-their-licences-except-one-notice/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/case-study-pip-ships-18-vendored-libraries-with-their-licences-except-one-notice/</guid>
      <description>&lt;p&gt;pip, the tool that installs Python packages, can&amp;rsquo;t count on any other package being installed first. So it vendors what it needs: copies of 18 releases from PyPI, kept in &lt;code&gt;src/pip/_vendor&lt;/code&gt; and listed in its &lt;code&gt;vendor.txt&lt;/code&gt;. pip itself is MIT. Eight of the libraries it carries are MIT too and four are Apache-2.0. The rest are one each under BSD-3-Clause, BSD-2-Clause, ISC, MPL-2.0 and PSF-2.0, plus packaging, which offers a choice of Apache-2.0 or BSD-2-Clause.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Case Study: Typer Copied Code From Click, Then Shipped the Click Licence</title>
      <link>https://remixware.com/case-study-typer-copied-code-from-click-then-shipped-the-click-licence/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/case-study-typer-copied-code-from-click-then-shipped-the-click-licence/</guid>
      <description>&lt;p&gt;Typer is a popular Python library for building command line tools. It began as a layer on top of Click, the command line library from the Pallets project, and for years it listed Click as a dependency. Typer is under the MIT licence. Click is under BSD-3-Clause, which lets anyone reuse its code as long as copies of the source keep Click&amp;rsquo;s copyright notice and licence text.&lt;/p&gt;&#xA;&lt;p&gt;We ran Remixware 0.2.1 on two typer releases, each compared with the Click release of its day: typer 0.12.5 with Click 8.1.7, and the current typer 0.27.3 with Click 8.3.1. The full reports are in the &lt;a href=&#34;https://github.com/softdevstudio/remixware/tree/main/test/results/case-studies/typer&#34;&gt;Remixware repository&lt;/a&gt;, and every number here comes from them.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
