Date/Time

April 1, 2019. 11am ET

Attendees

Name	Organisation

Name	Organisation
@Alvin Shih	Morgan Stanley
Aaron Davies	Morgan Stanley
Alok Dutt	Citi
@Rob Underwood (Deactivated)	FINOS
Peter Gyorok	Morgan Stanley
Jason Foster-Bey	JPMC
Latchezar Nikolov	Morgan Stanley

Action Items

Tasks Identified and Assigned

Alok to reach out to BAML and GS

@Alvin Shih to send out conventions that get used for qualifying names.

Task Report from the Last Meeting

(In the task report select the meetings notes from the LAST meeting in the 'Space(s) and page(s)' field to auto-populate this table– remove this note before publishing)

Decisions Made

Agenda

Time	Item	Who	Notes from the Meeting

Time	Item	Who	Notes from the Meeting
5 min	Convene & roll call.	All
5 min	Review and approve minutes from last meeting.	All	Approved by acclamation.
5 min	FDX (FinServ Developer Experience). Check with new joiners whether they're getting data-tech-kdb emails.	All	No concerns for people on the call.
10 min	Discuss updated FINOS Meeting Minutes Policy. Sections worth particular attention are: "Minutes only need to include essential information." / "Permission is now required for attribution.". Do "TODOs" become anonymized as well?	All	Although a few voiced a preference for attributions in the minutes, the kdb+ WG will give the updated policy a try. @Rob Underwood (Deactivated) reminded us that: Votes need to be recorded. Meetings must be public to assuage any antitrust concerns.
10 min	Review 2019 Roadmap for kdb+ Working Group (Draft).	All	Some discussion about the roadmap: Adopting open source can be a challenge, particularly in Prod. Even changing logging format slightly can cause problems. As senior leaders for kdb in our respective firms, we should be driving adoption. Try out / introduce libraries in "research" code. Hedge funds are clients of banks and standardized code can make conversations easier. Roadmap should include more context about what "enterprise kdb" means.
5 min	Pull request for qdoc is up on the incubator-qdoc branch.	All	No one has had a chance to look at it yet.
5 min	structlog as a model for kdb+ logging framework? Any volunteers to try it in their day-to-day coding and report back? Can the HDB utilities use some provisional logging API to allow forward progress?	All	No one familiar with structlog. Someone will give it a try.
5 min	Default security handler API. Comments on the latest email?	All	Clarifications: authz_ro does not handle fine-grained entitlements. Provides a mechanism for funneling users into function call APIs (aka. stored procs) which could enforce more complex entitlements. q treats callbacks over sockets as though they came from unauthenticated users. To allow them to use eval / reval, add ` (null sym). Gateways often don't have valid .z.u either. Better to deal with that through whitelisted functions. One member said that standardizing security APIs would be a "big deal" for the various kdb-using teams in his company.
5 min	Command line parsing API? What do folks think?	All	Discussion to continue on the data-tech-kdb mail group.
5 min	AOB	All

2019-04-01 kdb+ WG Minutes

Table of Contents