Changeset View
Changeset View
Standalone View
Standalone View
head/en_US.ISO8859-1/htdocs/news/status/status.xml
<?xml version="1.0" encoding="iso-8859-1"?> | <?xml version="1.0" encoding="iso-8859-1"?> | ||||
<!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN" | <!DOCTYPE html PUBLIC "-//FreeBSD//DTD XHTML 1.0 Transitional-Based Extension//EN" | ||||
"http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [ | "http://www.FreeBSD.org/XML/share/xml/xhtml10-freebsd.dtd" [ | ||||
<!ENTITY title "FreeBSD Status Reports"> | <!ENTITY title "FreeBSD Status Reports"> | ||||
]> | ]> | ||||
<html xmlns="http://www.w3.org/1999/xhtml"> | <html xmlns="http://www.w3.org/1999/xhtml"> | ||||
<head> | <head> | ||||
<title>&title;</title> | <title>&title;</title> | ||||
<cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword> | <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword> | ||||
</head> | </head> | ||||
<body class="navinclude.about"> | <body class="navinclude.about"> | ||||
<h2>Next Quarterly Status Report submissions (July – | <h2>Next Quarterly Status Report submissions (October, 2017 – | ||||
September) due: January 14th, 2018</h2> | September, 2018) due: October 31th, 2018</h2> | ||||
<p>Use the <a href="https://www.FreeBSD.org/cgi/monthly.cgi">xml | <p>Submit your entries as Pull Requests from your fork of | ||||
generator</a> or download and edit the <a href="report-sample.xml"> | <a href="https://github.com/freebsd/freebsd-quarterly">FreeBSD | ||||
xml-template</a>. Submissions should be submitted by e-mail to | Quarterly Status Reports GitHub repo</a> or submit them via e-mail to | ||||
<a href="mailto:monthly@FreeBSD.org">monthly@FreeBSD.org</a>.</p> | <a href="mailto:quarterly@FreeBSD.org">quarterly@FreeBSD.org</a>.</p> | ||||
<hr/> | <hr/> | ||||
<p>One of the benefits of the FreeBSD development model is a focus on | <p>One of the benefits of the FreeBSD development model is a focus on | ||||
centralized design and implementation, in which the operating system is | centralized design and implementation, in which the operating system is | ||||
maintained in a central repository, and discussed on centrally maintained | maintained in a central repository, and discussed on centrally maintained | ||||
lists. This allows for a high level of coordination between authors of | lists. This allows for a high level of coordination between authors of | ||||
various components of the system, and allows policies to be enforced over | various components of the system, and allows policies to be enforced over | ||||
the entire system, covering issues ranging from architecture to style. | the entire system, covering issues ranging from architecture to style. | ||||
▲ Show 20 Lines • Show All 248 Lines • Show Last 20 Lines |