To the future that may ask!

Some may be familiar with this commit: 5470d9b .

It's a commit wherein the license was added to each and every file.

But why?
-- You may ask.

It's for the protection of those that already have and will contribute to the repository.

Without a license, the maintainer and the individual authors of a repository are susceptible to "legal actions".

That is if any of the code in this repository is to be used for malicious actions.

But why the MIT License?
-- You may also ask.

I chose the MIT License for I couldn't choose the Unlicense "license".

The reason for that is... It's just not "reputable" enough to be considered as a "license" by some countries and some people.

Every license in the repository that I can see has your name, does that mean that you own our code inside of it?
-- You may ask that again.

I am only the maintainer and creator of this here repository.

You may substitute your name on the license on the header of your submitted file.

I do not literally "own" the code (except if I am the author of it), I just maintain them.

In other words, you are still the "author" of your submitted code, I'll just maintain them for the future.

I'm still the "author" of my code? Does that mean that I can do anything with it? Like, say... delete it?
-- Can feel the heat now.

Yes, you are still the "author".

You can do anything with it as long as I approve of it.

You can see me as the "maintainer" as the second safety lid on your "self-destruct" button.

If you would want to delete it, think about it for a moment, many others may still be relying on your code.

If you have a say on this, just add your comment below!