From owner-freebsd-hackers@freebsd.org Sat Oct 14 23:54:38 2017 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8D61AE3001B; Sat, 14 Oct 2017 23:54:38 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-2.mit.edu (dmz-mailsec-scanner-2.mit.edu [18.9.25.13]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 28AD0C65; Sat, 14 Oct 2017 23:54:37 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190d-9e7ff70000002861-74-59e2a3b5116c Received: from mailhub-auth-2.mit.edu ( [18.7.62.36]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-2.mit.edu (Symantec Messaging Gateway) with SMTP id C2.71.10337.5B3A2E95; Sat, 14 Oct 2017 19:54:30 -0400 (EDT) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-2.mit.edu (8.13.8/8.9.2) with ESMTP id v9ENsPSY003012; Sat, 14 Oct 2017 19:54:27 -0400 Received: from kduck.kaduk.org (24-107-191-124.dhcp.stls.mo.charter.com [24.107.191.124]) (authenticated bits=56) (User authenticated as kaduk@ATHENA.MIT.EDU) by outgoing.mit.edu (8.13.8/8.12.4) with ESMTP id v9ENsMUj025588 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Sat, 14 Oct 2017 19:54:25 -0400 Date: Sat, 14 Oct 2017 18:54:22 -0500 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: FINAL CALL for 2017Q3 quarterly status reports Message-ID: <20171014235422.GJ96685@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="Vxa5joy26gVGOrvU" Content-Disposition: inline User-Agent: Mutt/1.8.3 (2017-05-23) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDIsWRmVeSWpSXmKPExsUixG6nortt8aNIg54JjBZz3nxgsti++R+j A5PHjE/zWQIYo7hsUlJzMstSi/TtErgy/m44zVKwR7hi869VjA2MHwS6GDk5JARMJPauOcLS xcjFISSwmEmiZXEfO4SzkVHi0KxfUJmrTBI/ljYwgbSwCKhKzHzwiQ3EZhNQk1i/4hoziC0i IC+xr+k9O4jNDGT/2toEZHNwCAuYS7xfbQcS5gXa9uLUWTYIW1Di5MwnLBDlZRKrWyewgJQz C0hLLP/HARIWFVCWmLdvFdsERr5ZSDpmIemYhdABEdaSuPHvJROGsK3EunXvWRYwsq1ilE3J rdLNTczMKU5N1i1OTszLSy3SNdLLzSzRS00p3cQIClhOSd4djP/ueh1iFOBgVOLhzch6FCnE mlhWXJl7iFGSg0lJlPdc68NIIb6k/JTKjMTijPii0pzU4kOMKkC7Hm1YfYFRiiUvPy9VSYSX zRGolTclsbIqtSgfpkyag0VJnHdb0K5IIYH0xJLU7NTUgtQimKwMB4eSBG/XIqBGwaLU9NSK tMycEoQ0EwfnIUYJDh6g4W9AaniLCxJzizPTIfKnGBWlxHmngSQEQBIZpXlwvaBEI5G9v+YV ozjQW8K8G0GqeIBJCq77FdBgJqDB7yIegAwuSURISTUwzpSKVQ/7nNo8TXK9WlhayFy9aZ9m HJqQKlm9OnxOks/uDvXrd/65f1+cE37zlOnkzW3zJNXmqZ5jYztnqlez89GbzqDZEWttu210 b8/681WoeHux5rI9+29lvVi+cENOprxX235lV8Nu7gafH6ay7FnC1k0rkt+dfaA0b8fRuIBz zxQd+n8rKLEUZyQaajEXFScCAP9kQT8PAwAA X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Oct 2017 23:54:38 -0000 --Vxa5joy26gVGOrvU Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Dear FreeBSD Community, This is the last call for submissions for the 2017Q3 FreeBSD Quarterly Status update. The deadline for submissions is October 21, 2017, for work done in July through September. Status report submissions do not need to be very long. They may be about anything happening in the FreeBSD project and community, and provide a great way to inform FreeBSD users and developers about work that is underway and completed. Submission of reports is not restricted to committers; anyone doing anything interesting and FreeBSD related can -- and should -- write one! The preferred and easiest submission method is to use the XML generator [1] with the results emailed to the status report team at monthly@FreeBSD.org . (Do be sure, though, to save the form output and not the form itself! In particular, the Google Chrome "save as" function does not save the generated output for some reason.) There is also an XML template [2] that can be filled out manually and attached if preferred. For the expected content and style, please study our guidelines on how to write a good status report [3]. You can also review previous issues [4][5] for ideas on the style and format. We look forward to seeing your 2017Q3 reports! Thanks, Ben (on behalf of monthly@) [1] https://www.FreeBSD.org/cgi/monthly.cgi [2] https://www.FreeBSD.org/news/status/report-sample.xml [3] https://www.FreeBSD.org/news/status/howto.html [4] https://www.FreeBSD.org/news/status/report-2017-01-2017-03.html [5] https://www.FreeBSD.org/news/status/report-2017-04-2017-06.html --Vxa5joy26gVGOrvU Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQG3BAABCgAdFiEE2WGV4E2ARf9BYP0XKNmm82TrdRIFAlnio6gACgkQKNmm82Tr dRJMZAwg2OSeTx3F07vu0AlAWiHwJHuXlLszDWogAzSlR9j+rUmJ7wOtx9wjzoT9 XXT72qpqcgH9RJv4hXzFzt6VwI1yd7yDuqeucFYnPQbo87kGfHQLMXXcQT+IXCDo rmQiTAOs7uNHsyq9dlFMu2sxZlx/WURHuFXkNFR+jcly+bpVg2vFNyUwKSX7Ghsj 9U45k+jgJk/tTjCgFSXzonKM0lLovy0AVN2+vNGoG+/dU8JZb0GgZ4h2OzpYh28V fRAXN8YKEeKLielgiy7z7vtrPH7O/2TcqyjHbBOWCXlExbCJm3UBn0XXdnsp+oxY +iYDDUC3kD2m2tre0jFJvF09DulF97ornX+nqCSROX01WKp0XgEUK9qJe2SEU7Gz JuzMiyxpA8IaVgWHQ5or3NAgM0c0QcSpgPNDlZlPZ1/UDseGQBBRkygYvFRahnrG vM5AxWHFlj6LyZ1bhZcRCFeIWLLjkf12Hp1jj2s1S5FYzZJywraTUaBbzMag+7YN kPHCvEkBcZf/tQ== =DsOO -----END PGP SIGNATURE----- --Vxa5joy26gVGOrvU--