lizhimins opened a new issue, #10600:
URL: https://github.com/apache/rocketmq/issues/10600

   # RocketMQ Studio 社区共建招募
   
   ## 项目简介
   
   **RocketMQ 5.0 Studio:全新的 AI-Native 管控平台**
   
   RocketMQ 5.0 新增了云原生弹性架构、多语言 gRPC 接入,Lite Topic 等核心特性,完成了向 AI-Native 
异步通信引擎的范式升级。欢迎贡献全新的 AI-Native 的管控平台,由于任务较为复杂,本次主题将拆分为三个部分:AI-Native 统一管控平台, 
Proxy Admin 管控能力升级,大模型原生集成。
   
   - **赛道一:管控方向(AI-Native 统一管控平台)**:打造 RocketMQ 5.0 Studio 
核心可视化前后端服务,一站式实现多集群、多架构、多云环境的统一管控,为消息中间件管理树立 AI-Native 新标杆。
   - **赛道二:协议升级(Proxy Admin 管控能力升级)**:构建 Proxy Admin gRPC 
协议标准,将客户端连接管理与运行时诊断能力全面标准化开放,为精细化运维提供坚实底座。
   - **赛道三:AI Native(大模型原生集成)**:借助 Skill + CLI 标准化能力封装,资源管理与运维操作可被 LLM 
直接理解与调用,为 AI-Native 新时代的消息管控平台提供强劲引擎。
   
   基于此,RocketMQ 社区期望实现 "跨集群、跨架构、跨云的统一管控" 的愿景。
   
   **技术栈**:
   - 后端:Spring Boot 3.5 + Java 21
   - 前端:React 18 + TypeScript + Ant Design
   - 部署:Docker + Docker Compose
   
   📖 
