The MIT License

-


The MIT License is a software license that gives permission for reuse, modify, or sell as the programmer sees fit. The License is written in lots of big words, and I am a programmer not a lawyer so it's hard to understand it all. In my Open Source course, I learned of the acronym "IANAL", or I am not a lawyer. For an assignment, I am to write a simple blog about what do I think the MIT license means, explain it in my own words versus how a lawyer would read this.



Image obtained from https://opensource.org/licenses/MIT

The license starts off stating that the software code can be used free of charge in whatever way the person obtaining it sees fit. This includes using it, modifying the code, redistributing it, or even selling copies of the software. Now that may see weird, why would I allow someone to use my code free of charge and then let them sell my software while I make no profit? Well the next paragraph explains it. The software is provided "as if", meaning that any bugs found in the original software later on, the original programmer is absolved of any fault, he can not be sued for any faults. It is the responsibility of the person using the code. The MIT license also states that the license is to be included in all copies or substantial portions of the Software. This is how I interpreted the MIT License, now how would a lawyer describe the license? Let's take a look at how attorney Kyle E. Mitchell interprets the license in his blog.

Right from the start, Mitchell has a lot more to say about the license than me. Mitchell explains that the license is a promise not to sue, therefore protecting the original creator. Some of the verbs, use, copy, modify, merge, publish, distribute, sub license, sell copies, and permit have a specific meaning tied to them while others do not. Copy for example, has a specific meaning under the United States Code title 35, section 271(a). There is some conditions to be met first though before being able to use this software: you need to let others know that they also have permission to use the software under public law, credit the original creator, and ensure that the warranty disclaimer and limitation of liability follow the software around. Finally, the disclaimer is another protection for the original creator so that they do not get sued in case the software does not work, breaks, or causes trouble. Typically warranties do they exact opposite and reassure the new product owner that the product will not break, but not in this case. The author or copyright holder in this case is not liable for any damage or liability.

It's a good idea to read up on any license before using it, especially if the license is hard to read and other can explain it in much simpler words. As a future software developer, this is one license that I will use a lot in the future I imagine. It good to full understand what it means.


Comments

Post a Comment

Popular posts from this blog

DPS911 - Release 3

-
Image
This is my third release for my Open Source class. This release is a progression on my the second release , where I used WebTorrent for sharing resource files. In the previous release, I created two different pages, one for importing files and one is exporting files. With this release, I joined the two files together, and added a few new features, such as number of peers, and download progression.    For testing purposes, we have a temporary main page for testing things like the editor, the Linux terminal, or file editor. I've added the share link in there as well for easy access during testing.  The look of the page is elegant now, it looks professional compared to the previous iteration. It displays the progress of the download, remaining time, download speed, download progress, upload speed, number of peers, and the total time. Once the torrent is complete, a message pop ups on the bottom saying it is complete. To start the torrent, the Start Seed button needs t
Read more

DPS911 - Release 1

-
Image
About two weeks ago, I started a DPS911 Open Source Projects class, which is essentially a continuation of the previous DPS909 Topics in Open Source Development class that I took last year. The class size is much smaller, we have 4 students compared to the 30+ we had last time, which is nice the professor can spend more time with us as opposed to the entire 30+ class of students. For this class, we are starting a project that my professor has envisioned, for now we are calling it unbundled . This project is meant to recreate an operating system for web development in a browser environment. The idea is to have features such as accessing directory of files, a code editor, command line terminal, sharing files, and more, be available in the browser for use on any operating system. The project isn't re-inventing the wheel, the technology is already there, we are just putting everything together. Brackets , for example, will be used for the code editor, while webtorrent will be used f
Read more

DPS911 - Release 2

-
Image
This is my second release for the DPS911 - Open Source class. With this release, I created two pages for sharing resource files between users, one was for importing the files, and the other was for exporting. I am using Webtorrent streaming service for sharing the files. The pull request can be found here , while the issue is located here I did have some trouble with this release. Initially, I had the user selecting local files to share instead of resource files. The pages themselves are very simple, most of the work was done in the back-end. The import page only has an input field for the magnetURI, and a download button download all the files. The export page automatically starts the torrent when opened, sharing all of the resource files, and displaying the magnetURI. This release was simple, there's no extra features included such as number of seeders, progress, or number of files. All this will be included in the next release, which will include combining the pages into
Read more