05 DEC 2022 - InnerSource License Working Group Meeting #3

chamindra commented 1 year ago

Date

Monday 05 Dec 2022 - 11:00am EST / 4:00pm UK

Untracked attendees

Katrina Novakovic, Citi
Schlomo Schapiro

Meeting notices

FINOS SIG Leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.
All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.
FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.
FINOS SIG meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[x] Convene & roll call (5mins)
[x] Display FINOS Antitrust Policy summary slide
[x] Review Meeting Notices (see above)
[x] Approve past meeting minutes https://github.com/finos/InnerSource/issues/76
[x] Review FINOS Slack InnerSource SIG Channel - https://finos-lf.slack.com/archives/C01SYB503QT
[x] Review Actions from last meeting
- MD file creation - Chamindra - https://github.com/chamindra/InnerSource/blob/master/docs/licenses/clauses.md
- Results from reaching out to different orgs on org licenses / contracts - Katrina, Peter, Chamindra
- Adding of everyone in last meeting and those interested in OSPO to DL - James
[x] Review base MD file created to capture License rights / clauses
[x] Have an initial look into the CC license generator code https://github.com/creativecommons/chooser
[x] AOB, Q&A & Adjourn (5mins)

Action Items

[ ] Tidyup clauses.md with feedback during meeting - Chamindra
[ ] Open issue on clauses.md to get further offline feedback - Chamindra
[ ] Provide input on clauses - All
[ ] Schedule more detailed session on DB Inner Source license - Katrina

Minutes

We reviewed the high level clauses of the inner source license
- Feedback was provided by the working group and this was committed to the .md file in short form
- Further tidy up will be done by Chamindra on the clauses and feedback
- It will be subsequently published as an issue for further discussion
Katrina had reached out to Schlomo who had be instrumental in publishing the Deutsche Bahn (DB) Inner Source license to inner source commons. DB is a license for a German multinational in the transport sector
Schlomo provided the background of the DB Inner Source license however we ran out of time to go through the clauses in detail.
- DB is an example of an active inner source license that is being used, examples of which was requested at the last meeting
- We will look to schedule a subsequent session to go through the detail clauses and background for them.
Key items discussed/added around clauses
- Consider boundary conditions on mergers and aquasitions
- It is not just source code that needs to be considered, but also documentation, CI/CD and issues around product
- There might be additional data seperation walls (if data is in code) that need to be considered
- Identifying an Authorizing body in the license to handle policy and exceptions might be valuable
- Export restrictions on territories (e.g. encryption and data as code)
- Potential of having a copyleft clause in the inner source license as DB, which them mentioned encouraged sharing due to attribution
- Certain clauses might not be enforcable by law, however this is the case for any software license (e.g. GPL, Apache)
- Having a license for inner source can reuse existing compliance processes that exist for adopting open source and COTs licenses
- There is still a discussion if we need to create a base license (building off the DB work) or a license generator