Index: en_US.ISO8859-1/htdocs/news/status/report-sample.md
===================================================================
--- /dev/null
+++ en_US.ISO8859-1/htdocs/news/status/report-sample.md
@@ -0,0 +1,29 @@
+## Status Report Sample - This Will Become The Title ######
+
+Contact: John Smith,
+
+Link: [Link description here](http://www.example.com/project/url)
+
+Introduce your work. Do not assume that the person reading
+the report knows about your project. Paragraphs are separated
+with an empty line.
+
+Show the importance of your work. Status reports are not
+just about telling everyone that things were done, they also
+need to explain why they were done. Use Markdown syntax,
+the same you use on GitHub.
+
+What has happened since the last report? Let us know what
+is new in this area. If you don't know Markdown, just write
+it as if it was plain text.
+
+Optionally include the information about the sponsor.
+
+If help is needed, make this explicit. List tasks, with enough
+detail that people know if they are likely to be able to do them,
+and invite people to get in contact:
+
+ * First task
+ * Second task
+ * Third, if any
+
Index: en_US.ISO8859-1/htdocs/news/status/status.xml
===================================================================
--- en_US.ISO8859-1/htdocs/news/status/status.xml
+++ en_US.ISO8859-1/htdocs/news/status/status.xml
@@ -19,7 +19,8 @@
Submit your entries as Pull Requests from your fork of
FreeBSD
Quarterly Status Reports GitHub repo or submit them via e-mail to
- quarterly@FreeBSD.org.
+ quarterly@FreeBSD.org,
+ using the Markdown template.
One of the benefits of the FreeBSD development model is a focus on