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

Building Mozilla web browser from source

-
Image
This week I built the Firefox web browser from source. Mozilla currently has about 17,998,723 line of code, it is mostly built with C++ but also includes other languages such as HTML, C, JavaScript, Rust, and many more. I personally use Mozilla as my preferred browser, so it was interesting to download and modify the source code. Mozilla has easy to read  instructions  that I followed for downloading the source code, building it, then running. I'm using Mozilla on a Windows 10 system. Some of the prerequisites include installing Visual Studio with certain workloads, Rust, MAPI Header Files, and MozillaBuild. Once I installed everything necessary, I was ready to pull the Firefox source code using the command hg clone https://hg.mozilla.org/mozilla-central And then the wait begins. After patiently waiting for the a while, the downloading aborts. Uh oh, what happened? The message read: "Rust compiler not found". I have installed the Rust compiler and have
Read more

Async image load test with gh-pages

-
Image
I finally got the opportunity to try out GitHub Pages. GitHub Pages is a simple static HTML page that we can create from our GitHub repositories. It is perfect for documentation or anything related to the project. To get started, a gh-pages branch must first be created, and then it can be further setup in the settings section. For this project, I wrote a test case for async image loading. I built a simple page that would allow me to test this in multiple browsers. The page is very simple with an image, a counter, and a button to reload the image. As the user clicks the button, the image is reloaded. If the image is reloaded, the background changes colours and the counter is updated. The async testing has passed on all the browsers except for Safari. I decided to dig deeper into this and Safari is like this. I had to dig pretty deep into the webkit source files to see where the load event is fired. After digging around for a little bit, I found the ImageLoader.cpp file. The na
Read more

First bugs completed

-
Image
After working on my bugs for the past few weeks, I've finally completed two of my bugs! The bugs themselves were very simple to solve, but in this process, I've learned how to use a variety of different Git command, including clone, pull, add, fork, and pull request. I use to feel lost while using Git, now I'm much more confident with my new skills. Neither of my bugs were software-breaking bugs, and most users wouldn't even notice them. I finished my first bug in my previous blog, you can go and view it here . Deep inside of Firefox's Dev-tools, one button's boundaries extended to the end of the screen, instead of around the image only. The fix was relatively easy, a CSS class was already created and I only had to place the class name in the correct spot on the HTML page. I left the last blog after I completed the bug, without creating a Pull Request. During my previous lab, I practiced creating a Pull Request, so I had an idea on how to do it this time. I cr
Read more