Hi Community, here are the meeting minutes of our community meeting. The meeting is for anyone wanting to get involved in the HertzBeat dev, doc, ideas or discuss.
Time: 9:00 PM on the third week of each month. Mode: Online Tencent Video Conference Purpose: Building Open And Governance Community Moderator: @tom gaojian, ceilzcx, weitao, zhouyong, zhouqingran, gogo, zhangyuxuan, wushiqiang, liutianyou, musheng, zhu, tiejiaxiaobao, wangboshan, lou, xuchuanwei, liuhongyu, jiashu, tomsun28 record video: https://meeting.tencent.com/v2/cloud-record/share?id=c14b07f2-6aaf-45f0-8292-a303f1b9e15e&from=3&record_type=2 ### Discuss - Open Source Project Progress > Last month’s progress was discussed. Key tasks included editing protocol fields, completing the PC pricing information, and finalizing the channel S.road section. Next steps involve implementing common commands like fan and sensor info, and addressing three security components, with seven algorithms for authentication and integrity already completed. The RT Client section was also reviewed, focusing on section processing, specific connection handling, and command handlers. - Codebase and Functionality Discussion > The conversation covered the codebase size, noting that core commands like authentication are already implemented. Most features can now monitor the server, except for some handlers and algorithms. The plan is to merge existing code for community review, alongside discussions on template upload, version control, and short link implementation. - Backend Code Optimization and Repository Management > Several recommendations were made: setting buckets as public with access via backend API, generating secure short links internally, and keeping backend ports closed since two are in use. The project requires GPA billing, English comments, and using existing utility classes. There’s also a suggestion to separate modules into independent repositories and to reference the main repository for frontend code to avoid redundancy. Backend abstraction and table structure simplification were also discussed. - Frontend and Data Storage Optimization > Frontend issues were reviewed, proposing a unified file storage and interface for uploads/downloads, allowing others to contribute different implementations. The need for a template marketplace with login/registration features was discussed, along with how to incorporate it into the repository. Finally, the Prometheus task data issue was raised, questioning whether data should be created by default or user-configured during integration. - Data Handling and Plugin Management > Discussion focused on data configuration, code refinement, and minimizing external SDK dependencies, though existing upload features might be used if necessary. The release is planned for late September. Monitoring data was also discussed, suggesting adding a post-collection processing feature in the alert plugin manager. Plugin type recognition and its representation on the UI were considered to help users identify the plugin type they are uploading. - Plugin Customization and Versatility > The possibility of allowing users to customize plugin parameters to enhance versatility was explored. For instance, an alert plugin that sends data to a web interface could be adapted to different needs through user-defined parameters. The concepts of plugin sorting and responsibility chains were also discussed, along with how to handle common issues like network monitoring. Lastly, a markdown task was mentioned, encouraging contributions and standardization. ### Releases - preparing for release 1.6.1 next month. Best Wishes, Tom
