Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

2024 Dec 3 - Technical Oversight Committee Meeting Minutes #164

Closed
10 of 16 tasks
psmulovics opened this issue Nov 22, 2024 · 9 comments
Closed
10 of 16 tasks

2024 Dec 3 - Technical Oversight Committee Meeting Minutes #164

psmulovics opened this issue Nov 22, 2024 · 9 comments
Labels

Comments

@psmulovics
Copy link
Contributor

psmulovics commented Nov 22, 2024

Zoom Info

Meeting notices

  • FINOS Project 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 project 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

Minutes

  • ...
  • ...
  • ...

Action Items

  • ...
  • ...
  • ...
@psmulovics psmulovics changed the title 2024 Nov 26 - Technical Oversight Committee Meeting Minutes 2024 Dec 3 - Technical Oversight Committee Meeting Minutes Nov 25, 2024
@psmulovics
Copy link
Contributor Author

Peter Smulovics / Morgan Stanley

@eddie-knight
Copy link
Contributor

👋 :shipit: Eddie Knight / Sonatype

@eminty69
Copy link

eminty69 commented Dec 3, 2024

Elspeth Minty / RBC

@awaiken
Copy link

awaiken commented Dec 3, 2024

ola

@chris-twiner
Copy link

Chris

@opoupeney
Copy link

Olivier / Finos

@rocketstack-matt
Copy link
Member

Matthew Bain / Morgan Stanley

@psmulovics
Copy link
Contributor Author

psmulovics commented Dec 3, 2024

@mcderk presentation on LFX tooling

  • information about events, meetings, etc
  • Insights is the analytics tool
    • contributors, commits, issues, PRs, forks, stars, etc over time
    • Each information has a definition
    • Next to this there is a list of computed information, like contributor dependency (eg bus factors); organization dependency, active days, contribution outside working hours, etc, along with leaderboards per each metric, geographic distribution, etc.
    • Definitions are well rounded - eg working with issues are considered contribution as well; so it will be a superset of the information you can get natively from GitHub
    • It has the option to include the mailgroups as well showing relevant data based on individual, organization, etc. ; this is something for the TOC to decide whether there is value to ask Kieran to add the groups
    • Multiple ways to see project velocity
    • @eminty69 sees this as a possible tool to replace l.finos.org or the popup details of the landscape
    • Separate information about project health (openSSF), and contributor diversification over time
    • Some open questions like "how affiliation is tracked?", Kieran should get back to us sometime in Q1 with the new UX to continue the discussions
    • Companies can use it for their own purposes; self hosted version might be available later
    • Action item: Get @mcderk back in Feb/March to talk about progress

@eminty96 talking about Liaison Strategy

  • Many of Kieran's tooling is useful for the Liaison Strategy; on the other hand, we want to avoid the projects feeling Big Brother is watching over
  • We should be better in area definitions, eg it is not Morphir and/or Legend, it should be generally about 'reg tech' as an area, figure out how project gravitate to each other
  • Two different representations of projects (by Colin and Rob) existed before
  • Action item: divide projects, talk to maintainers
  • Action item: set up project matrix to see collaboration opportunities; set up a dedicated session for this with Juan's help

@chris-twiner talking about project lifecycle

  • Reasonable metrics - eg an active project but one maintainer might be an issue
  • Publishing results should be after the Liaison is already in affect
  • Action item: should we have more elaborate design for project lifecycle
  • Action item: Juan to set up mtg on this

@jgavronsky sharing preview on the strategic project selection for 2025

  • TOC OKR overview and short discussion about 2025

@psmulovics

@eddie-knight
Copy link
Contributor

eddie-knight commented Dec 3, 2024

Created #167 and #168 to collect next steps and any ongoing discussion about the Project Lifecycle and Liaison topics

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants