Hi Seata Community, I am writing to provide you with the minutes from our community meeting held on December 9, 2023. The meeting was productive, and we covered several important topics and conclusion as outlined below:
Moderator: Jiawei Zhang *Attendees* (PPMC only, others refer to the appendix): Jiawei Zhang, Jianbin Chen, Min Ji, Yuecai Liu, Yixia, Liang Wang, Jiangke Wu, etc., totaling 17 people. *Minutes of the Meeting in Chinese：* https://github.com/seata/seata/wiki/20231209 *Discussion items:* 1. Incubation progress update - Legal issues resolved. - Reported to Apache Secretary. 2. Library migration scope discussion - seata-java - seata-go - k8s - ctl - Official website - simple (java, go) 3. ASF ICLA contributor signing public email template - Completed. 4. Collect contributor information for those who have contributed more than 100 lines of code. - 83 individuals identified; email information pending collection, with email as the communication method. 5. ASF ICLA contributor signing - Contact respective developers via email after repository migration. 6. Homepage compliance and security. - Default language changed to English. - License check added to the official website. - Commercial links removed. - Maintainers list removed. - Security vulnerabilities fixed on the official website. - 41 frontend security vulnerabilities for Seata. - 5 remaining vulnerabilities for Seata Go. - 125 remaining vulnerabilities for Seata Simple. 7. Issue with decreasing Baidu search traffic. - CI generates sitemap, pre-renders content; 2 PRs for merging; automatic Baidu submission unsuccessful; official website has too few keywords. 8. Supplement documentation: development history, usage guide, split configuration documentation, split upgrade documentation, split deployment documentation. - Usage guide split completed (language-specific titles; Go pending completion). - Upgrade documentation split completed (PR pending review). - Configuration documentation, deployment documentation pending completion. 9. Abandon Yuque; migrate historical documents to the wiki. - Disorganized documents will not be migrated. - Design, extracurricular materials, and other documents need to be migrated (separate Java and Go wikis). - Create new directories for storage. 10. Documentation, release notes, and simple updates for 1.8.0 + 2.0.0. - Some release notes for 2.0 are incorrect. - A part of Seata Go PR changes missing in the change log; check if PR includes change log during code review. - Upgrade Seata version to 2.0 for Go Simple; progress completed for 3, large workload for about 50; requires division of labor. - Go Simple, some common logic needs optimization. 11. Branch maintenance. Public documentation for maintenance plan. - Maintain only the latest 3 versions (including the latest version). - 1.8.x branch, pending completion. - 2.x branch, pending completion. 12. Compatibility plan. API sorting - Frequently used APIs by users, Saga completed, encountered some issues (related to exceptions). - Client log files are independent. - Log formatting input, info, error, error code (need Seata-wrapped exceptions, consider internationalization). - State machine framework selection completed (development progress nearing completion). - Error code definition 13. Unit test coverage target 70% - Divide into different subtasks. - Target needs to be achieved. - Maintain coverage rate at 70% for changes. 14. Integrated test regression capability building. - Summer code end-to-end integration test framework, Docker Compose, pending confirmation. - Code with significantly similar content is not allowed. - Run integration tests afterward (independent repository). 15. Compatibility testing (jdk, arch, spring core+boot, druid) - OS, JDK, Spring Boot, compatibility testing PR completed, pending review (mock failure rate high, possibly due to Mockito version upgrade). - Separate workflows to increase parallelism. - Whether Redis needs compatibility testing (move to integration testing). 16. Performance benchmark - Only test framework consumption, SQL logic. - Open-source testing tools assistance, establish benchmarks. - Include graphical representation. 17. Mock testing - None for now, will continue syncing next week. 18. Code refactoring - None for now, will continue syncing next week. 19. Handling overdue PRs - Java: Closed those without follow-up before May 2022, and messages have been left; except for some important ones. - Go: Some authors have been contacted. - Long overdue PRs (important and necessary) will be followed up by us. 20. Support Spring Boot Actuator - Complete Redis. 21. Confirmation of unique identification of resource id + application name - Resource id may be duplicated, causing issuance problems; ensure uniqueness; final solution pending, to be discussed in the next meeting. 22. Confirmation of TCC usage, whether it needs to be compatible with special usage - If not compatible, prompt at startup. 23. Seata Go direction - Compliance governance: repository, governance of some dependent packages, CVE vulnerability fixes. - Set up and implement Seata Go Saga framework - Align with Seata Java's features and bug fixes; currently aligned with version 1.5.1, needs upgrading (follow the 2.x approach, no longer maintain dual branches) - Saga integration with OAM, cloud-native integration. - Ecological expansion: Bilibili, and others. Best regards, Jiawei Zhang
