2018-11-07 kdb+ WG Minutes

Table of Contents

Date/Time

  • November 7, 2018. 11am ET

Attendees

NameOrganisation
Morgan Stanley
Rob Underwood (Deactivated)FINOS
Phineas DashevskyUBS
Sam Eberspacher(individual)
Alok DuttCiti
Yanni KostalasNomura

Action Items

Tasks Identified and Assigned

  • Alok to reach out to BAML and GS
  • Jason to send out information about namespace conventions.
  • Alvin Shih to send out conventions that get used for qualifying names.
  • Alvin ask Jeff Borror to review Morgan Stanley q coding standards.
  • Alvin to email out link to C++ Core Guidelines.
  • Alvin to look into one-person-one-account policy at GitHub.
  • Alvin to write about what "industrial" coding style is and why kdb WG will pursue that route.

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

New attendees to the call: Phineas Dashevsky (UBS) and Yanni Kostalas (Nomura).

5 minReview and approve minutes from last meeting.AllApproved by acclamation.
5 minFINOS updates.  "Security Reference Data" Working Group is Approved.  Data Technologies press release going out ahead of OSSF.All

Alvin : FINOS released guidelines for participants on how to indicate involvement on Linkedin.

Sam : Suggested putting roadmap for kdb+ WG on the Wiki.

15 minOpen Source Readiness.  Try to exercise GitHub access from your company and become a "watcher".  How's access to the data-tech-kdb mail group working out?All

Rob : Google group, finos-data-tech no longer requires an invite.  Interested parties can join on demand.

Alvin : Asked everyone to take a look at the GitHub pull request for "q coding guidelines".  No reports of being blocked by firewall / web proxy by any of the attendees.

Sam : Google makes its employees join its GitHub Organization to manage permissions and follow what's being contributed.

Rob : Contributors with CCLA / ICLA on file are included in a JSON whitelist that is checked by GitHub.

15 min

"q coding guidelines" pull request is up.  https://github.com/finos-data-tech/kdb/pull/1  Please review and comment there.  Discuss of comments from samiam14 and see what action items fall out.

All

Sam : Said he's fine with releasing the "q coding guidelines".  People can submit pull requests to make changes or kick off discussions on the mail group.

All : Group was in favour of JavaDoc style for internal documentation standard over anything more obscure.

Sam : Noted that RFCs have well-defined semantics around words like, "should", "recommend", "may", "optional", etc.  Suggested we codify such conventions in a "meta document" / "standards for our standards".

15 minAOBAll

Sam : Would like kdb+ WG to reach 10 regular attendees.

Alok : Curious if Kx has someone in a "community development" role who'd like to run the WG meetings.

Alvin : Hoping FINOS will add some kind of collaborative document editing to The Platform.

Alvin : Rob made an e-introduction to someone at RedHat who's in contact with Anaconda.  I sent an email asking if they know who deals with packaging of Kx artifacts, but didn't hear back.


Need help? Email help@finos.org we'll get back to you.

Content on this page is licensed under the CC BY 4.0 license.
Code on this page is licensed under the Apache 2.0 license.