Actionbase Open-source Preparation

[em3s]

TL;DR
This issue prepares the open-source launch of Actionbase, a production-proven activity data engine. The primary focus for the initial release is clear conceptual communication and seamless developer onboarding.

Purpose

This umbrella issue tracks all preparation work required for the initial open-source release of Actionbase.
The goal of the initial release is to clearly communicate the concept and purpose of the project and to provide a hands-on guide that demonstrates how to build a real service (e.g., a social media app) using Actionbase.

Note

Kubernetes-based production provisioning and other operational guides will be addressed after the initial public release.

Actionbase

Actionbase is an OLTP-based activity data serving engine used across Kakao. It supports core user-activity features - including “likes” and “recently viewed” - with low-latency storage and retrieval. It can also be used for activity-driven services such as recommendations, feeds, and timelines. Actionbase is a production-proven platform operating reliably at scale.

Tasks

1. Chore

• Initialize .gitignore with Java, Kotlin, Gradle, and Go rules #5
• Update README for initial release #7

2. Hands-on Guide & Developer Experience

• 1. Provide a local development environment
  • Minimal local run scripts #35
• 2. Add a hands-on guide for building a sample service with Actionbase
  • Add initial Actionbase CLI #2
  • refactor(engine): Engine/TableBinding 통합 — QueryEngine 제거 #3
  • Initial trials merged; follow-up improvements in Implement Initial Hands-on Guide and Improve Onboarding Experience #29
• 3. Initialize the documentation website and link it to actionbase.io
  • Initialize the documentation website #6
  • Add CNAME for the custom domain actionbase.io #4
• 4. Add a top-level architecture overview (modules, directory layout)
  • added to README.md
• 5. Add a minimal CI pipeline (build, test, lint)
  • Add minimal CI workflows #11

3. Project Governance & Contribution Setup

• 1. Configure GitHub labels
  • defaults + a few added
• 2. Add CODE_OF_CONDUCT.md / CONTRIBUTING.md
  • defined in docs; will be copied into standalone files
• 3. Add a “Known limitations & current status”
  • written in Did We Need a Dedicated Interaction Database — or Did We Overbuild? #32; will be copied into a standalone file
• 4. Prepare initial “good first issue” items
  • additional items may be added later
• 5. Enable GitHub Discussions and define policies
  • Discussions enabled; policies to be added if needed

---

Issue and PR templates are tracked in #62
Roadmap is tracked in #63

[em3s]

Follow-up for the initial open-source preparation issue

Merge minimal, low-risk PRs first:

• .gitignore initialization (Initialize .gitignore with Java, Kotlin, Gradle, and Go rules #5)
• CNAME setup for actionbase.io (Add CNAME for the custom domain actionbase.io #4)

Remaining PRs:

• Update README for initial release (Update README for initial release #7)
• Consolidate changes after initial open-source review (Consolidate changes after initial open-source review #8)
• Initialize the documentation website (Initialize the documentation website #6)
• Add initial Actionbase CLI (Add initial Actionbase CLI #2)
• Add sample social media service for Hands-on Guide (refactor(engine): Engine/TableBinding 통합 — QueryEngine 제거 #3)

[em3s]

This issue is now closed with #62 and #63 created as follow-ups.

Thank you to everyone who contributed to getting the first public release ready and the project up and running.