Page MenuHomeFreeBSD
Differential D38398 Diff 116869 website/content/en/status/_index.adoc

Changeset View

Standalone View

View Options

website/content/en/status/_index.adoc

--- ---
title: "FreeBSD Status Reports" title: "FreeBSD Status Reports"
sidenav: about sidenav: about
--- ---
= FreeBSD Status Reports = FreeBSD Status Reports
== Next Quarterly Status Report submissions (January - March) due: March 31st, 2023 == Next Quarterly Status Report submissions (January - March) due: March 31st, 2023
Submit your entries as Pull Requests from your fork of link:https://github.com/freebsd/freebsd-quarterly[FreeBSD Status Report GitHub repo] or submit them via e-mail to status-submissions@FreeBSD.org, using the link:https://github.com/freebsd/freebsd-quarterly/blob/master/report-sample.adoc[report-sample.adoc template]. The following methods are available to submit your reports:
* submit a link:https://reviews.freebsd.org/[Phabricator review] and add the group _status_ to the reviewers list.
You should put your reports in the pertinent subdirectory of `doc/website/content/en/status/`;
* submit a pull request to the doc repository through link:https://github.com/freebsd/freebsd-doc[through its GitHub mirror] .
You should put your reports in the directory in the pertinent subdirectory of `doc/website/content/en/status`;
* send an email to status-submissions@FreeBSD.org including your report.
An link:../status/report-sample.adoc[AsciiDoc template] is available.
''''' '''''
One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree. One of the benefits of the FreeBSD development model is a focus on centralized design and implementation, in which the operating system is maintained in a central repository, and discussed on centrally maintained lists. This allows for a high level of coordination between authors of various components of the system, and allows policies to be enforced over the entire system, covering issues ranging from architecture to style. However, as the FreeBSD developer community has grown, and the rate of both mailing list traffic and tree modifications has increased, making it difficult even for the most dedicated developer to remain on top of all the work going on in the tree.
The FreeBSD Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information. The FreeBSD Status Report attempts to address this problem by providing a vehicle that allows developers to make the broader community aware of their on-going work on FreeBSD, both in and out of the central source repository. For each project and sub-project, a one paragraph summary is included, indicating progress since the last summary. If it is a new project, or if a project has not submitted any prior status reports, a short description may precede the status information.
For more exact guidelines on how to write good status reports, please consult link:howto/[our recommendations]. For more exact guidelines on how to write good status reports, please consult link:howto/[our recommendations].
▲ Show 20 Lines • Show All 158 Lines • Show Last 20 Lines