<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Explainers on remixware.com</title>
    <link>https://remixware.com/tags/explainers/</link>
    <description>Recent content in Explainers 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/explainers/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Copied Code Brings Its Licence Along: What Open Source Licences Ask of You</title>
      <link>https://remixware.com/copied-code-brings-its-licence-along-what-open-source-licences-ask-of-you/</link>
      <pubDate>Mon, 26 Oct 2026 00:00:00 +0000</pubDate>
      <guid>https://remixware.com/copied-code-brings-its-licence-along-what-open-source-licences-ask-of-you/</guid>
      <description>&lt;p&gt;Open source code is free to use, and it comes with conditions. Every open source project comes with a licence, and the licence is the deal: you may copy, change and share this code, as long as you do certain things in return. Those things are usually small. Sometimes they&amp;rsquo;re large enough to decide how you can ship your whole product.&lt;/p&gt;&#xA;&lt;p&gt;The conditions travel with the code. When a function moves from a library into your project, however it got there, its licence comes with it, even if the licence text stays behind. Here&amp;rsquo;s what the common licences ask, from the least to the most.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
