09 JAN 2023 - InnerSource SIG License Working Group Meeting #5

chamindra commented 1 year ago

Date

Monday 09 JAN 2023 - 11:00am EST / 4:00pm UK

Untracked attendees

Fullname, Affiliation, (optional) GitHub username
...

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

[ ] Convene & roll call (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve past meeting minutes
[ ] Review Inner Source License deep dive questionnaire (can be provided as a doc file if access is blocked)
[ ] Deep dive with Deutsche Bahn on their inner source project
[ ] Review any contributions to the clauses.md can be provided either as a pull request to https://github.com/chamindra/InnerSource/blob/master/docs/licenses/clauses.md or comments can be provided on the issue https://github.com/finos/InnerSource/issues/85
[ ] AOB, Q&A & Adjourn (5mins)

Minutes

We reviewed the questionnaire for the deep dive and initiated it's use with Deutsche Bahn
It was mentioned that many other known companies also have inner source licenses, but they are not published like Deutsche Bahn and publicly available
- The representation from DB felt a shared inner source license would be of value
Key Insight from the discussion at the SIG meeting
- Inner Source license has brand value in the organization
- It is part of the gradual process of professionalizing inner source
- Included in the license protection is application code, Devops config, data, documentation
- The inner source license is used only within the organization and not with vendors
- Licenses are well know mechanism in Open Source and a natural extension for Inner Source
- License is a tool for the expected behaviour but enforcement depends on a lot of factors including local laws
  - For example certain warranty terms are not compatible with German law
  - The license a more valuable communication tool than it is a hard legal instrument
- In particular Tax law is a key are of focus with transfer pricing as a result of inner source
- The owner of the code can be sometimes blurryP
- The use of copy left is less strong than in the open source world
- contributors get recognised directly by GIT contribution tracking
- Internal career recognition, copyleft and an element of fun are drivers for inner source
- The Inner source licenses is provided with no-warrenty but that is not the best instrument for getting support
- The governance body for the inner source license is informally the OSPO

Action Items

[x] Setup next Inner Source license WG meeting - Chamindra
[x] Tidy up clauses.MD with variations from DB - Chamindra
[ ] Look running Inner source questionnaire at Citi - Chamindra / Katrina
[ ] Seek other organisations that have an inner source license for deep dive similar to DB - All
[ ] Follow up on backstage inner source discussion - James / Andrew?