os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

- Refine the recommendations for getting more quarterly status reports in

Browse source 
time
This commit is contained in:
Gabor Pali 2013-05-22 20:39:46 +00:00
parent 2a00753a01
commit 871688b0c0
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=41708
1 changed files with 15 additions and 6 deletions

21
en_US.ISO8859-1/htdocs/news/status/README
View file

@ -16,12 +16,21 @@ Compiling status reports - best practices
get everybody to report. Starting early with kind reminders seems to get everybody to report. Starting early with kind reminders seems to
help ;) help ;)
3) The following groups have written very nice reports for the last rounds: 3) The following groups should be definitely approached for a report on
portmgr@, secteam@, re@ and deb@ for the FreeBSD Foundation. Various their recent activities:
conference organizers - depending on the season: BSDCan (info@bsdcan.org) - core@, portmgr@, doceng@, secteam@, re@, postmaster@, clusteradm@,
May, EuroBSDCon (info@eurobsdcon.org) Sept, AsiaBSDCon devsummit@
(secretary@asiabsdcon.org) March. Our readers seem to value - FreeBSD Foundation (deb@), participants of FreeBSD-Foundation-sponsored
these reports, so we should try to get them in if at all possible. 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: 4) Building the report:
- Accumulate the received reports in a single .xml file and use tidy(1) to - Accumulate the received reports in a single .xml file and use tidy(1) to