#️⃣ 7 January 2026 — Minutes

[atomizable]

OpenRiak Monthly Meeting Minutes

Date: January 7, 2026

---

Attendees

• Lee Barney
• Martin Sumner
• A.G. Madi / George Madi
• Adrian Fraiha
• Nicholas Adams
• Peter Clark
• Ted Burghart
• Robert Carbone

---

Agenda Overview

1. Performance Testing & Release 3.4
2. Documentation Updates
3. Upcoming Features & Releases
4. Governance & Subprojects
5. Working Group Status & Meeting Structure
6. Observability & Tooling
7. Security
8. Documentation & Training
9. Other Business

---

1. Performance Testing & Release 3.4

• Status: 3.4 is ready for release. Full-scale performance testing is incomplete due to lack of access to the standard test environment.
• Validation: Partial validation is being done on smaller setups; no major regressions expected.
• Testing Infrastructure & Funding:
  • Discussion on whether to fund cloud testing (AWS/GCP) or invest in hardware.
  • Funding proposals should be modest (e.g., $1,000/release).
  • Proposals with clear community benefit and "skin in the game" are more likely to be approved.
  • Hardware requirements: eight nodes, mixed/SSD ~1TB each, high throughput(10-25GBit) switch, etc. (for arm & intel!)
• Action: Martin will draft a funding/testing infrastructure proposal for the next meeting.
• Release Plan: Unless major issues are found in the next two days, 3.4 will be released without full nonfunctional test results.
• Links: OpenRiak 3.4.0 Release OpenRiak 3.4.0 Discussion

---

2. Documentation Updates

• Quick Docs: Spell check, link check, and mermaid diagrams are integrated. Docs will be available on both Quick Docs and the main repo for release. OpenRiak QuickDocs
• Man Pages: Outdated man pages (not updated in a while) will be removed for 3.4. Contributors can propose updated versions if needed.
• CLI Documentation: Work in progress to automate documentation generation from CLI commands.

---

3. Upcoming Features & Releases

• BitCask Metadata: Major storage backend changes (metadata handling) discussed; likely postponed to a future major version due to migration complexity.
• Outstanding Issues: List of issues for 3.4.1 is available; community volunteers needed to pick them up.
• Forthcoming Releases:
  • OTP 28 compatibility work ("folder io" branch) is advanced; deprecated features (DTrace, MapReduce, riak_repl, etc.) are being removed.
  • Decisions pending on LevelDB backend and riak_repl support.
  • Large set of internal patches/features being merged and reviewed, with potential for a 3.5 or 3.6 release before a full "folder io" (4.0) release.

---

4. Governance & Subprojects

• OpenRiak Control: New management/command tool discussed; will be a standalone project under OpenRiak but not bundled with the main release.
• Subproject Process: Community projects (like OpenRiak Control) should remain outside the main repo but referenced in documentation/ecosystem lists.
• Review Process: Main OpenRiak code gets full review; affiliated tools have looser governance.

---

5. Working Group Status & Meeting Structure

• Working Group: Once formalized, meetings will have more structure, with regular objective reports and possibly delegated leads.
• Meetups/Outreach: Local meetups starting in Tokyo; plans for digital participation. Phoenix-based site revamp in progress.

---

6. Observability & Tooling

• Stats Collection: Move to support Flow Nightingale for stats; distributed tracing being added (ODTL compliant but not using Erlang).
• OpenTelemetry: Considering standard output formats for easier integration with industry tools.
• Potential Redis (Valkey) Plugin: Interest in reviving a Redis-compatible plugin for OpenRiak to enable integration with tools like Databricks.

---

7. Security

• TLS and Internal Security: All security updates (including internal TLS) are ready, pending review and merge after the current release activities ease.

---

8. Documentation & Training

• CLI Documentation: Automation being developed to generate documentation from CLI commands, possibly including man pages.

---

9. Other Business

• Next Steps:
  • Release 3.4 after final validation.
  • Draft proposal for performance testing funding/infrastructure.
  • Remove outdated man pages.
  • Volunteers needed for outstanding issues in 3.4.1.
  • Plan for integrating new features
  • Continue governance and outreach efforts.
  • Next meeting to check progress on funding, outstanding issues, and integration of new features.

---

Action Items

• Release 3.4 after final validation.
• Draft proposal for performance testing funding/infrastructure (Martin).
• Remove outdated man pages.
• Volunteers needed for outstanding issues in 3.4.1.
• Plan for major backend and feature merges post-3.4.
• Continue documentation improvements and outreach.
• Schedule guided tour of large features/branches (Ted Burghart).

---

Adjournment

• Meeting adjourned with plans to reconvene next month (February 4th 2026, at the same time) and review progress on action items.

---

[sendtopms]

We are using LevelDB backend and it will be great not to deprecate it in OTP 28 compt release.

[ssantaaa47]

We are currently using the LevelDB backend, and it would be greatly appreciated if it were not deprecated in the OTP 28 compatibility release.

[martinsumner]

In the notes ripple should read riak_repl. I think "folder io" is a reference to the openriak-4.0 branch (i.e. "four dot oh").

[atomizable]

fixed 👌🏼