- Refine the recommendations for getting more quarterly status reports in

time

en_US.ISO8859-1/htdocs/news/status/README

@@ -16,12 +16,21 @@ Compiling status reports - best practices
    get everybody to report.  Starting early with kind reminders seems to
    help ;)
 
-3) The following groups have written very nice reports for the last rounds:
-   portmgr@, secteam@, re@ and deb@ for the FreeBSD Foundation.  Various
-   conference organizers - depending on the season: BSDCan (info@bsdcan.org)
-   May, EuroBSDCon (info@eurobsdcon.org) Sept, AsiaBSDCon 
-   (secretary@asiabsdcon.org) March.  Our readers seem to value
-   these reports, so we should try to get them in if at all possible.
+3) The following groups should be definitely approached for a report on
+   their recent activities:
+   - core@, portmgr@, doceng@, secteam@, re@, postmaster@, clusteradm@,
+     devsummit@
+   - FreeBSD Foundation (deb@), participants of FreeBSD-Foundation-sponsored
+     projects, rwatson@ can give hint useful hints on that.
+   - Various conference organizers, depending on the season:
+     - BSDCan (info@bsdcan.org) May (April-June)
+     - EuroBSDcon (foundation@eurobsdcon.org) Sept-Oct (October-December)
+     - AsiaBSDCon (secretary@asiabsdcon.org) March (January-March)
+   - All submitters for the previous quarterly status report (they may have
+     updates or further improvements).
+
+   Our readers seem to value these reports, so we should try to get them in
+   if at all possible.
 
 4) Building the report:
   - Accumulate the received reports in a single .xml file and use tidy(1) to