mrutkows opened a new issue #871: Create Markdown describing LICENSE file 
creation process
   We need to capture our own rules/policies, conventions and procedures for 
creating LICENSE file for any repo. under the Apache OpenWhisk project.
   It should include how we handle well-known exception procesess (e.g., 
copy-left, etc.) with examples for MIT/Google, etc, type licenses, as well as 
create a TEMPLATE file that has sections to fill out that includes (our 
   - Link back to the process page (that I am suggesting we create using this 
   - Sections for 1) listing source LICENSE exceptions 2) listing Binary file 
   where the "binary" exception list clearly states "these are binary library 
dependencies" that we do not copy into source and do not alter the code for.
   Also, each license we list or copy should have a clear SEPARATOR, for example
   So readers can easily see where one license stops and another starts (when 
they are copied in by requirements).

This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:

With regards,
Apache Git Services

Reply via email to