From owner-freebsd-hackers@freebsd.org Thu Jan 4 05:09:31 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 46CE9E8AA3F; Thu, 4 Jan 2018 05:09:31 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-7.mit.edu (dmz-mailsec-scanner-7.mit.edu [18.7.68.36]) (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 ADA7E79E56; Thu, 4 Jan 2018 05:09:30 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 12074424-339ff700000004d1-c5-5a4db590d190 Received: from mailhub-auth-4.mit.edu ( [18.7.62.39]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-7.mit.edu (Symantec Messaging Gateway) with SMTP id AE.FC.01233.195BD4A5; Thu, 4 Jan 2018 00:03:14 -0500 (EST) Received: from outgoing.mit.edu (OUTGOING-AUTH-1.MIT.EDU [18.9.28.11]) by mailhub-auth-4.mit.edu (8.13.8/8.9.2) with ESMTP id w04539wO021612; Thu, 4 Jan 2018 00:03:10 -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 w04535SA013744 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 4 Jan 2018 00:03:08 -0500 Date: Wed, 3 Jan 2018 23:03:05 -0600 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Second Call for 2017Q4 quarterly status reports Message-ID: <20180104050305.GL50827@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="82I3+IH0IqGh5yIs" Content-Disposition: inline In-Reply-To: <20171226002716.GG59505@kduck.kaduk.org> User-Agent: Mutt/1.9.1 (2017-09-22) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFtrKKsWRmVeSWpSXmKPExsUixG6nrjtpq2+UQcNFFYs5bz4wWWzf/I/R gcljxqf5LAGMUVw2Kak5mWWpRfp2CVwZv/+uYinYK1ZxddtllgbGacJdjBwcEgImEu97KroY uTiEBBYzSezo2c7excgJ5GxglJh6IhoicYVJYteUTawgCRYBFYmebd/YQGw2ATWJ9SuuMYPY IgLyEvua3oM1MwPZv7Y2gdnCAhYS1x88YASxeYGWbW/4xAyxwERiyak1UHFBiZMzn7CAHMQs UCYx55UDhCktsfwfB0gFp4CpxKONe8G2igooS+ztO8Q+gVFgFpLmWQjNsxCaZ4GdoyVx499L JgxhbYllC18zQ9i2EuvWvWdZwMi+ilE2JbdKNzcxM6c4NVm3ODkxLy+1SNdcLzezRC81pXQT IzjkXVR2MHb3eB9iFOBgVOLhbbjhEyXEmlhWXJl7iFGSg0lJlDcn1TtKiC8pP6UyI7E4I76o NCe1+BCjCtCuRxtWX2CUYsnLz0tVEuF1ywJq5U1JrKxKLcqHKZPmYFES5/Uw0Y4SEkhPLEnN Tk0tSC2CyWpwcAi0XDx5kAlqiARvxhbfKCHBotT01Iq0zJwShFImDs5DjBIcPECL7EFqeIsL EnOLM9Mh8qcYdTmezXzdwCwENkhKnNcWpEgApCijNA9uDii1SWTvr3nFKA70rjCvM0gVDzAt wk16BbSECWjJn/OeIEtKEhFSUg2MYqvmrZv6L/2SXp3NtPP9MQu9d3bP5XThSm3d/nORpNbW 5ZkzvE0Nrn8yYd9udEdMNXTZxwnzbZ9lvNixvz/ZoNnjd7XZqpDQeF2LBHZ/CaGtH3IXBqso n8r3eL57EbPhAfHDLsrLTYU6rjPkZBkeXWtcsev0+c/ffz4XMX3h5hh//X/gsScrlFiKMxIN tZiLihMBhpYdc0gDAAA= 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: Thu, 04 Jan 2018 05:09:31 -0000 --82I3+IH0IqGh5yIs Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Happy new year, and I hope that meltdown and spectre are not taking too much of everyone's time. That said, the submission deadline is still January 14th, so please do send in your status report entries to us! Thanks, Ben On Mon, Dec 25, 2017 at 06:27:16PM -0600, Benjamin Kaduk wrote: > Dear FreeBSD Community, >=20 > The deadline for the next FreeBSD Quarterly Status update is January 14, > 2018, for work done in October through December. >=20 > 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! >=20 > 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. >=20 > We look forward to seeing your 2017Q4 reports! >=20 > Thanks, >=20 > Ben (on behalf of monthly@) >=20 > [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 >=20 >=20 --82I3+IH0IqGh5yIs Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQG3BAABCgAdFiEE2WGV4E2ARf9BYP0XKNmm82TrdRIFAlpNtYMACgkQKNmm82Tr dRIlmgweLJpJVe7eOt7L3M7R0C50IcufXsJy3NvVxymHExOgeh6Izxn6HWmaL2+H ByrJLZkp8k2jQpvSICyakoIA/PPlo6troZUBAzNJqDeN+VEH35TB8b64SdJFBRtr /rQ5c9pJNDL6/KfPWajPIYc80lPUyhIYZgQKuc7UkW4d/He0JBgAuOTOQP6drxsw 71P0qpnm8vzN8AH6jQWhwDT9yINPn2s0JSprVJTW7w5don7EtXuLLhtnZk/T2pWd 0o5pot0KqyeqU/5DFvciZHEvcK1M/BXSVvN4wfu+Hopibc6quHEwosTW45qA19WL fRGUbApiTlT8AxnuB0Z197Z4QVE9CBaMdj22jWLViez93snBvnEoHAAyioScHmyQ W4/c6bxzku2o3Ql9szOyH/rVlYjnBJUQGsbBQUyMzGSw+nejdwo6WQ7nXtza4BIl 8iYnszR02ThEwRylYLpc3fnN0S69gqGuhu1mIhE6Svlf4sPW1nY8yJABf97nQ5I/ YMcMmXiJ3X0gew== =flZ4 -----END PGP SIGNATURE----- --82I3+IH0IqGh5yIs--