Do we need a LICENSE for this repo? And if we do, which one?

[qobilidop]

As @Dscano shared in #55 (comment), p4lang has a software license guidance. This repo will have some code for setting up the blog publishing infra, as added in #55. So:

• Question 1: Do we need a software license for this repo given that there will be very little code?

Most of the contents of this repo will be documentation. So:

• Question 2: Do we need a documentation license for this repo? If we do, which one to use?

Ping @Dscano @fruffy @jafingerhut @asl for discussion and suggestions. Thanks!

[fruffy]

Simple rules of thumb: All P4Lang repositories use the Apache 2.0 license. Anything we merge should be compatible with this license. MIT, BSD 2.0/3.0 are usually fine. GPL is not. We can add SPDX identifiers to the headers, if desired, but it is optional.

[qobilidop]

@fruffy Thanks for the clarification! Question 1 is clear then. I'll take care of adding the proper LICENSE file.

What about question 2? Do we need an additional documentation LICENSE like CC (Creative Commons)? I have some experience using it in one repo: https://github.com/google/cairn/blob/main/LICENSE-docs.

[fruffy]

What about question 2? Do we need an additional documentation LICENSE like CC (Creative Commons)? I have some experience using it in one repo: https://github.com/google/cairn/blob/main/LICENSE-docs.

I am not aware of any such requirements. We follow the LF licensing policy these days: https://www.linuxfoundation.org/blog/how-open-source-foundations-protect-the-licensing-integrity-of-open-source-projects.

We did not introduce CC for the P4 compiler documentation project either. @jafingerhut did you look into this at some point?