Apache Monthly Meetings

• 1: June 2, 2026
• 2: March 31, 2026
• 3: February 24, 2026
• 4: January 27, 2026
• 5: November 25, 2025
• 6: October 28, 2025
• 7: September 30, 2025
• 8: August 28, 2025
• 9: July 30, 2025
• 10: June 30, 2025

1 - June 2, 2026

Texera Apache Incubation – Monthly Meeting Minutes

Date: June 2, 2026
Participants:

• Texera Committers: Xuan Gu, Ali Risheh, Jiadong Bai, Chris Park, Yicong Huang, Xiaozhen Liu, Meng Wang, Xinyuan Lin
• Texera Contributors: Carlos Ernesto Alvarez Berumen, Grace Chia
• Apache Incubating Mentors: Ian Maxon
• Guests: Eugene Gu, Kary Zheng, Kyle Dang, Suryaa

1. Project and Community Development

New Committers

• Meng Wang — joined April 6, 2026
• Xuan Gu — joined May 11, 2026

Active Contributors (past two months)

• 29 active contributors, including 11 first-time contributors.

Hackathon

• The dkNET-AI · Apache Texera Agent Hackathon — the project’s first hackathon — drew 35 submissions and 10 awardees, and brought new developers into the community.

Conference Presentation

• “Supporting Our AI Overlords (SAO): AI Agents and Data Systems” was presented at the ACM Conference on AI and Agentic Systems (CAIS) on May 26, 2026 in San Jose, CA. Jiadong Bai represented the project.

2. Releases

First Apache Release — v1.1.0-incubating

• The project shipped its first Apache release, v1.1.0-incubating (released May 17, 2026), a major milestone since v1.0.0 (April 4, 2025).
• The release represents 800+ commits and over 1M changed lines of code. A LinkedIn announcement was published to help promote it.
• A large share of the chore/CI work was governance and compliance:
  • Trimming the DISCLAIMER to the ASF template.
  • Per-module LICENSE-binary/NOTICE files.
  • A strict license-drift checker.
  • ASF branch-protection rulesets.
  • Release-candidate (RC) bundling tooling.

Release Strategy

• Major release (e.g., v2.0): change of position/focus, significant large feature, or marketing/branding update.
• Minor release (e.g., v1.2): new features, refactoring, bug fixes.
• Patch release (e.g., v1.1.1): urgent bug fix; used only when absolutely needed.

Release Schedule

• Branch cuts follow a quarterly cadence with a targeted release roughly two weeks later:
  • v1.1 — branch cut March 1, 2026 (v1.1.0-incubating released May 17, 2026)
  • v1.2 — branch cut June 1, 2026, targeted June 15, 2026
  • v1.3 — branch cut September 1, 2026, targeted September 15, 2026
  • v1.4 — branch cut December 1, 2026, targeted December 15, 2026
  • v1.5 and v1.6 — projected for 2027
• Major versions are bumped strategically; patch versions only when absolutely needed.

Release Manager

• Coordinates the release timeline and branch cut; prepares RCs, source packages, tags, checksums, and signatures; coordinates the release vote and the incubation release vote; publishes approved artifacts; updates the website/download links and announcements; and keeps the community informed.
• One release manager owns one release line (e.g., the RM of v1.2 manages v1.2.0-incubating, v1.2.1-incubating, …). By default only one release is needed per line. Watch for the [CALL FOR VOLUNTEER] email on dev@texera.apache.org.
• Thanks to Xuan Gu for volunteering as RM of the v1.2 line, and Jiadong Bai as RM of the v1.1 line.

3. Discussions, Issues, and PRs

To keep work organized, different kinds of conversations belong in different places:

• GitHub Discussions — “Do we do it? Which option?” Decide which feature or direction to take, which UI/UX to provide, and which design option to choose among alternatives.
• GitHub Issues — “When/where (release) to do it?” Define the concrete task, bug, or feature (often summarized from a discussion), decide priority and targeted release, and coordinate with other work.
• GitHub PRs — “How do we implement it?” Verify the implementation is correct and has enough verification (tests, screenshots, videos, benchmarks).

Discussions are synced to dev@texera.apache.org.

4. PR Reviews

