From owner-freebsd-hackers@freebsd.org Fri Jan 12 04:53:17 2018 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 A4C06E70F14; Fri, 12 Jan 2018 04:53:17 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-5.mit.edu (dmz-mailsec-scanner-5.mit.edu [18.7.68.34]) (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 1BD3176B63; Fri, 12 Jan 2018 04:53:16 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074422-fc5ff700000030c7-1d-5a583e034520 Received: from mailhub-auth-3.mit.edu ( [18.9.21.43]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-5.mit.edu (Symantec Messaging Gateway) with SMTP id 1D.5E.12487.40E385A5; Thu, 11 Jan 2018 23:48:04 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-3.mit.edu (8.13.8/8.9.2) with ESMTP id w0C4m2hh024784; Thu, 11 Jan 2018 23:48:02 -0500 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 w0C4lxDY024134 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 11 Jan 2018 23:48:01 -0500 Date: Thu, 11 Jan 2018 22:47:59 -0600 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: FINAL CALL for 2017Q4 quarterly status reports Message-ID: <20180112044759.GT72574@kduck.kaduk.org> References: <20171226002716.GG59505@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="SUOF0GtieIMvvwua" Content-Disposition: inline In-Reply-To: <20171226002716.GG59505@kduck.kaduk.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprPKsWRmVeSWpSXmKPExsUixCmqrctiFxFlcG67ssWcNx+YLLZv/sfo wOQx49N8lgDGKC6blNSczLLUIn27BK6Ma0dWsRQcFK7o625mbGD8JNDFyMkhIWAiMbP3G2sX IxeHkMBiJom9p56wQDgbGSWeL9nGDuFcZZLo/3CbFaSFRUBVoun3NEYQm01ATWL9imvMILaI gLzEvqb37CA2M5D9a2sTmC0sYC5x+3MPE4jNC7TuVcNUMFsIyF5yag0jRFxQ4uRMkM0cQL1l Ev9fhUCY0hLL/3GAVHAKmEo82riXDcQWFVCW2Nt3iH0Co8AsJM2zEJpnITTPAjtHS+LGv5dM GMK2EuvWvWdZwMi2ilE2JbdKNzcxM6c4NVm3ODkxLy+1SNdULzezRC81pXQTIyi82V2UdjBO /Od1iFGAg1GJh/dBbniUEGtiWXFl7iFGSQ4mJVHePelAIb6k/JTKjMTijPii0pzU4kOMKkC7 Hm1YfYFRiiUvPy9VSYS3phuojjclsbIqtSgfpkyag0VJnNfDRDtKSCA9sSQ1OzW1ILUIJivD waEkwetqExElJFiUmp5akZaZU4KQZuLgPMQowcEDNPyqNVANb3FBYm5xZjpE/hSjLseNF6/b mIXALpAS5y0DGSQAUpRRmgc3B5SuJLL317xiFAd6UZhXH2QUDzDVwU16BbSECWjJ+Y2hIEtK EhFSUg2MC7NubPxdofe1P+xbepAYT1t7gPL1OjahoPnpxzNjn1ZXiG8yEjl40Pno9Mi2aL3b p49NkOn5ETyHv1kv8cHblBkMuzN4l7Bbsl2fck5nuekORfuM6GfyDg+K2QyviRzwynW97tXz tWaF7eXQUz8cd3kxiq7bJ2ATtePL3kMHeFqufpffa+euxFKckWioxVxUnAgAM1xHuTIDAAA= X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 12 Jan 2018 04:53:17 -0000 --SUOF0GtieIMvvwua Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Dear FreeBSD Community, This is the last call for submissions for the 2017Q4 FreeBSD Quarterly Status Update. The deadline for submissions is January 14, 2018, for work done in October through December. 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 2017Q4 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-07-2017-09.html [5] https://www.FreeBSD.org/news/status/report-2017-04-2017-06.html --SUOF0GtieIMvvwua Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQG3BAABCgAdFiEE2WGV4E2ARf9BYP0XKNmm82TrdRIFAlpYPfkACgkQKNmm82Tr dRJNTAwfU7M53e5Zdq1cg4FP3MZKi0dFyx7n12HxGuSk4ID9/J5UbVx1tVkTLFKk 58ewVKXLe6u2uo+dZ0IdUI2L4CY/V+/g6R1SQzSShjkaM5KU+GK/WIK6g2n0oTZt 5DtSAyiSM+w6FRl4b+UU+jbHaPusDNCoZEw3Oa4OxVZCMCXXtoaf/smyckErEyTj XMu2bfapXycqaijWH0lDfF/+nbsUkrffDt36cUBpcd3Ehok67oZe4qABCnd99b1X 0eAgS4HqwNk/ShtSrg5JJDPIBc2xBB/+W12MS2gBcpA883JB7wFixruH/hktRM8Z 6sx1d25fj2Fkza22SaOftcr9cGTECoKAsqkjX4yD+FTjm/rCra1MG3ELmA0zpRhp kVCRRuKbvjcvvdInYeeJRfjA1tmpGFVVAZWImxX1tsYk+yd1Hf1JSONDC1P3a4HN P1YHvos7PsR6mR1EYHeUntMi0vpFgwYJx4GqyeJwmWhHJ0Jfzuf5U17dG9n2oLhJ v/xWhtG5tJdnUw== =myiJ -----END PGP SIGNATURE----- --SUOF0GtieIMvvwua--