2023-04-17 - KDB Project Call Meeting Minutes

alvin-c-shih commented 1 year ago

Date

Monday, April 17, 2023 - 9:30am ET / 2:30pm UK

// Second Monday of every month

Attendees

Fullname	Affiliation	GitHub Username
James McLeod	FINOS	@mcleo-d
Conor McCarthy	KX Systems	@cmccarthy1
Jonny Press	AquaQ Analytics	@jonnypress
Peter Gyorok	KX Systems	@gyorokpeter
Ross Duffy	Morgan Stanley	@rdffy
Alvin Shih	Morgan Stanley	@alvin-c-shih
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.
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
(5 min) Approve previous meeting minutes.
- Approved by acclamation.
(5 min) Updates on Anaconda.
- KX current discussions with Anaconda focusing on PyKX.
- Some internal discussions on how internal packages might be released.
(10 min) Module loader interoperability.
- Points raised on the call about package naming conventions:
- Not really tied to Anaconda?
- Hierarchy would be useful.
- Java package names with fully qualified domain names seem too long.
- Use of \d should be avoided since it makes it harder to copy-paste function definitions during a prod outage.
- k doesn't like underscores in names.
- KX has an internal packaging manager called PaKX.
- Intended to be pronounced "packs", but some cannot resist the urge to pronounce it "pa-KX". :-)
  - If we were to agree to "packs", then PyKX would be pronounced "pikes".
  - Seems to run counter to everything else getting "KDB" branding whereas this started as "PyKDB" and is (for) now PyKX.
- Hopefully PaKX and dep.q maintainers can sync up before the next call.
(10 min) Learning more about PyKX to inform verbose.q:
- Resources to start with:
  - https://code.kx.com/pykx/1.4/api/q/q.html
  - Not all overloads are wrapped at this time.
  - Suggestion that mutating vs. nonmutating variants should have different names or live in different namespaces.
  - https://code.kx.com/pykx/1.4/api/ipc.html#pykx.ipc.QConnection
  - https://code.kx.com/pykx/1.4/api/query.html
- Pull request for verbose.q has vestigial utility functions that should be removed.
- Historical note that the "verbose" functions were added later!
(10 min) Looking at the getData API.
- https://code.kx.com/insights/1.3/microservices/data-access/getData.html
- Mainly to enable BI tools like Tableau.
- aj / wj functionality falls under the "vertical accelerators"
- Will be largely inspired by kdbRefinery getStats:
- https://code.kx.com/refinery/server-api-guide/domain/finance/getstats.html
(5 min) AOB, Q&A, Adjourn.
- KX Con coming up:
- https://kx.com/events/kx-con-2023/
- Aaron Davies presenting on RASP and abuse of debugger primitives.
- Conor McCarthy presenting on data science functionality.
- Any CCLA follow ups?