2018-12-05 kdb+ WG Minutes

2018-12-05 kdb+ WG Minutes

Table of Contents

Date/Time

  • December 5, 2018. 11am ET

Attendees

Name

Organisation

Name

Organisation

@Alvin Shih

Morgan Stanley

@Rob Underwood (Deactivated)

FINOS

Jason Foster-Bey

JP Morgan

Sam Eberspacher

(individual)

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)

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

OSR.  Updates on access to GitHub / Atlassian?

 

Jason: JPMC blocks http://atlassian.com .  Jason will try from his laptop.

Alvin: Administering Google Groups?  If I try my work email, it tells me, "Couldn't find your Google Account.".

@Rob Underwood (Deactivated): Suggested emailing help@finos.org and CC @Maurizio Pillitu with any blockers.  (Update 2018-12-27.  Have to administer through help@finos.org for now.)

5 min

Discuss suggested kdb+ WG roadmap emailed by Sam on 2018-11-29.  Any volunteers to maintain that as a Wiki page?

All

Sam: Will put the expanded charter and roadmap the Wiki based on what he'd emailed to data-tech-kdb ahead of the meeting.

Sam: Doesn't think we should be in the business of picking winners and losers.

Alvin: Is editing of the charter / roadmap on the Wiki a voting item?

Rob: Doesn't think so.

15 min

kdb+ WG participation.  What about kdb consulting firms with open source code bases?  DEVnet (Exxeleron) or AquaQ (TorQ)?

All

Alvin: Do participants in FINOS have to be members?

Rob: Anyone with a signed ICLA can participate.  Membership confers different benefits such as proposing new programs and voting.  For example,  will be led by Clovyr which is not a member.

Sam: Will try to get Ryan Hamilton of TimeStored in touch with Rob.

Sam: We should document our efforts to build community, do reach outs.

Jason: Reached out to Igor at RBC regarding kdb+ WG, but he's been keeping a low profile.  Try to increase participation by having multiple representatives from the same organization?

Alvin: Curation / gating of code?  What if there are divergent opinions on direction?

Rob: Up to the "committers" to deny pull requests.  Working Group lead decides who the committers are.

15 min

How to get more code out there?

 

Rob: Citing "First 90 Days", he'd like to see something attention-getting made available.

Sam: When we work on fundamental areas, like module loader, can get tricky to navigate it.

Alvin: A bit of a chicken and egg problem.  A couple of ideas: default security handlers, dbmaint.

Alvin: How to put the documents / code out for evaluation?  Perhaps a "contrib" / "incubator" area.

Rob: Should have a call with Maoo about a repo for ad-hoc contributions.  Probably by function rather than by company.

Alvin: Should "work in progress" get merged into master to make it easier for interested parties to see what people are working on, albeit in rough form?

Rob: Discoverability of work in progress subordinate to keeping a level of quality on master.

Jason: Agrees with Rob.  Suggests that README.md points to branches / forks for those who want to get involved with code that's not ready for wide consumption.

Sam: People can fork his fork to fix up things like namespacing, etc.

Rob: GitHub users who aren't on a CCLA won't be able to pollute the fork.  There's a bot that checks.

10 min

Discuss namespace recommendations as emailed by Sam on 2018-12-04.

All

Sam: Java's "strongly opinionated" about namespaces and possibly too verbose.  His emailed proposal assumed that q does not provide an aliasing mechanism to allow multi-component names to be shortened to something more manageable.

Alvin: Replied to the email showing how aliasing can be implemented in q.

5 min

AOB

All