From owner-svn-doc-all@freebsd.org Tue Nov 27 11:54:28 2018 Return-Path: Delivered-To: svn-doc-all@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 091381147881; Tue, 27 Nov 2018 11:54:28 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from mxrelay.nyi.freebsd.org (mxrelay.nyi.freebsd.org [IPv6:2610:1c1:1:606c::19:3]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mxrelay.nyi.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9FF8973655; Tue, 27 Nov 2018 11:54:27 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org (repo.freebsd.org [IPv6:2610:1c1:1:6068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mxrelay.nyi.freebsd.org (Postfix) with ESMTPS id 6301E1AE26; Tue, 27 Nov 2018 11:54:27 +0000 (UTC) (envelope-from trasz@FreeBSD.org) Received: from repo.freebsd.org ([127.0.1.37]) by repo.freebsd.org (8.15.2/8.15.2) with ESMTP id wARBsRfw086030; Tue, 27 Nov 2018 11:54:27 GMT (envelope-from trasz@FreeBSD.org) Received: (from trasz@localhost) by repo.freebsd.org (8.15.2/8.15.2/Submit) id wARBsRKM086029; Tue, 27 Nov 2018 11:54:27 GMT (envelope-from trasz@FreeBSD.org) Message-Id: <201811271154.wARBsRKM086029@repo.freebsd.org> X-Authentication-Warning: repo.freebsd.org: trasz set sender to trasz@FreeBSD.org using -f From: Edward Tomasz Napierala Date: Tue, 27 Nov 2018 11:54:27 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r52519 - head/en_US.ISO8859-1/htdocs/news/status X-SVN-Group: doc-head X-SVN-Commit-Author: trasz X-SVN-Commit-Paths: head/en_US.ISO8859-1/htdocs/news/status X-SVN-Commit-Revision: 52519 X-SVN-Commit-Repository: doc MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Rspamd-Queue-Id: 9FF8973655 X-Spamd-Result: default: False [1.57 / 15.00]; local_wl_from(0.00)[FreeBSD.org]; NEURAL_SPAM_SHORT(0.37)[0.371,0]; NEURAL_SPAM_MEDIUM(0.69)[0.687,0]; NEURAL_SPAM_LONG(0.51)[0.511,0]; ASN(0.00)[asn:11403, ipnet:2610:1c1:1::/48, country:US] X-Rspamd-Server: mx1.freebsd.org X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 27 Nov 2018 11:54:28 -0000 Author: trasz Date: Tue Nov 27 11:54:26 2018 New Revision: 52519 URL: https://svnweb.freebsd.org/changeset/doc/52519 Log: Update Status Reports HOWTO. Reviewed by: bcr Approved by: bcr (mentor) Differential Revision: https://reviews.freebsd.org/D18306 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 Mon Nov 26 16:08:45 2018 (r52518) +++ head/en_US.ISO8859-1/htdocs/news/status/README Tue Nov 27 11:54:26 2018 (r52519) @@ -16,12 +16,10 @@ deadline Follow up on missing reports - Are usually sent to freebsd-hackers@ CC freebsd-current@ as the lists with the most usual suspects for submitting reports. Forward to developers@ as well. Also ping individuals which are known to have - something cooking. - - The xml-template is at: - https://www.freebsd.org/news/status/report-sample.xml at the time of this - writing. Make sure to keep it up to date with regard to categories - to pick from and place them prominently in the CFR - otherwise people - submit plain text reports and you have to format them yourself. + something cooking, and folks who have submitted something for the + previous report, in case the project was continued. + - The Markdown template is at: + 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 @@ -65,10 +63,11 @@ deadline Follow up on missing reports - While the report draft is kept updated, other doc-committers (wblock, pluknet, and bjk, for example) may review the individual entries and propose fixes. - - As mentioned above, the received reports should be in a single .xml file, - where tidy(1) may be used to get them well-formatted. Usually s - without a description are missing the closing "/>" which is the cause for - most of the errors you will encounter. Sometimes other closing tags are + - Use md2docbook.py to convert from the Markdown draft to DocBook: + https://github.com/trasz/md2docbook + - Tidy up the draft - tidy(1) may be used to get it well-formatted. Usually + s without a description are missing the closing "/>" which is the cause + for most of the errors you will encounter. Sometimes other closing tags are missing. - Invoking tidy with the following options seems to cause the fewest problems: tidy -xml -i -wrap 74 -latin1 -preserve