<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Software on Hambz</title><link>/tags/software/</link><description>Recent content in Software on Hambz</description><generator>Hugo</generator><language>en-us</language><copyright>© Halladj Hamza</copyright><lastBuildDate>Mon, 29 Aug 2022 00:00:00 +0000</lastBuildDate><atom:link href="/tags/software/index.xml" rel="self" type="application/rss+xml"/><item><title>Software Licensing, Simply Put</title><link>/posts/post-11/</link><pubDate>Mon, 29 Aug 2022 00:00:00 +0000</pubDate><guid>/posts/post-11/</guid><description>&lt;p>One could wonder, &amp;ldquo;&lt;em>what is the point of having a license over software, the source code
is probably already there, in the public domain&lt;/em>&amp;rdquo; (for example published over GitHub),
well there is no short answer, and probably there will be no legal problems at all if you don&amp;rsquo;t use one(most of the
time, don&amp;rsquo;t take my word for it), but not having a license over software will eliminate
any rights or ownership over it, and it gets only worse from there as the lines
of ownership are blurred, for example: who owns the code, the writer who thought about
a solution and code it into reality or the cooperation which he works for,
or both. So what is exactly software licensing?&lt;/p></description></item></channel></rss>