Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

Table of Contents

Date/Time

  • August 5, 2019. 11am ET

Attendees

NameOrganisationGithub ID 
Rob Underwood (Deactivated)FINOSbrooklynrob
Aitana MyohlFINOS
Alvin ShihMorgan Stanleyalvin-c-shih
Peter GyorokMorgan Stanleygyorokpeter
Alok DuttCiti
Kai ZengUBS

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)

DescriptionDue dateAssigneeTask appears on
  • Asking about license for developers
2018-09-05 kdb+ WG Minutes
  • Decision - How to make use of the Kx/Kdb naming space in a consistent way across firms
2018-09-05 kdb+ WG Minutes
  • Share sample tests, configurations, in part to start to create guidelines for naming (on-going task as working group stands up)
2018-09-05 kdb+ WG Minutes

Decisions Made


Agenda

TimeItemWhoNotes from the Meeting
5 minConvene & roll call.

All


5 minReview and approve minutes from last meeting.AllMeeting minutes for 7/1 meeting were approved. 
15 minCode languishing on "incubator" branches. Should we have a policy or merging to master if no opposition for 2 months?  (Not like we'd be breaking any Production code.)All
  • No objections to merging to master a couple of items that have been sitting there for 2+ months.
10 minauthz_ro needs to reject lambdas / verbs.  Do we want to expose an API that registers a predicate for selected whitelisted functions to be more relaxed?  Or just one global argument checker?All
  • Leave the current signature to apply more restrictive checks on the argument types.
    • Don't want default implementation to be too heavy as it could create performance bottlenecks.
  • Provide another function to register a whitelisted function with custom argument checker that may be more relaxed.
  • UBS might be able to contribute test cases.
    • Try to get UBS participants onto Symphony chat to facilitate further discussion.
5 minFeedback on "include" and "InitHook"?All
  • A couple of callers said they'd try to take a look.


5 minFINOS has merged the idea of "Working Group" with "Project".All
  • It's a labeling thing that will not have impact on the day to day activity of kdb+
  • Call for opinions on changing or updating the project's name.
    • It was decided to keep the name as "kdb+ Project" for now.
5 minWays to help get the word out about kdb+ FINOS Project?All
  • Marketing materials (e.g. baseball cards) to distribute at meetups.
  • Some liked the idea of keeping the group small to start.
  • See if anyone in FinTech startups or kdb consulting are interested.
5 minAOBAll
  • Question: is there any Data Science work being done in any FINOS projects?
    • Not currently.

Action Items

  • Jason Foster-Bey to start follow-up thread re:structlog
  • Aaron Davies to send out HDB consistency doc.
  • Peter Gyorok to put "include" on GitHub.
  • Alvin Shih to put together qstructlog PoC.
  • Aaron Davies to get Symphony access to discuss authz_ro with Jason Foster-Bey.
  • Aaron Davies to get approvals for pushing kdb+ WG-related work to GitHub.
  • No labels