licensing gpl
Licensing a code which imports other module
<p>I made a discord bot using discord.py...and want to publish it in GitHub but what license do I publish it in? the discord.py is licensed under MIT and it states that &quot;<strong>the distributors include the copy of original MIT license with the distribution code</strong>&quot;...do i need to license the code under MIT?</p>
<p>And I also used a module in my bot's code named &quot;chatterbot&quot; which is licensed under BSD 3-clause license. And that also states that &quot;<strong>1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.</strong>&quot;</p>
<p>I didnot copied any code just imported them and used it in the code, does that count as redistribution of source code? and Do I need to license my GitHub repo as they state?</p>

<p>Both the MIT and BSD 3 clause license can be included with both more permissive and less permissive licenses, so long as you adhere to the requirements the licenses lay out.</p>
<p>In both cases, these licenses require that the original copyright notice be included in any distributed codebase, as you have noted in the question.</p>
<p>This does not mean, however, that the entirety of the new codebase need be MIT or BSD 3 Clause licensed - it just means that the portions of the codebase you have included under those licenses remain under those licenses, and this is made known to users of the codebase (by including the copyright notices).</p>
<p>So, to answer your questions directly:</p>
<blockquote>
<p>I didnot copied any code just imported them and used it in the code, does that count as redistribution of source code?</p>
</blockquote>
<p>Yes, it counts as redistribution of source code.  Whether you directly distribute the libraries themselves (by pre-packaging them into a binary) or create a derivative work (by relying on them - this is less clear cut, but in this case there is no downside to considering it), there is redistribution going on, so you need to adhere to the licenses.</p>
<p>However, in this case, adhering to the licenses is trivial.</p>
<blockquote>
<p>Do I need to license my GitHub repo as they state?</p>
</blockquote>
<p>No.  You merely have to include the MIT license and the BSD 3 Clause license in text documents in the repository, with a note as to which parts of the codebase they are applicable.</p>
<p>You do NOT have to license the entire repository or codebase to either one or the other - you can choose the GPL or even a proprietary license if you so wish.</p>
