In my option, there is no need to migrate the documents to a separate repository.
My main point is: 1. As an actual user of Apache HertzBeat, I believe that the monitoring template is a very core and commonly used feature. It requires the yml files and documentation to be kept in sync and updated. In the current repository, when contributors update the yml templates, they often forget to update the documentation (even though the community has reminded them, this is not a mandatory requirement). I think separating it into different repositories will only make this situation worse. 2. As a contributor to Apache HertzBeat, I believe that separating the repository is not conducive to the management and statistics of contributors by the PMC, and it also fragments focus and time, potentially increasing the workload on PMC members. Best Regards, Delei At 2025-09-17 23:05:14, "shown-apache" <[email protected]> wrote: >Hi all, > >TL;DR I propose creating a new Git repository under Apache HertzBeat for a >dosc repo: apache/hertzbeat-website. I’d like to proceed via >lazy consensus over 72 hours. If there are no binding -1 votes within 72 >hours, I will file an INFRA ticket to create the repository. > >Motivation > > - Currently, the main repository of Apache Hertzbeat is quite large, > which is not conducive to new developers cloning it for contribution; > >Proposed repository > > - Name: apache/hertzbeat-website > - Description: Apache HertzBeat Docs Website > - GitHub/GitBox: yes (under github.com/apache, following GitBox > permissions) > - Permissions: all project Committers get write access per GitBox/LDAP > defaults > >Scope and boundaries > > - Docs-only: Only store content related to the documents, including the >CI > and script configurations required for building the docs website. > >Maintenance and releases > > - Maintainers: HertzBeat PMC/Committers. > - License: Apache License 2.0; ensure third-party dependency compliance. > >Relationship to existing code > > - Independent sub-repo; no impact on existing repositories. > >Process > > - This thread runs under lazy consensus for 72 hours. > - If there are no binding -1 votes within 72 hours, I will open an INFRA > ticket to create the repo and share the link here. > >Feedback requested > > - Any risks or concerns > >Please share your thoughts and your +1/0/-1. Thanks! > >Best, Logic
