4 February 2026 — Minutes

[atomizable]

OpenRiak Monthly Meeting Minutes

Date: February 4, 2026

---

Attendees

• Adrian Fraiha
• Alistair Woodman
• Amos King
• Andriy Zavada
• A.G. Madi / George Madi
• Lee Barney
• Martin Sumner
• Nicholas Adams
• Peter Clark
• Ted Burghart
• Robert Carbone

---

Agenda Overview

1. Performance Testing
2. Observability & Tooling
3. Security Updates
4. Interoperability & Integration
5. Awareness & Outreach
6. Features & Development
7. Documentation & Training
8. Cadence & Concordance
9. Old/New Other Business

---

1. Performance Testing & Release 3.4

• 3.4 Release Status:

  • Released on January 10, 2026.
  • Outstanding tasks include updating the OpenRiak.org website to feature the latest release.
  • Action Item: Martin to finalize a funding proposal for performance testing infrastructure.

• 3.4.1 Progress:

  • Targeting a March 2026 release.
  • ~10 issues remain unresolved; volunteers needed to address these.
  • Action Item: Peter Clark volunteered to address CLI-related issues.

• Long-Term Goals:

  • Discussion on simplifying partition IDs by removing unnecessary zeros and reducing overhead in hash functions.
  • Migration to smaller partition IDs tabled indefinitely due to complexity and low priority.
  • On ZEROS Problem...
    -Regarding the ZEROS Problem-1
    -Regarding the ZEROS Problem-2

---

2. Observability & Tooling

• Client Discussion:
  • Challenges in aligning APIs (Http vs. protobuf) and transitioning to Cowboy for Http/2 support.
  • Proposal to integrate OpenTelemetry (Otel) for observability.
  • Action Items:
    • Draft a feature proposal for Otel integration.
    • Investigate Cowboy migration for Http/2 compatibility for OpenRiak 4.0

---

3. Security Updates

• TLS/Certificate-Based Authentication:

  • George Madi is merging updates to enable TLS and certificate-based authentication for Http APIs.
  • Thank you George! Updates expected by the end of the week.

• Security Features Evaluation:

  • Existing security features (e.g., user-based permissions) are inconsistent across APIs.
  • Proposal to rename "usernames" to "service accounts" for clarity.
  • Action Item: George to finalize security updates and align documentation with upcoming changes.

---

4. Interoperability & Integration

• Meetups:

  • Tokyo-based OpenRiak meetup established, with monthly events planned.
  • Future plans include hybrid (online/offline) events and collaboration with other open-source communities like OpenSearch.
  • Action Item: Explore hosting meetups in other regions (e.g., US, Europe) and sharing resources across global groups.

• Client Development:

  • Efforts focused on creating a single "example" client to serve as a template for additional language integrations.
  • Action Item: Nicholas Adams to lead interoperability discussions and resource allocation.

---

5. Awareness & Outreach

• Social Media Strategy:

  • Members encouraged to engage with OpenRiak-related content on LinkedIn and other platforms.
  • Ongoing efforts to promote OpenRiak training certifications and workshops via social media.

• Events:

  • Plans to integrate OpenRiak events into IETF calendars for better visibility.
  • Idea: Monthly meetups will follow themed topics (e.g., clustering, next-gen replication).
  • Well planned events can engage with each other over online to carry thread of progress through the month

---

6. Features & Development

• No Chair Identified:
  • A call for volunteers to lead this working group remains open.
  • Focus will be on prioritizing feature requests and aligning community contributions with project goals.
  • Features are currently being delegated into main 7/8 sub-working groups - this handles overflow

---

7. Documentation & Training

• Training Courses:

  • A successful training course on clustering and replication was conducted, with participants receiving certificates of completion. — 🎊 —
  • Future Plans: Develop additional training materials and expand certification offerings.
  • OpenRiak_Meetup_Tokyo_UserGroup

• Documentation Updates:

  • CLI documentation is being updated to align with actual command outputs and include examples of success/failure conditions.
  • Ongoing work to review and rewrite outdated documentation.
  • Action Item: Peter Clark will to continue to lead documentation updates.

---

8. Cadence & Concordance

• Meeting Structure:

  • Monthly meetings will continue to follow the officer report structure.
  • Chairs are encouraged to schedule "office hours" for their respective domains to engage with new contributors.
  • These will be broadcast on calendar so there is overflow.

• Action Items:

  • Robert will establish ability to share calendar for OpenRiak events and working group meetings on EEF website.
  • Robert will pilot a code reading meeting as office hours for contributors to familiarize themselves with the codebase.

---

9. Other Business

• 3.4.1 Release:

  • Targeted for shortly after March 4th, 2026, pending validation and resolution of outstanding issues.
  • Action Item: Volunteers needed for unresolved issues

• Experimental Features:

  • Discussion on enabling experimental configuration options (e.g., modular hash functions, open API integration) for future releases.

• Mentorship Program:

  • Proposal to establish a mentorship program to onboard new contributors and provide guidance.

---

Action Items Recap

1. Performance Testing:

   • Martin to draft a funding proposal for testing infrastructure.
   • Volunteers needed for 3.4.1 outstanding issues.

2. Observability & Tooling:

   • Draft an Otel feature proposal.
   • Investigate Cowboy migration and its impact on Http/2 support.

3. Security:

   • George to finalize TLS/certificate-based authentication updates and align documentation.

4. Interoperability:

   • Nicholas to lead client development discussions and organize regional meetups.

5. Documentation & Training:

   • Peter and James to continue CLI documentation updates.
   • Expand training materials and certifications.

6. Awareness & Outreach:

   • Promote OpenRiak content on social media.
   • Integrate events into shared calendars for increased visibility.

7. Cadence & Concordance:

   • Schedule guided tours of large features/branches.
   • Establish office hours for working group chairs.

---

Adjournment

• Meeting adjourned with plans to reconvene next month per usual
• Have a wonderful February everyone! 😉

---

NEXT MEETING:

• March 4th, 2026, - 4:00 UTC —
• 6am PST 9am EST 2pm GMT (UK) 11pm JST