**项目文档**:[README_zh.md](https://github.com/apache/rocketmq-dashboard/blob/rocketmq-studio/README_zh.md)
   
   ## 活动报名
   
   本项目已入选 **太易开源挑战赛**,欢迎通过官方渠道报名参与:
   
   🔗 
**报名链接**:https://www.taiyi.top/competition-details?id=2f410866-6fa3-11f1-b193-02420a000011
   
   ## 贡献说明
   
   ### Apache 贡献声明
   
   RocketMQ Studio 是 Apache RocketMQ 项目的子项目。参与本项目的贡献,你将成为 Apache 顶级项目的 
Contributor,贡献记录永久保存在 Apache 项目历史中,并有机会成为 Apache RocketMQ 的 Committer。
   
   ### 贡献类型
   
   我们欢迎各类贡献:
   
   | 类型 | 说明 | 难度 |
   |------|------|------|
   | 🐛 Bug 修复 | 修复已知问题 | ⭐ ~ ⭐⭐⭐ |
   | ✨ 新功能 | 开发新特性 | ⭐⭐ ~ ⭐⭐⭐ |
   | 📚 文档 | 完善文档和教程 | ⭐ |
   | 🎨 UI 优化 | 改进界面设计 | ⭐⭐ |
   | 🧪 测试 | 增加测试覆盖 | ⭐⭐ |
   | 🔧 重构 | 优化代码质量 | ⭐⭐⭐ |
   
   ### 快速开始
   
   1. **Fork 并克隆仓库**
      ```bash
      git clone https://github.com/YOUR_USERNAME/rocketmq-dashboard.git
      cd rocketmq-dashboard
      git checkout rocketmq-studio
      ```
   
   2. **启动开发环境**
      ```bash
      # 后端
      cd server && mvn spring-boot:run
   
      # 前端(新终端)
      cd web && npm install && npm run dev
      ```
   
   3. **选择 Issue 开始贡献**
      - 查看带 `good first issue` 标签的入门任务
      - 查看带 `help wanted` 标签的待开发任务
      - 在 Issue 下留言表达参与意愿
   
   ## 开发规范
   
   ### 提交规范
   
   使用 [Conventional Commits](https://www.conventionalcommits.org/) 格式:
   
   ```
   type: description
   
   feat: 新功能
   fix: 修复 Bug
   docs: 文档更新
   refactor: 代码重构
   test: 测试相关
   chore: 构建/工具
   ```
   
   ### 代码规范
   
   **后端 (Java)**:
   - 遵循 Apache RocketMQ Checkstyle 规范
   - 运行 `mvn checkstyle:check` 检查
   - POJO 类使用 DTO/VO 后缀命名
   
   **前端 (TypeScript)**:
   - 运行 `npm run lint` 检查
   - 使用函数式组件 + Hooks
   - 遵循 Ant Design 设计规范
   
   ### PR 流程
   
   1. 从 `rocketmq-studio` 分支创建功能分支
   2. 开发并确保测试通过(`mvn test` / `npm run lint`)
   3. 提交 PR 到 `apache/rocketmq-dashboard` 的 `rocketmq-studio` 分支
   4. 等待 Code Review 并响应反馈
   5. Review 通过后由 Committer 合并
   
   ## 沟通渠道
   
   - **GitHub Issues**:问题反馈和功能讨论
   - **GitHub Discussions**:社区交流
   - **邮件列表**:[email protected]
   
   ---
   
   期待你的加入!🚀
   
   ---
   
   # RocketMQ Studio Community Call for Contributors
   
   ## Introduction
   
   **RocketMQ 5.0 Studio: A Brand New AI-Native Management Platform**
   
   RocketMQ 5.0 introduces cloud-native elastic architecture, multi-language 
gRPC access, Lite Topic and other core features, completing the paradigm 
upgrade to an AI-Native asynchronous communication engine. We invite you to 
contribute to the brand new AI-Native management platform. Due to the 
complexity of the task, this theme is divided into three parts: AI-Native 
Unified Management Platform, Proxy Admin Management Capability Upgrade, and 
Large Model Native Integration.
   
   - **Track 1: Management (AI-Native Unified Management Platform)**: Build the 
core visualization frontend and backend services of RocketMQ 5.0 Studio, 
achieving one-stop unified management of multi-cluster, multi-architecture, and 
multi-cloud environments, setting a new AI-Native benchmark for message 
middleware management.
   - **Track 2: Protocol Upgrade (Proxy Admin Management Capability Upgrade)**: 
Build the Proxy Admin gRPC protocol standard, fully standardize and open client 
connection management and runtime diagnostic capabilities, providing a solid 
foundation for refined operations.
   - **Track 3: AI Native (Large Model Native Integration)**: With Skill + CLI 
standardized capability encapsulation, resource management and operations can 
be directly understood and invoked by LLM, providing a powerful engine for the 
AI-Native era message management platform.
   
   Based on this, the RocketMQ community aims to realize the vision of "unified 
management across clusters, architectures, and clouds".
   
   **Tech Stack**:
   - Backend: Spring Boot 3.5 + Java 21
   - Frontend: React 18 + TypeScript + Ant Design
   - Deployment: Docker + Docker Compose
   
   📖 **Project Documentation**: 
[README.md](https://github.com/apache/rocketmq-dashboard/blob/rocketmq-studio/README.md)
   
   ## Registration
   
   This project has been selected for the **Taiyi Open Source Challenge**. 
Welcome to register through the official channel:
   
   🔗 **Registration Link**: 
https://www.taiyi.top/competition-details?id=2f410866-6fa3-11f1-b193-02420a000011
   
   ## Contribution Guide
   
   ### Apache Contribution Statement
   
   RocketMQ Studio is a subproject of Apache RocketMQ. By contributing to this 
project, you will become a Contributor to an Apache top-level project, your 
contributions will be permanently recorded in the Apache project history, and 
you will have the opportunity to become a Committer of Apache RocketMQ.
   
   ### Contribution Types
   
   We welcome all kinds of contributions:
   
   | Type | Description | Difficulty |
   |------|-------------|------------|
   | 🐛 Bug Fix | Fix known issues | ⭐ ~ ⭐⭐⭐ |
   | ✨ New Feature | Develop new features | ⭐⭐ ~ ⭐⭐⭐ |
   | 📚 Documentation | Improve docs and tutorials | ⭐ |
   | 🎨 UI Enhancement | Improve interface design | ⭐⭐ |
   | 🧪 Testing | Increase test coverage | ⭐⭐ |
   | 🔧 Refactoring | Optimize code quality | ⭐⭐⭐ |
   
   ### Quick Start
   
   1. **Fork and clone the repository**
      ```bash
      git clone https://github.com/YOUR_USERNAME/rocketmq-dashboard.git
      cd rocketmq-dashboard
      git checkout rocketmq-studio
      ```
   
   2. **Start the development environment**
      ```bash
      # Backend
      cd server && mvn spring-boot:run
   
      # Frontend (new terminal)
      cd web && npm install && npm run dev
      ```
   
   3. **Choose an Issue to start contributing**
      - Check issues labeled with `good first issue` for beginners
      - Check issues labeled with `help wanted` for development tasks
      - Comment on the issue to express your interest
   
   ## Development Guidelines
   
   ### Commit Convention
   
   Use [Conventional Commits](https://www.conventionalcommits.org/) format:
   
   ```
   type: description
   
   feat: new feature
   fix: bug fix
   docs: documentation update
   refactor: code refactoring
   test: test related
   chore: build/tools
   ```
   
   ### Code Standards
   
   **Backend (Java)**:
   - Follow Apache RocketMQ Checkstyle rules
   - Run `mvn checkstyle:check` to verify
   - Use DTO/VO suffix naming for POJOs
   
   **Frontend (TypeScript)**:
   - Run `npm run lint` to verify
   - Use functional components + Hooks
   - Follow Ant Design specifications
   
   ### PR Process
   
   1. Create a feature branch from `rocketmq-studio`
   2. Develop and ensure tests pass (`mvn test` / `npm run lint`)
   3. Submit PR to the `rocketmq-studio` branch of `apache/rocketmq-dashboard`
   4. Wait for Code Review and respond to feedback
   5. Review approved, merged by Committer
   
   ## Communication Channels
   
   - **GitHub Issues**: Bug reports and feature discussions
   - **GitHub Discussions**: Community交流
   - **Mailing List**: [email protected]
   
   ---
   
   Looking forward to your participation! 🚀
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to