• Everyone is encouraged to review any PRs; contributors with more context should be requested as reviewers.
• AI reviews (local agents such as Claude Code and Codex, plus GitHub Copilot) are encouraged to add perspective, but should not replace human reviews — they provide an extra pair of eyes.
• Review and merge life cycle: author requests review → reviewer comments / requests changes → author addresses and re-requests review → reviewer approves (with non-blocking comments) → author resolves non-blocking comments and applies final touches → merger merges.
• Roles:
  • Author: make the code change, create the PR and link the issue, add tests that prove the change works, include screenshots/gifs for UI PRs, and request reviewers. Authors should do the heavy lifting to reduce reviewer load.
  • Reviewer: check that the PR matches its issue/discussion, assess code quality and test coverage, and optionally test to verify. Reviewing any PR you’re interested in is welcome; even lightweight feedback is valuable.
• Who merges: if the author is a committer, the author merges; if the author is a contributor, a reviewer merges; in rare cases where both are unavailable, a third committer may merge.

5. Testing

• Testing is especially significant for AI-generated code, and should be automated as much as possible in CI (unit tests — the current focus — plus E2E tests and benchmarks).
• Unit test coverage is reported via Codecov; the repository started at roughly 42% coverage.
• Filling the coverage gap helps avoid regressions (breaking old features, reintroducing bugs, or unnoticed behavior changes) and reduces per-PR review and per-release manual bug-bash workload.
• Approach:
  • Encourage test-only PRs to add tests.
  • For new feature/task PRs, aim for 100% coverage as guidance (not a hard requirement; the committer has final say). 0% coverage on changed code indicates it is untested and should be rejected.
  • For bug-fix PRs, add tests to confirm the fix and prevent recurrence.
• Goal: reach 90% test coverage by the end of summer.
• New CI/CD infrastructure: GitHub merge queue, label-based optional pre-merge CI plus full post-merge CI, label-based auto-backport workflows for release branches, and a contributor-facing comment-command bot.

6. Major Developments

