Clarify / clean up copyrights

[payne92]

Per tweet from @unwind

[unwind]

Great to see this ticket being opened. What I meant, as I recall, was that it's a bit unclear what copyright applies to the bare-metal-arm code. It's optimally structured to work as a starting point for projects on the FRMD board, but does that mean @payne92 has copyright to such projects?

I guess one idea would be to separate out the "bare-metal-arm" part into something even more bare, then add back the "demo project" parts that make it do something on the FRDM board into something that can be replaced by other projects.

Am I making sense?

[payne92]

Are you asking about copyright or license?

For license, it's my intent to make this widely available, and I chose the MIT license for that reason (and I clarified the LICENSE file). The MIT license is simple, and highly permissive.

For copyright, it's common in open source projects for the author to state the copyright, then transfer the rights with the license. For example, see the Python README, claiming copyright: https://github.com/python-git/python/blob/master/README

Does this make sense? I'm glad to tweak things if there's something blocking you from using this.

[unwind]

Yes, that sounds great! I guess I didn't understand that the license was MIT, that's a very good (and generous) choice for a project such as this.

I'll need to check up on how the copyright transfer works out, but it sounds as if you're aiming for a licensing solution that simply allows the project to be used as a starting point for "third-party" projects, which is great!

Thanks.