3 September 2025

[adkron]

3 September 2025

Roll Call

• George Madi
• Adrian Fraiha
• Nicholas Adams
• Ted Burghart
• Peter Clark
• Martin Sumner
• Dan Janowski
• Jonathan Männchen
• Robert Carbone
• Andrei Zavada
• Alistair Woodman
• Amos King

Agenda

• TODO from previous meeting - https://github.com/orgs/OpenRiak/discussions/27 (I think this will be mainly wrapping up on the build/GHA updates).
• Schedule follow-up calls on 4.0 proposal discussion (probably one for data-types and one for other proposals).
• Go through outstanding actions for 3.4 (I've experimented with GH projects for tracking the last few outstanding items - https://github.com/orgs/OpenRiak/projects/3/views/2)
• AOB -
• Public visibility of work being done

Old Business

Build

• Spoke with build and packaging, and it was suggested to use GitHub Actions.
• Include an AWS build
  • use AMI
  • AMI tabled until un-tabled up by Peter/Nicholas

"Big companies tend to want to download & install, not build"
"Prebuilt OTP would be amazing"

Data-Types/Structures (CRDTs)

*Special Meeting to be held in one weeks time: Wed Sept 10 '25 - 9am EST (7am PST, 10pm Japan)

New Business

3.4 Release

• Kanban board
• No client changes in 3.4

4.0 Release Plan

• If we can make items go dark in 3.4, we don't have to worry about updating their documentation.

Proposals

• Data types discussion - plan to meet next week
  • Someone doing CRDT work in Riak
• Get deprecation warnings out for things being taken away as soon as possible.
  • Announce them
  • Add to 3.4 release somehow
  • Add to 3.4 release notes
• Tiered Storage - delay discussion
• In-memory buckets - delay discussion
• TTL via Bucket Property - delay discussion

Public Visibility and Attracting Contributors

Types of Ecosystem Participants

• Rookie/Expeditious : API users who don't care about anything under the covers.
• Developer / Growth: People who want to be able to offer code support & add features to Riak.
• Large Companies: Large companies with 100s of nodes
  • Those companies should fund features that they want to have.
  • Rather than SBOM, think FBOM (Feature Bill of Materials)

Documentation

We need a a standard standardization we can stand and understand

• Discussion on what is the ultimate source of truth Cuttlefish isn't it

Perhaps:
- big_JSON_blob...
- @tag
- Category
- What is this feature that is being referenced...
Operational CRDTs may assist with versioning
- functions that give alerts to assist consistency between docs & actual settings...

Peter: Next / Structure an interim plan for Docs / Interim Review Process

General Discussion

TODO - Next/Actions

• Dan Janowski and Nicholas Adams to figure out AWS AMI
• Data Types 9:00 AM EST (7:00 AM PST, 10::00 PM Japan) on Wednesday, 10 September 2025 - meeting