BitBake Apache License and Packaging for OpenBMC Components

[Wilfred Smith]

What is the recommended way to handle license files for OpenBMC components?

I presume that any new code committed to the repositories should be Apache 2.0 unless special permission is granted. Based on a conversation regarding creating a StackExchange forum for OpenBMC, I presume MIT/OpenBSD-style licenses are verboten without special permission.

(1) What should the license tag be? (LICENSE = “Apache 2.0”?)
(2) Should a LICENSE file be created in the root directory? A COPYING file? Should we point to a common license file? With a checksum? If so, which one?
(3) Are there particular requirements or suggestions regarding how to package stuff?
(4) I presume SRC_URI file:/// links are okay since the git links are unknown and broken until the first version is checked in.
(5) How should I handle being in a subdirectory of a repository? The code I’m checking in will go into openbmc-tools. How does that work for CI?

I’ll go scan through the docs, but I didn’t find much commentary on these topics with light skimming. Just trying to get it right the first time.

Thanks in advance,

Wilfred
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ozlabs.org/pipermail/openbmc/attachments/20190917/1325ada7/attachment.htm>