diff --git a/en_US.ISO8859-1/htdocs/news/status/README b/en_US.ISO8859-1/htdocs/news/status/README --- a/en_US.ISO8859-1/htdocs/news/status/README +++ b/en_US.ISO8859-1/htdocs/news/status/README @@ -7,47 +7,46 @@ quarterly-submissions@FreeBSD.org 0) Timeline + - The months of January, April, July and October are dedicated to put + together the reports submitted during the precedent month. This can + include waiting for late submissions. + - portmgr@ entries default to the extended headline, because of the + overlap between quarterly reports and quarterly ports branches. + - All entries can have the deadline extended by emailing + quarterly-submissions@ up until the extended deadline. + - Quarterly status report publication is done during the same months + as soon as the report is ready. - First Quarter: - First call for reports: March 1st - 2 weeks left reminder: March 15th - Last reminder: March 24th - - Standard deadline for submissions: March 31st - - Deadline for submissions for portmgr@ and late reports - (a heads-up is appreciated): April 8th + - Standard deadline: March 31st + - Extended deadline: April 8th - Second Quarter: - First call for reports: June 1st - 2 weeks left reminder: June 15th - Last reminder: June 24th - - Standard deadline for submissions: June 30th - - Deadline for submissions for portmgr@ and late reports - (a heads-up is appreciated): July 8th + - Standard deadline: June 30th + - Extended deadline: July 8th - Third Quarter: - First call for reports: September 1st - 2 weeks left reminder: September 15th - Last reminder: September 24th - - Standard deadline for submissions: September 30th - - Deadline for submissions for portmgr@ and late reports - (a heads-up is appreciated): October 8th + - Standard deadline: September 30th + - Extended deadline: October 8th - Fourth Quarter: - First call for reports: December 1st - 2 weeks left reminder: December 15th - Last reminder: December 24th - - Standard deadline for submissions: December 31st - - Deadline for submissions for portmgr@ and late reports - (a heads-up is appreciated): January 8th - - The months of January, April, July and October are dedicated to put together - the reports submitted during the precedent month. This can include waiting - for late submissions. - Quarterly status report publication is done during the same months as soon as - it is ready. + - Standard deadline: December 31st + - Extended deadline: January 8th 1) Call for reports - - Send reports to the freebsd-quarterly-calls@ mailing list, to all submitters + - Send calls to the freebsd-quarterly-calls@ mailing list, to all submitters of last quarterly status reports (they may have updates or further improvements), and, depending on the season: - Various conference organizers: @@ -78,13 +77,13 @@ https://www.freebsd.org/news/status/report-sample.md - Reporting howto is at: https://www.freebsd.org/news/status/howto.html. It contains a great deal of useful hints for the submitters on how - to write good reports. But it also helps to forward all the completed + to write good reports. It also helps to forward all the completed reports to developers for reference, and point to the latest report in the CFR. 2) Building the report: - - Review and merge pull requests as they are coming in. - - Review and merge reports submitted via email. + - Review and merge pull requests as well as those submitted via email, as + they come in. - For each newly merged report, add its filename to the local Makefile: put it in the variable corresponding to the section where you want the report to appear. Sort the variables content as you want to sort the reports in the @@ -92,7 +91,7 @@ - While the reports are being updated, other doc-committers (wblock, pluknet, and bjk, for example) may review the individual entries and propose fixes. - - Write an introduction in a file named intro.md in the quarter directory. + - Write an introduction in a file named intro.md in the quarterly directory. It should be usually the last step in the process; a good introduction can be only written once all the reports have been collected. - theraven may be poked for composing a nice introduction for the reports. @@ -102,7 +101,7 @@ - Run "make" or "make all-xml" in the quarter directory. This step needs perl as it invokes the md2docbook perl script. Warning: md2docbook lacks some features and likely has some bugs. Do not waste your time working on it and - prefer manual solutions instead: once the conversion of the FreeBSD website + use manual editing instead: once the conversion of the FreeBSD website to Hugo/AsciiDoctor is finished the md2docbook script will become obsolete. - Copy the generated DocBook draft to en_US.ISO8859-1/htdocs/news/status/report-XXXX-YY-XXXX-ZZ.xml, @@ -119,31 +118,32 @@ - Files to edit and commit: - In doc/en_US.ISO8859-1/htdocs/news/status/ : - The quarterly report itself: - report-yyyy-mm-yyyy-mm.xml + The quarterly report itself: + doc/en_US.ISO8859-1/htdocs/news/status/report-yyyy-mm-yyyy-mm.xml - Update the next due date on the status report page and - add a link to the new report below that: - status.xml + Update the next due date on the status report page and + add a link to the new report below that: + doc/en_US.ISO8859-1/htdocs/news/status/status.xml - In doc/share/xml/ : - The news entry for the main website page: - news.xml + The news entry for the main website page: + doc/share/xml/news.xml - Sample: + Sample for the news entry (may need to add month): + + 15 June-October 2006 Status Report -

The June to October 2006 Status Report - is now available with 49 entries.

- +

The October to December 2020 Status Report + is now available with 49 entries.

+ + - After the html version of the report has been built and is online, run in the quarter directory "make all-txt" and prettify its output. This step - needs that you have installed www/lynx and lang/perl5.30 (or other version) - on your system. + requires that you have installed www/lynx and lang/perl5.30 (or newer= on + your system. lynx defaults to a width of 80 and will forcibly wrap URLs to fit within that size. The prettification process includes undoing that