• Apache name approved: the “Apache Texera” name was approved by the ASF (PODLINGNAMESEARCH-253).
• Agent Service: a new agent-service was added to manage LLM agents (#4495), enabling the Texera Agent to edit and execute workflows (#4540) and to support more default operator types (#4619).
• Python Virtual Environment (PVE): creating environments (#4484), installing/uninstalling user packages (#4902, #5035), executing Python UDFs inside PVEs (#5069), a UI parameter form (#5043), and a Kubernetes gateway config (#5138).
• New visualization operators: Radar, Wind rose, Parallel coordinates, ECDF, Carpet, Ternary contour, and WebGL polar charts.
• Engine (Amber): operator reconfiguration re-enabled (#4220), region restart support (#4441), state materialization across regions (#4490), jump-to-operator support (#4444), and Iceberg REST catalog support for result storage (#4272).
• Frontend: upgraded Angular 17 → 21 and migrated from Karma to Vitest.
• Backend: moved to Java 17 LTS, and Akka was renamed to Pekko (the ASF-licensed fork).
• New data-source operators: File Lister and File Scan From Input.
• Quality and testing: a deliberate stabilization phase — 111 of 401 commits (over a quarter) were test commits — paired with full Codecov integration and a coverage badge.

7. Next Steps

Ongoing efforts the team will continue:

• Control blocks
• Auto-generation of documentation
• Blogs
• Virtual environments (persistency, R support)
• Hugging Face operator
• Caching
• Macros
• Python ↔ Workflows

2 - March 31, 2026

Texera Apache Incubation – Monthly Meeting Minutes

Date: March 31, 2026
Participants: Chen Li, Meng Wang, Ali Risheh, Jiadong Bai, Andy Zhang, Xiaozhen Liu, Chris Park, Xinyuan Lin, Xuan Gu, Zuozhi Wang

1. Technical Updates

UI and Features

• Affiliation/Joining Reason in Admin Emails (#4326):
  • The notification emails sent to admins for new account requests now include the user’s affiliation and reason for joining, giving admins more context (this data is collected by the registration form from #4185).
• Edit Description Button in Workspace (#4271):
  • A button was added in the workspace to edit a workflow’s description, opening the Markdown editor introduced in #4212.
• Email to Dev List on DDL Change (#4250):
  • An email is now sent automatically to the dev mailing list whenever there is a database schema (DDL) change.
• Dataset Detail Page Layout (#4337):
  • The dataset detail page layout was improved.

Licensing and Compliance

• Rewrite Stack Overflow Code Snippets (#4283):
  • All Stack Overflow references were removed from the source code to comply with ASF licensing policy (Stack Overflow content is CC-BY-SA, which is incompatible with the Apache License 2.0).
  • Code derived from Stack Overflow (e.g., a camelCase-to-title regex) was rewritten, and SO-referencing comments were replaced with self-contained explanations.

2. Apache Release Preparation

Preparing v1.1.0-incubating Release

Merged PRs that added example content to the Docker Compose setup, aligned service/container naming, and bundled the examples into the release-candidate tarball:

• feat: add example datasets and workflows to Docker Compose (#4247)
• refactor: align docker-compose service and container names with image names (#4249)
• fix(ci): include example datasets and workflows into the docker compose tarball when creating the release candidate (#4253)

A pending documentation PR replaced the placeholder README in the Docker Compose folder with the full setup guide from the project wiki:

• chore(docs): include the wiki instruction as the README in the docker compose folder (#4320)

3. Community

• Contributors (March 2026, excluding committers and PPMC members):
  • Carlos Ernesto Alvarez Berumen
  • Xuan Gu
  • Jae Yun Kim
  • Matthew George Ball
  • Seongjin Yoon
  • Grace Wanheng Chia

4. Next Steps

The team will focus on the following items moving forward:

• Fixing license requirements by Whimsy.
• Supporting control blocks.
• Enabling operator caching.

3 - February 24, 2026

Texera Apache Incubation – Monthly Meeting Minutes

Date: February 24, 2026
Participants:

• Texera Team/Guests: Chen Li, Matthew Ball, Andy Zhang, Elliot Lin, Ali Risheh, Chris Park, Xuan Gu, Xiaozhen Liu, Jiadong Bai, Xinyuan Lin

1. Technical Updates

Infrastructure and Architecture

• Unified Proxy with Envoy Gateway (#4190):
  • The previous dual-proxy setup (Ingress Nginx for static routes plus a separate Envoy for computing units) was replaced with a single Envoy Gateway based on the Kubernetes Gateway API (implemented in #4191).
  • This simplifies the infrastructure and natively supports dynamic routing to ephemeral computing units without configuration reloads.
• Multipart Upload via File Service (#4136):
  • Dataset multipart uploads were redirected through the File Service, with server-side streaming to S3 and LakeFS managing multipart state.
  • New upload-session tracking (per-part ETags and completeness checks) lays the groundwork for reliable, resumable uploads.

UI and Features

• Markdown Editor for Descriptions (#4212):
  • Dataset and workflow descriptions now support Markdown, with a preview mode and an edit mode offering a formatting toolbar and side-by-side live preview (description columns widened to TEXT).
• Links Included in Region Display (#4226):
  • The region display calculation now includes links so that a region fully covers them, fixing cases where links fell outside the region boundary.
• User Registration Form (#4185):
  • First-time users are prompted for their affiliation (optional) and reason for joining (required), which is stored for admin review in the dashboard.
  • This consolidates the earlier separate “request access” and “affiliation” modals into a single form.

2. Apache Release Preparation

Release Pull Requests

• chore: update release workflow to comply with Apache release practice (#4128)
• feat(release): include container images and deployment artifacts in release (#4219)
• fix(ci): use consistent 9-char commit hash for image tags (#4231)

Release Candidate

• Release candidate v1.1.0-incubating-rc3 has been prepared.

3. Community

• Contributors (Feb 2026, excluding committers and PPMC members):
  • Carlos Ernesto Alvarez Berumen
  • Xuan Gu
  • Jae Yun Kim
  • Matthew George Ball
  • Seongjin Yoon

4. Next Steps

The team will focus on the following items moving forward:

• Fixing license requirements by Whimsy.
• Supporting control blocks.
• Enabling operator caching.

4 - January 27, 2026

Texera Apache Incubation – Monthly Meeting Minutes

Date: January 27, 2026
Participants:

• Texera Mentors: Ian Maxon
• Texera Team/Guests: Chen Li, Ali Risheh, David Yoon, Xuan Gu, Andy, Chris Park, Jiadong Bai, Xiaozhen Liu, Yicong Huang, Yunyan Ding, Shengquan Ni

1. Technical Updates

Infrastructure and Architecture

• Multipart Upload Redirection:
  • The team is implementing a redirection of multipart uploads through the File Service (Issue #4136).
  • The architecture utilizes an Angular proxy to handle requests and manage file metadata during the upload session initialization.
• Big Object Support:
  • Support for Big Objects in Python UDFs is being implemented (Issue #4100).
  • The design involves a Computing Unit Master JVM and interacts with MinIO for object storage and Iceberg for table management.
  • A Lifecycle Manager is included to handle deletion and object management.

Execution and Settings

• Materialized Execution Mode:
  • A new “Materialized” execution mode has been introduced (Issue #4158).
  • Users can toggle between “Pipelined” and “Materialized” modes in the settings panel.
• CI/CD Automation:
  • GitHub Actions have been added to Docker images to facilitate automatic pushing (Issue #4055).
  • The workflow supports building for specific target platforms (e.g., “both”) and includes options to enable R support.

Documentation and UI

• Dataset Customization:
  • Support has been added for custom cover images on datasets (Issue #4117).
• Documentation:
  • Design documentation for operators is being developed, including detailed property tables for operators like the Bar Chart.
  • Efforts are underway to automate document videos.

2. Community

• New Contributors (Jan 2026):
  • Carlos Ernesto Alvarez Berumen
  • Xuan Gu
  • Jae Yun Kim
  • GitHub developer “LJX2017”

3. Next Steps

The team will focus on the following items moving forward:

• Fixing license requirements by Whimsy.
• Supporting control blocks.
• Enabling operator caching.
• Supporting resumable upload.

5 - November 25, 2025

Texera Apache Incubation – Monthly Meeting Minutes

Date: November 25, 2025
Participants:

• Texera PPMC: Chen Li, Ali Risheh, Xiaozhen Liu, Meng Wang, Jiadong Bai, Chris Park
• Guests: Xuan Gu, Andy, Ryan Yiran Zhang

1. Apache Release Preparation

Current Status

• Repositories: Apache repositories have been created and nightly images are available.
• Distribution Directories: Directories on dist.apache.org have been created at dev/incubator/texera/ and release/incubator/texera/.

Release Candidate TODOs

• Before Staging:
  • Merge a few ongoing PRs.
  • Decide whether to include the rpy2 package.
  • Ensure the Release Manager’s GPG key is signed by other Apache committers.
• After Staging:
  • PMC members must test and vote for the release candidates.
• Post-Approval:
  • Move artifacts from the dev directory to the release directory.
  • Update the project download page and send an announcement email.

2. Technical Updates

Infrastructure and Dependencies

• Switch to Apache Pekko:
  • The project is replacing Akka with Apache Pekko (Issue #4009, #3237).
  • Reasoning: Akka utilizes a non-FOSS Business Software License, preventing the uptake of bug and security fixes; Pekko is Apache-licensed.
• CI/CD Improvements:
  • GitHub Actions have been added to Docker images (Issue #4055) to support automatic pushing.
• Big Object Support:
  • Implementation of “Supporting Big Objects” (Issue #4067) is underway.
  • The architecture involves Workflow Service Instances, Computing Units, and integration with MinIO and Iceberg for storage and lifecycle management.

Security

• Policy Documentation: A SECURITY.md file has been added to the repository outlining the security policy.
• Security Model Overview:
  1. Authentication: JWT-based token authentication with configurable expiration.
  2. Authorization: Role-based access control (RBAC) with four user roles.
  3. Resource Access Control: Fine-grained privileges for datasets, workflows, and computing units.
  4. Deployment Isolation: Separate security considerations for different deployment modes.

3. Community and Website

• Website Launch: The official site texera.apache.org is now up.
• New Contributors (Nov 2025):
  • Andy Zhang
  • Xuan Gu
  • Jae Yun Kim
  • GitHub developer “LJX2017”

4. Next Steps

The team will focus on the following items moving forward:

• Improving the Apache website.
• Supporting control blocks.
• Enabling operator caching.
• Supporting customizable interfaces on top of workflows.
• Implementing Python virtual environments.
• Running User Defined Functions (UDFs) in a separate container.

6 - October 28, 2025

Apache Texera (Incubating) Sync Meeting Summary

Date: October 28, 2025

Attendees

• Texera PPMC: Chen Li, Jiadong Bai, Yunyan Ding, Ali Risheh, Chris Park, Xiaozhen Liu, Yicong Huang
• Texera Mentors: Ian Maxon
• Guests: David Yoon, Ryan Zhang, Carlos Berumen, Andy, Roger, Qizhi Tian, Meng Wang

Agenda

1. Major development progress
2. October 2025 contributors
3. Plan for the next month

1. Major Development Progress

Key progress was made across community tools, codebase organization, and new features.

Community & Repository Management

• Codebase Reorganization: The package naming has been updated from edu.uci.ics to org.apache.texera to reflect its Apache status.
• GitHub Discussions: The team has started using the “Discussions on GitHub” feature to improve communication.
• Wiki Migration: Old Wiki pages are being migrated to GitHub Discussions to consolidate information.
• PR & Issue Templates: New templates have been implemented to improve the quality and consistency of pull requests and issue reports.

First Release Preparation

• Distribution Directories: The necessary directories on dist.apache.org for both development and release have been created.
• Docker Hub: The team is working with the ASF to set up an apache/texera registry on Docker Hub.

New Features & Improvements

• Admin Dashboard: The admin dashboard now shows active users.
• New Operator: A strip chart visualization operator has been added.
• Workflow Execution: The UI now displays the worker number for each operator during workflow execution, providing better insight into parallelism.

2. October 2025 Contributors

Thank you to all the contributors this month (excluding Committers and PPMC members):

• Xuan Gu
• Jae Yun Kim
• Andy Zhang
• Grace Chia
• Madison Lin
• “LJX2017” (GitHub developer)

3. Ongoing Tasks (Plan for Next Month)

• Set up the official texera.apache.org website.
• Prepare for the 6-month ASF review.
• Continue with system improvements, including:
  • Replacing Ingress and Envoy with Kong or Contour gateways.
  • Developing an access control service.
  • Working on the AI agent.
  • Migrating scripts.

7 - September 30, 2025

Texera Apache Incubation – Monthly Meeting Minutes

Date: September 30, 2025
Participants:

• PPMC: Yicong Huang, Xinyuan Lin, Chris Park, Jiadong Bai, Xiaozhen Liu, Yunyan Ding, Zuozhi Wang
• Mentors: Ian Maxon, Gordon K
• Guests: Qizhi Tian, Xuan Gu, Madison Lin, Ryan Zhang

1. Recent Accomplishments

Core System Enhancements

• Machine Learning Integration: Added new ML training operators for both linear and logistic regression.
• Data Visualization: A new choropleth map operator has been added for geographical data visualization.
• Architecture: The AccessControlService has been implemented as a new microservice to improve security and modularity. A diagram of the new cluster architecture is available.
• User Authentication: The user activity window has been separated from the JWT expiration to provide more flexible session management.
• Admin Settings: Added new configuration guidance in the admin settings for file upload parameters, including file size, concurrent parts, and part size.

Community and Outreach

• Official Website: Work is in progress with mentors to set up the official Apache website at https://texera.apache.org/.
• YouTube Channels: Two new YouTube channels have been launched to support the community:
  • Texera Project General
  • Texera Project Tutorials

2. September 2025 Active Contributors

This month, we’d like to recognize the following active contributors (excluding Committers and PPMC members):

• Xuan Gu
• Jae Yun Kim
• Andy Zhang
• Victor Fawole

3. v1.1.0-incubating Release Plan

A major ongoing effort is the upcoming v1.1.0-incubating release, which is planned for the next few weeks. The last major release was v1.0.0 on April 7, 2025.

Release TODO List

• 1. Namespace Preparation
  • Create dev and release namespaces on dist.apache.org.
  • Create the apache/texera repository on Docker Hub.
• 2. Artifacts Preparation
  • The release will include a source code tarball, a docker-compose tarball, and 9 docker images.
  • Each artifact will be accompanied by a signature and checksum.
• 3. Voting Procedure
  • The formal voting process will be initiated on the dev@texera.apache.org mailing list.
• 4. Wrap-up
  • Upon a successful vote, artifacts will be moved to the release namespace.
  • Docker images will be built and pushed to Docker Hub.
  • The release will be formally announced to the community.

For any questions regarding the release, please contact Jiadong Bai.

8 - August 28, 2025

Texera Apache Incubation – Monthly Meeting Minutes

Date: August 28, 2025 Chair: Chen Li Participants: Chen Li, Anzhi Zhang, Seongjin Yoon, Yichen Ren, Ali Risheh, Yicong Huang, Matthew Ball, Sarah Asad, Ryan Zhang, Dhriti Soni, Jae Yun Kim, Madison Liu

1. Apache Incubation Status Overview

• Incubation Start Date: April 12, 2025
• Mentors Assigned: 4
• PPMC Members: 13
• Committers: 13 (same as PPMC)
• External Contributors: 100+
• Website: https://texera.io
• Tutorial Videos are being developed to onboard new users.

2. Recent Accomplishments

Core System Enhancements

• Cloud Deployment: Investigated the use of AWS ECS for a more cost-effective deployment of Texera.
• Data Access Control: Added a new option allowing data owners to grant download access to public datasets, a key feature in preparation for NIH use cases.
• User Experience (UI/UX):
  • The admin dashboard now includes a feature to monitor user activeness.
  • File uploads now display the real-time upload speed and estimated time remaining.
  • A new dashboard tab has been added for managing computing units.
• Documentation: All project design decisions are now being documented in the issues tab on GitHub for transparency and tracking.

Community and Development

• Repository Migration: The Texera repository was officially transferred to the Apache GitHub organization on August 6, 2025.
• Monthly Sync: The project’s monthly sync meeting was successfully conducted with PPMC members, committers, and contributors.

4. Incubation Graduation Action Items

Software Grant Agreement (SGA) & Code Donation

• Status: ✅ Completed
• Details: The SGA process is complete, and the repository has been officially transferred to the Apache organization.

Apache Website & Documentation

• Status: ⚙️ In Progress
• Details: The primary remaining task is setting up the official Apache Texera webpage (http://texera.apache.org/). Work continues on consolidating user guides, developer setup instructions, and governance policies. We are analyzing the documentation structures of successful projects like Apache Flink and Spark to ensure an optimal user experience.

Reporting Schedule

• Next Monthly Report Due: September 6, 2025
• First Quarterly Report Due: November 2025

9 - July 30, 2025

Texera Apache Incubation – Monthly Meeting Minutes

Date: July 30, 2025
Chair: Chen Li
Participants: Chen Li, Anzhi Zhang, Seongjin Yoon, Yichen Ren, Ali Risheh, Yicong Huang, Yunyan Ding, Meng Wang, Matthew Ball, Sarah Asad, Xinyuan Lin, Ryan Zhang, Dhriti Soni, Jae Yun Kim

1. Apache Incubation Status Overview

• Incubation Start Date: April 12, 2025
• Mentors Assigned: 4
• PPMC Members: 13
• Committers: 13 (same as PPMC)
• External Contributors: 100+
• System Architecture: Cloud Infrastructure
• Project Logo: New logo based on a peacock motif
• Website: https://texera.io
• Tutorial Videos are being developed to onboard new users.
• Use Cases from the Medical Domain, including NIH and ADA data pipelines, are being documented and integrated.

2. Recent Accomplishments

Core System Enhancements

• Cloud Deployment: Successfully deployed Texera on AWS EKS, demonstrating scalability for over 20 concurrent students.
• Collaborative Features: Implemented shared write access for computing units among different users.
• Machine Learning Integration: Added new operators for scikit-learn model training.
• User Experience (UI/UX):
  • Enabled dynamic workflow configuration directly from the user interface.
  • Improved UI for displaying operator and port-level metrics.
  • Enhanced performance for retrieving resources from the Texera Hub.
• System Configuration: Introduced a new configuration parameter, max-concurrent-regions, to manage resource allocation.

Community and Outreach

• Data Science for All (DS4ALL): Utilized hub.texera.io to teach data science and AI/ML concepts to 34 students from high schools and community colleges.
• Middle School Program: Taught a data science workshop to 32 middle school students on July 21, 2025.
• Biology Summer Camp: Hosted an online summer camp on data science for biology, targeting undergraduate and graduate students with limited coding backgrounds.
• Academic Deployment: The platform is now officially deployed and in use at the UCI Department of Ophthalmology.

3. Project Roles and Responsibilities

The Texera project follows the standard Apache meritocracy model. The table below outlines the key roles, their permissions, and the process for joining.

4. Incubation Graduation Action Items

Software Grant Agreement (SGA)

• Status: In Progress
• Details: The copyright release form has been signed by the UCI Licensing Office and Chen Li. We are currently awaiting feedback from the Apache Foundation.

Documentation

• Status: In Progress
• Details: Work is underway to consolidate user guides, developer setup instructions, and governance policies into an Apache-compliant format. We are analyzing the documentation structures of projects like Apache Flink and Spark to ensure an optimal user experience. We are also exploring solutions for community-contributed documentation for public datasets.

Reporting Schedule

• Next Monthly Report Due: August 6, 2025
• First Quarterly Report Due: November 2025

10 - June 30, 2025

Texera Apache Incubation – Monthly Meeting Minutes

Date: June 30, 2025
Chair: Yicong Huang
Participants: Jiadong Bai, Yunyan Ding, Yicong Huang, Chen Li, Xinyuan Lin, Shengquan Ni, Cezar Cristian Andrei, Ian Maxon, Zuozhi Wang

1. Apache Incubation Status Overview

• Incubation Start Date: April 12, 2025
• Mentors Assigned: 4
• PPMC Members: 13
• Committers: 13 (same as PPMC)
• External Contributors: 100+
• System Architecture: Cloud Infrastructure
• Project Logo: New logo based on a peacock motif
• Website: https://texera.io
• Tutorial Videos are being developed to onboard new users.
• Use Cases from the Medical Domain, including NIH and ADA data pipelines, are being documented and integrated.

2. Incubation Graduation Requirements and Status

TODO 1: Software Grant Agreement (SGA)

• Status: UCI License office approved releasing the copyright of Texera to PPMC.
• Chen is finishing up some paperwork; he has requested modifications to the terms and is awaiting a response.
• Once resolved, the Apache SGA can be submitted quickly.

TODO 2: Codebase Cleanup

• Leads: Xinyuan Lin & Yicong Huang
• Progress:
  • Several major cleanups completed.
  • Two remaining issues:
    1. Pekko Migration: PJ suggests moving from Akka to Pekko; PPMC agrees. Will vote on emailing list.
    2. License Issue with Stack Overflow Code:
       • Current snippet is under Stack Overflow license, which is not Apache-compatible.
       • Proposed solution:
         • Create a GitHub issue referencing the snippet and document its origin.
         • Rewrite the logic to ensure compliance. Cezar’s Comment: Rewriting after understanding is acceptable and preferred.

TODO 3: Donate Codebase to Apache GitHub

• Action Item: Prepare the current codebase and initiate the transfer process.

TODO 4: Apache Website Setup

• Discussion on Website Hosting Strategy:
  • Options:
    1. Transfer texera.io domain to texera.apache.org
    2. Redirect texera.apache.org to texera.io (feasibility under discussion)
    3. [recommended] Maintain both domains separately for different purposes:
       • texera.apache.org: Code, documentation, and incubator artifacts
       • texera.io: Academic materials, publications, and grant-related content
  • Example Cited: AsterixDB has separate Apache and academic websites.
  • Cezar’s Recommendation: Ensure anything not officially under Apache IP is hosted outside apache.org.

TODO 5: Documentation

• Ongoing: Need to consolidate user guides, developer setup, and governance policies in Apache-compliant format.

TODO 6: Community Growth Initiatives

• Academic Collaborations:
  • University of Michigan, NIH, UCLA, Cornell
• Public Access Promotion:
  • Make hub.texera.io public
  • Make texera.dknet-ai.org public
• Community Programs:
  • Integration with DS4ALL summer program for data science education using Texera

4. Committer and PPMC Onboarding

Apache Roles Clarified

• Contributor: External code and documentation submissions
• Committer: Direct write access to the codebase
• PPMC Member: Governance, release voting, project direction
• Mentor: Oversight, compliance, and community best practices

New PPMC Member Proposal

• Zuozhi has been proposed (and welcomed back) as a new PPMC member. The official voting will start on the emailing list.

5. Official Communication Channels

• private@texera.apache.org – PPMC coordination, sensitive topics, voting
• dev@texera.apache.org – Technical discussions, code reviews, general development
• general@texera.apache.org – User Q&A, public community discussion

6. Reporting Schedule

• Next Monthly Report Due: July 2, 2025
  Next sync meeting will be at end of July, to sync and discuss about August report.
• Quarterly Reporting Starts: November 2025

Prepared by: Jiadong Bai and Yicong Huang
On behalf of the Texera PPMC