Hello Shown, First thanks for your proposal.
Previously, I remained neutral on this matter, since migrating out has both advantages and disadvantages. But after careful consideration, I believe the disadvantages outweigh the benefits. Looking at other Apache projects, most of them keep documentation in a separate repository, so maybe staying consistent with them could be better in theory. *Advantages:* 1. Stay consistent with most other Apache projects by keeping documentation in a separate repository. 2. Separate code and documentation, reducing the size of the main repository. 3. From a programmer’s habitual perspective, documentation should not be in the same IDE workspace where it may interfere with coding. *Disadvantages:* 1. Once separated from the main repository, issues and PRs related to documentation will receive much less attention. 2. Feature PRs cannot directly update documentation; they would need to be made in another repository, which is easy to overlook. 3. It may give the impression that documentation is not an essential part of the main repository, lowering its perceived importance. In conclusion, my opinion is *not to migrate the documentation into a separate repository*. I welcome discussion and other perspectives. Kind Regards, Chao Gong shown-apache <[email protected]> 于2025年9月17日周三 23:20写道： > hi guys, > > hi guys. my bad. I forget update email signature. > This is the voting email I sent. Please feel free to vote and offer your > opinions. > > > beat regards, shown. > > shown-apache <[email protected]> 于2025年9月17日周三 23:05写道： > > > 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 > > >
