svn commit: r45745 - head/en_US.ISO8859-1/htdocs/news/status

Wed Oct 8 01:13:28 UTC 2014

Author: wblock
Date: Wed Oct  8 01:13:27 2014
New Revision: 45745
URL: https://svnweb.freebsd.org/changeset/doc/45745

Log:
  Fix indentation and other whitespace.

Modified:
  head/en_US.ISO8859-1/htdocs/news/status/report-sample.xml

Modified: head/en_US.ISO8859-1/htdocs/news/status/report-sample.xml
==============================================================================

--- head/en_US.ISO8859-1/htdocs/news/status/report-sample.xml	Tue Oct  7 23:52:02 2014	(r45744)
+++ head/en_US.ISO8859-1/htdocs/news/status/report-sample.xml	Wed Oct  8 01:13:27 2014	(r45745)
@@ -4,61 +4,62 @@
 
 <!-- Optional category tag.  -->
 <!-- Tags include: proj, doc, kern, bin, arch, ports, vendor, misc, soc -->
-<project cat='proj'>
-  <title>Status Report Sample</title>
+  <project cat='proj'>
+    <title>Status Report Sample</title>
 
-  <!-- Required section -->
-  <contact>
-    <person>
-      <name>
-      <!-- For persons -->
-	<given>John</given>
-	<common>Smith</common>
-      </name>
-
-      <email>test at FreeBSD.org</email>
-    </person>
-
-    <!-- For teams or groups -->
-    <person>
-      <name>Wunderteam</name>
-
-      <email>team at FreeBSD.org</email>
-    </person>
-  </contact>
-
-  <!-- Optional section but highly encouraged. -->
-  <links>
-    <!-- A hypertext link with a description... -->
-    <url href="http://www.example.com/project/url/here">Description
-      here.</url>
-
-    <!-- And/or one without. -->
-    <url href="http://www.example.net/another/url" />
-  </links>
-
-  <!-- Required section. -->
-  <body>
-    <!-- Do not worry if you are not a native English speaker. -->
-    <p>Introduce your work.  Do not assume that the person reading the
-      report knows about your project.</p>
-
-    <p>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.</p>
-
-    <p>What has happened since the last report?  Let us know what is new
-      in this area.</p>
-  </body>
-
-  <sponsor>Optional sponsor</sponsor>
-  <sponsor>Another one</sponsor>
-
-  <!-- Optional section for listing tasks. -->
-  <help>
-    <task>If help is needed, make this explicit!</task>
-    <task>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.</task>
-  </help>
-</project>
+    <!-- Required section -->
+    <contact>
+      <person>
+	<name>
+	<!-- For persons -->
+	  <given>John</given>
+	  <common>Smith</common>
+	</name>
+
+	<email>test at FreeBSD.org</email>
+      </person>
+
+      <!-- For teams or groups -->
+      <person>
+	<name>Wunderteam</name>
+
+	<email>team at FreeBSD.org</email>
+      </person>
+    </contact>
+
+    <!-- Optional section but highly encouraged. -->
+    <links>
+      <!-- A hypertext link with a description... -->
+      <url href="http://www.example.com/project/url/here">Description here.</url>
+
+      <!-- And/or one without. -->
+      <url href="http://www.example.net/another/url" />
+    </links>
+
+    <!-- Required section. -->
+    <body>
+      <!-- Do not worry if you are not a native English speaker. -->
+      <p>Introduce your work.  Do not assume that the person reading
+	the report knows about your project.</p>
+
+      <p>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.</p>
+
+      <p>What has happened since the last report?  Let us know what is
+	new in this area.</p>
+    </body>
+
+    <sponsor>Optional sponsor</sponsor>
+
+    <sponsor>Another one</sponsor>
+
+    <!-- Optional section for listing tasks. -->
+    <help>
+      <task>If help is needed, make this explicit!</task>
+
+      <task>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.</task>
+    </help>
+  </project>
