2021-12-13 - KDB Project Call Meeting Minutes

[alvin-c-shih]

Date

Monday, December 13th, 2021 - 9:30am ET / 2:30pm UK

// Second Monday of every month

Attendees

Fullname	Affiliation	GitHub Username
James McLeod	FINOS	@mcleo-d
Peter Gyorok	Morgan Stanley	@gyorokpeter
Alvin Shih	Morgan Stanley	@alvin-c-shih
Dmitry Zakharov	Deutsche Bank	@dzmipt
Aaron Davies	Morgan Stanley	@adavies42

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

• (5 min) Convene, roll call, welcome new people.
• [x] Display FINOS Antitrust Policy summary slide
• [x] Review Meeting Notices (see above)
• (5 min) Approve previous meeting minutes.
  • Approved by acclamation.
• (10 min) Updates on CLAbot and labels?
  • Multiple FINOS projects have been migrated to Linux Foundation EZ CLA bot.
  • Wait until FINOS kdbProject before investing too much thought into this.
  • Some documents may need re-signing for this to happen.
  • Can change the background colors of labels on GitHub.
  • Light gray would be unobtrusive for default color scheme.
  • One caller asked about dark mode.
  • Could pick a medium gray that is a compromise.
  • Another caller asked what it means to not be covered by a CLA.
  • Lack of CLA means contributor retains intellectual property rights and code could pose legal problems to consumers.
  • Admin can override, but should not.
• (5 min) Updates on kdb Boothroyd?
  • FINOS Perspective looking for ways to get integrated into other projects.
  • Worth a discussion with Boothroyd team.
  • For Perspective to be integrated into kdb Studio, would need help.
  • No one on the call has experience integrating an HTML5 widget into a Java Swing application.
• (15 min) Updates on kdb Studio (FINOS / dzmipt)?
  • CLA for dzmipt?
  • Some administrative matters taking time at employer.
  • Seems to have to go-ahead for an ICLA.
  • RSyntaxTextArea onboarding challenges?
  • Scanning tool blocked it, but got manual approval.
  • Someone noticed that the license file is buried in the directory structure.
  • GitHub "About" box and other tools look for it at the top level.
  • Will submit a PR to maintainer to fix that.
  • Building / reformatting dzmipt branch?
  • Successfully built.
  • Any significant unification work will have to wait for the ICLA to be executed.
• (5 min) Volunteers for documenting kdb Studio / Boothroyd / modules?
  • FINOS has done a commendable job engaging software developers.
  • Can they also engage Business Analysts and Technical Writers?
  • Something to bring up at a future board meeting.
• (10 min) Clarification of FINOS / Linux Foundation overlap?
  • CCLA is with FINOS.
  • FINOS CCLA does not automatically result in a CCLA with Linux Foundation.
  • Would need to sign a new CCLA to contribute.
  • Linux Foundation projects that might be of interest to FINOS members:
  • Cloud Native Computing Foundation is part of the Linux Foundation and has a Financial Services working group.
    • https://cncf.io
  • HyperLedger is also affiliated with the Linux Foundation
    • https://hyperledger.org
  • A few callers agreed that one CCLA across the entire Linux Foundation would simplify things and open the doors to wider participation.
  • See if representatives from LF Legal can join the upcoming FINOS All-Community call.
• (5 min) AOB, Q&A, Adjourn.
  • FINOS All-Community call coming up late January / early February.

Action Items

• @mcleo-d to organise meeting with Perspective and @ColinEberhardt to understand how Perspective can be integrated into KDB and potentially Boothroyd.
• @mcleo-d to work with @dzmipt on signing an ICLA following internal DB discussions.
• @mcleo-d to follow up on the following licensing issue ... https://github.com/bobbylight/RSyntaxTextArea license last good: 3.0.4 first bad: 3.1.0
• @mcleo-d to propose a FINOS All Community talk on how the FINOS community can navigate The Linux Foundation, including CLAs and what is transferable.

WebEx info

Webex

• https://finos.webex.com/finos/j.php?MTID=me61719ca3c3295a7cc76762d78392bc3

Dial-in and Project Materials

• US: +1-415-655-0003 US Toll
• UK: +44-20319-88141 UK Toll
• Access code: 2704 417 0390
• GitHub Repos:
  • https://github.com/finos/kdb
  • https://github.com/finos/kdb-studio
• Wiki Page:
  • https://finosfoundation.atlassian.net/wiki/spaces/DT/pages/329383945/kdb+Project
• KDB Metrics on FINOS
  • https://metrics.finos.org/goto/033b15c80f0d08cab70f40f4358932f6

[mcleo-d]

Hello 👋🏻

[dzmipt]

Hello!

[gyorokpeter]

Hi

[alvin-c-shih]

Howdy!

[adavies42]

Hi

[dzmipt]

QQ: re license... how license check happened? I would suspect that it should be started from maven central (from which the binaries are taken). And it looks there is a license section in both RSyntaxTextArea 3.0.4 and 3.1.0: https://search.maven.org/artifact/com.fifesoft/rsyntaxtextarea/3.0.4/jar https://search.maven.org/artifact/com.fifesoft/rsyntaxtextarea/3.1.0/jar

[dzmipt]

and w.r.t. github webpage - it is really checked a LICENSE file in the root (here are some description: https://docs.github.com/en/communities/setting-up-your-project-for-healthy-contributions/adding-a-license-to-a-repository) and i tested how it would look like if the file would be in the root: https://github.com/dzmipt/RSyntaxTextArea