Create policy on license headers about dev-docs HOT 6 CLOSED

Add:

• For imported libs. (or files or tools) that require attribution via license, need to document how that these are license files are copied/posted in a subdirectory structure under project root. Will document according to accepted process at other OSS foundations.

I will make a pass today to submit a PR for the libs/tools we already reference in both requirements.txt files...

from dev-docs.

@russellb FYI, i created a scan-tool used an Apache foundation we used to lint the things you listed originally (i.e., license headers or one-liner as well as checks for other things like invalid whitespace chars. (and it has include/exclude params. to skip non-source directories).

I can look to bring over if you like?

from dev-docs.

Automated license checking would be a welcome addition to me! Pending details, I'd be most interested in automatic detection of someone trying to introduce a license-incompatible dependency. I know there are other important things we could check for.

I'd prefer not to have a hard requirement on the license ID lines, at least at this stage. Later maybe

from dev-docs.

draft PR here: #17

from dev-docs.

This is in review right now and awaiting approval from legal.

from dev-docs.

Update on this is @russellb will need to do an additional follow up with legal.

from dev-docs.