I was looking at the Blinky sample and noticed it’s labeled “Public Domain” at the top. While this is the least restrictive way to license something, it (counterintuitively) makes it harder for people to contribute updates and/or patches.
For example, I work for Google and we have specific rules about which repos we can contribute to. Generally speaking, all of the standard open source licenses explicitly grant three specific rights: reproduction, modification, and distribution.
Here’s the counterintuitive part: Public domain and other unlicenses could lead to copyrighted versions of the same work. Shakespeare’s Romeo and Juliet is in the public domain, but a specific production’s script (with language edits, stage blocking, etc.) is a freshly copyrighted work.
I’d love to contribute patches (e.g. to make the web IDE work better on smaller screens), but can’t do that unless the work is licensed using a recognized open source license: Apache 2, MIT, ISC, etc. All of these ensure that the code remains open for everybody to contribute changes and use the code on an equal footing.