3 Things I Learned About the MIT License



The task was simple. We had to first read the MIT License, followed by The MIT License, Line by Line by Kyle E. Mitchell and talk about what we learned or thought was interesting.

One of the very first things that I learned and my main take away from this reading was to not simply trust or believe that there isn't much to a license if its writing is less than 200 words. I was impressed by just how much depth there was to the 171 word text.

Secondly, I learned that the MIT License isn't one, but many (a family as a matter of fact) of licenses.

And lastly, I learned that the MIT License has outlasted most of the software licensed under it.

Popular posts from this blog

Assignment 1 - Fixing a real bug

Image
This is a continuation from my previous post on  getting a thimble testing environment to run . To keep you up to speed, my goal was to fix this issue right here: As you can see, if one doesn't publish a project, the description isn't saved to the server. The text is persisted if you stay within the project editor page, which could fool a user into thinking the text is actually being captured, only to be surprised if they leave it. If everything within this page is saved without publishing, why isn't the description doing it as well? Well, my task was to fix that. The actual problem narrowed down to how an ajax request is made in order to save the data to the server. Every time a user "published" a project, all of the data would be saved, the description included. "Unpublishing" a project would do the same, all of the data within the page would be saved. When not publishing, the page saved only certain elements, such as the Project name (upper left
Read more

Lab 6/7 Github Stuff

The tasks for this lab allowed me to get a little more familiar with Github. We were to design a library, and to do so we first had to create 4 functions. They had to show the filename without the path, show the file size in bytes, and finally the last two had to show the sha1 and MD5 digest for a file's path. In terms of languages used, I chose Python since it is one of the languages I chose to focus more on this term. License wise, I picked BSD3. I created a repo and published all of my code on to the master branch. As for the last part of this lab, I contributed towards someone's lab, by using an example with some code that I saw online. I have yet to receive an answer on whether this piece of code helped or not, but hopefully it leads them in the right direction, if it doesn't solve the issue altogether. Contributing to someone else's code is something that we got some first hand experience with thanks to our release 0.1 assignment, but this was good reinforcement o
Read more