Date: Wed, 22 May 2013 20:39:46 +0000 (UTC) From: Gabor Pali <pgj@FreeBSD.org> To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r41708 - head/en_US.ISO8859-1/htdocs/news/status Message-ID: <201305222039.r4MKdk36056980@svn.freebsd.org>
next in thread | raw e-mail | index | archive | help
Author: pgj Date: Wed May 22 20:39:46 2013 New Revision: 41708 URL: http://svnweb.freebsd.org/changeset/doc/41708 Log: - Refine the recommendations for getting more quarterly status reports in time Modified: head/en_US.ISO8859-1/htdocs/news/status/README Modified: head/en_US.ISO8859-1/htdocs/news/status/README ============================================================================== --- head/en_US.ISO8859-1/htdocs/news/status/README Wed May 22 19:50:09 2013 (r41707) +++ head/en_US.ISO8859-1/htdocs/news/status/README Wed May 22 20:39:46 2013 (r41708) @@ -16,12 +16,21 @@ Compiling status reports - best practice 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?201305222039.r4MKdk36056980>