28 Nov 2023 - InnerSource SIG Meeting Minutes

[chamindra]

Date

Tuesday 28 NOV 2023 - 10:00am EST / 3:00 UK/UTC

Attendee Identity

Please identify yourself when you attend the meeting by providing your name and affiliation in reply to this thread. Alternative we will need to add you here if you do not have a Github id

• 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 [email protected] 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 FINOS Slack InnerSource SIG Channel - https://finos-lf.slack.com/archives/C01SYB503QT
• Update on License Generator and next steps on development - https://github.com/finos-labs/innersource-license-generator
• Update on site updates
• AOB, Q&A & Adjourn (5mins)

Decisions Made

• Decision 1
• Decision 2
• ...

Minutes

Action Items

• Action 1
• Action 2
• ...

Zoom Details

• https://zoom.us/j/97717618541
• Meeting ID: 977 1761 8541
• Passcode: 878599

Join by phone

Find your local number: https://zoom.us/u/adJnH9JOiY

Mailing List

Email [email protected] to subscribe to the InnerSource SIG
mailing list.

[robmoffat]

Rob / FINOS 🍌

[katnovakovic]

Katrina Novakovic - Citi

[chamindra]

Hi :wave Citi

[miguel-capitao-db]

Miguel Capitao - DB

[robmoffat]

• Went through notices
• Focusing today on License generator

BI: We should publish our talks in the FINOS blog.
RM: happy to write this up and publish today.

License Generator

CdS: Lots of refactoring on the license generator recently. Territory clause still to do. Functionally, you can take the code as-is and modify internally the license clauses.

At the moment, the clauses (e.g. https://github.com/finos-labs/innersource-license-generator/blob/main/src/license-clauses/attribution-org-project.txt) are not written by a legal team and would need legal review.

RM: Anyone in mind for this?

KN: Yes, we have someone in mind, they should be able to review soon.

CdS: Does this need a further review by IS Commons?

BI: They will need a deeper understanding of the tool for that. We’ll need to give them a clear call-to-action for the tool (especially from a legal perspective).

CdS: We have a backlog. Eventually, we need to consider deploying this. Backstage might be an option.

RM: Raised finos-labs/innersource-license-generator#19 to cover this.

MC: Backstage instance of innersource commons needs funding.

BI: can you talk about the issues on the license generator in the weekly blog,, RM?

RM: yep, will do.

Migrating to OSR

BI: Maturity matrix needs an update - we need to look through and decide about this. Just migrate over as-is.

CdS: We need get-involved, intro etc migrated over. Added content to how to contribute to the license generator on the get-involved page.

RM: Do we need open roles?

BI: I don’t think we need to nominate for 2024.

RM: I could put this in the blog article too.

Theming

RM: showed some theme mock-ups.

MF: added a comment about information architecture. Suggested changing from “Body of Knowledge” to “Handbook@”