• Minutes approved by acclamation.

Pull request for .finos.query.renameKeys[...] / .finos.query.renameCols[...]  submitted:

• https://github.com/finos/kdb/pull/23

• Request to update with support for keyed tables.
  
  • Will merge what's there and contributor will update when they face that use case.

Request for something resembling "Master Table Library" from Business Metrics.

• Allows load-balanced set of gateways to cache frequently-accessed results from the back end.
• Useful for making UI more responsive.
• Simple to create for a single process.
• Leader using async broadcast to followers is significantly more development effort.

• Existing implementation tied to BMET load balancer implementation.
  
  • All MS load balancer implementations have been langagaes other than q.  (Java / C++ / Erlang)
  • Previous meetings showed a reluctance to bring in non-q code (eg. Python).
  • -30!x "deferred response" feature from 3.6 opens the door to a pure-q load balancer.
  • See if one gets contributed.

Barclays involvement with FINOS?

• Currently not a member and has not signed CCLA.
• Discussions underway for participation with Alloy.
  • https://www.finos.org/alloy

Hard fork for "Studio for kdb+" created:

• https://github.com/finos/kdb-studio

Try to get the word out to those who've already hacked on it.

Volunteers to review / approve PRs?

Anybody interacted with the IntelliJ plugin maintainer?

• https://plugins.jetbrains.com/plugin/10894-kdb-studio

• Motion made to make Peter Gyorok and Aaron Davies provisional maintainers for Studio for kdb+ repository.
  • No one voted to oppose, so motion passed.
• Look into whether license / vulnerability scanning is already active.
• No recent NetBeans vulnerabilities according to:
  • https://www.cvedetails.com/product/34910/Oracle-Netbeans.html?vendor_id=93
• Focus will be on building the code and accepting pull requests.
• Look into the IntelliJ plugin variant later:
  • https://plugins.jetbrains.com/plugin/10894-kdb-studio

RFC for more featureful q IPC protocol?

• Requirements for encrypted "data in motion"?  (Cloud.)
• Standard way for client to authenticate the server?
• Piggyback on some existing protocol?

• Existing protocol supports SSL:
  • https://code.kx.com/q/kb/ssl/
• Need to review TLS support:
  • https://code.kx.com/platform/tls/
• Protocol should support:
  
  • Reporting of connection denied vs. failed.
    • This ambiguity is confusing for load balancers.
  • Two-way handshake.
    • Negotiate strongest common encryption protocol.
    • Client given means to authenticate the server to prevent man-in-the-middle attacks.
• Morgan Stanley has compiled a wish list.
  • Will need some updating before publishing on FINOS GitHub.

Anyone played with QDoc?

• https://code.kx.com/developer/libraries/documentation-generator/

Gaining traction in your neck of the woods?

Retire finos/qdoc?

• https://github.com/finos/kdb/tree/master/qdoc

• No strong feelings about retiring finos/kdb/qdoc .
  
  • Leave it for now.
• Kx Analyst has been conveniently packaged within MS.
  • Will see how much uptake there is of Kx qDoc over time.

• Should check in with the AquaQ folks at some point.