Create LICENSE

[edelmanjm]

Chose Mozilla Public License because it:

• Permits use of the library in derivate works to be licensed under a different license (important for closed-source use during the build season)
• Requires changes to the library itself be licensed under the same license (ensures the ongoing health of the project)

[RobinsonZ]

Not so sure about that. More thoughts coming soon.

[RobinsonZ]

I'm not a fan of copyleft in general, and I think we shouldn't have it on ROOSTER. Most teams will (if they even use it) want to make modifications for their use case, and we shouldn't require them to explicitly fork the repo especially given that many teams straight-up don't use Git/Github.

Looking at other FRC libraries the MIT license seems to be favored, and for good reason. It's a permissive license that you don't have to worry about. I vote that we use that.

[edelmanjm]

@RobinsonZ They don't have to use GitHub, just make the changes available in some form. Admittedly GitHub is the easiest way of doing this, but they're welcome to just post file if they want. Note also that Mozilla defines the boundary as the source file: if they extend an existing file rather than modifying the original, copyleft doesn't apply. Mozilla is pretty permissive.