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.)

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.

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, Decentralized Ecosystem Growth Program 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.

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.

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

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.