Legal Team/Minutes/2016-12-22

Attendees

• Paul Madick
• Dennis Clark
• Brad Edmon
• Mark B - Juniper

Agenda

1) Review licenses still "under review" on list: https://docs.google.com/spreadsheets/d/11AKxLBoN_VXM32OmDTk2hKeYExKzsnPjAVM7rLstQ8s/edit?pli=1#gid=695212681

• see notes for LPG-Bolivia-1.0 and Unicode licenses in spreadsheet (to add)
• discussed Net-SNMP and corresponding question as to BSD-3-Clause with additional Sun clauses:
  • this is a stack of licenses with 6 parts, that includes repetition of BSD-3-Clause, MIT_CMU, and a variation of BSD-3-Clause with additional info at the top (Sun variation). Should we add this as a license stack or rely on license expressions to identify? If the latter, then we'd need to either add BSD-3-Clause-Sun variation or use LicenseRef for that part.
  • People do reproduce this as is, project includes file-level references to full stack in a copying file for recent versions, easier to identify for very common project. This would require matching as a whole. If added as a whole, would we want to add a note that license expressions could also be used?
  • Does adding as a whole undercut automation and use of license expressions? does this cut against or complicate automation for license detection, use of license expression, and otherwise introduce duplication?

Decision: confer with tech team on this: what is tooling perspective on adding this license stack versus not? is it helpful to add it or does that not add value from a automation/tooling perspective?? (inclination to not add as stack and rely on license expressions - see below re: Sun BSD-3-Clause notes also)"

2) Timing of 2.6 release of license list: will release in first week of January to Git repo. Switch over to Github as master will happen end of January, so this will ensure everything is current before that happens.