licensing
Does MIT license oblige me to publish its code in open sources
<p>I found several libraries on GitHub that I plan to use for a commercial application. They are all licensed under MIT or Apache 2.0. Having studied them, I realized that I can use them for free in development, but does this oblige me to publish its code in open sources after developing the application?</p>

<p>You'll want to read the actual licenses yourself and understand what is required.  If you don't understand, then you'll want to consult an attorney.</p>
<p>But neither of these licenses are all that complex in my opinion.</p>
<ol>
<li>MIT:</li>
</ol>
<blockquote>
<p>Permission is hereby granted, free of charge, to any person obtaining a copy     of this software and associated documentation files (the &quot;Software&quot;), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:</p>
<p>The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.</p>
</blockquote>
<ol>
<li>Apache 2.0:</li>
</ol>
<blockquote>
<ol start="4">
<li>Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without       modifications, and in Source or Object form, provided that You       meet the following conditions:</li>
</ol>
<p>(a) You must give any other recipients of the Work or           Derivative Works a copy of this License; and</p>
<p>(b) You must cause any modified files to carry prominent notices           stating that You changed the files; and</p>
<p>(c) You must retain, in the Source form of any Derivative Works           that You distribute, all copyright, patent, trademark, and           attribution notices from the Source form of the Work,           excluding those notices that do not pertain to any part of           the Derivative Works; and</p>
<p>(d) If the Work includes a &quot;NOTICE&quot; text file as part of its           distribution, then any Derivative Works that You distribute must           include a readable copy of the attribution notices contained           within such NOTICE file, excluding those notices that do not           pertain to any part of the Derivative Works, in at least one           of the following places: within a NOTICE text file distributed           as part of the Derivative Works; within the Source form or           documentation, if provided along with the Derivative Works; or,           within a display generated by the Derivative Works, if and           wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and           do not modify the License. You may add Your own attribution           notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.</p>
</blockquote>
<p>Nowhere does either license require you to publish your application's source code, even if your application is directly based on the original code.</p>

<p>Neither the MIT license nor the Apache 2.0 license requires a user to publish anything, even if the user has created a modified version or a derivative work based on an original that s/he received under either license. What they do require is that if the user distributes the code, it must be with similar rights.</p>
<p>More specifically, the MIT license requires that if the user &quot;furnishes&quot; the software to others, they must be granted the same permissions to &quot;deal in&quot; the work that the user got under the MIT license.</p>
<p>The Apache 2.0 license requires that if the user decides to &quot;reproduce and distribute copies of the Work or Derivative Work&quot; then certain things must be included in the distribution, which will have the effect of putting that distribution under the same license. See the detailed license text elsewhere in this thread or available on the web through an easy search.</p>
