> For the complete documentation index, see [llms.txt](https://book.bsdcn.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://book.bsdcn.org/status/readme.md).
# FreeBSD 状态报告
本项目经过校对与审阅。
* 状态报告原文：
* 作者：参见具体状态报告页面，全文翻译自 FreeBSD 项目
* 本文档部署地址：
上游原文许可证：**只要明确标注来源并给予相应署名，就可全文转载或部分转载这些状态报告。**
FreeBSD 中文社区译制。本翻译项目遵循 [BSD 2-Clause 许可证](https://github.com/FreeBSD-Ask/FreeBSD-Status-Report-CN/tree/main/LICENSE/README.md)。
## 页面说明
FreeBSD 开发模式的优势之一，在于其专注于集中化的设计与实现——操作系统由中央代码库统一维护，并通过集中管理的邮件列表进行讨论。这种模式能高度协调系统各组件的开发者，确保覆盖架构到代码风格等各方面的各项策略在整个系统中得以强制执行。然而随着 FreeBSD 开发社区的壮大，邮件列表流量与代码库修改频次与日俱增，即使是最专注的开发者也难以全面掌握代码库中的所有动态。
FreeBSD 状态报告机制正是为解决这一问题而设立，它为开发者提供了向社区通报其工作进展的渠道，无论这些开发基于中央代码库还是独立进行。每个项目及子项目都会附一段摘要说明，阐述自上次报告以来的进展。若属新项目或未提交过历史报告的项目，则会在状态信息前附加简短描述。
项目组会定期编写并发布特别状态报告，开发者峰会报告便是其中之一。开发者峰会为开发者提供面对面探讨项目相关议题的交流平台，所有有志为 FreeBSD 项目作出重大贡献的人士均可参与，这类峰会极具参与价值。
***
若你有意提交状态报告，或想了解状态报告的发布流程，请参阅 FreeBSD 项目的 [状态报告流程说明](https://docs.freebsd.org/en/articles/freebsd-status-report-process/)。
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://book.bsdcn.org/status/readme.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.