From owner-freebsd-current@freebsd.org Wed Jun 7 23:33:38 2017 Return-Path: Delivered-To: freebsd-current@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 7178FD7F3E8; Wed, 7 Jun 2017 23:33:38 +0000 (UTC) (envelope-from kaduk@mit.edu) Received: from dmz-mailsec-scanner-1.mit.edu (dmz-mailsec-scanner-1.mit.edu [18.9.25.12]) (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 043423291; Wed, 7 Jun 2017 23:33:37 +0000 (UTC) (envelope-from kaduk@mit.edu) X-AuditID: 1209190c-afdff70000001600-ed-59388d485873 Received: from mailhub-auth-1.mit.edu ( [18.9.21.35]) (using TLS with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by dmz-mailsec-scanner-1.mit.edu (Symantec Messaging Gateway) with SMTP id 87.0E.05632.84D88395; Wed, 7 Jun 2017 19:33:29 -0400 (EDT) Received: from outgoing.mit.edu (outgoing-auth-1.mit.edu [18.9.28.11]) by mailhub-auth-1.mit.edu (8.13.8/8.9.2) with ESMTP id v57NXRUF004009; Wed, 7 Jun 2017 19:33:28 -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 v57NXOud010771 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 7 Jun 2017 19:33:26 -0400 Date: Wed, 7 Jun 2017 18:33:24 -0500 From: Benjamin Kaduk To: freebsd-hackers@FreeBSD.org Cc: freebsd-current@FreeBSD.org Subject: Call for 2017Q2 Quarterly Status Reports Message-ID: <20170607233323.GZ39245@kduck.kaduk.org> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha512; protocol="application/pgp-signature"; boundary="3eH4Qcq5fItR5cpy" Content-Disposition: inline User-Agent: Mutt/1.7.1 (2016-10-04) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFvrDIsWRmVeSWpSXmKPExsUixCmqrOvZaxFpsPevgcWcNx+YLLZv/sfo wOQx49N8lgDGKC6blNSczLLUIn27BK6Ma0u9C/4LVjTOaGNvYLzA38XIySEhYCJxpvcHYxcj F4eQwGImiYWfHjBBOBsYJZY93MYC4VxhkrjUsYoFpIVFQEVi6vYFYDabgJrE+hXXmEFsEQF5 iX1N79lBbGYg+9fWJjBbWMBQYvqCjWA2L9C663u2QtmCEidnPmGBqC+TOP/yNFsXIweQLS2x /B8HSFhUQFni7+F7LBMY+WYh6ZiFpGMWQgdEWEvixr+XTBjCthLr1r1nWcDItopRNiW3Sjc3 MTOnODVZtzg5MS8vtUjXUC83s0QvNaV0EyM4YCV5djCeeeN1iFGAg1GJhzdAziJSiDWxrLgy 9xCjJAeTkihvhSdQiC8pP6UyI7E4I76oNCe1+BCjCtCuRxtWX2CUYsnLz0tVEuGd3QRUx5uS WFmVWpQPUybNwaIkziuh0RghJJCeWJKanZpakFoEk5Xh4FCS4LXpAWoULEpNT61Iy8wpQUgz cXAeYpTg4AEa/qMOZHhxQWJucWY6RP4Uo6KUOK8BSLMASCKjNA+uF5RoJLL317xiFAd6S5iX AaSKB5ik4LpfAQ1mAhrMd8kEZHBJIkJKqoEx8rKjzqzo3umpq7lve7hb7A33vTnzfmu8ZISU t8iUno63iWIVt/pVmJbNcDucK9TyKYp7Rl/Jh0cmJTL833J6F/7ida6vlNkZycG33025sf6I uLr8H88v33e89cv7NmWq5ZQj8QEcbiIHTnLsuHoqlMOIYVlioOtMhrTHbZ1vpu598OB40ikl luKMREMt5qLiRACokFRpDwMAAA== X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 07 Jun 2017 23:33:38 -0000 --3eH4Qcq5fItR5cpy Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Dear FreeBSD Community, The deadline for the next FreeBSD Quarterly Status update is July 7, 2017, for work done in April through June. 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!) 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 2017Q2 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-2016-10-2016-12.html [5] https://www.FreeBSD.org/news/status/report-2017-01-2017-03.html --3eH4Qcq5fItR5cpy Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQGgBAABCgAGBQJZOI00AAoJECjZpvNk63USKBwMIKJS/VEY3Eh18tFggVc8+rHQ NE7Z+nMUfMokRM9eiBnHTODfVsUMoyycD5z8HTTQaSKEmH5W5knzMz6hk5VpvV1P fObTMuxounYJ8nLb5DyhWRJJSg2qMYw+OY9cr2f9zVBjo3hg/0V4J+tuMAd7qr1r RReHfErfee5cv5GYY1eg0QW37wkBCsn96+q7wU3Vuin+BjK9Xt70EfMTvOlzx2p3 fyO4xbQjXqYvHJI33ewda2n7FzvyPuKekr71e2zkLYhSEt0JI9sV8sp3mO2BeK8z kDjAmexdJpucd3eJRfNj7dSvTdG2spQlXV4l/VFJ04a362gkQ7pNhiHQYPaFlCL7 OFf598FWzepoQUZMKRiJLdqWd32tRtFmbprw/idhiu/kb18LSvyj6zUnUSsTIjgA 7T3EbeXOe5bUqWIAMS/9GBkqmqBs6x0yi8057FWbljq8nJflk8QJdqbTCTLDRoDl DlOurghfTpFZRlSbrchgAAwBDVhQzAjZznFMr/6j9QvLR5U= =rleg -----END PGP SIGNATURE----- --3eH4Qcq5fItR5cpy--